#Biglybt optimization update#
#Biglybt optimization manual#
#Biglybt optimization Pc#
#Biglybt optimization torrent#

PeerB is on a 'foreign' network (IP address not included in btpolicy.xml) PeerA is on the 'local network' according to btpolicy.xml There's an obscure uTorrent/BitTorrent option called 'isp.peer_policy_url' (or dubbed by the file name 'btpolicy.xml'): it is a list of IPs that will be preferred for transfer. My last addition was only tangential to your problem.

You do have a Raspberry Pi already, make use of it to act as an open local retracker for 'retracker.local' And yes, thats a very rare my primary advice was to use a local tracker. But even for testing purpose for my lan issue, they lack the needed features or have to less information for specific options. I want to mention, that i tested other Bittorrent clients like tixati, deluge and qbittorrent too. The developer made this possible by adding some options for the networkinterface binding. i can even inject the qbittorrent client running on the raspberry pi with.

#Biglybt optimization manual#

Manual inject peer with port will start immidiatly the transfer over LAN with 100mbit (laptop via wlan). Both also see eachother when the other device is closing the program or reboot ect (i mean the biglybt plugin peer lan finder can see it and is also injecting the peers ect).

They are online over VPN with different countries. I can print with the wlan printer and transfer stuff over lan with all 6 devices. At this point, i think, the last step is on my system/network configuration. Technically its working after i got in touch with the developer of biglybt.

#Biglybt optimization update#

Update until i try it again with new ideas.Īt the moment, iam stuck with the configuration for automtic using the lan peer finder.

#Biglybt optimization torrent#

My point on this is, that i dont have to copy the files myself and to waste the uplaod from other people to get the torrent ready on both my systems without the fullspeed over lan.

#Biglybt optimization Pc#

I make a backup now and i will try to get the pc and the laptop connected via peer finder (local peer exchange) with the Pi.

I have a raspberry pi with qbittorrent without vpn in the normal lan which can maybe work as a bridge. my next guess why they cant find eachother over lan is, that bigly isnt allowed to use the normal connection because of the bind to the vpn net option? so bigly cant see my local network? is my assumption correct? I forwarded the port for local peer finder in airvpn too (dont know if its needed or if both systems need a seperate port, but its impossible to use another in bigly for the second system.) But i think thats not needed anyway, because i want to use my lan at home and not the lan in the datacenter (which is blocked anyway?). In eddie the options 'allow lan& private' is active and i can see all systems in windows network, print and transfer files manually. Now my idea was to use local peer exchange to synchronisise the same torrents on both systems with their combined advantages over my lan. So they send their pieces which the other client didnt have (because of different peers or more time over night^^) to eachother over the internet connection and the limits. They can see each other like normal clients (iam using the friendfunction too). And of course it can use the slow uplaods from the few peers at night. I already have seen improvement, where my swedish connection (pc) is at a disadvantage over one from switzerland on the laptop and the other way around. In the client area from airvpn i have two 2 devices and iam on different servers. So i got eddie on my laptop and made a fresh biglybt installation with nearly the exact configuration. I dont let my pc on when iam not at home or at night. Now iam going a step further to optimize my very old torrents or torrents with very few peers. The complete torrent thing is running very good.