this post was submitted on 03 Jul 2023
14 points (93.8% liked)

Selfhosted

39939 readers
376 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Just wondering how many of us use ipv6 for our local hosts, as with my router upgrade, my ISP only allows me to have 253 IP ipv4 addresses (and I don't want to have to buy a new router/gateway, a 10gbe router/gateway is expensive).

Anyway, do you guys use statically assigned ULA addresses? Statically assigned global addresses? DHCPv6? SLAAC? What do you guys do for DNS resolution, avahi/mdns everywhere (given that ipv6 addresses seem to change all the time).

I've currently mostly gotten ipv6 working (dual stack) on machines I touch, my my k3s cluster is out of commission until I can figure out a way to not have them consume any precious ipv4 addresses.

I'm not even sure what prefix I want to choose for the cluster / service CIDR, should I be using a ULA or the one specified https://docs.k3s.io/installation/network-options#dual-stack-ipv4--ipv6-networking, 2001:cafe:42::

you are viewing a single comment's thread
view the rest of the comments
[–] i_am_not_a_robot@discuss.tchncs.de 1 points 1 year ago (1 children)

Residential ISP routers are almost universally trash because most people just want to receive media streams on at most a few devices at a time.

You might be able to set static routes in the ISP router so you can run your own router with its own subnet and have all your addresses routable within your home network anyway. If you have your network on 10.0.0.0/8 and your router is 192.168.0.2 on your ISP's network in your house, then you tell the ISP's router that 10.0.0.0/8 is reachable via 192.168.0.2 and cross your fingers that it can route IP correctly. Unless the ISP's router advertises that static route via DHCP, other devices on the ISP's network in your house will likely need to be told about your network's routing in order to be able to communicate with devices on your network. MDNS name resolution is unlikely to work across the two networks. Some other features, such as automatic port forwarding, may not work, but may be possible if you tell the ISP router to forward all ports to your router by default.

In my network I run DNS so everything is resolvable by name. Most of the time the names are filled in my autoconfiguration. Some K8S services are connected to the rest of the house by Multus so they have their own IP addresses.

[–] kelvie@lemmy.ca 1 points 1 year ago

The problem I have here is that it's expensive (and takes up space/power) to run a router that can handle 10gbe -- my uplink is 3gbe right now. So it's either shell out for a beefier router, or work around it.