The following problem has been bugging for the past two days . I have been using bittornado for my torrent needs ever since I was in to torrents. Bittornado is curses base and I tried Azureus which is java base for a while but I didn’t really tinker with it that much . Anyways ,I have a router in between my computer and my cable modem . I have OPENWRT White Russian on it. It’s really nice to have a little bit of something in between you and wild net outside ..
My home computer network looks like this :
* Debian Sid on a Pentium 3 500mhz
* Linksys WRT54G ver 2.2 i think
* Openwrt on the Linksys
I was trying Azureus 18.104.22.168 and I notice that It keeps telling me that my Router is not set up right . I always get a either a DHT firewalled or NAT firewalled status on the lower status bar .I went about googling for solutions :
1. I sshd to my router and added the ff line in my /etc/firewall.user: iptables -t nat -A prerouting_rule -i $WAN -p tcp –dport 6880:6990 -j DNAT –to 192.168.1.100:10000
iptables -A forwarding_rule -i $WAN -p tcp –dport 10000 -d 192.168.1.100 -j ACCEPT
iptables -t nat -A prerouting_rule -i $WAN -p udp –dport 6880:6990 -j DNAT –to 192.168.1.100:10000
iptables -A forwarding_rule -i $WAN -p udp –dport 10000 -d 192.168.1.100 -j ACCEPT
2. I reloaded the firewall after that by : #/etc/init.d/S45firewall restart
3. however that didn’t work ,so ;I tried changing /etc/config/firewall ,this file is used by NBD’s qos-scripts and according to the info I googled supposedly makes it easy to change the nat behaviour ..
I added this line: forward:dport=6880-69990:192.168.1.100:10000
All this suppose to setup my my portforwarding , this supposedly forwards all incoming connections to my routers ports 6880-6990 to my computers port 10000. .
I tried to look at my computers netstat output but all I can see was that my port 10000 is open and when I used shields-up to probe my port 6880-6990 ,it was also open but still no NAT success with Azureus..
I also noticed that the netstat output shows that there are tcp6 and udp6 ports that are open . I didn’t know that I was using anything that has to do with ipv6 .. So I googled my friend google ..hehehehe .. and I came across this forum for redhat users … It suggested there to turn off aliases for ipv6 in /etc/modutils/aliases . That took care of the ipv6 problem when I rebooted no more ipv6 ports opened but i still have no nat for Azureus ..
I finally got a working /etc/firewall.user line that worked .after so many hours of tweaking . I read somewhere that azureus or bittorrent for that matter doesn’t like the usual ports opened coz some isp’s are blocking this ,so I thought about it.. Maybe just change the dport to something else and don’t change the forwarding rule to another port .
So my final rule that got me is this :
iptables -t nat -A prerouting_rule -i $WAN -p tcp –dport 60881 -j DNAT –to 192.168.1.100
iptables -A forwarding_rule -i $WAN -p tcp -d 192.168.1.100 -j ACCEPT
iptables -t nat -A prerouting_rule -i $WAN -p udp –dport 60881 -j DNAT –to 192.168.1.100
iptables -A forwarding_rule -i $WAN -p udp -d 192.168.1.100 -j ACCEPT
That dport flag on the prerouting rule is arbitrary .. You can change it to anything . After this I reloaded the firewall and to make sure ,I rebooted the router and also my computer ..
I also change the port settings on Azureus and voila! Magic! My azureus is going green eversince ..
A few pointers ,give it a little while if at startup its yellow .. it takes a while for it to change ..Also,there are some torrents out there that is bad ,meaning ,there is no seeds and tracker site is down ,So if you run into this then it’s not really you thats the problem . Also, I don’t have to say this but if you’re torrenting you must be prepared to give,i mean don’t try to be a leech.. or you’ll get what’s coming to you ..
I hope this helps all those Azureus users out there. Coz ,this has got me some lost hours of sleep!