Option to limit transmission based upon connected network
Option to limit transmission based upon connected network
This would be similar to the scheduled speed limit option. It should allow transmission to pause/restart, or limit speeds based upon the network the computer is connected to. This would especially be useful on laptops which can frequently change networks during the day as it is moved around. It find it embarrassing to find out that transmission is still running or has restarted when I am at a client's office. I imagine most users would only want to run it when on their home network.
Re: Option to limit transmission based upon connected network
I second that kind of feature. ATM I'm stuck with Vuze, as it got the option to bind the client's transfer to a certain network interface (en0, en0[1], 192.168.2.54 or a hostname are formats accepted). Combined with the option, that only the specified interface should be used (even when offline) I can be sure, that no traffic goes in or out on other networks. That comes in handy, as I use two network interfaces on my laptop regularly, on with no transfer limit and no TOS prohibiting filesharing (home network with WLAN) and another with a traffic cap and TOS prohibiting filesharing/high-bandwith usage (UMTS modem). Other than that, I'm really tempted to switch from Vuze to Transmission.
More generaly spoken, I'm rather surprised that only a few torrent clients implemented that as of now, given that nearly all network related software offers the user to select the IP adress/network interface and port (which torrent clients do) were the service should be made available (f.e. only on my desktop machine SMTP, FTP server, Squid, Privoxy, sshd, etc.).
Edit: After some snooping around the interwebs, I found the "bind-address-ipv4" key in settings.json seems to be what I was looking for. But it isn't mentioned in the configuration parameters list. I installed the Mac client and checked the corresponding plist files, but there seems to be no similar option available; neither is a corresponding option available in the GUI settings. Any chance this functionality could make it to the Mac client (if it isn't there as of now, albeit undocumented)? Does the "bind-address-ipv4" key take only IPV4 addresses as values, or are hostnames or interface device names like en0 valid too? And what is the behaviour, if the selected interface goes down, do all transfers stall or is another interface used as fallback?
Edit2: Apparently the "bind-address-ipv4" key doesn't seem to be recognized when put in the .plist file. I tested using the IP address of the interface, the associated name (via. /etc/hosts) or the interface name (en2) as values, but in the log Transmission notes that the listening socket is bound to 0.0.0.0 (or ::, in case of IPv6) on the specified port anyway. So I pledge for implementing that feature on OSX, and, if possible, either dynamic updates in runtime (like rtorrent), or a behaviour similar to Vuze (denying any traffic if the interface is down). Tested using 1.9.1 on OSX 10.5
More generaly spoken, I'm rather surprised that only a few torrent clients implemented that as of now, given that nearly all network related software offers the user to select the IP adress/network interface and port (which torrent clients do) were the service should be made available (f.e. only on my desktop machine SMTP, FTP server, Squid, Privoxy, sshd, etc.).
Edit: After some snooping around the interwebs, I found the "bind-address-ipv4" key in settings.json seems to be what I was looking for. But it isn't mentioned in the configuration parameters list. I installed the Mac client and checked the corresponding plist files, but there seems to be no similar option available; neither is a corresponding option available in the GUI settings. Any chance this functionality could make it to the Mac client (if it isn't there as of now, albeit undocumented)? Does the "bind-address-ipv4" key take only IPV4 addresses as values, or are hostnames or interface device names like en0 valid too? And what is the behaviour, if the selected interface goes down, do all transfers stall or is another interface used as fallback?
Edit2: Apparently the "bind-address-ipv4" key doesn't seem to be recognized when put in the .plist file. I tested using the IP address of the interface, the associated name (via. /etc/hosts) or the interface name (en2) as values, but in the log Transmission notes that the listening socket is bound to 0.0.0.0 (or ::, in case of IPv6) on the specified port anyway. So I pledge for implementing that feature on OSX, and, if possible, either dynamic updates in runtime (like rtorrent), or a behaviour similar to Vuze (denying any traffic if the interface is down). Tested using 1.9.1 on OSX 10.5