IPv6 Gateway - dpinger down

Started by shavenne, January 31, 2020, 04:14:56 PM

Previous topic - Next topic
January 31, 2020, 04:14:56 PM Last Edit: January 31, 2020, 04:16:34 PM by shavenne
Hi!

I have a problem with OPNsense on both versions 19.7 and 20.1.

I'm getting an IPv6 address (without prefix like intended) via DHCP6 or SLAAC on this device and it seems to work fine. But: The gateway monitor says it's down and dpinger for that gateway is also stopped. I can start it manually and it brings the status up to Online and it's pinging my set monitor ip .. but when I reboot it's stopped again and reporting offline. Am I doing something wrong or is it a bug?!

(Btw.: I have another setup with two available connections with IPv6. Is IPv6 Multi-WAN still not possible? It seems can't get both to work. Just one or the another. Regardless if I use SLAAC or DHCPv6.)

Best regards from Germany
Sven

February 01, 2020, 05:18:40 PM #1 Last Edit: February 01, 2020, 05:24:15 PM by p1n0ck10
i have the same issues. since they changed the monitorgateway to dpinger i have this problems only with the ipv6 gateway.

i tried to configure the priority from the both gateways to different values. standard priority is 254 on both and i used 1 for the ipv6 gateway and 2 for the ipv4 gateway. on opnsense 19.7.10 it runs good with reboots but now i upgraded to 20.1 and i have the same issues again.

- now i deleted both gateways
- configured on ipv6 gateway: uncheck disable gateway monitoring, set ipv6 monitor ip, set upstream gateway and set the priority to 1
- configured on ipv4 gateway: uncheck disable gateway monitoring, set ipv4 monitor ip, set upstream gateway and set the priority to 2
- apply settings
- reboot and it works again

i tested this with 2 reboots in half hour. i don't know if this works for you too?

February 03, 2020, 11:59:08 AM #3 Last Edit: February 03, 2020, 12:01:16 PM by shavenne
Doesn't seem to work for me.
Have set the priorities, rebooted, and it's reporting as Offline again and dpinger is stopped.  :'(
I may could do a script which forces dpinger to (re)start after a reboot but I kinda expect it to crash again after a reconnect!? Is it even crashing? I don't find anything in the logs if it even tries to start.

It's so annoying.. I want to switch from PfSense to OPNsense at work because PfSense has also a extremely annoying bug (doesn't always switch back the gateway from a failover which causes some services to be down here). Even though we aren't having a second connection with IPv6 yet it will always be annoying to login and see a big red Offline there. And no: Disable monitoring is not an option for me ;)

February 03, 2020, 07:27:27 PM #4 Last Edit: February 03, 2020, 07:45:09 PM by p1n0ck10
have you tried to change the intervall? Not set the same IP for different gateways? I found these articles in the forum:
https://forum.opnsense.org/index.php?topic=11430.0
https://forum.opnsense.org/index.php?topic=11448.0