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

    Internset Service Database in pfSense

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

      Hi there,

      dont know if this is the right place or someone got an answer to that but is there a similiar database for the Internet Service identification as in fortigate / fortinet? It would be really nice if there would be such list to maybe allow / traffic shape this traffic accordingly to there service identification instead of ports and manual handling.

      Just a thought maybe someone already pointed that out or gave that as an Feature Request, didnt find anything so far.

      Kind regards,

      G GertjanG 2 Replies Last reply Reply Quote 0
      • G
        Gblenn @sysadminfromhell
        last edited by

        @sysadminfromhell Are you thinking about something similar to Snort App ID perhaps? Can't find it now, but I think I have seen a long thread about that in the IDS/IPS section.

        1 Reply Last reply Reply Quote 0
        • GertjanG
          Gertjan @sysadminfromhell
          last edited by

          @sysadminfromhell

          pfSense is the router firewall from heaven.
          Nothing is limited or forbidden by default.
          If there is a limit, it's the admin .. ;)


          More serious : I think I understand what you mean. No such thing exist. but there is this : Firewall > Traffic Shaper > Wizards.
          In the good old days, a 'router' could look into the data part of an Ethernet packet and see what a user (device) was doing, and make decisions based on what it found.
          These days, all the router sees :
          Source and destination IP.
          Source and destination port.
          A sequence number.
          A time stamp.
          The size of the payload and packet.
          A couple of flags.
          And the payload itself.

          And forget about the payload, it's encrypted with some TLS (that what we wanted, right ;)).
          All the other info : pretty random actually.
          So, how to draw useful info from noise ?

          No "help me" PM's please. Use the forum, the community will thank you.
          Edit : and where are the logs ??

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

            Some services are pre-defined in the shaper wizard but it's by no means definitive.

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