No, there’s no direct port blocking involved because P2P can work on all ports.
As such, the F5 BigIP identifies the packets themselves with the p2p protocol in them and blocks the packets themselves that are identified as P2P.
This way, the only torrent traffic that may get through is the kind running inside a VPN. Even then though, we can identify encrypted torrents by other means (Deep Flow Inspection, trace the VPN traffic or directly monitor the student machines that are owned by the university).
What do you mean by blocking “100% of all P2P traffic”?
100% of all P2P protocols, literally are blocked by our University F5 BigIP by rule.
All of them (including certain Lemmy features).
https://en.m.wikipedia.org/wiki/List_of_P2P_protocols
When your IT has a small budget, you do what you need to do in order to mitigate the actions of the few.
Sorry I still don’t understand. Did you just block typical ports?
No, there’s no direct port blocking involved because P2P can work on all ports.
As such, the F5 BigIP identifies the packets themselves with the p2p protocol in them and blocks the packets themselves that are identified as P2P.
This way, the only torrent traffic that may get through is the kind running inside a VPN. Even then though, we can identify encrypted torrents by other means (Deep Flow Inspection, trace the VPN traffic or directly monitor the student machines that are owned by the university).