Hi all,
Wondering if anyone has been successful in binding to a specific interface and using source based routing with ktorrent? I'm trying to get ktorrent to use my vpn link (swissvpn) but no luck.

I'm 92.7% sure I have the routing tables setup correctly - ping and traceroute using the source address work properly (anyone know any other apps that support binding to a specific interface I could test with?). When I look at the open ktorrent ports, however, it shows everything going over the ethernet, not ppp0.

Thanks!

ToadP wrote:Hi all,
Wondering if anyone has been successful in binding to a specific interface and using source based routing with ktorrent? I'm trying to get ktorrent to use my vpn link (swissvpn) but no luck.

I'm 92.7% sure I have the routing tables setup correctly - ping and traceroute using the source address work properly (anyone know any other apps that support binding to a specific interface I could test with?). When I look at the open ktorrent ports, however, it shows everything going over the ethernet, not ppp0.

Thanks!

I see the problem, it seems that when we bind at startup, the network interface to bind on, has not been set yet, resulting in binding on all interfaces.

This is now fixed in SVN

Thanks!

The incoming port is now binding on ppp0 but it looks like the tracker is still binding on all. I assume that why all the peers are connecting to the ethernet, not the ppp interface?

ToadP wrote:Thanks!

The incoming port is now binding on ppp0 but it looks like the tracker is still binding on all. I assume that why all the peers are connecting to the ethernet, not the ppp interface?

Tracker stuff is done using KIO, which is part of KDE, as far as I know, there is no way to specify the interface to use. I will see if I can find a way to do that.

You are however correct, trouble with this is that all incoming connections will use the address of the interface KIO used (if not behind a NAT of course).