OpenVPN - works for 1 WAN, issues with DUAL WAN
-
I have the exact same issue. Did you ever figure it out?
-
no solution, gave up, waiting for 2.1 to try again
is documentation outdated or is there something inherently wrong with a single openvpn server listening on all interfaces?
this suggests running 2 openvpn servers http://doc.pfsense.org/index.php/Multi-WAN_OpenVPN -
there is no reason why it wouldn't work … i currently have it working on multiple sites.
-
It seems it only works on whichever of the two WANs the 'default' gateway at the time as shows under diagnostic>routes
What can i do about this to be able to connect to either?
-
tried something random,
got non-default WAN2 working by switching OpenVPN to tcp mode,
am i really the only one to ever come across this?
tcp isn't ideal, is there a workaround to be able to use udp?@themisa:
It seems it only works on whichever of the two WANs the 'default' gateway at the time as shows under diagnostic>routes
What can i do about this to be able to connect to either?
-
Since you mention a different behavior between TCP and UDP, have you by any chance enabled NAT reflection for port forwards ? (under System -> Advanced -> Firewall & NAT)
-
No, it's disabled (default)
ok. this http://forum.pfsense.org/index.php/topic,8297.msg46717.html seems identical,
i tried this as per their suggestion, didn't help.
pf wiki http://doc.pfsense.org/index.php/Multi-WAN_OpenVPN
mentions 'udp caveats' at the top, and it suggests running 2 vpn server which i triedto recap:
single openvpn server with 'any' for interface and 'tcp' allows me to connect from either WAN,
'udp' only works on 'default gateway' which is the problem -
Well, then perhaps heper could share the way he configured it.
-
Hi all,
I used the links from themisa to help configure multi-wan OpenVPN for a non pf-sense router, but what was missing is that in addition to adding a 'local $IP' line to the duplicated config, you need to change the subnet for for VPN connections, having the DHCP address pools separated, but on the same subnet was not sufficient.
Hope that helps.
-
@themisa:
No, it's disabled (default)
ok. this http://forum.pfsense.org/index.php/topic,8297.msg46717.html seems identical,
i tried this as per their suggestion, didn't help.pf wiki http://doc.pfsense.org/index.php/Multi-WAN_OpenVPN
mentions 'udp caveats' at the top, and it suggests running 2 vpn server which i triedto recap:
single openvpn server with 'any' for interface and 'tcp' allows me to connect from either WAN,
'udp' only works on 'default gateway' which is the problemadd to advanced options of openvpn client:
local 127.0.0.1;lport 0
Set "Interface" to any real interface, but NOT "any" (otherwise OpenVPN will not start).
In Gateway groups add group what suits your need (WAN as Tier 1, Second WAN as Tier 2 in your case);
in Rules add floating rule with following settings:
Quick: Enabled
Interface: select both WAN interfaces
direction: out
Proto: TCP/UDP or plain TCP
Source: Any
Destination: IP of OpenVPN server to whom you connecting
Dest port range: add your ports
Gateway: Choose previously created Gateway group.Should work (although without failback)
-
I have same issue.
On my OVPN server, i can have either of the vpn connections up if the other one is down. The log produces this:Oct 5 14:42:24 php: /status_interfaces.php: Starting 3gstats.php on device '' for interface 'wan'
Oct 5 14:42:29 check_reload_status: Reloading filter
Oct 5 14:42:32 php: : Gateways status could not be determined, considering all as up/active.
Oct 5 14:42:34 php: : Resyncing OpenVPN instances for interface WAN.
Oct 5 14:42:34 kernel: ovpns1: link state changed to UP
Oct 5 14:42:34 kernel: ifa_add_loopback_route: insertion failed
Oct 5 14:42:34 kernel: ovpns1: link state changed to DOWNIf ovpns1 is up then the log changes to ovpns2: if_add_loopaback_route: insertion failed etc.