If you want to route your network traffic through a particular network interface, as opposed to letting your OS’s routing algorithms decide for you, you configure this via Tools->Options->Connection->Advanced Network Settings (under ‘bind to local IP or interface’). A typical scenario is when you have a VPN connection. A PPP based on might well be represented in your system by an interface named ‘ppp0’ and could therefore enter this here. A new option has been added to check that the interface is present when you start Vuze - a warning will be raised if it is not found. This can help diagnose problems that occur if the VPN isn’t connected:
If you want to ensure that traffic is only ever routed over that interface you would also select the option further down the page named ‘enforce IP bindings…’. There was previously a bug whereby if you selected this option but then failed to specify any interfaces to bind to Vuze would effectively fail to route the connections at all. It was not at all obvious why the connections were failing so the behavior has been changed to log a warning in this case and ignore the ‘enforce’ request. Feedback please if you think is is incorrect behavior!
The ability to explicitly test a SOCKS connection from the configuration screen has also been added:
and a few bugs fixed around error reporting and detection.
Another bug has been fixed regarding the right-click upload-speed menu in the status icon, this was sometimes missing.
This idea suggested access to the download link used to access a torrent is useful. Whilst this is not always knows (if you download a torrent file to your hard drive and then add it from there for example) where it is a new menu option gives you access (and a magnet link otherwise):