Problem Using Bit Torrent

This is my theory: Smart WiFi acts like a big wireless router for everyone who subscribes to the service. But in order for Bit Torrent to work, port-forwarding must be enabled. For port-forwarding to work, you must have a static IP address in the router. But I guess Smart WiFi has all its clients connect through DHCP so you have no static IP address. This is just my guess...

[Edited on 9.6.05 by lamski]

 

try other bittorrent clients. I prefer Azureus over the original bittorrent client.

 

This answer to your problem:

To open ports in the Mac OS X firewall, do the following:

1. Open System Preferences.
2. Click Sharing.
3. Select the Firewall tab.
4. Click the New... button.
5. Click the popup menu in the dialog that appears, and choose Other....
6. In the Port Number, Range, or Series field, enter 6881-6999.
7. In the Name field, enter BitTorrent (or any other identifying string.)
8. Click OK.


If you are using a linux box as your firewall machine, and are using iptables as your NAT/firewall, here's how you can enable portforwarding to a specific machine for BitTorrent. Either append to your iptable configuration script or put this in a file of its own. This was written in bash, but should work for ash, zsh or plain old bourne shell too (not csh however).
---- start shellscript ----

#!/bin/bash
#bittracker portforwarding
BTFORWARDADDR=192.168.1.3
BTPORTS="6890 6891 6892 6893 6894 6895 6896 6897 6898 6899"
for pt in $BTPORTS; do
/sbin/iptables -t nat -A PREROUTING -i ppp0 -p tcp --dport $pt -j DNAT --to-destination $BTFORWARDADDR:$pt
/sbin/iptables -A FORWARD -s $BTFORWARDADDR -p tcp --dport $pt -j ACCEPT
done


---- end shellscript ----
What this does is for each port in the BTPORTS string, establish a prerouting forward to send it directly to the machine listed in BTFORWARDADDR instead of mangling it through NAT. Also, in the event you have a default setting of DENY or REJECT for your forwarding rules, it allows forwarding from the BTFORWARDADDR machine on each of the BTPORTS out to the net.


In addition to the syntax illustrated here, iptables supports the specification of a range of ports using the syntax --dport $START:$END so the whole 6881-6999 range used in BT 3.2+ can be NAT'ed. For example...

=== start script ===

#!/bin/bash BTFORWARDADDR=192.168.2.20 PORTSTART=6881 PORTEND=6999

/sbin/iptables -t nat -A PREROUTING -i ppp0 -p tcp --dport $PORTSTART:$PORTEND -j DNAT --to-destination $BTFORWARDADDR
/sbin/iptables -A FORWARD -s $BTFORWARDADDR -p tcp --dport $PORTSTART:$PORTEND -j ACCEPT

=== end script ===
This assumes that the host to which these ports will be forwarded, BTFORWARDADDR, will be using the same range i.e. no port redirection is required.

[Edited on 9.6.05 by teng]

 

i use azureus too.. great app btw..

 

me i use tomato torrent no problems here...

 

hmm... weird. I tried this a few months ago but I still got NAT errors using Azureus. I'm now using Tomato. Not as fancy as Azureus, but it gets the job done.

 

quote]Originally posted by Adel
Hi, Reg. We're treading on very thin piracy ice here. Let's just keep the discussion confined to BT clients, shall we? [/quote]

Sorry about that will delete my message right away

 

This is just a guess. but maybe the ISP is blocking the Port number your using. Some ISPs are known to do that because torrents are wildly known to spread piracy. Try other 4 digits Port numbers.

 

While downloading/trying out your BT clients read this..