Why and How I Got My Own ASN(chown.me)
chown.me
Why and How I Got My Own ASN
https://chown.me/blog/getting-my-own-asn
121 comments
Setting up an email server once sounds awesome. Coding an email server system from scratch also sounds awesome. But running an email server indefinitely doesn't sound super fun.
I've been running email servers since the '90s, and there's surprisingly little work that needs to be done once it's up and running.
I ran email servers for my personal domains in the 90s and early 2000s. What eventually caused me to move everything to gmail was the massive pain of dealing with spam and trying to keep up with the latest spam filtering, which is essential.
You don't need to keep up with anything if you use bogofilter, or similar statistics based methods, to classify it. You can do server side filtering based on other non-content things like DNS lookups, or IP blacklists, but that's just adding needless failure modes on the receive side. I don't do any non-content filtering, to keep things simple for the senders and latency down. Statistical methods are just that effective on a personal mail server level.
I've been running my own mailserver for the last ten years and I must say that nowadays I'm not even running an antispam filter anymore because I basically don't get spam.
What I do instead (instead of running an antispam server) is checking all stuff that a proper mail admin would do, that is:
- greylisting (postgrey)
- reject hosts not listed in spf records for the sender (spf-policyd)
- verifying dkim signatures, if present (opendkim)
Also f#@k spamhaus and those people, they will mark you as a spam host on pure prejudice.
What I do instead (instead of running an antispam server) is checking all stuff that a proper mail admin would do, that is:
- greylisting (postgrey)
- reject hosts not listed in spf records for the sender (spf-policyd)
- verifying dkim signatures, if present (opendkim)
Also f#@k spamhaus and those people, they will mark you as a spam host on pure prejudice.
Wonder how it works for you... I've been running my own mail infrastructure for 10+ years. hosting tens of domains with hundreds of thousands of messages daily.
That's said, most of my spam senders match SPF and have proper DKIM records. Only few absolutely outrageous spammers ignore it.
Setting DKIM and SPF is not a rocket science and I'd be extremely surprised if spammers wouldn't do that.
That's said, most of my spam senders match SPF and have proper DKIM records. Only few absolutely outrageous spammers ignore it.
Setting DKIM and SPF is not a rocket science and I'd be extremely surprised if spammers wouldn't do that.
Uh ... Your dkim settings are for your recipients to validate your emails.
You should ALSO be checking dkim signatures on incoming e-mails (opendkim does that IIRC).
Also, I forgot to mention that I REQUIRE tls for incoming smtp connection. That's another thing rising the bar for spammers.
If you're using postfix, it's very open by default, in the sense that it doest not come with spf and/or dkim/dmarc tooling and it's not going to, for example, require (or even allow) ssl/tls for incoming smtp connections (and won't use it for outgoing smtp connection).
One last thing: a little bit of spam leaks trough... But it's like less than a single spam email per two weeks.
You should ALSO be checking dkim signatures on incoming e-mails (opendkim does that IIRC).
Also, I forgot to mention that I REQUIRE tls for incoming smtp connection. That's another thing rising the bar for spammers.
If you're using postfix, it's very open by default, in the sense that it doest not come with spf and/or dkim/dmarc tooling and it's not going to, for example, require (or even allow) ssl/tls for incoming smtp connections (and won't use it for outgoing smtp connection).
One last thing: a little bit of spam leaks trough... But it's like less than a single spam email per two weeks.
> I forgot to mention that I REQUIRE tls for incoming smtp connection
This would cut quite a number of legitimate emails for me. Surprised it works for you.
This would cut quite a number of legitimate emails for me. Surprised it works for you.
I forgot to mention:
I also require SSL/TLS for incoming smtp/submission connections.
I also require SSL/TLS for incoming smtp/submission connections.
Spam is basically a non-issue these days. Just run your favorite bayesian filter locally and it's taken care of. On my mail server I don't do any silly blocking, simply pass everything through spamprobe and my spam rate is so close to zero that I don't notice. Maybe like once a month.
Rspamd has made that trivial for a number of years. It's an amazing tool.
Same here. I started running my own mail servers back in 1994. Through the years, I've run smail, sendmail, qmail. My current stack is postfix, dovecot, rspamd running on FreeBSD.
Sure, you and many people. I'm saying there's an in-between level of enthusiasm where you do want to learn new things and experiment but without getting yourself into any long-term commitments.
I'm sure you'd agree that it's also easier to scale your experiments/interest if you only do small experiments rather than go all the way in every dimension.
I'm sure you'd agree that it's also easier to scale your experiments/interest if you only do small experiments rather than go all the way in every dimension.
doing any activity indefinitely is not fun, is a day job
I've set up an email server and I found it pretty grueling.
there's quite a bit of stuff to study, that's true
Thank you for your kind words!
I’m glad he decided to do this, but I would never do it myself.
If anyone is in the bay area and wants to run physical hardware and peer with folks, FCIX down in the HE facility in Fremont is very welcoming to small networks and doesn't have port fees (although you do need to be in the HE facility).
The "On the Metal" podcast episode[0] about the FCIX exchange was a really enjoyable listen. I had no idea that things like that could still just "pop up". I assume those days were long-passed.
[0] https://oxide.computer/podcasts/kenneth-finnegan
[0] https://oxide.computer/podcasts/kenneth-finnegan
It certainly helps that HE sounds really friendly to the whole thing - donated fiber, and they got a couple grand in switchgear donated from someone.
Just finished that episode yesterday. The internet is spooky sometimes lol
Oh wow that's fantastic! Are you referring to https://fcix.net/ ? Thanks so much for the tip. Do you know how much it costs to grab a dedicated box in the HE Fremont facility?
So they don't do dedicated boxes (sadly), they rent by the rack (including 1gb of transit + 15A power). https://he.net/colocation.html has the info. If you just want a dedicated box that isn't drawing a lot of power I've probably got some room in my rack and we can chat (and I imagine some of the other BGP for fun group folks are in similar positions).
Sure I'd be interested! Let me know if there's contact info on your site or some other method of contact. I'm fine with Email or Matrix.
Ah, blast from the past. HE brought us T-1's, T-3's, and IPv6 transit way back.
Equinix owns PAIX on 529 Bryant St. as SV8.
It's interesting how racks still aren't so much volume-, mass-, or network bandwidth-/transit-constrained, but power-constrained.
Equinix owns PAIX on 529 Bryant St. as SV8.
It's interesting how racks still aren't so much volume-, mass-, or network bandwidth-/transit-constrained, but power-constrained.
It's very easy to run out of cumulative watts of grid power feed, cooling capacity and generator/UPS/power backup capacity in a facility before you run out of floor space in a datacenter.
Even with what is now a "small" 5kW thermal power budget per 44U cabinet, measuring 24 inches wide x 48 inches deep, you can easily exceed that 5kW long before you physically fill the cabinet with servers.
Even with what is now a "small" 5kW thermal power budget per 44U cabinet, measuring 24 inches wide x 48 inches deep, you can easily exceed that 5kW long before you physically fill the cabinet with servers.
Power in is directly heat out (that mechanical motion of fans twirling just isn't giving more than a rounding error).
You can only get so much cooling density. And loading up a rack can use a signifigant portion of cooling.
Its pretty easy now-a-days to get 18kW into a rack, which will require 5 tons of cooling. Ie. enough cooling to handle a 3,000 ft^2 house.
You can only get so much cooling density. And loading up a rack can use a signifigant portion of cooling.
Its pretty easy now-a-days to get 18kW into a rack, which will require 5 tons of cooling. Ie. enough cooling to handle a 3,000 ft^2 house.
I got my first ASN in April, 2021 from a LIR. It was an amazing experience. If you live in the west part of North America like me, you can get a IX VPS at FreeRangeCloud (disclaimer: I'm not affiliated with them). You can connect to Unmetered Exchange, EVIX and OPTiX just using one machine. You can also contact HE to get a free transit at Unmetered Exchange.
For software, I'm using Bird, because I couldn't get OpenBGPd insert routes into my FIB. (I'm using OpenBSD, not the portable one)
For software, I'm using Bird, because I couldn't get OpenBGPd insert routes into my FIB. (I'm using OpenBSD, not the portable one)
I was renting a VM from FRC but I had to let it go because I had loss and nothing was done to fix it :(
Regarding the routes in the FIB, I had the problem as well. Hopefully claudio@'s answer may help you (provided you want to test again) https://marc.info/?l=openbgpd-users&m=161510661928340&w=2 (ctrl-f "1. Why the FIB isn't filled?")
Regarding the routes in the FIB, I had the problem as well. Hopefully claudio@'s answer may help you (provided you want to test again) https://marc.info/?l=openbgpd-users&m=161510661928340&w=2 (ctrl-f "1. Why the FIB isn't filled?")
I can understand the people here complaining about how it's "difficult" to get an ARIN ASN. But you don't really need an ASN unless you intend to be an ISP.
If you want to be serious about having and using an ASN for its intended purpose, you're looking at a minimum of a couple hundred dollars a month anyways for a 1U system in colocation with a hosting company that will set up a router-to-router BGP relationship with you. Even if to start, just singlehomed to one IP transit provider sending you full tables. And ideally also a connection to an IX that exists at the same location.
In US dollars, budget something like $2400-3000 a year to be serious about it what I described above...
The ARIN minimum bar to meet is actually not that high - you need to register an LLC or the local equivalent in your state or province, though of course something like a C-corp is perfectly acceptable as well. Other corporate legal entities like a US state's 501c3 or a Canadian non-profit society or registered charity are also acceptable.
They are not set up for individual persons to get an ASN.
One of the main purposes of having an ASN is to be truly multihomed, to 2 or more transit providers sending you full BGP tables, and you announce your own IP space to your upstream(s), as small as at least one /24 of ipv4, and whatever size you have for ipv6 such as a /32, or /36 or /48, and to join peering exchanges. The number of individual persons who really need to have a BGP-to-BGP full tables relationship with more than 1 ISP are really small. If you need such a thing you are almost certainly some sort of corporate entity (see above) and doing the ARIN membership joining paperwork should be very straightforward.
If you want to be serious about having and using an ASN for its intended purpose, you're looking at a minimum of a couple hundred dollars a month anyways for a 1U system in colocation with a hosting company that will set up a router-to-router BGP relationship with you. Even if to start, just singlehomed to one IP transit provider sending you full tables. And ideally also a connection to an IX that exists at the same location.
In US dollars, budget something like $2400-3000 a year to be serious about it what I described above...
The ARIN minimum bar to meet is actually not that high - you need to register an LLC or the local equivalent in your state or province, though of course something like a C-corp is perfectly acceptable as well. Other corporate legal entities like a US state's 501c3 or a Canadian non-profit society or registered charity are also acceptable.
They are not set up for individual persons to get an ASN.
One of the main purposes of having an ASN is to be truly multihomed, to 2 or more transit providers sending you full BGP tables, and you announce your own IP space to your upstream(s), as small as at least one /24 of ipv4, and whatever size you have for ipv6 such as a /32, or /36 or /48, and to join peering exchanges. The number of individual persons who really need to have a BGP-to-BGP full tables relationship with more than 1 ISP are really small. If you need such a thing you are almost certainly some sort of corporate entity (see above) and doing the ARIN membership joining paperwork should be very straightforward.
> budget something like $2400-3000 a year to be serious about it what I described above...
Companies like Vultr can provide cheap BGP services (free in the case of Vultr) which can be combined with cheap VPS instances as gateways that back-haul your subnet to a home or office server. This type of setup is mentioned down thread. You could easily end up paying more in ARIN fees than infrastructure costs.
> One of the main purposes of having an ASN is to be truly multihomed
For me the main interest in having my own ASN is IP portability across hosting providers. Unfortunately, IP reputation is a thing, especially for e-mail. If I had a portable subnet I wouldn't need to sweat how and where I host my infrastructure. In my case, I could change my office ISP from Cogent to AT&T without worrying about losing e-mail.
EDIT: I'm probably overblowing the risk of being blocked by GMail, Office365, etc, after an IP migration. Don't let me dissuade any aspiring SMTP admins. Nonetheless, my overarching concern is maintaining control of my digital presence (personal and business), no matter how hard Google, Amazon, and others try to squeeze all the small players out of the space.
Companies like Vultr can provide cheap BGP services (free in the case of Vultr) which can be combined with cheap VPS instances as gateways that back-haul your subnet to a home or office server. This type of setup is mentioned down thread. You could easily end up paying more in ARIN fees than infrastructure costs.
> One of the main purposes of having an ASN is to be truly multihomed
For me the main interest in having my own ASN is IP portability across hosting providers. Unfortunately, IP reputation is a thing, especially for e-mail. If I had a portable subnet I wouldn't need to sweat how and where I host my infrastructure. In my case, I could change my office ISP from Cogent to AT&T without worrying about losing e-mail.
EDIT: I'm probably overblowing the risk of being blocked by GMail, Office365, etc, after an IP migration. Don't let me dissuade any aspiring SMTP admins. Nonetheless, my overarching concern is maintaining control of my digital presence (personal and business), no matter how hard Google, Amazon, and others try to squeeze all the small players out of the space.
What if you have two separate ISPs at home (for redundancy) but want your home devices to have stable IP addresses?
Couldn't you achieve this with a simpler/cheaper setup (a single Vultr server set up with their BGP service), and your home devices tunneling everything through it?
And doesn't this use case warrant your own address space?
Couldn't you achieve this with a simpler/cheaper setup (a single Vultr server set up with their BGP service), and your home devices tunneling everything through it?
And doesn't this use case warrant your own address space?
Residential last mile ISPs are highly unlikely to offer bgp as a service. What you'll get is default route DIA.
If you actually do find a cooperative fiber based last mile ISP that will set up bgp with you in your house, I'd be shocked if the service quotation for such a custom weird thing doesn't start from a floor price of $400 a month.
If you actually do find a cooperative fiber based last mile ISP that will set up bgp with you in your house, I'd be shocked if the service quotation for such a custom weird thing doesn't start from a floor price of $400 a month.
Yep. And the cable company isn't going to let you do BGP over DOCSIS, that's for sure.
Backhaul over tunnels is really the only viable solution to "BGP at home."
Backhaul over tunnels is really the only viable solution to "BGP at home."
They hit on a point I rarely see mentioned: ARIN makes acquiring assets as an individual prohibitively difficult and expensive. Especially for IPv6 where European LIRs hand them out like candy e.g. https://clients.stratagem.host/cart.php?gid=14
Having dealt with ARIN, RIPE, and APNIC quite a lot over the years, this is bang on. APNIC is fairly ambivalent. ARIN expects everyone to be a formally organized entity. Only RIPE seems to truly get that an individual person could be doing something on their own behalf, probably because forming a proper limited company was such a huge paperwork endeavor in most of RIPE's service area.
ARIN really needs the concept of sponsoring LIRs, because right now everyone has to deal directly with ARIN and that means ARIN has to fit their policies to try to fit everyone. While it's technically possible to get IPv6 PI space from ARIN as an individual person end user, and it's gotten easier than in the past, it still looks really daunting to the hobbyist or small network operator.
As for LIRs handing them out like candy, I joined RIPE as an LIR and RIPE will allocate an IPv6 /29 to an LIR for the low cost of zero Euro (well, except for the membership, which is a bit spendy) and that's 524,288 /48s so no reason for me to not slap up a web page and see if I can earn back a few of the EUR I will be paying to RIPE. I'm glad people do it for the pittance we see here.
ARIN really needs the concept of sponsoring LIRs, because right now everyone has to deal directly with ARIN and that means ARIN has to fit their policies to try to fit everyone. While it's technically possible to get IPv6 PI space from ARIN as an individual person end user, and it's gotten easier than in the past, it still looks really daunting to the hobbyist or small network operator.
As for LIRs handing them out like candy, I joined RIPE as an LIR and RIPE will allocate an IPv6 /29 to an LIR for the low cost of zero Euro (well, except for the membership, which is a bit spendy) and that's 524,288 /48s so no reason for me to not slap up a web page and see if I can earn back a few of the EUR I will be paying to RIPE. I'm glad people do it for the pittance we see here.
Frankly it needs to be at least a little bit of a pain to get PI space. As the post briefly mentions, every prefix announced consumes memory in every router on the internet. If everyone had their own PI space it would literally break the internet.
I have a legacy /24 that predates ARIN. I know several other local "early internet" users that also have their own netblocks. Back then, all you had to do was fire off an email. The company name didn't even have to be real.
>If everyone had their own PI space it would literally break the internet.
That's an odd way of saying "spurring innovation in the realm of internet routing implementations!
Damn middleboxers. Always trying to keep the little guy off the net!
That's an odd way of saying "spurring innovation in the realm of internet routing implementations!
Damn middleboxers. Always trying to keep the little guy off the net!
ARIN doesn't want or need LIRs because its operating model is based upon having a direct relationship with the entities that hold the ASNs and IP space. If you want to change this you'll need to run for the ARIN board and get a sufficient number of other board members to agree with you for what would be a seismic shift in their entire operating model.
> RIPE will allocate an IPv6 /29 to an LIR
Last time I checked it was a /32.
More than that requires justification (and potential Euro payments depending on context/cirumstances).
Edit to add: Grrr... I see there was a policy change after $myco received its IPv6 allocation [1]. Typical. ;-(
[1] https://www.ripe.net/participate/policies/proposals/2012-10
Last time I checked it was a /32.
More than that requires justification (and potential Euro payments depending on context/cirumstances).
Edit to add: Grrr... I see there was a policy change after $myco received its IPv6 allocation [1]. Typical. ;-(
[1] https://www.ripe.net/participate/policies/proposals/2012-10
How fussy are APNIC? I have a Pty Ltd I can put it though, and I'd like my own addressing and ASN and am willing to pay the $1500 a year fee. My justification with a networking plan however would be bullshit, as I just want to play and learn as an individual.
I am curious, what happens if I get a /48 from you and some time later you decide you don't wish to be a LIR anymore. Do I get to keep my /48 somehow (i.e., does RIPE guarantee this)?
Depends on whether the /48 is PI (provider-independent) or PA (provider-aggregable). In the case above (LIR gets /29 and splits it to /48s) it is PA, so the /48 is just a part of the provider's address range, you cannot keep it if the provider ceased to be LIR (or if you wanted to change providers).
But you can instead request /48 PI range in 'sponsoring LIR' mode, which would be independent allocation from RIPE (and subject to small yearly fee), just processed by the LIR. Then you could keep it if you change LIRs.
But you can instead request /48 PI range in 'sponsoring LIR' mode, which would be independent allocation from RIPE (and subject to small yearly fee), just processed by the LIR. Then you could keep it if you change LIRs.
Your /48 isn't portable, so, no, too bad. If you've got a contract which extends beyond the period where they're an LIR, maybe you have a breach and would seek compensation, but RIPE doesn't care. See also, "What do you mean the guy I leased this apartment from has sold it?".
Most IPv4 space also isn't portable. Even if you have a /24 (enough IPv4 space that it could be portable) it usually isn't, if you actually need portable space you need to make sure that's what you're actually getting, it will probably cost more.
If it's portable then you can just take it with you to another provider.
Most IPv4 space also isn't portable. Even if you have a /24 (enough IPv4 space that it could be portable) it usually isn't, if you actually need portable space you need to make sure that's what you're actually getting, it will probably cost more.
If it's portable then you can just take it with you to another provider.
This was not my experience with ARIN at all. I requested resources as an individual (sole proprietor) and they were issued to me under my own name. The only requirement is that you have a justified use and $250 per year, which is the cost for 3X-Small allocation (/40 or less of IPv6, /24 of IPv4). As of this year it is also $50 to have an "org" created. This is not prohibitively difficult, though it might be prohibitively expensive for some.
Last I looked, ARIN charged $550 (one time fee) to issue an ASN, on top of the recurring fee. Not expensive if you're serious, but if you're a hobbyist and just need a 32-bit ASN number, you may as well explore cheaper alternatives. Based on my own research, that would cover 20+ years of fees for some LIRs in the RIPE region.
An ASN isn't needed unless you are multi-homed. If you're connecting through just one ISP, you can do BGP peering with them using a private ASN. That said, if you do need an ASN, I don't know why they should be so expensive.
Yes, I understand. I set up my first AS in the 90's, back when you were considered a god if you had a T1 line. We had two T1's, one to MCI and another to BBN!
This seems like a very good deal! Has anyone bought this before?
Kind of biased but I'd like to think it's a good deal too, cheers. I priced it as such as to hopefully entice more people to engage with IPv6 and try to bring down the barriers to learning. If you've any specific queries feel free to fire those over.
Is there perhaps a guide on your website that could detail the steps involved to get an ASN and ipv6 up and running? Also could you explain the free /48 included? Thanks.
There isn't, but there ought to be so that's on the todo now. But I'll try to give you a quick rundown here.
The steps to getting an ASN essentially entail setting up some objects over at the RIPE database and then letting us know what these are, we will then send you some paperwork to print, sign & return to us. From here, we submit this application to RIPE (along with company documents, if applying as a company) and they will then request ID verification from you directly (if applying as an individual) or seek to validate your Company, if applying as a company. A few days later, RIPE will give you an ASN. This is the short version but it is essentially just a bit of paperwork and that's all.
The /48 is PA space we give to you in order for you to announce via BGP, with your fresh new ASN. This is included for the life of your ASN (or the heat death of the universe, whichever comes first) and you are free to take that and announce it wherever you want. We do make a polite request that you peer with us but it's not a requirement. If you do peer with us we can help get you up & running and your prefix announced.
Hope that helps a little & if not, feel free to find me on Discord (link is in the footer of the website) and I'll be happy to walk you through it.
The steps to getting an ASN essentially entail setting up some objects over at the RIPE database and then letting us know what these are, we will then send you some paperwork to print, sign & return to us. From here, we submit this application to RIPE (along with company documents, if applying as a company) and they will then request ID verification from you directly (if applying as an individual) or seek to validate your Company, if applying as a company. A few days later, RIPE will give you an ASN. This is the short version but it is essentially just a bit of paperwork and that's all.
The /48 is PA space we give to you in order for you to announce via BGP, with your fresh new ASN. This is included for the life of your ASN (or the heat death of the universe, whichever comes first) and you are free to take that and announce it wherever you want. We do make a polite request that you peer with us but it's not a requirement. If you do peer with us we can help get you up & running and your prefix announced.
Hope that helps a little & if not, feel free to find me on Discord (link is in the footer of the website) and I'll be happy to walk you through it.
Thank you for your info! That's extremely helpful and accessible! I already made the purchase and look forward to more of your awesome product!
The thing that really surprises me here is that he found cheap hosts willing to run a BGP session with him. Who offers this in North America?
He mentions one of his VMs is in Toronto, but not with whom...
edit: Looks like https://xenyth.net/products/vps-hosting/ Xenyth Cloud. Curious if there's any VM hosts in e.g. California that would do this.
He mentions one of his VMs is in Toronto, but not with whom...
edit: Looks like https://xenyth.net/products/vps-hosting/ Xenyth Cloud. Curious if there's any VM hosts in e.g. California that would do this.
Hey, OP here. It's not that unusual actually. Check bgp.services (I mentioned it in https://chown.me/blog/getting-my-own-asn#findinghosters).
A few years ago someone gave a talk "anycast on a shoestring": https://ripe69.ripe.net/wp-content/uploads/presentations/36-...
The author explained how they found hosting services.
A few years ago someone gave a talk "anycast on a shoestring": https://ripe69.ripe.net/wp-content/uploads/presentations/36-...
The author explained how they found hosting services.
I've done this as well recently, and the list at bgp.services helped a lot. Vultr is a good example, they have locations across the globe.
+1 for Vultr. I currently use them to announce a /24.
I wanted to like Vultr. I gave them a fair chance but then they changed the IP on my VPS without telling me. It changed from a Swedish IP to an American IP overnight and left me confused in every way.
Everything broke and support wasn't willing to explain what happened. It felt like they decided my account was suspicious and they routed all my traffic through some firewalled/monitored egress to inspect my traffic. I couldn't even SSH in, I had to go the the dashboard and grab the IP they had reassigned to my host.
Everything broke and support wasn't willing to explain what happened. It felt like they decided my account was suspicious and they routed all my traffic through some firewalled/monitored egress to inspect my traffic. I couldn't even SSH in, I had to go the the dashboard and grab the IP they had reassigned to my host.
Really? That sounds extremely shitty. As a customer of Vultr, it makes me a bit scared, but during the 5~ or something years I've used them, that never happened to me.
You'd be doing everyone a service by continuing to dig out a reason for why that happened, and if they don't provide it, lambast them over social media or something so they do provide some sort of justification.
You'd be doing everyone a service by continuing to dig out a reason for why that happened, and if they don't provide it, lambast them over social media or something so they do provide some sort of justification.
It happened probably 6-7 months ago and worse yet, services I had downstream actually were sensitive to the geolocation of the caller. Fortunately I caught it quickly enough when someone I was working with tried to SSH into the host and couldn't.
Surely the account was being paid via cryptocurrency however it was already verified through the linking of an actual traditional credit card like they required.
Surely the account was being paid via cryptocurrency however it was already verified through the linking of an actual traditional credit card like they required.
I believe Vultr does: https://www.vultr.com/docs/configuring-bgp-on-vultr/
I also know of:
https://freerangecloud.com/
https://freerangecloud.com/
Frantech/BuyVM offer this - https://frante.ch
They have Vegas, Miami, NY and Luxembourg and do BGP, Anycast, DDoS protection etc.
They have Vegas, Miami, NY and Luxembourg and do BGP, Anycast, DDoS protection etc.
Try FreeRangeCloud in Vancouver. They offer IX VPS that allows you to connect to Unmetered Exchange, OPTiX and EVIX. HE is providing free IPv6 transits at Unmetered Exchange, so you can just email them to setup.
Does anyone have a simple to read & concise resource to educate myself on this topic.
I understand what an ASN is at a super high level, but have to admit that the vast majority of the acromyns in this article were new to me.
Any good resources to read on this subject?
I understand what an ASN is at a super high level, but have to admit that the vast majority of the acromyns in this article were new to me.
Any good resources to read on this subject?
I don’t have any resources, but as a hobby homelab / networking guy with too much Mikrotik hardware at home, this is what I learned:
* There are a bunch of organizations responsible for distributing all IP ranges (i.e. ARIN and RIPE);
* Each of these ranges they assign, get a unique ASN;
* Once I have such an ASN, I can go to an ISP and say, “please broadcast this for me and route it to my network”
* ISP will verify whether you speak the truth (hopefully);
* They will add an entry in their route tables for your range, so that any traffic they receive is correctly routed to your port:
* They will start broadcasting your routes, using protocols such as RIP;
* They will then start broadcasting your IP ranges with their uplinks they peer with using BGP;
* The internet has now learned how to reach your servers behind your IP ranges.
This is a bit simplified, but in general is how I understand things work.
Would love it if someone with more knowledge on the matter can elaborate a bit on the BGP broadcasting part, and how ISPs protect against bad actors / scammers / whatever. I know there are recent improvements in BGP security, but it all still seems very insecure to me, and humans are still a critical factor here?
Additionally, I understand that BGP is necessary because typical route table entries being broadcasted using RIP etc are too narrow, too smal, and you want to be able to aggregate a whole bunch of routes into large blocks, which is what BGP is for? Did I get that right?
* There are a bunch of organizations responsible for distributing all IP ranges (i.e. ARIN and RIPE);
* Each of these ranges they assign, get a unique ASN;
* Once I have such an ASN, I can go to an ISP and say, “please broadcast this for me and route it to my network”
* ISP will verify whether you speak the truth (hopefully);
* They will add an entry in their route tables for your range, so that any traffic they receive is correctly routed to your port:
* They will start broadcasting your routes, using protocols such as RIP;
* They will then start broadcasting your IP ranges with their uplinks they peer with using BGP;
* The internet has now learned how to reach your servers behind your IP ranges.
This is a bit simplified, but in general is how I understand things work.
Would love it if someone with more knowledge on the matter can elaborate a bit on the BGP broadcasting part, and how ISPs protect against bad actors / scammers / whatever. I know there are recent improvements in BGP security, but it all still seems very insecure to me, and humans are still a critical factor here?
Additionally, I understand that BGP is necessary because typical route table entries being broadcasted using RIP etc are too narrow, too smal, and you want to be able to aggregate a whole bunch of routes into large blocks, which is what BGP is for? Did I get that right?
This is a huge help as a quick start on this subject. Thanks a lot.
Question: so if I want to host a web application at hosting provider X, and I have my own ASN and want to use my own IP addresses - I assume then that the hosting provider needs to "support BGP"? Is that accurate?
Question: so if I want to host a web application at hosting provider X, and I have my own ASN and want to use my own IP addresses - I assume then that the hosting provider needs to "support BGP"? Is that accurate?
> I assume then that the hosting provider needs to "support BGP"? Is that accurate?
Indeed, one way or another, they need to support BGP which if they are using their own ASN and data center, they most likely already do but it's not 100% they allow their customers to use their own. Sometimes they advertise that they support BGP for their customers (like Vultr: https://www.vultr.com/docs/configuring-bgp-on-vultr/), sometimes they can provide the service to you if you ask nicely and sometimes they don't want anything to do with customer BGP.
Indeed, one way or another, they need to support BGP which if they are using their own ASN and data center, they most likely already do but it's not 100% they allow their customers to use their own. Sometimes they advertise that they support BGP for their customers (like Vultr: https://www.vultr.com/docs/configuring-bgp-on-vultr/), sometimes they can provide the service to you if you ask nicely and sometimes they don't want anything to do with customer BGP.
That is correct, here’s a helpful explanation about BGP from CloudFlare: https://www.cloudflare.com/en-gb/learning/security/glossary/...
[deleted]
> Any good resources to read on this subject?
Everything you wanted to know about BGP from the Network Startup Resource Center (NSRC):
* https://learn.nsrc.org/bgp
Everything you wanted to know about BGP from the Network Startup Resource Center (NSRC):
* https://learn.nsrc.org/bgp
Glad to see mention of self-organized non-profit ISPs in France on HN homepage! I'm sure more people around here would be interested to learn how it works and maybe start their own, if you have english-speaking resources at hand :)
Congratulations on your network setup! It's impressive for such a low budget
Congratulations on your network setup! It's impressive for such a low budget
The Ipv6 pool is quite vast. Yet I am a little surprised that an individual can receive a /48 without much trouble: that a lot of IPs.
This is based on the recommendations in https://datatracker.ietf.org/doc/html/rfc3177
A relevant snippet:
> This means that we feel comfortable about the prospect of allocating 178 billions /48 prefixes under that scheme before problems start to appear. To understand how big that number is, one has to compare 178 billion to 10 billion, which is the projected population on earth in year 2050
A relevant snippet:
> This means that we feel comfortable about the prospect of allocating 178 billions /48 prefixes under that scheme before problems start to appear. To understand how big that number is, one has to compare 178 billion to 10 billion, which is the projected population on earth in year 2050
~So that's a maximum average 17.8 IPs per person? Seems awfully low, considering people these days have multiple devices connected to the Internet at any given time: phone, watch, tablet, laptop(s), perhaps desktop(s), security cameras, IP phones, refrigerators, washing machines, TVs, video game consoles, I could go on...~
Edit: oh, wow I misread that completely. It's 17.8 /48 ranges per person on average. Yep, that should be enough for quite a while.
Edit: oh, wow I misread that completely. It's 17.8 /48 ranges per person on average. Yep, that should be enough for quite a while.
Every phone gets a /48!
> The Ipv6 pool is quite vast. Yet I am a little surprised that an individual can receive a /48 without much trouble: that a lot of IPs.
A /48 is considered one "site" in current thinking. Since IPv6 subnets are /64, you have 16 bits between the /48 and the /64. This is the equivalent of using 10/8 for your network and using /24 IPv4 subnets: in both cases you can have upto 2^16 subnets.
The main difference being that a /24 can have ~250 hosts, but a /64 IPv6 subnet can hold the equivalent of four billion Internets (2^32 * 2^32).
But one of the selling points of IPv6 is reducing/eliminating the mental math about worrying about if you have "enough" addresses (and then carving things into /26, /30, etc).
A /48 is considered one "site" in current thinking. Since IPv6 subnets are /64, you have 16 bits between the /48 and the /64. This is the equivalent of using 10/8 for your network and using /24 IPv4 subnets: in both cases you can have upto 2^16 subnets.
The main difference being that a /24 can have ~250 hosts, but a /64 IPv6 subnet can hold the equivalent of four billion Internets (2^32 * 2^32).
But one of the selling points of IPv6 is reducing/eliminating the mental math about worrying about if you have "enough" addresses (and then carving things into /26, /30, etc).
> A /48 is considered one "site" in current thinking.
This is the really important part. As they continue to hand out IPv6 like candy, the minimum prefix length will get shorter.
No ISP wants a hundred million+ routes in their routing table, so people will start to drop anything shorter than a /42, /40, /38, etc. until the table gets small enough and shunt everyone elses traffic off to Hurricane Electric or the like as a default route.
People have this mindset of "we added a bunch of zeros, its an infinite resource now!" which is how we ended up in this mess to start with.
This is the really important part. As they continue to hand out IPv6 like candy, the minimum prefix length will get shorter.
No ISP wants a hundred million+ routes in their routing table, so people will start to drop anything shorter than a /42, /40, /38, etc. until the table gets small enough and shunt everyone elses traffic off to Hurricane Electric or the like as a default route.
People have this mindset of "we added a bunch of zeros, its an infinite resource now!" which is how we ended up in this mess to start with.
> This is the really important part. As they continue to hand out IPv6 like candy, the minimum prefix length will get shorter.
Unlikely.
> No ISP wants a hundred million+ routes in their routing table […]
Too late. IPv4 are set to hit 1024K (2^20) in January 2024 at current trends:
* https://blog.apnic.net/2021/03/03/what-will-happen-when-the-...
Already close to 10^6:
> I see 904560 IPv4 prefixes. This is 30 fewer prefixes than 6 hours ago and 416 more than a week ago. 59.10% of prefixes are /24.
* https://twitter.com/bgp4_table
* https://bgp.potaroo.net
* https://www.cidr-report.org/as2.0/
Also: https://twitter.com/bgp6_table
Unlikely.
> No ISP wants a hundred million+ routes in their routing table […]
Too late. IPv4 are set to hit 1024K (2^20) in January 2024 at current trends:
* https://blog.apnic.net/2021/03/03/what-will-happen-when-the-...
Already close to 10^6:
> I see 904560 IPv4 prefixes. This is 30 fewer prefixes than 6 hours ago and 416 more than a week ago. 59.10% of prefixes are /24.
* https://twitter.com/bgp4_table
* https://bgp.potaroo.net
* https://www.cidr-report.org/as2.0/
Also: https://twitter.com/bgp6_table
> Unlikely
What is your basis for this opinion? Network operators are already talking about it.
> Too late. IPv4 are set to hit 1024K (2^20) in January 2024 at current trends
Allow me to expand that number for you: 1,048,576
One million. A reasonable upper bound for max announced v4 prefixes is somewhere around two million. You can handle that in a few GB of RAM. IPv6 could see 100x or 1000x that number based on how we are handling allocations, at which point prefix trimming will happen.
What is your basis for this opinion? Network operators are already talking about it.
> Too late. IPv4 are set to hit 1024K (2^20) in January 2024 at current trends
Allow me to expand that number for you: 1,048,576
One million. A reasonable upper bound for max announced v4 prefixes is somewhere around two million. You can handle that in a few GB of RAM. IPv6 could see 100x or 1000x that number based on how we are handling allocations, at which point prefix trimming will happen.
IIRC /64s are ideally meant to address to individual subnets (the bottom 64 bits aren't intended for routing) so it's only really 64k addresses in the conventional sense.
/48 is actually a relatively standard allocation even for home connections, although /56 is more common.
/48 is actually a relatively standard allocation even for home connections, although /56 is more common.
I think what Rogers in Canada does is reasonable. They issue a /64 by default and a /56 if you set an assignment hint.
This was key to me understanding IPv6 - you don't really do variable length subnets. You just get a /48 and break that up into /64's. Because the space is so vast, you can do inefficient things with no chance of running into allocation issues like v4 and you don't have to mentally try and subnet a 128 bit address which maybe some can handle but hurts my head.
The intent of the standard /48 end user size was to prevent residential ISP's from being stingy and only assigning one IP. They wanted homes to have as many publicly routable subnets as the would ever need or want.
This was later revised to "/56 by default, /48 if you ask with no justification needed"
This was later revised to "/56 by default, /48 if you ask with no justification needed"
Another point to consider is the IPv6 global routing table for internet routers. Suppose you decided to give end users /120s instead and those /120s were all routable on the internet. That means there are 120 bits of addressing just to find the network. There are 2^120 such networks in theory. If you could actually enumerate this, you'd be well on your way to bruteforcing AES128. In other words, this is just infeasible.
By handing out /48s the routing table stays manageable. This is the smallest address block you can announce via BGP for this reason.
Given the utter vastness of IPv6 we are also able to do things like carve out an entire /7, fc00::/7, for unique local addresses, and still tell people they shouldn't actually need these addresses at all.
As to the actual process of getting a PI block, I think it is likely to involve some questions. A similar objection exists to handing out smaller than /48s: more people having their own block implies more routing entries. Much better if an existing provider carves you a /48 out of their allocation and routes you traffic. This is probably balanced against the fact that by requiring you to deal with an existing LIR and set up BGP (and your LIR won't want you to muck that up) the number of people who will actually do this just for fun is limited.
By handing out /48s the routing table stays manageable. This is the smallest address block you can announce via BGP for this reason.
Given the utter vastness of IPv6 we are also able to do things like carve out an entire /7, fc00::/7, for unique local addresses, and still tell people they shouldn't actually need these addresses at all.
As to the actual process of getting a PI block, I think it is likely to involve some questions. A similar objection exists to handing out smaller than /48s: more people having their own block implies more routing entries. Much better if an existing provider carves you a /48 out of their allocation and routes you traffic. This is probably balanced against the fact that by requiring you to deal with an existing LIR and set up BGP (and your LIR won't want you to muck that up) the number of people who will actually do this just for fun is limited.
I was surprised about that too.
I got 1 static ipv4 Form my ISP and a /48 for IPv6.
Not sure what to do with that, but still cool.
The IETF IPv6 allocation scheme was crazy from the start. The standard subnet size for autoconfiguration purposes is /64 = 18 Billion Trillion addresses. Of course reality is that autoconfiguration is only marginally useful and lots of things like servers and infrastructure links are statically assigned or assigned through dhcpv6. Most of the time I assign /112's to server subnets to limit the risk of IPv6 neighbor discovery attacks.
The standard /48 assignment size from ISP's to end-users was targeted mainly at stingy residential ISP's that were only assigning one IP per customer. They wanted any customer to have as many publicly routable subnets as they would ever need or want, but 65k is a lot of subnets. This was later updated to a default of /56 (256 subnets) but you could still get at /48 just for asking.
It got even weirder on RIR to ISP portable allocations. One of the original schemes would have RIR's allocating a "TLA" /16 (!) to only a few mega ISP's. Most ISP's/hosts would have to get their "NLA" address blocks from and be subservient to the 800 pound gorillas in the industry. https://www.rfc-editor.org/rfc/rfc2450.txt, https://www.rfc-editor.org/rfc/rfc2374
This was loosened somewhat in 2000 with RFC2928 which designated a "Sub-TLA" /29 as the initial ISP size. This would open it up to many more potential registrants, at least in theory. https://www.rfc-editor.org/rfc/rfc2928.html
The TLA/Sub-TLA/NLA system was abandoned in 2003 with RFC3587 after panic set in that nobody was deploying IPv6. https://www.rfc-editor.org/rfc/rfc3587.txt. ARIN had only made 30 Sub-TLA assignments by the end of 2002.
While RFC3587 wisely punted allocation policy to the RIR communities, the RIR's still had very restrictive policies inherited from RFC2450. Only around 2004 did they loosen to the point that ordinary networks could start requesting addresses. Google for example got their first IPv6 allocation in 2005. The problem is by then few networks were interested or just assumed they wouldn't qualify. When I got my first /32 in late 2004 there were less than 1000 routes in the global IPv6 table! Today there are ~135,000.
These more permissive rules only applied to ISP's/Hosts. End user orgs of any size were not allowed to start requesting portable /48's directly from RIR's until 2006 after much debate in RIR communities and vocal objections from IETF members and certain large ISP's.
Today router silicon and RIR policies have converged to a reasonably functional state. Too bad it took 20 years to get here or IPv6 might actually be on it's way to replacing IPV4. Instead that is still about 20 years away.
The standard /48 assignment size from ISP's to end-users was targeted mainly at stingy residential ISP's that were only assigning one IP per customer. They wanted any customer to have as many publicly routable subnets as they would ever need or want, but 65k is a lot of subnets. This was later updated to a default of /56 (256 subnets) but you could still get at /48 just for asking.
It got even weirder on RIR to ISP portable allocations. One of the original schemes would have RIR's allocating a "TLA" /16 (!) to only a few mega ISP's. Most ISP's/hosts would have to get their "NLA" address blocks from and be subservient to the 800 pound gorillas in the industry. https://www.rfc-editor.org/rfc/rfc2450.txt, https://www.rfc-editor.org/rfc/rfc2374
This was loosened somewhat in 2000 with RFC2928 which designated a "Sub-TLA" /29 as the initial ISP size. This would open it up to many more potential registrants, at least in theory. https://www.rfc-editor.org/rfc/rfc2928.html
The TLA/Sub-TLA/NLA system was abandoned in 2003 with RFC3587 after panic set in that nobody was deploying IPv6. https://www.rfc-editor.org/rfc/rfc3587.txt. ARIN had only made 30 Sub-TLA assignments by the end of 2002.
While RFC3587 wisely punted allocation policy to the RIR communities, the RIR's still had very restrictive policies inherited from RFC2450. Only around 2004 did they loosen to the point that ordinary networks could start requesting addresses. Google for example got their first IPv6 allocation in 2005. The problem is by then few networks were interested or just assumed they wouldn't qualify. When I got my first /32 in late 2004 there were less than 1000 routes in the global IPv6 table! Today there are ~135,000.
These more permissive rules only applied to ISP's/Hosts. End user orgs of any size were not allowed to start requesting portable /48's directly from RIR's until 2006 after much debate in RIR communities and vocal objections from IETF members and certain large ISP's.
Today router silicon and RIR policies have converged to a reasonably functional state. Too bad it took 20 years to get here or IPv6 might actually be on it's way to replacing IPV4. Instead that is still about 20 years away.
I have a /29, there's a lot of IPv6.
I went through the same journey some years ago. Now sharing my ASN 57821 with friends. We use OpenBSD for edge routing validate RPKI as well. My motivation was that I couldn’t get IPv6 otherwise. So I ended up with an ASN, v4 and v6 address space from RIPE. Not the worst deal of my life and the source of tons of practical learning regarding networking.
The only unholy thing I have to do by splitting /64 from my VPS into multiple subnets at home is to use DHCPv6 in my home net instead of SLAAC and use NDP proxy on the VPS.
Probably cheaper and less bothersome than acquiring an ASN and setting up BGP. :)
Probably cheaper and less bothersome than acquiring an ASN and setting up BGP. :)
I like how he mentioned the fixes he did to BSD and even though they were cosmetic and man pages fix.
I always spot those small things, but I always feel silly submitting them on github since sometimes they feel so minor.
I always spot those small things, but I always feel silly submitting them on github since sometimes they feel so minor.
OpenBSD tends to really value high quality man pages.
However to submit a patch you have to email a diff to their mailing lists. They even prefer it inline vs as an attachment.
The GitHub repo linked in the post is just a read only mirror, not used by the OpenBSD project for development.
However to submit a patch you have to email a diff to their mailing lists. They even prefer it inline vs as an attachment.
The GitHub repo linked in the post is just a read only mirror, not used by the OpenBSD project for development.
I think all of the BSDs appreciate thoughtful patches to improve the documentation. Most of the BSD devs are so deeply familiar with the OS that they do not have the perspective of an inexperienced user trying to read the docs and figure things out.
>Well wg(4) doesn't support multicast, and ospf6d (and even eigrpd) needs it. You can do without buuuut... I tried and struggled with ospf6d, so sticking with bgpd was way easier.
Not sure what magic I'm pulling off but I run OSPFv2 and OSPFv3 between 3 routers in a triangle using WireGuard and FRR on VyOS and it's working fine. I just set allowedIPs to everything on the interfaces to let the multicast address traffic go through.
Not sure what magic I'm pulling off but I run OSPFv2 and OSPFv3 between 3 routers in a triangle using WireGuard and FRR on VyOS and it's working fine. I just set allowedIPs to everything on the interfaces to let the multicast address traffic go through.
I also use WireGuard to connect my home router to a VPS to get my home connected to my network. However, VPNs highly depend on the availability of your residential ISP, the speed and stability are not desirable, especially when I run some servers at home. Having a dedicated line with BGP would be good, but there's no such a thing I guess for residential users.
BGP is only necessary to advertise large blocks of provider independent address space. It would still go through your provider's routers however, with appropriate BGP filtering, unless you managed to use some kind of tunneling system. Unless you had a large block of provider independent space and were physically multi-homed to multiple providers, using BGP is more likely to cause problems than help. If you do not connect to multiple ISPs there is not really any reason to use BGP at all.
Aside from a nice article, what a great domain.
The amount of overhead it takes to encrypt a full tunnel on an endpoint device is absolutely not worth it compared to GRE.
Yeah, network hardware is already a bottleneck most of the time, it’s much more effective to keep encryption out of the critical path there.
Besides, I wonder what the threat model is; you will still want end-to-end encryption on top of it, so why bother with encrypting the traffic below as well?
Besides, I wonder what the threat model is; you will still want end-to-end encryption on top of it, so why bother with encrypting the traffic below as well?
FYI: https://ipv6.he.net Try that before delving into (E)BGP and peering.
> I had to escape all the : in my shell
Why? The colon character is not a special character in shell commands.
Why? The colon character is not a special character in shell commands.
(OP here) I'm not sure actually
I'm running bash I have to escape it otherwise the shell doesn't autocomplete.
But ls/vim seems to be fine with the path without escaping so I guess I'm wrong.
Anyway, another problem is: ~/git/git.chown.me/ipam (master %=)$ vim ipv6/2a0e\:f43\:\:-48/2a0e\:f43\:<tab><tab> I get: 2a0e:f43:0:100:-56/ 2a0e:f43:0:fd00::-56/ 2a0e:f43:0:fe00::-56/ 2a0e:f43:0:ff00::-56/ 2a0e:f43::-56/
it's a mess to find the difference between the possibility haha
I'm running bash I have to escape it otherwise the shell doesn't autocomplete.
But ls/vim seems to be fine with the path without escaping so I guess I'm wrong.
Anyway, another problem is: ~/git/git.chown.me/ipam (master %=)$ vim ipv6/2a0e\:f43\:\:-48/2a0e\:f43\:<tab><tab> I get: 2a0e:f43:0:100:-56/ 2a0e:f43:0:fd00::-56/ 2a0e:f43:0:fe00::-56/ 2a0e:f43:0:ff00::-56/ 2a0e:f43::-56/
it's a mess to find the difference between the possibility haha
The author uses OpenBSD which uses ksh as their default shell. I just ran ksh on Arch Linux and even though `touch foo:bar` worked, when I did tab-completion the shell escaped the colon anyway, making my command `touch foo\:bar`. I assume its related to this, but I've never used ksh before so I can't explain the difference in the tab-completion behavior.
bash is the same - `:` isn't special but tab-completion escapes it.
Tab-completion is probably being conservative about escaping it in case you're using it as a path separator, like when setting a `$PATH`-like var.
Tab-completion is probably being conservative about escaping it in case you're using it as a path separator, like when setting a `$PATH`-like var.
The shell doesn't know what the underlying filesystem is.
: is special on NTFS for alternative data streams, and I think HFS+ named forks? (The mac syntax is foo/..namedfork/rsrc, I don't know how that translates to linux)
"foo\:bar" is a file name with a colon in it. "foo:bar" is an ADS named bar on the file foo.
: is special on NTFS for alternative data streams, and I think HFS+ named forks? (The mac syntax is foo/..namedfork/rsrc, I don't know how that translates to linux)
"foo\:bar" is a file name with a colon in it. "foo:bar" is an ADS named bar on the file foo.
Maybe. The motivation may have been lost to history.
bash added `:` to the list of completion word break characters with bash 2.0 [1][2]. Bash 2.0 was released in 1996. NTFS-3G started in 2006 but it was "forked from the Linux-NTFS", and I can't find any history for this project. NTFS itself was released in 1993.
HFS+ seems to have been released in 1998, so it can't be the reason. But even regular HFS had resource forks and it was released in 1985.
No idea where to look in ksh's source.
[1]: https://github.com/bminor/bash/commit/ccc6cda312fea9f0468ee6...
[2]: https://github.com/bminor/bash/commit/ccc6cda312fea9f0468ee6...
bash added `:` to the list of completion word break characters with bash 2.0 [1][2]. Bash 2.0 was released in 1996. NTFS-3G started in 2006 but it was "forked from the Linux-NTFS", and I can't find any history for this project. NTFS itself was released in 1993.
HFS+ seems to have been released in 1998, so it can't be the reason. But even regular HFS had resource forks and it was released in 1985.
No idea where to look in ksh's source.
[1]: https://github.com/bminor/bash/commit/ccc6cda312fea9f0468ee6...
[2]: https://github.com/bminor/bash/commit/ccc6cda312fea9f0468ee6...
> "foo\:bar" is a file name with a colon in it. "foo:bar" is an ADS named bar on the file foo.
That does not make sense. The shell does not itself know anything about ADSs, and therefore, in both cases, sends the string "foo:bar" as arguments to commands.
That does not make sense. The shell does not itself know anything about ADSs, and therefore, in both cases, sends the string "foo:bar" as arguments to commands.
The : character is a no-op character in bash, ksh, and maybe others.
https://stackoverflow.com/questions/7444504/explanation-of-c...
https://stackoverflow.com/questions/7444504/explanation-of-c...
Correction: The : character, by itself, is the name a built-in command. However, the : character is not interpreted in any special way either as part of the name of another command, or as an argument to a command.
Contrast this with the characters $, [, (, etc.
Contrast this with the characters $, [, (, etc.
[deleted]
Be careful who you peer with. You might catch some pathogenic routes. Always use protection.
What?
We have too many people who don't like stuff like this, who say it's "too hard", and that people shouldn't do hard things (just see any thread on the Internet about people running their own email servers). It's wonderful to see someone sharing something non-trivial in a way that makes it ever so slightly more attainable to the rest of us.