DPINGER Error 65 After Upgrade, Both Gateways Show Offline

Started by House Of Cards, August 18, 2025, 04:50:14 AM

Previous topic - Next topic
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.

How is your WAN interface configured? Is it static or DHCP or PPPoE?
What is the interface IP?
What is the gateway IP?

It's configured via DHCP, and is from a cellular modem.

You cannot view this attachment.

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...

Looks like 1.1.1.1 is assigned as a gateway for some reason.

What shows System > Gateways overview?

Here you go.  1.1.1.1 has always been set as the Monitor address.

You cannot view this attachment.

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?

They seem to be there...  I've always had this set to automatic, and this is what is there...

You cannot view this attachment.

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.

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.

Today, for no reason what-so-ever the IPv4 gateway now shows no packet loss, but the IPv6 gateway is still offline.  I haven't changed the configuration, but it just recovered all on its own.  I have no idea...  Let's see if it holds up.


replace the monitor address with 192.168.12.1 and see what happens after you hit apply

also I've never seen two wan connections that say "active". only one

I don't recommend to monitor the local IP of the router. It doesn't give true information about internet accessibility.

August 27, 2025, 11:25:02 AM #13 Last Edit: August 27, 2025, 11:27:48 AM by DEC670airp414user
Quote from: viragomann on August 27, 2025, 11:17:37 AMI don't recommend to monitor the local IP of the router. It doesn't give true information about internet accessibility.
I was suggesting a basic troubleshooting step. the OP doesn't need to leave it.
a lot of gateway issues are resolved by opening the not working monitor,   and click save and it comes back online.
the 2 active messages are also not normal from my years of using opnsense

https://docs.opnsense.org/troubleshooting/network.html#errno

It didn't hold up.  WAN shows 100% loss for days now, having never recovered again.  I show DHCP6 online for the last week.