Messages

Over a year old this post, but i'm having the same issue. I even rolled back the version thinking it was a update.

It's weird as if i add a route (system, config, routes) for an ip address to route out via the wireguard tunnel, start pinging it and then up and down the tunnel. I can see the ping go from 5-8ms (tunnel is down) to 20-35ms (tunnel is up) but i get the same DIFFERENT ADDRESS from device on the LAN.

followed the same guide as person above but also crossed checked with https://gist.github.com/morningreis/eeda36e8bb07dcb750d77e9a744776e8

*** Now working for me
I changed the 10.2.0.2/32 that Proton and the guide said to use, to 10.2.0.2/24 and it's all working now... strangely

I getting something like this, if i tell unbound to go out on WAN2 it works, if i set it to WAN1 it looks like it sends in the logs but never gets a responce. If i quirey an internal name or override name it resolves fine. Looking at my nextdns logs the quiery never makes it to them.

If i select both WANs it takes ages to resolve (prob timing out on one interface then moving over)

this is since the update i did this morning.

My stupid fault, i had some wonky firewall rule that didn't get loaded till the reboot

So just to add, after checking all the things here i found that my mirror in the updates settings was set to a mirror that was removed at some point.
It took ages to do the update, and then always said there was no updates.
after i changed the mirror it seemed to rebuild and work as expected.

Seemed it was a one off.

Rather than change the gateway to get it working, today i tried disabling the interface on opnsense, then reenableing it. That has also worked.

Gonna try ticking the do not remove option in the interface as well, see if it's maybe removing a dead route or something that its then not readding....

So upgraded to 23.7.8_1 and the gateway doesn't need changing every time the interface comes up. Didn't see anything on the release notes (tho it was before my morning coffee)

So i'm on 27.7.8 and since i updated (i missed a few releases and jumped from 27.7.1 or 3) i have to go into firewall routes for my second LAN and change the gateway to get it to route traffic.

I have a work from home router which i turn off when i finish work at the end of the day, and then turn on again in the morning. With out fail it can't connect to the internet unless i go in to the opnsense firewall and change the gateway.

I have a group with my two WANs in it, but it doesn't matter what i set it to, wan group, either single wan, every morning it won't 'allow' traffic. I turned on logging on the rule i'm changing the gateway on but it doesn't seem to show any deny or block/drop

I'm kinda lost but did see a change to a gateway package between the releases....