Project

General

Profile

Bug #8136

dpinger for WAN DHCPv6 gets fails to update gateway IP

Added by Kristopher Kolpin about 3 years ago. Updated 15 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Renato Botelho
Category:
Gateway Monitoring
Target version:
2.5.0
Start date:
11/27/2017
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.4.2
Affected Architecture:
amd64

Description

There appears to be an issue with dpinger when the IPv6 link-local address for a native DHCPv6 connection changes.

When a PPPoE session drops, the link-local IPv6 address of the default gateway at the ISP's end changes. Unfortuntaely, dpinger is still attempting to ping the previous IPv6 link-local address and does not automtically update to the new one. This results in a perpetual "pending" blue box on the pfSense router's home page. The errors can be seen in the log files.

Associated revisions

Revision 37194aa2 (diff)
Added by Renato Botelho 4 months ago

Ticket #8136: Reconfigure dpinger when IPv6 reconnects

When SLAAC interface is disconnected and reconnected, rc.newwanipv6 is
never executed because dhcp6c is the only trigger for that. Add a
workaround on rc.linkup to force it to run in these cases so dpinger is
configured and gateway status works

Revision acb79de0 (diff)
Added by Renato Botelho 4 months ago

Ticket #8136: Make sure dpinger is configured

Improve solution applied in 37194aa24e calling setup_gateways_monitor()
instead of running rc.newwanipv6

History

#1 Updated by Jim Pingle almost 3 years ago

  • Target version changed from 2.4.3 to 2.4.4

#2 Updated by Steve Beaver over 2 years ago

  • Target version changed from 2.4.4 to 48

#3 Updated by Jim Pingle almost 2 years ago

  • Target version changed from 48 to 2.5.0

#4 Updated by Steve Beaver 5 months ago

  • Assignee set to Renato Botelho

#5 Updated by Kristopher Kolpin 4 months ago

Hi Renato, please see my comment in ticket # 9324. Maybe these two issues are related?

#6 Updated by Renato Botelho 4 months ago

  • Status changed from New to In Progress

#7 Updated by Renato Botelho 4 months ago

  • Status changed from In Progress to Feedback

This problem should not happen in this case if you check the option "Use IPv4 connectivity as parent interface". Could you please re-test with the next round of snapshots?

#8 Updated by Danilo Zrenjanin about 2 months ago

Can you provide more details on how to replicate the issue? Is it related only to the PPPoE link? Can you provide the PPPoE client setup details to replicate the issue?

#9 Updated by Renato Botelho 22 days ago

Danilo Zrenjanin wrote:

Can you provide more details on how to replicate the issue? Is it related only to the PPPoE link? Can you provide the PPPoE client setup details to replicate the issue?

Before the fix I just unplug WAN cable and plug it again and gateway moved to Pending status forever

#10 Updated by Renato Botelho 15 days ago

  • Status changed from Feedback to Resolved

No more reports but it's not happening anymore on my home router, so I believe it's safe to say it's resolved.

Also available in: Atom PDF