pfSense fails to restore IPV6 after WAN side service interruption
-
@jcyr said in pfSense fails to restore IPV6 after WAN side service interruption:
That will only work if Comcast assigns the same V4 and V6 addresses to you upon re-registration. I know this to be mostly true for Comcast, but not guaranteed.
I don't recall my v4 address ever changing, unless I change the MAC address on my WAN interface... same for v6, as long as you'd have the same DUID you should receive the same prefix...
I suppose one could write a script to restart the interface periodically until the 192.168.100.0/24 address clears.
-
pfSense has a gateway monitoring function. Perhaps that might help. However, I haven't tried it, as I don't have a need to. What is the intended function of gateway monitoring?
-
@ljr said in pfSense fails to restore IPV6 after WAN side service interruption:
I suppose one could write a script to restart the interface periodically until the 192.168.100.0/24 address clears.
Or start with RTFM: https://docs.netgate.com/pfsense/en/latest/book/interfaces/ipv4-wan-types.html#dhcp and try to reject the lease.
-
@Grimson I'll certainly try that. But that's IPV4 stuff and never had a problem with V4.
-
@Grimson said in pfSense fails to restore IPV6 after WAN side service interruption:
Or start with RTFM: https://docs.netgate.com/pfsense/en/latest/book/interfaces/ipv4-wan-types.html#dhcp and try to reject the lease.
Well, in retrospect it was amateur to suggest hacking a script. But, shit, that does the trick.
Sorry.
-
@Grimson I have been rejecting leases from my cable modem, 192.168.100.1, for some time now. Doesn't appear to have an impact on this issue(s).
Rebooted pfsense late last night and the WAN did not get an ipv6 address. Waited a good long time. A second reboot set it right. I then disconnected the cable, waited a few minutes, and reconnected. It worked.
Too many variables, I need to set aside some time and work this through methodically.
-
@jwj said in pfSense fails to restore IPV6 after WAN side service interruption:
@Grimson I have been rejecting leases from my cable modem, 192.168.100.1, for some time now. Doesn't appear to have an impact on this issue(s).
Rebooted pfsense late last night and the WAN did not get an ipv6 address. Waited a good long time. A second reboot set it right. I then disconnected the cable, waited a few minutes, and reconnected. It worked.
Too many variables, I need to set aside some time and work this through methodically.
Indeed, there appears to be more than one path to failure.
-
@Grimson Well that didn't work! Had another service interruption today and ignoring leases from the modem's DHCP prevented even IPV4 from recovering when the modem registered upon resumption of service. Had to bounce the WAN link to restore LAN side connectivity.
-
I see this as well, IPv6 will not come up until apply button is pressed in the WAN interface or a second reboot (sometimes)
This is with Arris CM8200B and 2.4.5-RELEASE-p1
-
