Text only | Text with Images

OPNsense Forum

English Forums => 25.7 Series => Topic started by: House Of Cards on August 18, 2025, 04:50:14 AM

Title: DPINGER Error 65 After Upgrade, Both Gateways Show Offline
Post by: House Of Cards on August 18, 2025, 04:50:14 AM
Immediately after the upgrade to 25.7, both of my gateways show "100% Loss" in the widget, and the log has numerous "Warning dpinger WAN_GW 1.1.1.1: sendto error: 65" messages.  I've tried rebooting the router, rebooting the modem, restarting services, etc...  In all different orders.  All I managed to do was get the initial IPv4 gateway showing 100% packet loss, to getting both the IPv4 and IPv6 gateways to show 100% loss.

I can browse, so the internet is working.  Been working for years, until the moment I upgraded.

Any ideas what could cause this?
Thanks.
Title: Re: DPINGER Error 65 After Upgrade, Both Gateways Show Offline
Post by: viragomann on August 18, 2025, 11:00:39 AM
How is your WAN interface configured? Is it static or DHCP or PPPoE?
What is the interface IP?
What is the gateway IP?
Title: Re: DPINGER Error 65 After Upgrade, Both Gateways Show Offline
Post by: House Of Cards on August 18, 2025, 07:59:25 PM
It's configured via DHCP, and is from a cellular modem.

Screenshot_20250818_135420.png

I can ping 1.1.1.1 from a PC on the network, and the firewall is processing rules and traffic.  Yet, the gateway monitor reports the network as offline with 100% loss.  There have been no configuration changes, just the upgrade.  Any specific configuration you need to know?

Thanks for the help...
Title: Re: DPINGER Error 65 After Upgrade, Both Gateways Show Offline
Post by: viragomann on August 18, 2025, 08:10:16 PM
Looks like 1.1.1.1 is assigned as a gateway for some reason.

What shows System > Gateways overview?
Title: Re: DPINGER Error 65 After Upgrade, Both Gateways Show Offline
Post by: House Of Cards on August 18, 2025, 08:18:08 PM
Here you go.  1.1.1.1 has always been set as the Monitor address.

Screenshot_20250818_141435.png
Title: Re: DPINGER Error 65 After Upgrade, Both Gateways Show Offline
Post by: viragomann on August 18, 2025, 08:39:41 PM
Well, I'd expect, that it would work with these settings. But the gateway is shown as offline, using 1.1.1.1 as monitoring IP.
You can ping 1.1.1.1 from inside your network, but obviously OPNsense can't.

This let me suspect, that outbound traffic on the WAN from OPNsense itself is not natted properly.
Are you missing the outbound NAT rule for the source range of 127.0.0.0/8?
Title: Re: DPINGER Error 65 After Upgrade, Both Gateways Show Offline
Post by: House Of Cards on August 18, 2025, 09:07:02 PM
They seem to be there...  I've always had this set to automatic, and this is what is there...

Screenshot_20250818_145941.png
Title: Re: DPINGER Error 65 After Upgrade, Both Gateways Show Offline
Post by: House Of Cards on August 18, 2025, 10:31:21 PM
Maybe some strange and obscure issue because of the Double NAT that cellular internet causes?  But it always worked until now, so I suspect something changed on the OPNSense side.
Title: Re: DPINGER Error 65 After Upgrade, Both Gateways Show Offline
Post by: Ikyo on August 19, 2025, 12:45:22 AM
I am thinking that something might have changed.  I have a similar setup with GFiber as my primary and Mobile Internet for my secondary.  The GW monitoring shows a lot of latency/packet loss on the Mobile Internet port.  When I go into the CLI on OPNSense and ping the monitoring IP, I don't see the same issues.

217 packets transmitted, 217 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 34.208/51.097/83.731/9.542 ms

I also know that it is using the Mobile Internet because when I ping the other monitoring IP (8.8.8.8) the latency is far less.  I am wondering if it might be something related to the multiple NAT.
Text only | Text with Images