When a peer connects to the libtorrent listen socket (2.2.2.2:55914), that socket is bound to 2.2.2.2, and packets sent from libtorrent on that socket would have source 2.2.2.2. Also TCP connections initiated from deluged (libtorrent) to other peers should be bound to 2.2.2.2, and it looks to be th...

Have no panacea for you but as suggested, check the logs. Specifically, I would start by keeping an eye on what the kernel is spitting on dmesg while the problem is occurring and noting anything that repeats over and over or anything else clearly suspicious. Might also be a good idea to run deluged ...

Thanks for answering! Does that mean that the -i flag doesn't necessarily mean that packets going to a tracker have 2.2.2.2 as the source address, even when given that I'm not altering the packets before they hit the wire? Because my current thinking is that -i 2.2.2.2 has the effect of all outgoing...

I've got two interfaces both configured with their own IP. Say their IPs are 1.1.1.1 and 2.2.2.2, and I wanted to bind deluged to 2.2.2.2; I've done this with deluged -i 2.2.2.2 -u 2.2.2.2 . Here's the output from lsof : deluged 23629 2000 8u IPv4 10667839 0t0 TCP 2.2.2.2:58846 (LISTEN) deluged 2362...