WireGuard - Error from unconfigured IP range.

Started by lagus, Today at 09:59:40 AM

Previous topic - Next topic
Today at 09:59:40 AM Last Edit: Today at 10:01:19 AM by lagus
Hey, is this a bug in the operating system or some hidden config not even the config file is aware of?

This is an old system that has this trouble is upgraded over and over again since from the 19.x releases I think. And during the years I have had both IPsec and OpenVPN but only got S2S VPN to reliably to work with Wireguard much because of this OpnSense routers main connection is a 4G with _very_ dynamic public IP. Both other Peers are Mikrotik routers

Now I'm trying to reconfigure WG a little bit to partly change the external port and bring in another peer in to the same network. Unfortunately something skewed a working setup sometime between me adjusting the external port and adding the new peer.

It seems like my routes from WG peers disappeared and static routes (that were working before?) does not apply. Below is all I can see in the logs.

Note: in my attempts to troubleshoot, I have made 'grep' commands on the config file and the whole filesystem. The only place this range shows up in is within old backup files! - Where else is is hidden? It's like it's magically just appearing to mess things up.


Version: OPNsense 25.7.3_7-amd64
HW: Netgate SG-4860
vmware Virtual Env & Netgate SG-4860