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

    NAT issues port fowarding

    2.1 Snapshot Feedback and Problems - RETIRED
    3
    3
    1187
    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.
    • D
      Duglz
      last edited by

      I recently dove into pfsense and after installing 2.0.3 and realizing that it did not support my nic drivers I moved over to 2.1.

      Everything has been perfect up until I'm having issues with port forwarding. I can not get anything to forward to my internal network. Below is my current setup.

      MODEM (DHCP) –--> WAN NIC (PFSENSE) -----> LAN NIC (PFSENSE) -----> SWITCH -----> PCs

      http://imgur.com/a/XXefv

      I can connect straight to it if I get rid of PFSENSE from the same box.

      Here are some packet snaps that I have done as well.

      On the LAN interface. (it's timing out connecting to my ip)
      00:41:45.249897 IP 192.168.1.100.49293 > XXXXXXXXXX.25565: tcp 0
      00:41:48.249879 IP 192.168.1.100.49293 > XXXXXXXXXX.25565: tcp 0

      Connecting in with the above rules on the WAN interface shows nothing.

      Port Test Results:
      Connection to 192.168.1.103 25565 port [tcp/*] succeeded!

      1 Reply Last reply Reply Quote 0
      • AhnHELA
        AhnHEL
        last edited by

        You're trying to access your server from within your own LAN, judging by the 192.168.1.100 connection to your server @ 192.168.1.103.

        In the GUI, go to System/Advanced/Firewall-NAT/

        and enable NAT Reflection mode for port forwards.

        pfSense Docs

        AhnHEL (Angel)

        1 Reply Last reply Reply Quote 0
        • W
          wallabybob
          last edited by

          @Duglz:

          I can not get anything to forward to my internal network. Below is my current setup.

          It is often necessary to reset firewall states after "major" rule changes. See Diagnostics -> States, click on Reset States tab, read and click on Reset button.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post