| Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
add_port_mapping_in_nat_router [2012/09/14 22:49]
greywizard [Cascaded routers] |
add_port_mapping_in_nat_router [2015/08/15 04:21] (current)
|
| <html><span style=color:darkred;font-weight:bold>Note:</span></html> <html><span style=color:darkred;font-style:italic>If you are connected to the Internet through a wireless modem (usually a USB stick) which uses mobile phone wireless telecommunications technology (such as GPRS, EDGE, EVDO, HSPA, UMTS, etc.) most likely your Internet connection will be firewalled at the ISP site by default (so you basically get only half of an Internet connection, without the possibility of successful incoming connections). Short of contacting your ISP to ask if there is a possibility to get full Internet connections on the same device or changing your Internet subscription plan for one that has incoming connections unfirewalled by default (all xDSL, cable or FiOS providers usually offer unfirewalled connections), there is nothing you can do on your side to unblock incoming connections, therefore there is no point in following this guide or any other port-forwarding guide, for that matter, because you will still have incoming connections blocked on all your ports!</span></html> | <html><span style=color:darkred;font-weight:bold>Note:</span></html> <html><span style=color:darkred;font-style:italic>If you are connected to the Internet through a wireless modem (usually a USB stick) which uses mobile phone wireless telecommunications technology (such as GPRS, EDGE, EVDO, HSPA, UMTS, etc.) most likely your Internet connection will be firewalled at the ISP site by default (so you basically get only half of an Internet connection, without the possibility of successful incoming connections). Short of contacting your ISP to ask if there is a possibility to get full Internet connections on the same device or changing your Internet subscription plan for one that has incoming connections unfirewalled by default (all xDSL, cable or FiOS providers usually offer unfirewalled connections), there is nothing you can do on your side to unblock incoming connections, therefore there is no point in following this guide or any other port-forwarding guide, for that matter, because you will still have incoming connections blocked on all your ports!</span></html> |
| |
| 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's firewall and forwarding it on the setup page of your router, for BitComet. Software firewall configuration (the one residing on your computer) is discussed in the next topic ([[create_firewall_rules|Create Firewall Rules]]). | 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's firewall and forwarding it on the setup page of your router, for BitComet. Software firewall configuration (the one residing on your computer) is discussed in the next topic ([[create_firewall_rules|Create Firewall Rules]]). |
| |
| |
| 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, to manually check whether you have a MODEM or a ROUTER, follow these instructions below: |
| |
| * Click on Start -> Run -> type //cmd// -> press Enter or OK -> type //ipconfig// -> press Enter. | * Click on Start -> Run -> type //cmd// -> press Enter or OK -> type //ipconfig// -> press Enter. |
| 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, yours will vary according to your ISP and your particular equipment): | 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, yours will vary according to your ISP and your particular equipment): |
| |
| {{: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 "router" mode. The "listen port" collocation is to be understood as the port number you've set on the //Options->Connection// page of BitComet, under the "Listen port" section. | 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 "router" mode. The "listen port" collocation is to be understood as the port number you've set on the //Options->Connection// page of BitComet, under the "Listen port" section. |
