OK. Please NO remarks at my fancy Pirate Theme and a disclaimer
*** WARNING ***
This is meddling with your Internal IP Address and although no harm can come of hardware you can quickly, IF NOT DONE RIGHT, prevent you from internet access.
BE WARNED and make sure you do everything correct or ASK first in PM's before doing anything you don't fully understand. This is basic network setup and although it's BASIC for myself and many others SOME might have problems and I don't wanna hear I didn't warn you!
OK the first general problem with Torrent is the use of DHCP IP Ranges. In the past everything had to have Fixed IP ranges but with the innovation of the DHCP
, or `Dynamic Host Configuration Protocol`, it's made things a lot easier.
This unfortunately is the first demise of most Torrent setups, especially through a personal router that many employ these days for home LAN activities. Now, with DHCP you can have a lovely and efficient Torrent setup however in the realm of PorForwarding, Fixed IP's are much easier to work with especially if your new to the game.
What we first need to do is enable your Torrent machine to carry a Fixed IP address behind a router. This is different for each router make and model by typically follows the same naming conventions and theories applied so no sweat. In this example I'm using a LinkSys WRT54G
Wireless router with a custom firmware flash by DD-WRT.
First Step is to allow the router, using DHCP by default, to give yourself 1 IP address that the Torrent machine can carry as it's own. In my personal setup I have 3 wired PC's and 2 Wireless devices. I setup my router to START it's DHCP Range +1 to the IP I wish to use on the Torrent machine, in this case 192.168.1.100.
As you can see above, I've kept the router DHCP enabled but stated to start issuing addresses at the .101 octet so it never gives out the .100 octet.
You can ALSO see that I've pointed out the Subnet Mask and the IP of the router which to Windows is known as the Gateway. Remember those
Now on to our configuration of our TCP/IP Settings in Windows.
Once you've set the router to allow 1 IP, typically at the start of the range, to never be used it's time to configure your Network Settings to fix this IP to your Torrent machine. This is very easy and many will have already been in these screens but I provide for those new since in today's world most routers are Plug and Play with Windows and you really never, ever need to do anything -- unless you want to do something
Here is the first, goto your Network Connections and find the Local Connection link. You can find this by going to START->CONTROL PANEL->NETWORK CONNECTIONS or sometimes a link directly off your Start Menu.
Right click your Local Area Connection, or known connection's link, and select Properties.
Now once in the properties for the connection, scroll down if need be and find `Internet Protocol (TCP/IP) Settings`. This is where you set the new Fixed IP for your Torrent machine. Select the option `Internet Protocol (TCP/IP) Settings` then hit the `Properties` button
Once there select the option to `Use The Following IP Address:`
Enter the Fixed IP you've given yourself, in this case 192.168.1.100,
The Subnet Mask (remember the router above?) as 255.255.255.0
and finally the Gateway (as the router IP above) as 192.168.1.1
You can also specify the Default DNS Server as I have above, but again I know what I'm doing and use a 3rd party DNS supplier but for most it's left as `Obtain Automatically`.
OK, so now save all your changes with OK buttons and the network connection should if everything is configured in the router, your connection is properly setup; resync to the router but now using the specified IP address you want!
Test the connection by going to web or some other IP traffic related application and if found in working order, proceed to the next setup of configuring portforwarding for your router & Azureus.
Port Forwarding is really easy. Yes it is trust me.
You need to FIRST understand what it is then you'll see why I say that. Bear with me here but basic Port Forwarding has to do with today's NAT Routers. Now NAT you say, what's that? NAT stands for `Network Address Translation`.
OK you say but what's it mean and what's it for? Well quite simply behind today's routers your are behind what's called an IANA range or a private IP range. Ranges such as typical market routers tend to follow the 192.168.xxx.xxx ranges. These ranges are meant for internal routing of systems on the internet/network. They are typically NOT intended for public use on a LAN/WAN or any other large scale network. Essentially what today's NAT routers give you is you own private sandbox, if you where, of IP Addresses that you can do what you want without stepping on other toes.
The NAT portion is where the router gains an IP adress from your Internet Service provider and holds on to it much as if you were directly connected to the service via the computer Network Card. It holds this IP address as your sole pipeline in and out of the internet. When something goes out from a computer behind the router, it serializes the request with the internal IP of the private range from which it came. So this is how one router can SHARE multiple connections, NAT. It translates outgoing and incoming requests, through the one shared IP but with a little configuration that tells it where to route back as in the original PC that requested it.
Now with sharing ports on a router you can see quickly that without this NAT ability the router would not be able to send the appropriate information to the client that requested it. So goes the same for Port Forwarding. What this does is add the ability to not only specify where to send it but to trigger on the PORT it's using as well.
So in example you can state any incoming traffice of say Torrent nature, coming in on Port 50321 is to be directly routed to a specific IP address and port if you so desire.
Ok, getting long and I can delve more later if needed. Basically Port Forwarding tells the router that anytime traffic comes INBOUND to the router on a specific port (ie: torrent port) ROUTE it to a specified IP address.
We'll now show this setup. First find your Port Forwarding setup in your router. Makes and models differ but the same rules apply. Again, I'm using DD-WRT custom firmware. Once you find the settings you need to first add the default BitTorrent port ranges. This is commonly OVERLOOKED and is a case for UnHappy NAT in Azureus or other NAT enabled clients. The default BitTorrent range is 6881-6889. You can see below those specified to port to our Fixed IP and using BOTH protocols, those being UDP and IP.
Also, you need to Port Forward the Azuerus Port your going to define later. It's HIGHLY RECOMMENDED that you change the default and any port you wish can be used up to the limits of TCP/IP. Choose one in the 4-6 digit range and remember it. In this example I use the port 50321.
Also a reminder that many, MANY ISP's now block or limit bandwidth on default Torrent Ports so this also helps resolve that issue as they can't quite block ALL ports and choosing one out far usually defeats this blockage.
OK, enable the Port Forwarding, save the changes and you are now done in the router -- we hope! On to Azureus Setup!
This is the easiest.
Load up Azureus client and once loaded goto the Settings/Options. You should see a multitude of options but the first we need to concentrate is the Port you specified to use in the Port Forwarding setup, in this case 50321.
As you can see below, enter the Incoming Port number as that you've specified in the router
Hit SAVE and proceed to now disabling uPNP which is the like the Port Forwarding DHCP protocol. Basically what it does is dynamically, at application runtime, configure a uPNP device (router) to portforward automatically each time. This way you don't have to worry about all we are doing here but honestly I've done it for years and the fixed IP is easier and you get better yields.
Turn off uPNP in Azureus here:
OK so now when that's all done I like to stop Azureus and restart, let it sync to the IP and start using the Port Forwarded Ports you've setup. If your lucky and followed well or asked questions before doing something you didnt' know, you'll see HAPPY NAT like below