Commit graph

6 commits

Author SHA1 Message Date
steering7253
67fc67b837
Let me make something clear here.
I don't have time to write out a justification.
I don't have time to write out exactly how every IP is used.
That's not fun.
I do (did) this for fun.

It was pretty fun.
I ended up buying a few yearly servers to peer with people.
I've got my LAN set up with 17 current leases (which isn't all the
devices that are currently set up, just all the ones that have been on
lately). I've got my IoT and admin VLANs waiting to be set up, although
to be fair those are somewhat waiting on physical cabling. It can talk
to my servers with no NAT and no extra address space for me to keep
mental track of. Everything's great!

For even more fun, I wanted to get my VM host, bhs2, set up better so that I could run more
services on it (like autopeering). Unfortunately, 2^(32-29)=8, and I
already have 8 IPs used from my /29.

But frankly, wasting my time writing this and putting it all in order to
make sense to someone else is... not fun.

Which is, again, why I chose to limit the amount of IPs and not need to
do this.

Anyway, since you're so short on IP's, this should help.

I hope you have the day you deserve so long as you ignore your own
policies <3
2026-05-19 16:34:58 -06:00
Kioubit
a0ae5ca697 Convert geofeed entries to use the new attribute 2026-05-14 00:34:54 +03:00
steering7253
e518abe297
update nserver for steering-lan, add dnssec 2026-05-01 17:46:40 -06:00
steering7253
363fd65d6a
add cgit.dn42 and ns2.steering.dn42 2026-04-17 23:28:10 -06:00
steering7253
3b0505daf4
add 1459.dn42 and update ns ipv6 2026-04-05 18:16:45 -06:00
steering7253
355d08ac6e
add steering 2026-01-06 21:20:29 -07:00