Project

General

Profile

Bug #8192

dpinger - Change in ISP link-local IPv6 address drops connectivity

Added by Kristopher Kolpin almost 2 years ago. Updated 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Gateway Monitoring
Target version:
Start date:
12/11/2017
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.4.2
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.

History

#1 Updated by Jim Pingle over 1 year ago

  • Target version changed from 2.4.3 to 2.4.4

#2 Updated by Steve Beaver about 1 year ago

  • Target version changed from 2.4.4 to 48

#3 Updated by Luke Hamburg about 1 year ago

Is this a dupe of #8136?

#4 Updated by Jim Pingle about 1 year ago

One is for DHCPv6, one is for PPPoE. They could be different problems, they could be the same problem, needs more research to tell.

#5 Updated by Kristopher Kolpin 11 months ago

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.

#6 Updated by Kristopher Kolpin 11 months ago

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.

#7 Updated by Jim Pingle 7 months ago

  • Target version changed from 48 to 2.5.0

#8 Updated by Jim Pingle 2 months ago

  • Category changed from Routing to Gateway Monitoring

Also available in: Atom PDF