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

    Nat/Firewall | Just don't get it

    Firewalling
    2
    2
    498
    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.
    • P
      ParDonny
      last edited by

      Hi guys,

      this seems like something that should be realy easy but I just dont get it. Is there something that I'm missing. Trying to open up port 80 on pfsense and forward it to my apache proxy server. I only have a WAN network on my Pfsense. Still using my ISP router and setup the Pfsense as a DMZ host so all ports are forwarded to Pfsense. Pfsense tells me "all good" after adding the NAT rule + Firewall rule, however, mxtoolbox says port is closed.
      Also the proxy should not be the problem. I can use it internally ( using my own bind DNS, setup internal FQDN's, that works).

      • NAT Rule: http://imgur.com/D5uNjbf
      • Associated Firewall rule created from within the NAT creation: http://imgur.com/oNyflv5
      • MXtoolbox portscan says no: http://imgur.com/wRoB0rF
      • However, firewall logs says YEEY!: http://imgur.com/DU9QTqa

      Website not reachable. What am I missing.

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        All looks fine. Local firewall or other ACLs on the target web server maybe?

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

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