Originally Posted by
rvt
For the general gist of it though, you would add in a network tag (just like the source tag) in the info part of the torrent during upload, with a value of PIPE or WAIX. That gives each torrent a seperate hash while having the same files, so you can have them all on the same tracker.
Then you need to store a field in the DB so you can tell if it's limited to a certain network when you pull the torrent details for announce.
If it is, you check the users IP against the IP list for that network. No match means no download.
Finally, someone on the network will need to download the non-network torrent to get the files, then seed the files with the network torrent, or the initial seeder should run all 3 at once. If you want to do it with the initial seeder, you'll need to allow them to bypass the IP check. Just check if their user ID is the torrent owner for that.
Bookmarks