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

    80/tcp open http, 21

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 2 Posters 298 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
      samgoodboy
      last edited by

      Hi,
      We have blocked all the ports accept 5865 but when we do nmap below ports shows open and when we telnet from cmd it gives black page but no traffic monitor on the router or firewall.. What is the meaning of http?

      80/tcp open http?

      110/tcp open pop3?

      113/tcp closed ident

      143/tcp open imap?

      2000/tcp open cisco-sccp?

      5060/tcp open sip?

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Where are you testing from? What are you tested against? What firewall rules do you have in place?

        Initially it looks like you're hitting something other than pfSense. Like you have a 1:1 NAT rule in there maybe.

        Steve

        1 Reply Last reply Reply Quote 0
        • S
          samgoodboy
          last edited by

          We testing from laptop which is on other network.. Telent to oublic ip which is configured inside the firewall.. We dont see any traffic hitting firewall because is blocked at router end itself.. But when we telnet from windows machine it gives black screen and in namp report it shows open...

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            The public IP is assigned to a client inside the firewall? On an internal interface?

            Are you passing that traffic to it?

            If you have allow rules on WAN and enable logging on those rules you will see traffic passed in the firewall log.

            There is nothing in pfSense that ever listens on port 110 so either that traffic is being forwarded to something else or you are testing against something else accidentally.

            A diagram of how you're testing might help here.

            Steve

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