NAT issues for bit torrent, can't solve it

BiGBrOwNPimpsta · Jun 19, 2007, 01:55 PM

Well I get the NAT problem with my Linksys WRT54GS router, and for 1 year have tried to resolve the issue with no luck. Only way to get bit torrent (or azureus or the WoW updater) to work at full speed is unplugging it. I followed the guide on port foward correctly but i think I might be doing something wrong?

I obtained a static IP through the guide I guess, when it asked me to enter the IP of my computer I was confused which one to use. I tried the one assigned by my ISP which starts with a 74.xx.xx.xxx to generate the static IP for each computer, the ones generate started with 74 as well and when entered into network settings it didn't work. So I used my IPv4 address obtained in command prompt and entered it, it generated working static IPs and I guess this was the correct one. I added the ports to foward with the static IP I obtained in the Linksys config utility. In addition, I set the port to be used in Azureus (like before) and I still had no luck. I think I used the correct static IP, the guide gets a little confusing. So I checked the AzureusWiki and found this

Quote:

IP Forwarding Through the Broadband Modem
If your network consists of a DSL modem connected to a router and the local computers connect to the router, you may need to enable IP Passthrough on the modem. Otherwise, it may be impossible to successfully port forward through the router, as described in the next section.

So I checked the following section, since I have Siemens Speedstrem 4200 DSL Modem for Bell Sympatico here in Canada, connected to the router.

Quote:

Port Forwarding Through The Router
At this point you should now have a static internal/private IP address for the computer that is running Azureus. Log into your router's configuration table so that we may actually port forward. Depending on the device's manufacturer and the model itself, the "place" where you do the forwarding will differ: NAT, NATP, Custom Services, and Virtual Server are the most commonly named sections, though it's entirely feasible yours is named something else, but the fundamental procedure for creating a port forwarding rule is more or less the same and self-explanatory.

You may be lucky and find a step-by-step guide for this procedure at http://www.portforward.com/routers.htm . Select your particular model from the list, go to Port Forwarding the (your modem/router model), and then select the Default Guide link.

The Rule will need a unique Service Name or a Number to identify it.
The Rule will need to know what port number to have forwarded to it.
If the option asks for a range, simply input the same number for From and To (example: From: 56912 To: 56912).
The Rule will need to know which protocol to use for that port. Use both TCP and UDP.
Azureus requires the TCP protocol for "regular" incoming data transmissions.
Azureus (2.3.0.0 and newer) requires the UDP protocol to be enabled for DHT to function properly.
If the router does not ask for one protocol or the other, it should be safe to assume it defaults to using both.
If the router only allows you to choose one protocol or the other, then you will need to create two rules for that port (use a different Service Name or Number), one for each protocol.
The Rule will need to know which IP address to forward to. You will, of course, use the static IP address you have already assigned yourself.
The Rule will need to be enabled, and then saved/applied.

I checked portforward.com, and nothing is there about my modem. So there may be an issue with getting the modem configured to work properly with the router and port fowarding, and I'm sure I'm doing something wrong. Can anyone help me out?

Judas · Jun 19, 2007, 02:33 PM

There shouldn't be any MODEM specific problems, it generally should just work.

However the linksys router i had issues with... i'm not to fond of them at all..

I know some ISPs are clamping down on bittorrent known ports.

Some Bittorrent apps keep moving the port around everytime you load it up, so you'll want to make sure it's static.

Also, UTorrent is by far the easiest and fastest torrent client i've used yet.

BiGBrOwNPimpsta · Jun 19, 2007, 02:53 PM

Quote:

Originally Posted by Judas

There shouldn't be any MODEM specific problems, it generally should just work.

However the linksys router i had issues with... i'm not to fond of them at all..

I know some ISPs are clamping down on bittorrent known ports.

Some Bittorrent apps keep moving the port around everytime you load it up, so you'll want to make sure it's static.

Also, UTorrent is by far the easiest and fastest torrent client i've used yet.

it works fine WITHOUT the router, so Bell is fine with bit torrent. i could try uTorrent

edit - same issue with uTorrent

Zelig · Jun 19, 2007, 03:37 PM

I've got my setup working fine with a Linksys WRT54GL and one of Bell's offshoot DSL service.

Can you screenshot the port forwarding page of the router's config? I'll explain what to input to the text fields, and why.

