Messages

Calm down guys, Franco is already working on a patch :)

Thanks @Franco - installed on 6 firewalls with no issues

Hi,

Given that this issue will need to be addressed in OPNsense at some point, is there a plan to incorporate the relevant upstream patches? If so, is there any rough timeline or release target for when that might happen?

If not, what is the process for getting that agreed?

Thanks
Nick

Ah, okay... That works - thank you!

Btw, is there a reason that the UI doesn't list the WAN address as an option? Could this be considered as an addition?

I'm currently running WireGuard on a non-standard port, and it works fine under normal conditions. The issue arises when I'm on restrictive external networks where outbound traffic on that port is blocked, making the VPN unusable.

To improve reliability, I'd like WireGuard to listen on an additional port so there's a higher chance of the traffic being allowed through. I attempted to set this up using an inbound NAT rule, but the Redirect target IP field doesn't let me select the WAN address.

I also considered running a second WireGuard instance, but that introduces another interface and leads to routing conflicts.

Has anyone found a clean way to achieve this setup?

Thanks in advance!