6 ms·
With IPv6, it's common to have multiple addresses on an interface. So on options is to assign yourself an [RFC 4193](https://datatracker.ietf.org/doc/html/rfc4
by _ikke_ 9mo ago
With IPv6, it's common to have multiple addresses on an interface.
So on options is to assign yourself an [RFC 4193](https://datatracker.ietf.org/doc/html/rfc4193 https://datatracker.ietf.org/doc/html/rfc4193) fc00::/7 random prefix that you use for local routing that is stable, while the ISP prefix can be used for global routing.
Then you don't need to renumber your local network regardless of what your ISP does.
- mixdup 9mo agoWhat if I want my devices visible on the public internet? Then I'm tied to my ISP's addresses. Or, I have to maintain both addressing schemes
- _ikke_ 9mo agoThat's why I mentioned multiple addresses. The public addresses (assigned using SLAAC or DHCPv6) are for global reachability, while you use the local prefix for stable addresses within your network. If you want stable global addresses, you should request an AS number and prefix, and choose a provider that allows you to announce it with BGP.
- parineum 9mo ago> and choose a provider Lots of people don't have much choice. Frankly, my IoT washing machine having a public IP address sounds like it'll get shut off when I don't let it online or don't pay my subscription fee.
- Dylan16807 9mo ago> Lots of people don't have much choice. Yeah but it's not like IPv4 is any better at giving you a stable public address.
- preisschild 9mo agoFunfact my washing machine has a public ipv6 address, but egress/ingress conns to the WAN are blocked. works great.
- patmorgan23 9mo agoThis is also the case with IPv4.