edit: For simplicity, set any network settings on the computers to automatically obtain DHCP addresses, those should be the default settings.

Yousaif · Jun 19, 2007, 06:35 PM

Your router has been found to have issues with too many connections causing issues with slow downloads and poor performance. Try limiting your active connections to under 200.

I found a fix for the issue. You can check it out here http://www.utorrent.com/faq.php#Spec..._GL_GS_routers

BiGBrOwNPimpsta · Jun 19, 2007, 06:56 PM

here is the screen shot

and that firmware trick looks complicated yousaif LOL i dont like flashing firmware unless I have to, especially something not made by the manufacturer. its usually safe though. and i just checked, my router firmware version is the one that fixes the issue

Zelig · Jun 19, 2007, 07:12 PM

Okay, that should work, if everything else is configured properly.

Torrents actually only need 1 port, and TCP connections open.

Although it sounds like the router is the problem, because of ISP issues, it's generally recommended not to use default torrent ports. I've got torrents set to 61111, you need to set this in the Azureus settings, as well as the router settings.

And I'm assuming the computer where you're trying to run torrents has been assigned the 192.168.1.146 IP address?

BiGBrOwNPimpsta · Jun 20, 2007, 02:27 PM

Quote:

Originally Posted by Zelig

Okay, that should work, if everything else is configured properly.

Torrents actually only need 1 port, and TCP connections open.

Although it sounds like the router is the problem, because of ISP issues, it's generally recommended not to use default torrent ports. I've got torrents set to 61111, you need to set this in the Azureus settings, as well as the router settings.

And I'm assuming the computer where you're trying to run torrents has been assigned the 192.168.1.146 IP address?

well i used portfoward.com's static IP instructions to set one on my computer, using my external IP will not work at all to generate a valid static IP so I used my IPv4 address I found in ipconfig. The first computer static IP addy was generated .146, the second .147, third .148 etc...so I used the first addy as my static IP in my router settings. Still no luck, I also reset the router.

LHC · Jun 20, 2007, 04:03 PM

I used Azureus for torrents too

When I had problems like that, I encrypted the outgoing connections, and things started working well for me. I'm not sure if this is the same issue for you, but it doesn't hurt to try

Since my computer isn't exactly functional at the moment, I'm not EXACTLY sure where it is in the settings

I think it's under the first tree, and is labeled as "Encryption Settings" or something similar

Set it to use RC4 encryption, and just as a test, check the box about outgoing connections

Sorry it's not very clear, but it's the best I can do without my computer as a guide

BiGBrOwNPimpsta · Jun 20, 2007, 04:15 PM

yep i used both plain and RC4, did no diff

BiGBrOwNPimpsta · Jun 25, 2007, 01:08 AM

ok i got an error from azureus saying my 74.xx.xx.xx:6112 port is blocked, if i did the port fowarding correctly, wouldn't it of worked fine?

i am confused with this port fowarding junk. if the modem is connected directly to the comp its fine, but i need wireless for my other laptop!

H3X4D3C1M4L · Jul 4, 2007, 02:34 PM

Bell shouldn't have any issue with BT. I use that same modem (IIRC) and a WRT54GC at the moment and I port forward fine. You might need to update firmware

BiGBrOwNPimpsta · Jul 4, 2007, 02:56 PM

Quote:

Originally Posted by H3X4D3C1M4L

Bell shouldn't have any issue with BT. I use that same modem (IIRC) and a WRT54GC at the moment and I port forward fine. You might need to update firmware

can you show me what you did?

BiGBrOwNPimpsta · Jul 17, 2007, 12:02 PM

well i did more and more research on portforward.com, but it didnt let me sign into their forums. found some stuff about my modem causing a double router issue and thats why the ports can't be opened. tried the solution and no luck. so, i spoke to linksys, they told me to contact the ISP and set it up in PPPoE bridged mode. my ISP bell sympatico couldnt do it, they said even ift hey knew they would fail. so i ended up upgrading to the ultra service which they give you a wireless/modem upgrade your speed to a consistent 5mbps at all times (i think its 5-6mbps) for the same price and signed a 2yr contract. i've been happy with them so I didn't mind signing it.

with this, i can do port forwarding they said. so my bit torrent plagues will be over! 2/3 computer problems solved! (other 2 being my intel controller problem which is solved, and a nero 7 enhanced bug still bothering me)