Gateway status unknown ....

[bringha]

Hello all

After recent reboot, I enabled gateway monitoring of the ipv6 default gateway. I noticed that the gateway monitoring on the ipv6 side is shown with status 'pending' and later 'unknown'. Earlier posts did relate this to the apinger problem. my gateways.log holds a lot of messages like

Code: [Select]

Apr 19 13:07:49 OPNsense apinger: Starting Alarm Pinger, apinger(15864)
Apr 19 13:07:59 OPNsense apinger: Exiting on signal 15.
When I disable gateway monitoring on the IPv6 gateway then everything is displayed fine /ipv6 gateway has state online) ....

I am running opnsense behind a fritzbox with a 'read from interface' config ... I have a firewall rule in WAN allowing ICMPv6 traffic. Is there any other prerequisite to make ipv6 gateway monitoring work?

Thanks for your help

Br br

 

[franco]

Sometimes apinger can't timely extract the link info and just show pending or unknown forever. This can be solved with a restart from the services diagnostics page mostly. If not it fails to extract the IPv6 connection info for another reason, we need to find it.

If the monitoring is disabled, the link is assumed to be always healthy. Others scripts rely on this info so it looks weird but you would also expect everything to think the link is there.


Cheers,
Franco

[bringha]

Hi Franco,

thanks for your reply. I manually restarted apinger as recommended and - indeed - it now runs longer for only <5 secs... (now already more than 6 mins ...)

However still, when I activate the ipv6 gateway monitoring, I still get status 'unknown'. This should also not be surprising as there is no ipv6 gateway configured in /var/etc/apinger.conf

Although ipv6 is activated....

Under which circumstances this behavior happens?

Br br

[franco]

It must extract an IP address from the link. If the configuration is not yet completed, it never tries again. That's a very old issue that was added when apinger was adapted for *sense.

What is the IPv6 set to? SLAAC? DHCPv6?


Cheers,
Franco

[franco]

PS: gateway code received a number of cleanups with 17.1.5, maybe that slightly changes the picture?

[bringha]

Hi Franco

I am running already 17.1.5. There is no change in this behavior. Opnsense operates behind a fritzbox which is providing the ISP interface

WAN gets ipv6 via DHCPv6 Client; using IPv4 connection. It gets a /60 prefix hint from the fritzbox and sends prefix hint so that all other interfaces read from WAN with different prefix IDs each.

So consequently, ipv6 gateway is shown as 'dynamic'.

The WAN ipv6 address is a fe80:: one only

br br