Project

General

Profile

Actions

Regression #13238

closed

WAN_DHCP6 gateway stuck pending with "Do not wait for RA" set

Added by Daryl Morse almost 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Gateways
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
22.05
Release Notes:
Force Exclusion
Affected Version:
2.7.0
Affected Architecture:

Description

My specific situation is the following:

ISP requires the following settings:

Request only an IPv6 prefix
Do not wait for a RA

WAN_DHCP6 is stuck pending / unknown indefinitely.

The file /tmp/hn0_defaultgwv6 is missing.

The ISP gateway address is link-local.

IPv6 is working, but DHCPv6 addresses are not being allocated.

This issue is discussed in https://forum.netgate.com/topic/170445/wan_dhcp6-pending-unknown-and-dhcpv6-server-not-working. This is possibly related to the M and O flags not being set in the RA message.

This issue does not exist in 2.6.0 and it was introduced into 2.7.0-DEVELOPMENT in the February 2022 time frame.

Actions #1

Updated by Hayden Hill almost 2 years ago

I am having the same issue in the development versions of 22.05. "Do not wait for RA" seems to be the culprit as well.

Actions #2

Updated by Daryl Morse almost 2 years ago

Hayden Hill wrote in #note-1:

I am having the same issue in the development versions of 22.05. "Do not wait for RA" seems to be the culprit as well.

In my case, I'm pretty sure "do not wait for RA" is NOT the problem. With my ISP, if "do not wait for RA" was not working, there would be no IPv6 at all. However, IPv6 is working, except for dpinger not running and dhcpv6 not running. I suspect this is because of the missing gateway file.

Actions #3

Updated by Jim Pingle almost 2 years ago

  • Status changed from New to Pull Request Review
  • Assignee set to Jim Pingle
  • Target version set to 2.7.0
  • Plus Target Version set to 22.09

I think I've spotted the problem here. In #6880 the scripts were changed around a bit and the withoutra path isn't getting the script header that should be setting the router file(s).

Try the attached patch and see if it helps for you.

Internal MR: https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/812

Actions #4

Updated by Jim Pingle almost 2 years ago

  • Tracker changed from Bug to Regression
  • Plus Target Version changed from 22.09 to 22.05
Actions #5

Updated by Jim Pingle almost 2 years ago

  • Status changed from Pull Request Review to Feedback
  • % Done changed from 0 to 100
Actions #6

Updated by Jim Pingle almost 2 years ago

  • Release Notes changed from Default to Force Exclusion
Actions #7

Updated by Daryl Morse almost 2 years ago

Jim Pingle wrote in #note-3:

I think I've spotted the problem here. In #6880 the scripts were changed around a bit and the withoutra path isn't getting the script header that should be setting the router file(s).

Try the attached patch and see if it helps for you.

Internal MR: https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/812

Thank you for taking a look at this problem. I applied the patch. It fixed the problem of dpinger not starting, but dhcpv6 is still not starting up properly. Let me know if you need any info or log files from my systems.

Actions #8

Updated by Jim Pingle almost 2 years ago

  • Subject changed from WAN_DHCP6 Stuck Pending / Unknown and DHCPv6 Not Working to WAN_DHCP6 gateway stuck pending with "Do not wait for RA" set

The dhcpd problem appears to be a regression from #12527 and is unrelated to this.

Actions #9

Updated by Jim Pingle almost 2 years ago

I have picked this back into the 22.05 branch and it will be included in the release.

Actions #10

Updated by Jim Pingle almost 2 years ago

  • Status changed from Feedback to Resolved

Works on latest internal test snapshot.

Actions

Also available in: Atom PDF