Bug #8136
closed
dpinger for WAN DHCPv6 gets fails to update gateway IP
0%
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.
Updated by Jim Pingle almost 7 years ago
- Target version changed from 2.4.3 to 2.4.4
Updated by Anonymous
Updated by Jim Pingle almost 6 years ago
- Target version changed from 48 to 2.5.0
Updated by Kristopher Kolpin about 4 years ago
Hi Renato, please see my comment in ticket # 9324. Maybe these two issues are related?
Updated by Renato Botelho about 4 years ago
- Status changed from New to In Progress
Updated by Renato Botelho about 4 years 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?
Updated by Danilo Zrenjanin almost 4 years 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?
Updated by Renato Botelho almost 4 years 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
Updated by Renato Botelho almost 4 years 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.