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

    Bittorrent (p2p) blocking or limiting pfsense

    Scheduled Pinned Locked Moved Firewalling
    5 Posts 4 Posters 10.7k 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.
    • X
      xcore2soul
      last edited by

      how can i block or limit the bittorrent (p2p) on pfsense???

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

        Naive torrent clients just use the standard ports, but most modern torrent clients use a mixture of TCP and UDP with random ports and all encrypted. Blocking torrent is futile.

        The only way to mostly stop torrent is to block all traffic and force everything through a proxy. Technically, someone could tunnel torrent traffic through a proxy. It wouldn't very fast for them, but it would work.

        The lowest hanging fruit is to block incoming ports, don't allow port forwarding, and white-list what destination ports can be used. 80, 443, 8080, and other standard ones.

        1 Reply Last reply Reply Quote 0
        • N
          nfr
          last edited by

          You can use Snort to block P2P using the emerging threat P2P category. Just set it up on the LAN or other internal interfaces so you can identify the computer being blocked.

          Warning: setting up snort is a time consuming process that also uses RAM and CPU.

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

            Snort can catch the low hanging fruit, but it cannot detect trackerless, DHT, or the actual transfers if encryption is enabled in BitTorrent. The BT protocol was semi-recently designed to be nearly impossible to detect other than by its bandwidth usage.

            1 Reply Last reply Reply Quote 0
            • A
              almabes
              last edited by

              You can also detect it by the states the protocol consumes in the firewall.  The protocol will use upwards of 10k states.

              I had to do this at a customer site.  I ended up just blocking the IP of the PC entirely in the firewall, reporting it to the owner, and removing the software.  The offender was fired.

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