03-09-2017 01:22 PM
03-09-2017 01:48 PM
yes
you'll need a rule where web-browsing is processed so when bittorrent sends out it's http connections it can get allowed as webbrowsing at first, but then blocked when the application morphs into bittorrent
03-11-2017 11:16 AM - edited 03-11-2017 11:21 AM
Hello All,
Does it mean that l need both applications "bittorrent" and "web-browsing" inside one rule with action deny? Will it match with my usual (normal) web-browsing traffic that will be denied as well?
03-13-2017 02:31 AM
no they don't need to be in the same rule, you just need web-browsing somewhere in the policy (preferably below the bit-torrent block rule)
it's because bit-torrent uses http to get to certain parts or as a file transfer method, but just like most web-based applications (facebook,...) it starts out as a normal web-browsing session that only becomes 'bad' after a few packets (once AppID sees torrenting)
once AppID recategorizes your app, a session that was first allowed for web-browsing on rule #2, will now go through another security policy check and hit rule #1 which blocks bit-torrent
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
