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

Port forwarding - Wirewall rules, setup a web server

Scheduled Pinned Locked Moved NAT
8 Posts 4 Posters 5.8k 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
    jacobegan
    last edited by Dec 29, 2010, 4:15 PM

    OK here is my situation, I have a web server running on TCP 80 with an internal IP address of 10.0.11.1.  I am trying to allow the WAN address to connect to it.  Everything worked fine before I switched to pfsense (which is 1000x better than syswan). Below is how I setup the nat forward:
    http://egantechnologyservices.com/sup/1.bmp

    Also, below is the firewall rule it made:
    HTTP://egantechnologyservices.com/sup/2.bmp
    as well as http://egantechnologyservices.com/sup/3.bmp

    When I go into the firewall logs, I get this error:
    http://egantechnologyservices.com/sup/4.bmp

    But the page never comes up.

    Any suggestions?

    1 Reply Last reply Reply Quote 0
    • T
      tommyboy180
      last edited by Dec 29, 2010, 4:30 PM

      Your firewall rules are working but when your try to browse your own external address the NAT isn't reflected. You need to enable NAT reflection under the System -> Advanced tab.

      Please search the forums next time.

      -Tom Schaefer
      SuperMicro 1U 2X Intel pro/1000 Dual Core Intel 2.2 Ghz - 2 Gig RAM

      Please support pfBlocker | File Browser | Strikeback

      1 Reply Last reply Reply Quote 0
      • J
        jacobegan
        last edited by Dec 29, 2010, 4:32 PM

        I tried turning nat reflection on the last time and when I try to access the interface for the pfsense at 10.0.1.2 it always brings up my website.  So, no help.  I did however read that on the forum

        1 Reply Last reply Reply Quote 0
        • C
          Cry Havok
          last edited by Dec 29, 2010, 5:27 PM

          So change the management port for pfSense, something that you should also have found about when you searched ;)

          1 Reply Last reply Reply Quote 0
          • J
            jacobegan
            last edited by Dec 29, 2010, 5:37 PM

            That still didnt fix it.

            1 Reply Last reply Reply Quote 0
            • T
              thegambler
              last edited by Dec 30, 2010, 1:56 AM

              are you leaving the machine on the same ip address as the ip address you are looking to call?

              1 Reply Last reply Reply Quote 0
              • J
                jacobegan
                last edited by Dec 30, 2010, 1:58 AM

                no, the pfsense is on 10.0.1.2 and the web server is at 10.0.11.1
                If thats not what you are asking, let me know.

                1 Reply Last reply Reply Quote 0
                • T
                  thegambler
                  last edited by Jan 14, 2011, 4:57 AM

                  all ip addresses are static bound to all machines. and they run all the time. the 10 dot ip addresses work great all machines can talk to eachother from one lan to the other, active directory updates from one lan to the other, just cant figure out how to make the 2 boxes talk. but every thing seams to be working fine i just need to update everything twice in both boxes.

                  Thanks for the help

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post
                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                    [[user:consent.lead]]
                    [[user:consent.not_received]]