2 WAN interfaces toubleshooting on Azure
-
Hello everyone,
I have deployed pfSense on Azure with two WAN interfaces and one LAN interface. The WAN interfaces are in the front subnet (172.20.2.0/24) and have separate public IP addresses, while the LAN interface is in the back subnet (172.20.3.0/24). I configured NAT from the first WAN interface to my web server at 172.20.3.5, and the connection using the public IP works well.
However, when attempting to set up NAT from the second WAN2 interface to my second web server, I encounter connectivity issues. I've observed incoming packets from users using tcpdump on the VM, as well as packet captures on pfSense (on both LAN and WAN2 interfaces, and also the WAN interface). I understand that this is related to asymmetric routing and the default gateway for WAN interfaces.
The default gateway for WAN interfaces is the same for connecting to the internet, which is the Azure default gateway on the subnet (first address on the subnet - 172.20.3.1). I haven't encountered this scenario before, and I lack experience with pfSense and the specific infrastructure in Azure.
I attempted to address the issue with some outbound rules, but I haven't achieved the expected results. I would be grateful for assistance with this problem, and I appreciate anyone willing to share their knowledge and experience.
Kindly share your thoughts.
Thanks -
@ddave421 said in 2 WAN interfaces toubleshooting on Azure:
I have deployed pfSense on Azure with two WAN interfaces and one LAN interface. The WAN interfaces are in the front subnet (172.20.2.0/24) and have separate public IP addresses
This makes no sense at all. Assign both IPs to a single interface instead.
-
@viragomann
Do you mean assign additional interface configuration on NIC:
🔒 Log in to view -
@ddave421
Yes, this one.
But this ist Just an additional IP on the NIC.