Bug #8192
open
dpinger - Change in ISP link-local IPv6 address drops connectivity
Added by Kristopher Kolpin almost 7 years ago.
Updated about 4 years ago.
Category:
Gateway Monitoring
Affected Architecture:
amd64
Description
When connecting via PPPoE on a DSL connection, the IPv6 link-local address on an ISP's router may change periodically. This may occur with or without a drop in the PPPoE connection. Unfortunately, dpinger does not communicate with the new IPv6 link-local address at the ISP.
Disabling gateway monitoring action does not mitigate this issue. Disable gateway monitoring must be checked for IPv6 connectivity to be maintained in the event of an IPv6 link-local address change at the ISP's router.
- Target version changed from 2.4.3 to 2.4.4
- Target version changed from 2.4.4 to 48
One is for DHCPv6, one is for PPPoE. They could be different problems, they could be the same problem, needs more research to tell.
I'm seeing this again in 2.4.4. Disabling gateway monitoring and gateway monitoring action in 2.4.2 100% resolved this issue. I was able to repeat by going back to 2.4.2.
I spoke with my ISP. It appears as part of a load balancing script on their end the PPPoE session will be dropped and redirected to another authentication server. During this process my static IPv4 and static IPv6 (global) stay the same. However, the IPv6 link-local address (ISP) will be different if the authentication server is different. As I said above, pfSense 2.4.2 used to handle this properly if I disabled gateway monitoring and gateway monitoring action.
- Target version changed from 48 to 2.5.0
- Category changed from Routing to Gateway Monitoring
- Assignee set to Luiz Souza
- Priority changed from Normal to Low
- Target version changed from 2.5.0 to CE-Next
Also available in: Atom
PDF
Updated by 
Updated by Anonymous 
Updated by 
Updated by