Messages

Ok so the core patch did not apply for one reason or another... I made a backport and edited the original post.

Thanks for testing so far.


Cheers,
Franco

Which one should we use?

opnsense-patch 1dba25fed8

OR

opnsense-revert opnsense os-zerotier && opnsense-patch dfd9f1766d && opnsense-patch -c plugins 4f9e03089

Weird stuff here, I've been replicating this problem on physical and virtual appliances as nothing is making sense. I'm testing multi wan, and I noticed if I go to gateway, disable one of them and apply, my trace routes still go through the disabled gateway. If I wait for the state to drop, or kill all the states, then it starts following the new route ignoring the disabled gateway.

The reason I got here is because when using gateway groups and one of the WAN fails, it does not kill the states and keeps trying to send traffic via the failed gateway. When I reset the states, then things work as they should.

Is anyone aware of this? Seems to be a bug to me, it should reset the states when one of the WAN fails.

I'm trying to set up additional local Wireguard servers with different configuration to serve different purpose and use separated interfaces. So far, it doesn't matter what I do, the additional servers can never do handshake with the clients.

I'm pretty sure I've done everything exactly the same as I did for the primary server and the clients, so I'm trying to figure out how am I being so stupid that I cannot make the additional servers to work. If there something obvious besides wrong public keys that could be at play here?