[SOLVED] DHCP6 Gateway is shown as disconnected in 24.7

[MenschAergereDichNicht]

Hi,

i just installed 24.7. It is a new build with a history of only two weeks.

So far the update process was very smooth and the important stuff (my work network) is working.

I see only one thing that seems to behave different to the previous version. On the WAN interface i configured IPv4 using a static IP and IPv6 using DHCPv6.
Both have a gateway that monitors the connection. With version 24.7 the gateway for the DHCPv6 configuration is shown disconnected in the Web-GUI. But if i ssh into the router and ping6 the monitor IP it works.

[MenschAergereDichNicht]

It seems to have something to do with the priorities of the gateways.
I made a mistake with the priority of the IPv4 gateway on the same interface. I used a differnt (lower) priority there. After adjusting the value to the same as the DHCPv6 gateway both gateways are shown as connected.

I still don't understand the root cause but at least my configuration is slightly more correct now.

[MenschAergereDichNicht]

After a failover to the secondary WAN which has no IPv6 and switching back to the primary WAN the DHCPv6 gateway is shown as disconnected again.
Somehow it looks like there is a status update missing.

[MenschAergereDichNicht]

It looks like the "Gateway Monitor" service for the DHCP6 gateway was not running. I missed it because the new dashboard does not show the services in the default configuration.
After a restart of the service the gateway is green again.

I am still not sure why the service was not running from the start. At least before the failover i see no reason because there should have been IPv6 connectivity.

[guest34985]

I have a similar problem and after reading your postings fiddled around with priority of IPv4 and IPv6 gateway. Result: both gateways came up (CF DNS servers as Monitor IPs, because Telekom does filter ICMP on the actual gateways). But after a reboot IPv6 gateway is offline again while IPv4 is up.

[guest34985]

Hm, I found something. In my case adding a monitoring IP for IPv6 does NOT lead to a route creation for that respective address through the IPV6 WAN interface while for IPv4 it does. In 1 out of 10 attempts a route was created and voila: the IPv6 gateway was online. After the reboot the route was missing so gw was offline again.

[franco]

FWIW, I agree that the services widget should be a dashboard default because otherwise this is harder to catch than necessary.


Cheers,
Franco

[MenschAergereDichNicht]

I just updated to version 24.7_5. Now the DHCP6 gateway monitor service is always off. I can't activate it anymore from the dashboard.

The systen general log shows the following entry:

"Warning   opnsense   /usr/local/sbin/pluginctl: The required GW_WAN1_DHCP6 IPv6 interface address could not be found, skipping."

[MenschAergereDichNicht]

After finishing the previous post the gateway monitor was working again. It looks like it just takes some time after a reboot to get active.

[guest34985]

Could you please check with a Monitor IP on the Internet (e.g. DNS Servers) and see if the respective Host Routes are put into the routing table for IPv4 and IPv6?

[MenschAergereDichNicht]

Well. The DHCP6 gateway has a internet monitor IP (2606:4700:4700::1111).
Currently it is working and the routing table contains the following:

ipv6   default   <IP6 of my fritzbox as gateway address>   UG   NaN   1500   igc3   WAN1
ipv6   2606:4700:4700::1111   <IP6 of my fritzbox as gateway address>   UGHS   NaN   1500   igc3   WAN1

The IPv4 route is also available.

I am a little bit hesitant to reboot the router at the moment. Therefore i can not check the table in case of a problem.

[guest34985]

I see. If that second IPv6 route is set automatically (incl. after a reboot) then it's fine. For me that did not work so far while IPv4 Host route was set up just fine.

[guest34985]

Well. The DHCP6 gateway has a internet monitor IP (2606:4700:4700::1111).
Currently it is working and the routing table contains the following:

ipv6   default   <IP6 of my fritzbox as gateway address>   UG   NaN   1500   igc3   WAN1
ipv6   2606:4700:4700::1111   <IP6 of my fritzbox as gateway address>   UGHS   NaN   1500   igc3   WAN1

I happen to also use CF DNS for IPv6 gateway check. I just tested after upgrading to version 24.7_5, and the error persists, so no Host Route to 2606:4700:4700::1111 is inserted into the routing table, so as a consequence the gw check fails. IPv4 is fine.

[MenschAergereDichNicht]

It looks like there is a behaviour change in regard to DHCPv6 handling with version 24.7 .
In my case it seems to be timing related (a few minutes after a reboot i can manually start the gateway monitor).
I don't exactly know the role of the "gateway monitor watcher" but if i go by the name the manual start should not be necessary.

Update: At least i *think* that it is timing related. I also edited the gateway configuration between several tries to start the gateway service (i tried to manually enter the gateway IP6 and than removed it again). I did not check if my editing somehow created the route. I guess i will see it on the next reboot... .

[guest34985]

It looks like there is a behaviour change in regard to DHCPv6 handling with version 24.7 .
In my case it seems to be timing related (a few minutes after a reboot i can manually start the gateway monitor).

I just noticed you have a point that I can confirm. I noticed that indeed the Gateway Monitor dpinger service for IPv6 was NOT running and I could start it manually after some time. As soon as I did that the IPv6 route was inserted into the routing table. So, my observation was rather a symptom and not the cause!