Bind to IP addr inconsistent behaviour. How to force bind?

[XjR43]

My issue with deluged is occurring on both windows 7x64 and ubuntu 12.04. At the moment I can only test it in windows, but i recollect similar behaviour in the past on ubuntu. When I specify a listen IP address, whether in conf or as deluged --interface=192.168.192.33 or in the GUI, the bind will work. It however will not always be forced should that IP address go away. Today I found that if i assigned an IP bind for my wifi interface it would work only until the interface went down, whereby deluged would switch over to my ethernet interface on a different subnet.

This issue means that the bind is essentially useless as it is not reliable. For the moment I am using the interface launch option for the daemon instances and also blocking traffic through firewall. This is not ideal.

Is there anything like Vuze has with its force bind to IP/interface whereby no matter what state the IP/interface is in at launch or thereafter, the bind will be respected fully?

deluge == 1.3.11
libtorrent == 0.16.18.0
wifi net == 192.168.192.0/24
ethernet net == 192.168.0.0/24

[Cas]

Sorry not currently.