No ping possible after changing the IPv6 prefix (dynamic prefix by provider).
-
Hello everyone,
I'm encountering a issue that I'd like to share with you. I'm wondering if anyone else has had the same experience and found a solution?
Here's the scenario (pfSense version 2.7.2):
-
The pfSense is behind an AVM FRITZ!Box 7590 (with everything set to default on it).
-
The pfSense receives an IPv6 address (WAN interface) from the AVM FRITZ!Box 7590 via DHCP or optionally SLAAC.
-
An ICMPv6 ping to the IPv6 internet is now possible.
-
After the forced disconnection by the DSL provider, the FRITZ!Box receives a new IPv6 prefix. The pfSense also quickly gets a new IPv6 address. In ifconfig, both IPv6 addresses are now visible: the previous IPv6 address (marked as "deprecated"), and the new address.
-
Attempting an ICMPv6 ping to the IPv6 internet is no longer possible, even though the correct "new" IPv6 source address is displayed in the terminal during the ping attempt. However, via packet capture, I've noticed that the old IPv6 address (which is marked as deprecated) is still being used as the actual source address.
This behavior does not occur when the pfSense establishes the internet connection itself via PPPoE.
Is this behavior known, and what can I do?
Rebooting the pfSense resolves this issue, but that can't be the solution every time (to be done manually)…
Thank you for your help!
-
-
@voglcloud That's how it is.
Not much you can do about it other than running some script via cron for fixing this.This behavior does not occur when the pfSense establishes the internet connection itself via PPPoE.
That is news to me.
-
@Bob-Dig Thank you for the quick response.
Not much you can do about it other than running some script via cron for fixing this.
So, is this behavior normal? What causes it? Is it known whether the problem will be fixed?
That is news to me.
So, should the problem occur here as well? At least I haven't observed it so far. I will take a closer look when I get the chance...
