Deluged refuses to use correct interface

[xamindar]

I have two interfaces on my deluged server that both have internet access. Eth0
is the default route and main connection. Eth1 also goes out to internet and
it's the one I am trying to get deluged to use but it refuses.

eth0 ip is 172.16.0.3
eth1 ip is 192.168.1.253

deluged --help says:

Code: Select all

  -i IFACE, --interface=IFACE
                        Interface daemon will listen for bittorrent
                        connections on, this should be an IP address
  -u IFACE, --ui-interface=IFACE
                        Interface daemon will listen for UI connections on,
                        this should be an IP address

Ok, so I want it to use eth1 for downloading torrents and only eth0 for access
to the ui. Seems simple enough.
I run:

/usr/bin/deluged --do-not-daemonize -i 192.168.1.253 -u 172.16.0.3

and then I wait.....and no activity on the 192.168.1.253 interface while the
172.16.0.3 interface is as active as can be. Are these options just there to
piss people off? What am I doing wrong? Thanks for any help I'm pulling my hair out here.

[Cas]

What version of Deluge and what OS?

Does deluge work normally if you do not specify interface or disable lan interface?

The only suggestion I have is to try enabling logging as this can show up problems.

[loki]

My guess, and this is only a guess, the deluge process is only connecting to the first network it sees and it's therefore not working the way you want it to.