pfSense 2.5.1 multi-WAN routing trouble
-
@jegr Hi! I put some time apart to setup pfSense 2.5.2 BETA on my homelab in a VM. I can confirm that Multi-WAN with OpenVPN port forwarding is working!
So this is great news and I hope we can see more and more bugs fixed in upcoming snapshots. I have a couple of remarks about things not working but I will post them in the development forum. I am glad to help :)
-
Hi All.
Sorry for my English. It's not my native language.
I'm passing with the same problem using OpenVPN and Multi Wan using the same server port on TCP connection for any interface.
I did a work around that have worked to me.
Follow what I did:
-
I've created a new server entry using UDP4 using the same cert, only changing Tunnel Network.
-
On this new connection, I've set a Carp IP of whe Second Wan interface.
This is my new setup:
- On service 1, I have a TCP listening on 2301 port with "Any" Interface.
- On service 2, I have a UDP port 2302 with CARP "WAN2" Interface.
On the OpenVPN client, I've setup two ovpn files, one pointing to service 1 and other pointing to service 2 and my office users choose which they want to use.
I'm anxious to update my pfsense box to 2.5.2 ASAP. While Netgate doesn't release this version, I hope this work around works to you.
-
-
Hi folks,
I came across a very similar problem with a Netgate pfSense running version 21.05.01 and a Multi WAN setup [DSL as WAN1 (Tier1) and 4G router on Opt1 as WAN2 (Tier2)] using gateway groups for automatic failover.
- Server side: CentOS7 with OpenVPN 2.4.11-1.el7
- Client side: pfSense BSD with OpenVPN 2.5.2
The situation was as follows:
- OpenVPN site-to-site connection was successfully established between server (CentOS) and client (pfSense)
- ping FROM server TO pfsense worked fine
- Once traffic was sent from pfsense to the server VPN, the connection immediately dropped, 100% reproducible
I played around with different compression settings and stuff but nothing really helped.
However, the final solution to reconfigure the OpenVPN from TCP to UDP.
Hope that helps someone in the future. :)