Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Am I missing an outbound NAT rule?

    Scheduled Pinned Locked Moved HA/CARP/VIPs
    2 Posts 1 Posters 1.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      jeff
      last edited by

      In my testing configuration, LAN is 192.168.11.0/24, and WAN is 192.168.0.0/24. See the attached pictures for configuration details. Basically, I want to be able to forward from 192.168.0.202:80 (a CARP IP address) to 192.168.11.4:80. The web server is definitely running, because it serves pages on its 192.168.11.4 address. Its firewall is set to allow all traffic. For instance, I can telnet from pfsense to 192.168.11.4:80.

      On the web server, I can run tcpdump -i any -w 80.pcap 'tcp port 80', which yields 2 incoming "HTTP [SYN]" packets, and no outbound traffic. This is also exactly the traffic the MASTER pfsense router sees. The slave sees no port 80 traffic, as you would expect.
      ![firewall forwarding.png](/public/imported_attachments/1/firewall forwarding.png)
      ![firewall forwarding.png_thumb](/public/imported_attachments/1/firewall forwarding.png_thumb)
      ![firewall outbound.png](/public/imported_attachments/1/firewall outbound.png)
      ![firewall outbound.png_thumb](/public/imported_attachments/1/firewall outbound.png_thumb)
      ![firewall rules.png](/public/imported_attachments/1/firewall rules.png)
      ![firewall rules.png_thumb](/public/imported_attachments/1/firewall rules.png_thumb)
      ![firewall virtual ip.png](/public/imported_attachments/1/firewall virtual ip.png)
      ![firewall virtual ip.png_thumb](/public/imported_attachments/1/firewall virtual ip.png_thumb)
      routes.png
      routes.png_thumb
      ![web server packet capture.png](/public/imported_attachments/1/web server packet capture.png)
      ![web server packet capture.png_thumb](/public/imported_attachments/1/web server packet capture.png_thumb)
      ![carp status.png](/public/imported_attachments/1/carp status.png)
      ![carp status.png_thumb](/public/imported_attachments/1/carp status.png_thumb)

      1 Reply Last reply Reply Quote 0
      • J
        jeff
        last edited by

        This turned out to be a problem due to the web server having an interface on the 192.168.0.0/24 network. Taking that interface down allowed packets to flow freely, how they were meant to.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.