4 ms·
Mobile carriers here are bringing back NAT on ipv6 now. Wannacry fears? NAT for the sake of firewalling? Phones still seem to get individual addresses.
by mavendependency 9y ago
Mobile carriers here are bringing back NAT on ipv6 now. Wannacry fears? NAT for the sake of firewalling?
Phones still seem to get individual addresses.
- fulafel 9y agoIf anyone sees a mobile provider does this, please complain loudly.
- betaby 9y agoWhich one? Really curious. Another point to mention, that I've seen mobile operators sends you multiple /64s, thus if you run in adnroid shell 'ip addr' you see one /64 while if you connect say to ripe.net it shows completely different IPv6 address from different range, while still no NAT. Perhaps that was your case, perhaps not. Details would be very interesting.
- p1mrx 9y agoIf your address on ripe.net doesn't match any of your local interface addresses, then that's NAT (or perhaps a transparent proxy) by definition. Well, in some environments, it's possible to bind() to an IP address that's not actually present on a local interface, but it's unlikely that your browser would support that.
- betaby 9y agoOn other side I can ping IPv6 address of the tethered laptop. And for tethered devices ripe reported IPv6 matches interface. Indeed, transparent proxy / media gateway could be the case for the phone itself.