It depends on how your network is laid out and where the bottlenecks are, but yes, it can be faster to use BitTorrent. In theory, instead of sending out 7 copies of the same files, your source server should only need to send out 1 copy, split among the receivers. By the time that happens, … Read more
In theory it is possible but why would you want to? If you are only going to have a few people looking at it, then you loose the benefits of distributed bandwidth.
If each apartment has its own port on a managed switch somewhere in the building, seeing their traffic levels should be pretty simple with something like MRTG. However, this seems like more of a legal issue than a technical issue. IANAL, but by trying to police the connection the owner is essentially giving up any … Read more
Not knowing what exactly your problem is, I can recommend pscp from parallel-ssh as a tool to upload small files to multiple servers. You prepare a list of servers to upload to and let it know what to take locally and where to put it remotely. For example: $ pscp -h list-of-servers file.torrent /tmp/ [1] … Read more
Same issue here. I am using mod_security to block the user-agent SecRule REQUEST_HEADERS:User-Agent “Bittorrent” “id:10000002,rev:1,severity:2,log,msg:’Bittorrent Hit Detected'” I would change the log to nolog after you verify it is working to avoid filling up your log file SecRule REQUEST_HEADERS:User-Agent “Bittorrent” “id:10000002,rev:1,severity:2,nolog,msg:’Bittorrent Hit Detected'”
A BitTorrent magnet link identifies a torrent using1 a SHA-1 or truncated SHA-256 hash value known as the “infohash”. This is the same value that peers (clients) use to identify torrents when communicating with trackers or other peers. A traditional .torrent file contains a data structure with two top-level keys: announce, identifying the tracker(s) to … Read more
You really do want a Multicast File Transfer Program: UFTP, with decent documentation and proxt-style extensions for NAT/router traversal too.