Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| add_port_mapping_in_nat_router [2011/01/16 00:46] – [Add Port Mapping in NAT Router] greywizard | add_port_mapping_in_nat_router [2015/08/15 04:21] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Add Port Mapping in NAT Router ====== | ====== Add Port Mapping in NAT Router ====== | ||
| - | To get the best speeds, BitComet needs a open listening port, just as most other P2P applications do. But if you are behind a router or use Windows Internet Connection Sharing (ICS) or you are behind a firewall, you might need to make some adjustments before you get rid of the infamous [[bitcomet_status_bar|yellow light]] and BitComet works as intended. Namely, you'll probably have to configure your router and/or firewall(s) in order to open the listening port of BitComet. In this topic we will discuss the configuration of the router (port forwarding) both automatic (through UPnP) and manual, to the end of opening a port in your router' | + | < |
| + | |||
| + | To get the best speeds, BitComet needs an open listening port, just as most other P2P applications do. But if you are behind a router or use Windows Internet Connection Sharing (ICS) or you are behind a firewall, you might need to make some adjustments before you get rid of the infamous [[bitcomet_status_bar|yellow light]] and BitComet works as intended. Namely, you'll probably have to configure your router and/or firewall(s) in order to open the listening port of BitComet. In this topic we will discuss the configuration of the router (port forwarding) both automatic (through UPnP) and manual, to the end of opening a port in your router' | ||
| As with software personal firewalls, there are a wide variety of routers available, and because of the sheer number, it is impossible to include port forwarding instructions for each router model in this user guide. Fortunately many routers support Universal Plug and Play (UPnP), which simply allows BitComet to open and forward a port on the router automatically, | As with software personal firewalls, there are a wide variety of routers available, and because of the sheer number, it is impossible to include port forwarding instructions for each router model in this user guide. Fortunately many routers support Universal Plug and Play (UPnP), which simply allows BitComet to open and forward a port on the router automatically, | ||
| - | Also you need to make sure that UPnP is enabled on your Windows OS or if it's not or you're not sure, you can manually | + | Also you need to make sure that UPnP is enabled on your Windows OS or if it's not or you're not sure, you can configure/ |
| If after that you find that you are still in a firewalled state (i.e. yellow status light), then it likely means your router does not support UPnP, or it includes an implementation incompatible with the UPnP mapper used by BitComet. | If after that you find that you are still in a firewalled state (i.e. yellow status light), then it likely means your router does not support UPnP, or it includes an implementation incompatible with the UPnP mapper used by BitComet. | ||
| Line 16: | Line 18: | ||
| end of the first paragraph on this page. | end of the first paragraph on this page. | ||
| - | So, to sum it up, there are two ways you can go about port forwarding, in order to open your listen port in your router: | + | __So, to sum it up, there are two ways you can go about port forwarding, in order to open your listen port in your router:__ |
| * Automatic (through UPnP); | * Automatic (through UPnP); | ||
| * By manually configuring port forwarding. | * By manually configuring port forwarding. | ||
| Line 22: | Line 24: | ||
| They are both presented below (first Automatic then Manual), but make sure that you acknowledge them for what they are: two **alternative** methods towards the same end (materialized in the two independent parts of the guide: the first one about UPnP port mapping and the second one about Manual port mapping).\\ | They are both presented below (first Automatic then Manual), but make sure that you acknowledge them for what they are: two **alternative** methods towards the same end (materialized in the two independent parts of the guide: the first one about UPnP port mapping and the second one about Manual port mapping).\\ | ||
| If you choose one or another is up to you, just make sure that you know which method you want to follow and that you read the appropriate part of the guide. | If you choose one or another is up to you, just make sure that you know which method you want to follow and that you read the appropriate part of the guide. | ||
| + | |||
| ====== BitComet UPnP Auto Port Mapping ====== | ====== BitComet UPnP Auto Port Mapping ====== | ||
| Line 75: | Line 78: | ||
| ====== Manually Configure Port Mapping at Router setup page ====== | ====== Manually Configure Port Mapping at Router setup page ====== | ||
| + | |||
| + | < | ||
| Sometimes, UPnP Auto Port Mapping just won't work. Be it from an incompatible UPnP flavor on your router or an incompatibility between your Windows version' | Sometimes, UPnP Auto Port Mapping just won't work. Be it from an incompatible UPnP flavor on your router or an incompatibility between your Windows version' | ||
| Line 86: | Line 91: | ||
| and search for it. | and search for it. | ||
| - | OR | ||
| - | To manually check whether you have a MODEM or a ROUTER, follow these instructions below: | + | |
| + | Alternatively, | ||
| * Click on Start -> Run -> type //cmd// -> press Enter or OK -> type // | * Click on Start -> Run -> type //cmd// -> press Enter or OK -> type // | ||
| Line 102: | Line 107: | ||
| Your LAN IP address is the identifier of your computer within your local network, but is not public for anyone else to see, besides the other computers within your network. Your WAN IP address is the IP address that people outside of your network see, but it does not reveal the internal IP address allocation on your LAN, which may contain multiple computers, each (naturally) having their own LAN IP. In the context of setting up a static IP for port forwarding, your WAN IP is irrelevant, and is normally not used in any step along the way. | Your LAN IP address is the identifier of your computer within your local network, but is not public for anyone else to see, besides the other computers within your network. Your WAN IP address is the IP address that people outside of your network see, but it does not reveal the internal IP address allocation on your LAN, which may contain multiple computers, each (naturally) having their own LAN IP. In the context of setting up a static IP for port forwarding, your WAN IP is irrelevant, and is normally not used in any step along the way. | ||
| - | < | + | **So, why do you need to forward your port?** |
| + | |||
| + | Most applications communicate with the Internet, using an __outgoing__ connection type, which means that the connection with the host computer at the other end (usually a server) is being //initiated from your machine//, from your side. In that case an entry gets added into the NAT table of the router, containing the socket (the pair of IP address and port of your PC and of the host computer you're connecting to) so that the router will know where to send (into your private LAN) all the reply packets that come for that connection.\\ | ||
| + | |||
| + | However there are a certain number of applications which need to use __incoming__ connections as well in order to function properly, which means that the connection is being //initiated by the other host computer//, not by yours. BitTorrent clients (and P2P applications in general) are such applications. Thus, in order for BitComet to function properly, it needs a open port on which it listens and receives incoming connections from other peers.\\ | ||
| + | |||
| + | The problem in case of NAT routers (overloading NAT or PAT, to be more specific) is that since one WAN IP address serves multiple computers, when the router receives incoming connections it cannot know by default for which computer (IP address) of the LAN they are meant, so it doesn' | ||
| + | That is why it needs a rule set in its configuration settings, which says something of the type: " | ||
| + | |||
| + | Basically, this is what you'll be doing when setting up port forwarding. In case the hardware firewall of the router is enabled, port forwarding will usually open that port number in the firewall, too. But for some other models you'll have to open it explicitly. | ||
| + | |||
| + | < | ||
| **Now onto the actual steps:** | **Now onto the actual steps:** | ||
| Line 127: | Line 143: | ||
| * DNS Servers (some users may have 2, be sure to copy both of them!) | * DNS Servers (some users may have 2, be sure to copy both of them!) | ||
| - | < | + | < |
| + | |||
| + | {{: | ||
| + | |||
| + | On Windows Vista and Windows 7 the steps to reach to the Properties windows will differ a little: Click on //Start --> Control Panel --> Network and Sharing Center//. In the window that opens click in the Tasks Pane (on the left) on the //Change Adapter Settings// (for Windows 7) or on //Manage Network Connections// | ||
| + | |||
| + | Alternatively, | ||
| + | |||
| + | Inside the Connections window locate and right click on the connection your PC uses to connect to the Internet. | ||
| + | Click on Properties in the context menu and inside the dialog box which opens scroll down to and select TCP/IPv4.\\ | ||
| + | |||
| + | {{: | ||
| Next, click Properties, and an extra window should pop-up. As shown below:\\ {{: | Next, click Properties, and an extra window should pop-up. As shown below:\\ {{: | ||
| Line 175: | Line 202: | ||
| ===== Cascaded routers ===== | ===== Cascaded routers ===== | ||
| - | < | + | < |
| - | If you don't know what type of devices you have, retrieve the model numbers from them (they should be marked on the device or on the label beneath) and search them on the Internet.// | + | //If you don't know what type of devices you have, retrieve the model numbers from them (they should be marked on the device or on the label beneath) and search them on the Internet.// |
| - | The main difference between a simple modem and a modem/ | + | The main difference between a simple modem and a modem/ |
| - | On the other hand, a router will end your ISP's network at its WAN interface (the router connected directly to the Internet has the public IP given from your ISP, assigned to its WAN interface). From there further downstream, (for the LAN side) private [[http:// | + | On the other hand, a router will end your ISP's network at its WAN interface (the router connected directly to the Internet has the public IP given from your ISP, assigned to its WAN interface). From there further downstream, (for the LAN side) private |
| - | Since more and more devices come in integrated combo models, **modem/ | + | Since more and more devices come in integrated combo models, **modem/ |
| Be it for the purpose of adding wireless capabilities to the LAN or for increasing the number of available Ethernet ports on the LAN in order to add several computers or for whatever other reasons, many users find themselves using two cascaded routers (many of them unknowingly!). | Be it for the purpose of adding wireless capabilities to the LAN or for increasing the number of available Ethernet ports on the LAN in order to add several computers or for whatever other reasons, many users find themselves using two cascaded routers (many of them unknowingly!). | ||
| If that is your case, then you're probably using a topology similar with the one below (the IP addresses used in the figure below are used for exemplification, | If that is your case, then you're probably using a topology similar with the one below (the IP addresses used in the figure below are used for exemplification, | ||
| - | {{:network_scheme_01.png|}} | + | {{:network_scheme_02.png|}} |
| For the purpose of the following discussion we're going to assume that you use a topology similar to the one above (which is the most common). We'll also assume that both your devices are operating in " | For the purpose of the following discussion we're going to assume that you use a topology similar to the one above (which is the most common). We'll also assume that both your devices are operating in " | ||
| - | So, usually the user has an Internet connection (DSL or cable) which comes plugged into the modem/ | + | So, usually the user has an Internet connection (DSL or cable) which comes plugged into the modem/ |
| - | From one of Router1's LAN (Ethernet) ports (often there is only one), usually, another Ethernet cable emerges which is plugged into the other router/ | + | From one of __Router1__'s LAN (Ethernet) ports (often there is only one), usually, another Ethernet cable emerges which is plugged into the other router/ |
| - | We'll call this second device, | + | We'll call this second device, |
| - | We'll call the network between | + | We'll call the network between |
| The thing you need to understand is that NAT ([[wp> | The thing you need to understand is that NAT ([[wp> | ||
| - | That is because NAT is being performed //once// from the public IP address used by the WAN-Router1 | + | That is because NAT is being performed //once// from the public IP address used by the WAN interface |
| - | Note that the Router2's WAN interface is assigned a private address from LAN-A but it has no idea about that; as far as Router2 | + | Note that the __Router2__'s WAN interface is assigned a private address from LAN-A but it has no idea about that; as far as __Router2__ |
| - | You will have 2 private address | + | You will have 2 private address |
| Therefore all the instructions from the previous section apply twice! | Therefore all the instructions from the previous section apply twice! | ||
| - | You will need to treat Router2 | + | You will need to treat __Router2__ |
| - | Then you will need to perform port forwarding once more on Router2. This time you will, finally, assign a fixed IP to your PC, from the range of LAN-B. Then you will forward the same listen port on Router2 | + | Then you will need to perform port forwarding once more on __Router2__. This time you will, finally, assign a fixed IP to your PC, from the range of __LAN-B__. Then you will forward the same listen port on __Router2__ |
| Detailed instructions on the forwarding steps, you can find in the previous section. This section here has the purpose of merely elaborating the specific differences for this particular case. | Detailed instructions on the forwarding steps, you can find in the previous section. This section here has the purpose of merely elaborating the specific differences for this particular case. | ||
| < | < | ||
| - | So, using the IP addresses from the topology in the figure above, you will have to forward the listen port on Router1 | + | So, as an example, using the IP addresses from the topology in the figure above, you will have to forward the listen port on __Router1__ |
| - | On Router2 | + | On __Router2__ |
| < | < | ||
