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

    Ports 80 & 443 Open!

    Scheduled Pinned Locked Moved Firewalling
    8 Posts 6 Posters 8.2k 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.
    • S
      samline
      last edited by

      I did a port scan from: GRC Shields Up!, scanning: "COMMON PORTS"

      I am showing ports 80 & 443 open

      Is there any specific settings or services in PFsense I need to disable?

      Do I have to make custom firewall rules to block WAN traffic to ports 80 & 443 on my LAN & DMZ for these open ports to be closed?

      I am running SNORT, PFblocker, & Service Watchdog packages.

      Every time you use the Shields Up scan with SNORT running, you must clear the blocked GRC IP address in the SNORT logs after every scan. (in case anyone would like to duplicate the test).

      Thanks.

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

        What are your firewall rules on WAN?

        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
        • S
          samline
          last edited by

          @Derelict:

          What are your firewall rules on WAN?

          Third and fourth rules are an attempt to close 80 & 443 with a rule set. These did not work.

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

            See that last rule?  You're allowing traffic into your WAN from the internet for any traffic not explicitly blocked by the rules above.

            Those port 80/443 rules at the top block traffic only from WAN address to LAN address.  Which is pretty much impossible to be received in the WAN interface.

            I would change those to source any dest WAN address if you want an explicit block rule for them (unnecessary) and I would absolutely, positively disable that last rule unless you know exactly why you need it.

            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
            • K
              kejianshi
              last edited by

              Well…  At least it wasn't rule number one (-;

              1 Reply Last reply Reply Quote 0
              • johnpozJ
                johnpoz LAYER 8 Global Moderator
                last edited by

                Why would you create such a rule?  There would not be a reason to create such a rule??  What where you trying to accomplish with a any any on you wan?

                An intelligent man is sometimes forced to be drunk to spend time with his fools
                If you get confused: Listen to the Music Play
                Please don't Chat/PM me for help, unless mod related
                SG-4860 24.11 | Lab VMs 2.8, 24.11

                1 Reply Last reply Reply Quote 0
                • H
                  Harvy66
                  last edited by

                  I think he's also a bit confused on how WAN address and LAN address works. I assume he has the explicit blocks added because he thought they'd block port 80/443 for WAN to LAN.

                  WAN IP is the NIC IP address the WAN interface has, and LAN IP is the NIC IP that the LAN interface has, not the IPs of other devices on your LAN. As it stands, the only thing blocked is the WAN NIC from talking to the LAN NIC, but not the devices on either end.

                  If you're attempting to block 80/443 to your firewall from the Internet, do Source * and Dest WAN-IP. If you just want to block 80/443 from coming in to any IP, then just place a block on source and dest of * on your WAN interface.

                  Firewall rules only apply to new states, states are created at the time they are first seen, and states are first seen by the interface they first arrive on.

                  1 Reply Last reply Reply Quote 0
                  • C
                    cmb
                    last edited by

                    You never, ever want a pass rule like that on WAN where WAN is an Internet connection, delete it.

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