I have just found the time to start learning about our new firewall. As a test I have tried creating a policy for blocking bittorrent traffic, but it seems to have only limited effect. Transmission still happily downloads the torrent although I can see from the logs in the firewall that at least some of the traffic is being denied.
That should cover all of the various bittorrent apps like ares, kazaa, and even generic-p2p apps. Plus, if Palo Alto ever adds another bittorrent app in their app/content releases, the app will automatically be added to your policy.
I tried your suggestion on building the application filter, but unfortunately the result is much the same. It still can't identify all the bittorrent traffic. I think the traffic that is missed is classified as 'unknown-tcp' and 'incomplete'.
Now we are getting somewhere. If you are seeing insufficient-data in the log, that means the firewall did not collect enough packets to determine what the application was. For unknown-tcp, you might want to take a packet capture and submit that to Palo Alto Support. Maybe they need to adjust the decoder for bittorrent traffic.
It does same for me. AND I followed instruction for allow list and exclusions and still, ever time bittorrent is run it blocks it. So Malwarebytes technicians your telling me this Mawarebytes Premium service CANNOT tell the difference between a P2P program and a real virus!?!?!?!? That's immensly encouraging. That's hard to believe but rather than try to get it to work for the 50th time I'm just gonna uninstall it and quit my free premium trial 4 days early. What a hassle! Goodbye.
I would like to set up a file server that is searchable, preferable via the web. I'm wondering if it would be possible to achieve this using the bittorrent protocol and have a single client sharing every single torrent on the server. I guess I could use some available tracker solution for the webinterface or write one myself.
You could use oneswarm, that is designed for private data sharing using bittorrent like protocol. As I see it you could have at least one client set up to be the server which will always be available to hosts your family photos and whatnot.
I don't really know what the actual limits are to oneswarm but you can share whole directories in it. I do know bittorrent clients tend to become really sluggish if you have many torrents running at the same time.
One issue you're going to run into here is that you've only got a limited number of ports / sockets on a single IP address. If you're going to run a system where you have all your files shared via a bittorrent style protocol you're going to run out pretty quickly if you do anything that people are interested in. After you run into this problem, you'll have to start adding new IP addresses, and that'll get old pretty fast.
You'd be better off using one of the many free web apps out there that include a file upload module. Using bittorrent to share files amoung a few people sounds like a fantastic way to have all the difficulty of use that bittorrents bring with none of the benefits of massively distributed hosts and reduced bandwidth at any one point to make up for it.
Any idea how i could stop the notification completely. I have feeling bittorrent still trying to access my machine but how i will be able to remove this completely. The pop up message is really annoying.
Field name Description Type Versions bittorrent.azureus_msgAzureus MessageLabel1.0.0 to 4.2.0 bittorrent.bdictDictionaryLabel1.0.0 to 1.10.14 bittorrent.bdict.entryEntryLabel1.0.0 to 1.10.14 bittorrent.bintIntegerSigned integer (32 bits)1.0.0 to 1.10.14 bittorrent.blistListLabel1.0.0 to 1.10.14 bittorrent.bstrStringCharacter string1.0.0 to 1.10.14 bittorrent.bstr.lengthString LengthUnsigned integer (32 bits)1.0.0 to 1.10.14 bittorrent.continuous_dataExtended MessageByte sequence2.0.0 to 4.2.0 bittorrent.extendedExtended MessageByte sequence1.6.0 to 4.2.0 bittorrent.extended.idExtended Message IDUnsigned integer (8 bits)4.0.0 to 4.2.0 bittorrent.info_hashSHA1 Hash of info dictionaryByte sequence1.0.0 to 4.2.0 bittorrent.jpc.addrCache AddressCharacter string1.0.0 to 4.2.0 bittorrent.jpc.addr.lengthCache Address LengthUnsigned integer (32 bits)1.0.0 to 4.2.0 bittorrent.jpc.portPortUnsigned integer (32 bits)1.0.0 to 4.2.0 bittorrent.jpc.sessionSession IDUnsigned integer (32 bits)1.0.0 to 4.2.0 bittorrent.lengthField LengthUnsigned integer (32 bits)1.0.0 to 1.8.15 bittorrent.msgMessageLabel1.0.0 to 4.2.0 bittorrent.msg.aztypeMessage TypeCharacter string1.0.0 to 4.2.0 bittorrent.msg.bitfieldBitfield dataByte sequence1.0.0 to 4.2.0 bittorrent.msg.lengthMessage LengthUnsigned integer (32 bits)1.0.0 to 4.2.0 bittorrent.msg.prioMessage PriorityUnsigned integer (8 bits)1.0.0 to 4.2.0 bittorrent.msg.typeMessage TypeUnsigned integer (8 bits)1.0.0 to 4.2.0 bittorrent.msg.typelenMessage Type LengthUnsigned integer (32 bits)1.0.0 to 4.2.0 bittorrent.peer_idPeer IDByte sequence1.0.0 to 4.2.0 bittorrent.piece.beginBegin offset of pieceUnsigned integer (32 bits)1.0.0 to 4.2.0 bittorrent.piece.dataData in a pieceByte sequence1.0.0 to 4.2.0 bittorrent.piece.indexPiece indexUnsigned integer (32 bits)1.0.0 to 4.2.0 bittorrent.piece.lengthPiece LengthUnsigned integer (32 bits)1.0.0 to 4.2.0 bittorrent.portPortUnsigned integer (16 bits)1.6.0 to 4.2.0 bittorrent.protocol.nameProtocol NameCharacter string1.0.0 to 4.2.0 bittorrent.protocol.name.lengthProtocol Name LengthUnsigned integer (8 bits)1.0.0 to 4.2.0 bittorrent.reservedReserved Extension BytesByte sequence1.0.0 to 4.2.0 bittorrent.versionClient versionCharacter string2.0.0 to 4.2.0
df19127ead