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

    Snort blocking the *internal* IP when bittorrent is detected?

    Scheduled Pinned Locked Moved pfSense Packages
    3 Posts 2 Posters 2.0k 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.
    • U
      UBBERdave
      last edited by

      Hello,

      When using snort to detect bittorrent, the alert is generated, and an IP is blocked.

      However- the IP is always the INTERNAL ip (eg 192.168.3.10) of the machine running the BT client, meaning the machine in question is completely cut off from the outside for an hour.

      Other rules (eg porn filter etc) block the correct IP (the remote host).

      What's going on here? Is this fixable?

      Cheers,
      Dave

      1 Reply Last reply Reply Quote 0
      • M
        MainFrame
        last edited by

        Set your internal IP on the "white list", then it works.

        1 Reply Last reply Reply Quote 0
        • U
          UBBERdave
          last edited by

          Pretty sure it doesn't, even WITH the internal IP whitelisted… >_<

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