||02-01-2005 09:47 PM
Shorewall and BitTorrent not playing nice
I recently installed the command-line version of BitTorrent (the GUI isn't working, but that's another matter). Whenever I type in:
(which is the torrent file for dropline gnome source ISO) it says, "error(s):[18:41:06] Problem connecting to tracker - <urlopen error (111, 'Connection refused')>".
I did some looking into it and found out that BitTorrent needs ports 6881-6889 and 6969 open, so I went into /etc/shorewall/rules and added the following lines:
ACCEPT fw net tcp 6881:6889,6969
ACCEPT fw net udp 6881:6889,6969
ACCEPT net fw tcp 6881:6889,6969
ACCEPT net fw udp 6881:6889,6969
Unfortunately, when I restart shorewall (or the whole computer) and run nmap, I get this:
[dane@Orchestrator dane]$ nmap -p 6881-6969 192.168.1.250
Starting nmap 3.50 ( http://www.insecure.org/nmap/ ) at 2005-02-01 18:46 PST
All 89 scanned ports on Orchestrator.The.Band (192.168.1.250) are: closed
Nmap run completed -- 1 IP address (1 host up) scanned in 0.309 seconds
So it would seem that shorewall is just ignoring those lines in the rules file, however, it seems to obey the other rules in there. Weird.
If anybody knows what I can do about this, I would greatly appreciate your help.