On Tue, 2007-06-12 at 16:27 +0200, Florian Philipp wrote: > > Have you tried running netstat? > > netstat > Active Internet connections (w/o servers) > Proto Recv-Q Send-Q Local Address Foreign Address State > tcp 0 1 HOMER_GENTOO64.PHHE:ftp 212-87-13-68.sds.:40202 FIN_WAIT1 > > Active UNIX domain sockets (w/o servers) > Proto RefCnt Flags Type State I-Node Path > unix 2 [ ] DGRAM 975 > @/org/kernel/udev/udevd > [...] > nothing interesting except the first line.
So you see no SYN requests to your server on port 21 > > > > Have you ensured rtorrent is > > listning on TCP 21 (in Linux you usually have to be running as root to > > do this) > > Yes. It runs as root (not that I would like it, maybe I should chroot it...) > and port 21 is rtorrent's only chance to download. So, it works. Chrooting is not going to get around needding root access to listen on port 21. Plus don't you still need to be root to chroot? > > You mean stuff like iptables? No. This is my theory but I haven't verified it. Bittorrent clients are programmed to listen/connect to a range of ports by default (I think it starts at 6882). Your client is connecting and saying "connect to me on port 21". The other clients see this but it's not in their IP range so they refuse to connect to you. You might be able to tell your client to listen on tcp/21 but that doesn't mean everyone else has told their clients to connect. But if you are sure this *has* worked then that would make my theory incorrect. Like I said I've never verified it, but that seems like the likely scenario. The other scenario is if you're not even seeing SYN requests is that requests are being blocked to your computer from that port, possibly by your ISP. But again if this were the case then it should also be the case for Windows, Knoppix, etc. Can you verify your claim (i.e. go into knoppix or whatever, run rtorrent on tcp/21 and verify via netstat that clients are connecting to you on that port)? -- Albert W. Hopkins -- [EMAIL PROTECTED] mailing list
