Associated server nic problem

General support for problems installing or using Deluge
Post Reply
MageMinds

Associated server nic problem

Post by MageMinds »

Hi,

I have a little server at home (Windows 2K8 Server R2) on which deluge daemon is running. I had Intel NIC Bonding activated and that was giving me problem to connect to the daemon. Most of the time I tried the connection broke and I saw nothing. I have 2 other installation of deluge daemon on which I was able to connect every time. The only difference between those two other servers and mine, was that mine was the only one with nic bonding. I updated the Intel drivers, no luck. I disable the nic bonding and now it works like the two others... I know it's a hard to debug for you guys, I can live with the nic bonding disabled, it's a home server after all..

In the log I see something like that every time I connect to the daemon using a remote gui, but composing that post I realized that this is how the Connection Manager works. I tough it was related to my problem, but it is not apparently... Oh I almost forgot it does the same too on a linux based daemon. All the tests where done using a Windows client.

Maybe you should implement a better way for the connection manager to "ping" the daemon making a clean connection break. But since that doesn't cause any problem, I sure you'll be putting more efforts where it's worth!

From Work to Home (using a VPN)

Code: Select all

[INFO    ] 09:29:45 rpcserver:223 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion.
[INFO    ] 09:29:45 rpcserver:203 Deluge Client connection made from: 10.0.0.16:1629
[INFO    ] 09:29:47 rpcserver:203 Deluge Client connection made from: 10.0.0.16:1632
[INFO    ] 09:29:48 rpcserver:223 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion.
[INFO    ] 09:29:49 rpcserver:203 Deluge Client connection made from: 10.0.0.16:1635
From Home to Friend (also using VPN) (Friend have W.2K8.R2 too)

Code: Select all

[INFO    ] 09:37:06 rpcserver:203 Deluge Client connection made from: 10.77.2.60:52350
[INFO    ] 09:37:07 rpcserver:223 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion.
[INFO    ] 09:37:08 rpcserver:203 Deluge Client connection made from: 10.77.2.60:52352
Last edited by Cas on Mon Jan 30, 2012 4:28 pm, edited 1 time in total.
Reason: It's nic bonding not nic bounding
Cas
Top Bloke
Top Bloke
Posts: 3681
Joined: Mon Dec 07, 2009 6:04 am
Location: Scotland

Re: Associated server nic problem

Post by Cas »

You have not included the version of Deluge or libtorrent you are using.

Did you specify the ip address of the bonded NICs for 'interface' in the config?
Post Reply