'My own piece of the Internet: Part 1', a blog post discussing the process of getting an ARIN ASN and a /24 IPv4 block for their home setup
From the blog post
obtaining an ARIN ASN and a portable /24 IPv4 block for a home networkI’ve wanted my own Internet address space for a long time. Not “my ISP gave me some statics” space which I’ve had for well over a decade now, but a block that belongs to me, announced into the global routing table by equipment I own, and ideally sitting in the rack in my house. Type the prefix into bgp.tools and see my own ASN sitting there as the origin. How cool! (ok, cool for some, but not most)
14 replies
This is an awesome series, but that 20 month wait for a /24 IPv4 subnet would be unbearable to me. I'd rather just go mostly-IPv6 and maybe run NAT64 or something on a VPS to cover legacy uses.
I say this because while some are fine with waiting, I view self hosting as an act of self sufficiency and resilience, which really shouldn't be on someone else's timeline. If IPv4 subnets are the only thing holding someone who's willing and able to run an AS, I would genuinely recommend ditching IPv4 and the scarcity that comes with it, even with the translation costs elsewhere. Perfection must not become the enemy of good-enough.
How in the hell are you already using almost 126 public IPs?? Surely you condense some of those services? That must cost more than you like...
The arr stack alone is 8-12 IPs. Basic net stack is 3-6. Servers, personal devices, IoT...shit adds up.
Reverse proxy my friend....
Using one static IP per service feels so much like .. 1990s...
... As well as owing a /24, I admit.
Can't announce </24 :(
Or >/24.…. Depending on semantics :)
Not sure why most of the arr stack would even need public IPs?
Why shouldnt they if you have enough ips? Nat still is an ugly workaround
Workaround to what? Why would radarr need a public-facing presence?
And even if there is a use case, the routing alone would be a nightmare.
ipv4 exhaustion. Devices are meant to have routable addresses. How would that make routing harder?
Ipv4 TLD exhaustion happened in 2011, but it was functionally impossible to get a public IP directly from IANA closer to 2005.
And the routing would be a nightmare because if you have multiple gateways between non-overlapping CIDR ranges, you need to tell routing equipment how the packet should return to its source.
So ignoring there being no reason to expose sonarr or radarr to the public at large in the first place, you would be working with two potential scenarios with multiple IPS: either you have two distinct subnets blocks behind your gateways, or you you have two gateways to a single subnet.
In the first case, you would have to route traffic between the two subnets, which makes the scenario not make sense, because why would you need packets between two local hosts to pass through their gateways through public space when they could just be in the same subnet. In the second case, you would have to specify to all your internal hosts two gateways so traffic know which public IP to return to.
Neither of these scenarios make sense when NAT is a much simpler (and cheaper)solution.
The are stack should not be public… there should at most be one public ip for that.
Wait what? Is you serious?
I did this back in the 00s, got the /24 immediately. Wish I'd kept it going today.
Same energy:
https://youtu.be/Jpuqmjd12lg
Title: I Got My Own AS Number. Here's: What It Took
I skimmed over your posted blog. Reads like a somewhat same process.
Literally "Same, same but different" ^^