core: dhcpd6 doesn't start automatically when no IPv6 address is assigned to the WAN interface
Hi there! đ
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
- I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
- I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue
Describe the bug
While I imagine this is not unusual, my ISP - Orange France - doesnât support ia-na and only provides me with a PD (that I can flawlessly use with interface tracking for the LAN interface). Unsurprisingly, the WAN interface only gets a link-local IPv6 address but no globally routable one.
The problem is that the dhcpd6
service doesnât automatically start when no IPv6 address is assigned to the WAN interface, most likely due to this short circuit in rc.newwanipv6
:
⌠which seems to be confirmed by the logs:
/usr/local/etc/rc.newwanipv6: Failed to detect IP for WAN[wan]
One way to fix that would probably consist in assigning a global IPv6 address to the WAN interface using the PD sent by the ISP but I havenât been able to find a way to achieve that. Is that even possible?
As a workaround, I tweaked rc.newwanipv6
to always call plugins_configure('dhcp', false, array('inet6'))
before exiting. While it works fine (after all, dhcpd6
doesnât really care if the WAN interface doesnât have an address), it seems a bit gross đ
Am I overlooking something?
Thanks! đ¤
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 47 (29 by maintainers)
Commits related to this issue
- interfaces: DHCPv6 advanced has a different flag to disable NA #5332 — committed to opnsense/core by fichtner 2 years ago
- interfaces: proper logic in adv/custom/basic modes #5332 Clarify the logic: custom first (cannot enable tracking extension due to unknown contents -- could be scanned but not for today), advaned sett... — committed to opnsense/core by fichtner 2 years ago
- interfaces: DHCPv6 advanced has a different flag to disable NA #5332 (cherry picked from commit ca2f7b0ffa37e1cc2535bbf205e31f797cce35a8) (cherry picked from commit 7583ce52a93b519e364a279f2d9129d013... — committed to opnsense/core by fichtner 2 years ago
Quick info: this will be shipped in todayâs 22.1.7 đ
@kevinchalet @fichtner I just updated to 22.1.4 + checked âRequest IPv6 prefix onlyâ in the basic tab and yay, thanks! Just a quick heads up for anyone reading this thread in the future (and before new release with @fichtnerâs patches is published) : I had to 1/ switch to âbasicâ tab and enable checkbox 2/ save 3/ go to âadvancedâ 4/ save
Interesting. Iâm half way between two ISPs at present, my old static provider and my new FTTP provider, who I have to use dhcp/dhcpv6 with. Now, I do have the option to request an IA on the WAN as well as a PD, and I notices after a reboot that the dhcpdv6 needed to be started, I put that down to just momentary madness. Iâll try and confirm and see if it is because of no wan address, I donât think it is though.
@kevinchalet as promised https://github.com/sponsors/opnsense
I finally moved to 22.1.4 so here we go:
I think I understand the dilemma better now. Can somebody with the issue provide the following output on 22.1.4?
Thanks, Franco
Hi, Iâm also using Orange France as ISP, with IPv6 interface tracking and I had the same issue since a long time. Just to add, I upgraded to 22.1 (and now 22.1.4) and the issue is still present.