6 ms·

> get static IPv6 addresses instead of a dynamic one behind an ISP NAT. Some UK ISPs give out /48s (cough Sky) but with dynamic allocation. So you reboot your

> get static IPv6 addresses instead of a dynamic one behind an ISP NAT. Some UK ISPs give out /48s (cough Sky) but with dynamic allocation. So you reboot your router and every single IPv6 device on your network needs to re-address. Makes routing/port forwarding a PITA and nearly impossible using IPv6.

midasuni 4y ago
Even if it was static changing the ISP will result in a new public range, meaning an internal re number, unless you use NAT, in which case you may as well use ipv4 and nat. If you have two ISPs (say a backup 5G) then you have to renumber every time the main goes down. If you want to load balance you’re screwed, unless of course you use nat. Residential ISPs won’t allow you to bgp peer your own /48
- throw0101c 4y ago
  > Even if it was static changing the ISP will result in a new public range, meaning an internal re number, unless you use NAT, in which case you may as well use ipv4 and nat. Kind of: if you use IPv6's ULA (fc00/7 [1]), then you can have a NAT-like translation layer using NPTv6 [2]. The advantage of NTPv6 over NAT44 is that you get an entire prefix to play with instead of a single IP on your router's WAN interface. If you wish to have multiple services (web, SSH, Minecraft), then with IPv4 hole punching you can only have one server on the default port and the second system with the same service needs to be on a different port. With IPv6/NPTv6 you can have each service on a different IPv6 address and live on its default port. You also have the flexibility of either only allowing one particular port in for that service/IPv6 address, or just allowing all traffic in without any firewalling/filtering. So NPTv6 is no worse than NAT44 in the simple cases, but also has extra functionality over it. [1] https://en.wikipedia.org/wiki/Unique_local_address https://en.wikipedia.org/wiki/Unique_local_address [2] https://en.wikipedia.org/wiki/IPv6-to-IPv6_Network_Prefix_Translation https://en.wikipedia.org/wiki/IPv6-to-IPv6_Network_Prefix_Tr...
- cassianoleal 4y ago
  > Even if it was static changing the ISP will result in a new public range I bet most people change ISPs with a frequency that's a fraction of the frequency they reboot their routers. In any case, only a few devices in most households require static public IPs (only the ones you connect to from the outside directly). If you put those in DNS, all you need to do is change their AAAA records. For internal comms, IPv6s in the link- or site-local ranges are better anyway.
- xen2xen1 4y ago
  I guess that's a good point, even if my ISP did have IP V6, I'd need to get a static from that too. Bet they'd want me to pay extra for that one on top of the V4 cost.
yrro 4y ago
Huh? I'm only able to get a single /64 with Sky. If I enable PD then I get nothing. Perhaps this is the fault of the Unifi Dream Machine's poor IPv6 support... maybe I should take another look?
- magicalhippo 4y ago
  I thought the same with my ISP, but it turned out it was pfSense who didn't do the right thing or something. Switched to OpenWRT and I got a /56 right away.

midasuni 4y ago

Even if it was static changing the ISP will result in a new public range, meaning an internal re number, unless you use NAT, in which case you may as well use ipv4 and nat. If you have two ISPs (say a backup 5G) then you have to renumber every time the main goes down. If you want to load balance you’re screwed, unless of course you use nat. Residential ISPs won’t allow you to bgp peer your own /48

throw0101c 4y ago
> Even if it was static changing the ISP will result in a new public range, meaning an internal re number, unless you use NAT, in which case you may as well use ipv4 and nat. Kind of: if you use IPv6's ULA (fc00/7 [1]), then you can have a NAT-like translation layer using NPTv6 [2]. The advantage of NTPv6 over NAT44 is that you get an entire prefix to play with instead of a single IP on your router's WAN interface. If you wish to have multiple services (web, SSH, Minecraft), then with IPv4 hole punching you can only have one server on the default port and the second system with the same service needs to be on a different port. With IPv6/NPTv6 you can have each service on a different IPv6 address and live on its default port. You also have the flexibility of either only allowing one particular port in for that service/IPv6 address, or just allowing all traffic in without any firewalling/filtering. So NPTv6 is no worse than NAT44 in the simple cases, but also has extra functionality over it. [1] https://en.wikipedia.org/wiki/Unique_local_address https://en.wikipedia.org/wiki/Unique_local_address [2] https://en.wikipedia.org/wiki/IPv6-to-IPv6_Network_Prefix_Translation https://en.wikipedia.org/wiki/IPv6-to-IPv6_Network_Prefix_Tr...
cassianoleal 4y ago
> Even if it was static changing the ISP will result in a new public range I bet most people change ISPs with a frequency that's a fraction of the frequency they reboot their routers. In any case, only a few devices in most households require static public IPs (only the ones you connect to from the outside directly). If you put those in DNS, all you need to do is change their AAAA records. For internal comms, IPv6s in the link- or site-local ranges are better anyway.
xen2xen1 4y ago
I guess that's a good point, even if my ISP did have IP V6, I'd need to get a static from that too. Bet they'd want me to pay extra for that one on top of the V4 cost.

yrro 4y ago

Huh? I'm only able to get a single /64 with Sky. If I enable PD then I get nothing. Perhaps this is the fault of the Unifi Dream Machine's poor IPv6 support... maybe I should take another look?

magicalhippo 4y ago
I thought the same with my ISP, but it turned out it was pfSense who didn't do the right thing or something. Switched to OpenWRT and I got a /56 right away.