|
|
|
|
|
by magicalhippo
76 days ago
|
|
Please don't put words in my mouth. I did not say "Because pfSense, does really bad things." How pfSense works is fairly reasonable if every IPv6 deployment had been as the original designers intended, ie you have a static prefix. It's just that the way IPv6 ended up getting deployed in practice was often not aligned with that original vision. And that has been a large source of IPv6 frustration. |
|
I can't see why an ISP is dynamically changing the IPv6 addressing for a client, but if that's what is going on, then v6 NPT is your friend (RFC6296 - https://datatracker.ietf.org/doc/html/rfc6296).
But pfsense's behaviour is a bit iffy too, unless when you say 'public IP', you mean the IPv6 address being used on the pfsense facing the clients? (I'm assuming it's using DHCPv6 prefix delegation, and the delegation is being changed? And potentially the uplink subnet as well).