20.7.7 Upgrade Broke Gateway Status and looking to fix it

[cyrus104]

I just upgraded from 20.7.5 to 20.7.7 using the regular upgrade process, 20.7.5 was working perfect since installing it and survived several reboots. I made a backup configuration right before the upgrade.

After the upgrade I went from see the gateway status for my wan and multiple vpn clients but now only 1 of the vpns is showing an online status the other show offline (but are workign). I've included the syslog for when I try to reboot the dpingers that fail to start.

I have checked/deleted the /tmp/pppoe0*(WAN) files, same with ovpnc1*(EXPRESSVPN).

Code: [Select]

Dec 20 15:17:24 op opnsense-devel[81393]: /status_services.php: Choose to bind WAN on Array since we could not find a proper match.
Dec 20 15:17:24 op opnsense-devel[81393]: /status_services.php: The WAN IPv4 gateway address is invalid, skipping.
Dec 20 15:17:30 op opnsense-devel[81393]: /status_services.php: Choose to bind EXPRESSVPN_VPNV4 on Array since we could not find a proper match.
Dec 20 15:17:30 op opnsense-devel[81393]: /status_services.php: The EXPRESSVPN_VPNV4 IPv4 gateway address is invalid, skipping.

[mimugmail]

Are you on stable or devel?

[cyrus104]

I thought I was on stable but looks like I was/am on dev. I've changed it back and that removed a :devel package but otherwise no change.

I'm guessing I can't go back to stable, I'll need to wait for the next stable release.

[mimugmail]

opnsense-update -t opnsense

[cyrus104]

# opnsense-update -t opnsense
The package 'opnsense' is already installed.
Your system is up to date.

Version is OPNsense 20.7.7_1 right now and confirmed it was switched to stable.

[mimugmail]

And gateway status working again?

[cyrus104]

That's a negative, getting the same error in syslog.

[franco]

"Choose to bind" message only exists on the development version, not in 20.7.x.


Cheers,
Franco

[cyrus104]

Understood, I checked and made sure that the syslog is still printing out the error I have in code above.

Here is my version info from the dashboard:
OPNsense 20.7.7_1-amd64
FreeBSD 12.1-RELEASE-p11-HBSD
OpenSSL 1.1.1i 8 Dec 2020

Thank you for helping.

[XeroX]

I've the same issue. Gateway is always down, dpinger doesn't want to start.

OPNsense 21.1.a_272-amd64
FreeBSD 12.1-RELEASE-p11-HBSD
LibreSSL 3.1.5

[franco]

Wait for development package of 20.7.8. Use release track if required.


Cheers,
Franco

[alexdelprete]

I've the same issue. Gateway is always down, dpinger doesn't want to start.

OPNsense 21.1.a_272-amd64
FreeBSD 12.1-RELEASE-p11-HBSD
LibreSSL 3.1.5

I had the same issue, used those same versions as you, then switched to stable after readng this thread and the problem is solved for me. Was driving me crazy.

OPNsense 20.7.7_1-amd64
FreeBSD 12.1-RELEASE-p11-HBSD
LibreSSL 3.1.5

BTW: is there a way to change the gateway name? I receive the error "Changing name on a gateway is not allowed."

Thanks.

[mimugmail]

Not via UI, only remove and readd is possible

[alexdelprete]

Not via UI, only remove and readd is possible

I'll try exporting the configuration, modify gw name with the editor, restore it.