WAN interface - only connection from LAN

  • I have configured pfSense with 3 interfaces, 2 x WAN and 1 x LAN

    • connection from WAN 1 and WAN 2 to public IP works fine
    • connection from public IP to WAN 1 works fine
    • connection from public IP to WAN 2: no connection
    • connection from LAN to WAN 2: connecting to pfSense

    I'm totally confused, why no inbound traffic to WAN 2??

    What information should I post to troubleshoot the issue?

    Thanks in advance!

  • LAYER 8 Netgate

    What kind of inbound traffic?


  • Actually all inbound traffic.

    I created a port forwarding NAT rule from WAN 2 (port 443) to a server on the LAN, no reply.

    When I make WAN 2 the default gateway, www.ipchicken.com returns the IP of WAN 2 when checking from a host on the LAN.

  • LAYER 8 Netgate

    Inbound port forwards have (practically) nothing to do with the default gateway. reply-to is set on those states which automatically routes reply traffic out the interface the connection arrived into.

  • The concept is quite simple. I would like to route the traffic on port 443 / interface WAN 1 to LAN server 1; traffic on port 443 / interface WAN 2 to LAN server 2.

    Is this possible with pfSense?

    Attached I have some status information and diagnostics.

    ![Schermafbeelding 1.png](/public/imported_attachments/1/Schermafbeelding 1.png)
    ![Schermafbeelding 1.png_thumb](/public/imported_attachments/1/Schermafbeelding 1.png_thumb)
    ![Schermafbeelding 2.png](/public/imported_attachments/1/Schermafbeelding 2.png)
    ![Schermafbeelding 2.png_thumb](/public/imported_attachments/1/Schermafbeelding 2.png_thumb)
    ![Schermafbeelding 3.png](/public/imported_attachments/1/Schermafbeelding 3.png)
    ![Schermafbeelding 3.png_thumb](/public/imported_attachments/1/Schermafbeelding 3.png_thumb)
    ![Schermafbeelding 4.png](/public/imported_attachments/1/Schermafbeelding 4.png)
    ![Schermafbeelding 4.png_thumb](/public/imported_attachments/1/Schermafbeelding 4.png_thumb)

  • This issue is solved. The problem was in the virtual interface assigned by OpenStack

    I dropped the interface and added a new one. After configuration in pfSense the interface works fine.

Log in to reply