peer connection problems
Posted: Mon Feb 07, 2011 11:37 pm
I've been trying to get myself running with deluge but am having problems. I'm using 1.3.1 on Mac OS X 10.6.5 with libtorrent 0.15.4. I've previously been running on Vuze 4.4 and am using the same ports to minimise firewall/NAT problems. What I'm seeing is that deluge seems to have no problems scraping trackers, but it doesn't seem to behave at all when it comes to peers. All I see, I see through wire-sniffing, and what that tells me is that there are no outbound connection attempts, while all inbound traffic gets a TCP reset back. For TCP connections, what I see happening is that the peer is able to get a three-way handshake, but when it moves on to the BitTorrent handshake, it promptly gets an RST. What this tells me is that nothing in the network path up to and including the host firewall is preventing the connection from being established. I can confirm that the listener is where it's supposed to be by looking at lsof, but, as you may expect, it never sees any sockets with BitTorrent peers, although I do see the tracker connections when those happen around start-up. There is absolutely nothing showing up in the debug logs about peer traffic. I've tried running with LittleSnitch filtering disabled, but one thing it tells me as a monitor with or without filtering active is that it sees all these connections as going through to deluge itself.
I've tried generating a core.conf from scratch, changing only the port numbers. I've also made a few basic changes to make sure that values greater than zero were in place for bandwidth settings, just in case there were some problems with unlimited resource settings being interpreted incorrectly or creating some other odd problem. I'm attaching that file here
The only other thing I see is that deluge occasionally ignores the preferences for port settings, giving me something I haven't specified for the IPv4, while obeying my wishes for the IPv6 port. Restarting seems to fix this.
I've tried generating a core.conf from scratch, changing only the port numbers. I've also made a few basic changes to make sure that values greater than zero were in place for bandwidth settings, just in case there were some problems with unlimited resource settings being interpreted incorrectly or creating some other odd problem. I'm attaching that file here
The only other thing I see is that deluge occasionally ignores the preferences for port settings, giving me something I haven't specified for the IPv4, while obeying my wishes for the IPv6 port. Restarting seems to fix this.