Messages

Hi again,
Ok I managed to make instances to work with a specific WAN in multiWAN. The best way is to use static routes for the VPN IP adress. It's working rock solid. Unfortunetly I wasn't able to get sensible results with vpn connection that is based over a domain name address (with IP that can change over time).I wasn't able to force a specific WAN using firewall rules.

You can configure outbound NAT rule to translate the source IP in either WAN address.

OK, but on those ppoe WANs the IPs are changing every 8/12 hours, it's somehow problematic to translate to an IP that is not valid at a given time or I'm getting something wrong?

OK, but on those ppoe WANs the IP changes every 8/12 hours... So it's quite problematic or I don't get it right?

I'd rather do it for client services. As some IPs on my subnets are using VPN connection to other remote networks.

Yes but I have 2 ppoe WANs with a non static IP (which I would like to use as WANs for client services). As is I can't bind addresses.

Hello everyone,
As legacy openvpn support will end with 26.1 version and openvpn instances will be the only way to connect to a server and to create a server, is there or more exactly will there be a way to choose the WAN in a multiwan for the openvpn client or sever. As for now it's only possible to my knowledge on the legacy mode.