[solved] tunnelbroker.net: weird public ipv6 address reported for all devices
-
As a learning exercise I changed from the ISP provided DHCPv6 configuration to using tunnelbroker.net (guided by https://docs.netgate.com/pfsense/en/latest/recipes/ipv6-tunnel-broker.html)
I now have a routed/64 configured on the LAN and a routed/48 allocated and split across a number of VLANs.
Everything is working fine as far as I can see, every device can talk to the internet over the GIF tunnel.
The only problem is when I check the public ip address using whatsmyip and the likes, the device IPv6 address is shown as being the IPv6 Tunnel Endpoint Client Address (as seen on the tunnelbroker.net dashboard). This is regardless of which device I use to check the IP with, the LAN and VLAN devices all show the same public IPv6 address.
As I didn't test this configuration on 24.11 I am not sure if it is a 25.03-BETA bug or a simple configuration error on my side.
(it feels a lot like IPv4 NAT, but why whould that happen on IPv6?)
Any ideas?
-
... and the thought of IPv4 NAT kept me digging deeper... and I found the issue.
It was an "unexpected" manual mapping entry in Firewall / NAT / Outbound on the "old" IPv6 interface (ISP WAN) that caused NAT64 to be configured for all IPv6. Not sure if that is the way is is supposed to work, or if it's a bug.
-
NAT64 is not applied via outbound NAT, what you describe is just plain outbound NAT on IPv6, but it would only happen that way if you manually configured it to do that. The default automatic rules wouldn't behave that way.
-
@jimp thank you for the clarification. Yes, I think it must have been very late at night when that got added...