Hi!
My problem started after upgrading from 19.7.1 to 19.7.2.
I run multiple (4-6) load balanced OpenVPN Clients from my OpenSense to commercial VPN-Services,
all the VPN-Client have been set to use one of multiple WAN-IF as outgoing Interface.
All outgoing user traffic is set to use only gateway group with tunnel gateways.
As soon as i have any one client-tunnel established, all consecutive attempts to bring another OpenVPN Client up will fail.
I looks as if OpenSense is ignoring interface-selection in the configuration and is instead trying route through the already established client-tunnel over the active TUN-IF (OVPNC#) instead of WAN-IF.
Any one of my OpenVPN ClientConfigs will work as long as it is the first to activate.
On rare occasion i can get two of the Clients up if they are both activated in very rapid succession,
but that's not a very common occurrence (race condition!?).
I've since done a few attempts downgraded back to 19.7.1 everything works fine,and upgraded to 19.7.2 and then it breaks again.
MultiWAN and 4-6 VPN Clients with Load balancing for has been working well for me on prior 19.x.x versions, except having to fiddle a bit when 19.7 hit (the common problem with broken gateways).
Am i missing some new setting in 19.7.2? or is this a bug?
I haven't seen anyone else complain about this over the past few weeks,
Maybe this just an uncommon setup...
BR
Should be fixed in 19.7.3
I think it was https://github.com/opnsense/core/commit/ff8b53dc2d so it would patch using:
# opnsense-patch ff8b53dc2d
Needs a packet filter reload.
Cheers,
Franco
I didn't try the patch, but I did update to 19.7.3 and it's working better now.
Thanks!