openvpn instances

[tbs]

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.

[viragomann]

You can specify a bind address in both, server and client.

However, remember that the clients outbound traffic obeys the OS routing table. If you want it to go out to another gateway, you have to redirect it with a policy-routing rule.

[tbs]

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.

[keeka]

I've bound (binded?) an openvpn server instance to 127.0.0.1 and port forwarded the relevant interface.

[tbs]

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

[viragomann]

Yes but I have 2 ppoe WANs with a non static IP (which I would like to use as WANs for client services).

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

[tbs]

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?

[tbs]

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?

[viragomann]

OPNsense provide automatically generated aliases for the interface addresses, which you can use for translation in an outbound NAT rule.

So "WAN1 address" (pppoe) should be the current pppoe IP at any time. As well "WAN2 address".