NAT problem

When had cable there were no problems with downloading and uploading
torrent files.
But now I have a asdl modem and router and now the upload stays very low.
I will explain te situation

Internet ----> asdlmodem ------> one pc
ext ip address 82.168.202.249 ip 192.172.1.33

Now the same situation but with router and two pc's
Internet --------->asdl modem------------->router
------------------> two pc's
ext ip address 82.168.202.249 ip 192.172.1.33
ip 192.168.2.100 and 101

he question is what to configurate the modenm or the router and whit
what kind of address so i will be seen by the Net

Han Lubach


Han Lubach

"Han Lubach" <(E-Mail Removed)> wrote in message
news:42b6cc79$0$1378$(E-Mail Removed) .nl...
> When had cable there were no problems with downloading and uploading
> torrent files.
> But now I have a asdl modem and router and now the upload stays very
> low.
> I will explain te situation
>
> Internet ----> asdlmodem ------> one pc
> ext ip address 82.168.202.249 ip 192.172.1.33
>
> Now the same situation but with router and two pc's
> Internet --------->asdl
> modem------------->router ------------------> two pc's
> ext ip address 82.168.202.249 ip 192.172.1.33
> ip 192.168.2.100 and 101
>
> he question is what to configurate the modenm or the router and whit
> what kind of address so i will be seen by the Net
>
> Han Lubach


Cable broadband is asynchronous regarding upload and download speed, as
well as for aDSL (hence the "a" in that acronym). Cable and DSL differ
not only in download speed (which is fastest) but also in upload speed
(which is slowest). Did you compare the "promised" upload speed between
your cable and DSL providers? Could be the upload speed with DSL is
severely less than what you had with cable.

Vanguard schreef:

> "Han Lubach" <(E-Mail Removed)> wrote in message
> news:42b6cc79$0$1378$(E-Mail Removed) .nl...
>
>> When had cable there were no problems with downloading and
>> uploading torrent files.
>> But now I have a asdl modem and router and now the upload stays very
>> low.
>> I will explain te situation
>>
>> Internet ----> asdlmodem ------> one pc
>> ext ip address 82.168.202.249 ip 192.172.1.33
>>
>> Now the same situation but with router and two pc's
>> Internet --------->asdl modem------------->router
>> ------------------> two pc's
>> ext ip address 82.168.202.249 ip 192.172.1.33
>> ip 192.168.2.100 and 101
>>
>> he question is what to configurate the modenm or the router and whit
>> what kind of address so i will be seen by the Net
>>
>> Han Lubach
>
> That isn't the problem the torrent users can not see me so i have to
> do something with portforwarding or port triggering to make me visible
> but the problem is where to do this router or modem anfd what kid of
> addresses

Han

> Cable broadband is asynchronous regarding upload and download speed,
> as well as for aDSL (hence the "a" in that acronym). Cable and DSL
> differ not only in download speed (which is fastest) but also in
> upload speed (which is slowest). Did you compare the "promised"
> upload speed between your cable and DSL providers? Could be the
> upload speed with DSL is severely less than what you had with cable.

"Han Lubach" <(E-Mail Removed)> wrote in message
news:42b72d33$0$1357$(E-Mail Removed) .nl...
> Vanguard schreef:
>
>> "Han Lubach" <(E-Mail Removed)> wrote in message
>> news:42b6cc79$0$1378$(E-Mail Removed) .nl...
>>
>>> When had cable there were no problems with downloading and
>>> uploading torrent files.
>>> But now I have a asdl modem and router and now the upload stays very
>>> low.
>>> I will explain te situation
>>>
>>> Internet ----> asdlmodem ------> one pc
>>> ext ip address 82.168.202.249 ip
>>> 192.172.1.33
>>>
>>> Now the same situation but with router and two pc's
>>> Internet --------->asdl
>>> modem------------->router ------------------> two pc's
>>> ext ip address 82.168.202.249 ip 192.172.1.33
>>> ip 192.168.2.100 and 101
>>>
>>> he question is what to configurate the modenm or the router and whit
>>> what kind of address so i will be seen by the Net
>>>
>>> Han Lubach
>>
>> That isn't the problem the torrent users can not see me so i have to
>> do something with portforwarding or port triggering to make me
>> visible but the problem is where to do this router or modem anfd what
>> kid of addresses
>
> Han
>
>> Cable broadband is asynchronous regarding upload and download speed,
>> as well as for aDSL (hence the "a" in that acronym). Cable and DSL
>> differ not only in download speed (which is fastest) but also in
>> upload speed (which is slowest). Did you compare the "promised"
>> upload speed between your cable and DSL providers? Could be the
>> upload speed with DSL is severely less than what you had with cable.
>


You need to port forward to a static IP address. Whether you do that in
the router or not depends on your router. Some will let you assign a
specific and static IP address in their DCHP server based on the MAC
address of the target host. Then you can define port forwarding in the
router to go to a specific IP address because that IP address is always
assigned by the router's DHCP server to go to the same host with that
MAC address. Some routers don't permit assigning static IP address by
MAC address in their DHCP server, so you have to go to the host and
configure its TCP properties to use a static IP address (not in the same
range as the DHCP server for the router) instead of DHCP.

You might also have to configure a rule in the router for that forwarded
port. Normally the router's firewall will allow inbound connects if
there was an outbound request to match with it; i.e., the router's
firewall will normally block unsolicited inbound connects. However,
your P2P software probably has to accept unsolicited inbound connects.
Since those connects come from an indefinite number of external hosts
with varying IP addresses, you cannot filter the inbound connects based
on their IP address.

Since P2P program punish their users that don't actually share their
bandwidth, that is why you got the slow file transfer speeds. You need
to open you router to grant access to your intranetwork host (and hence
the loss of security by punching holes in your router's firewall). You
could configure your P2P host into a DMZ if the router supports that.
As to what you can, well, that depends entirely on WHAT is your router
which was never identified.

Vanguard schreef: "Han Lubach" &lt;(E-Mail Removed)&gt; wrote in message news:42b72d33$0$1357$(E-Mail Removed)...
Vanguard schreef:

"Han Lubach" &lt;(E-Mail Removed)&gt; wrote in message news:42b6cc79$0$1378$(E-Mail Removed)...

When&nbsp;&nbsp; had cable there were no problems with downloading and uploading torrent files.
But now I have a asdl modem and router and now the upload stays very low.
I will explain te situation

Internet&nbsp;&nbsp;&nbsp;&nbsp; ----&gt;&nbsp;&nbsp;&nbsp;&nbsp; asdlmodem&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp ;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ------&gt;&nbsp; one pc
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n bsp;&nbsp; ext ip address 82.168.202.249&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp ; ip 192.172.1.33

Now the same situation but with router and two pc's
Internet&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; ---------&gt;asdl modem-------------&gt;router ------------------&gt; two pc's
ext ip address 82.168.202.249&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ip 192.172.1.33 ip 192.168.2.100 and 101

he question is what to configurate the modenm or the router and whit what kind of address so i will be seen by the Net

Han Lubach

That isn't the problem the torrent users can not see me so i have to do something with portforwarding or port triggering to make me visible but the problem is where to do this router or modem anfd what kid of addresses

Han

Cable broadband is asynchronous regarding upload and download speed, as well as for aDSL (hence the "a" in that acronym).&nbsp; Cable and DSL differ not only in download speed (which is fastest) but also in upload speed (which is slowest).&nbsp; Did you compare the "promised" upload speed between your cable and DSL providers?&nbsp; Could be the upload speed with DSL is severely less than what you had with cable.



You need to port forward to a static IP address.&nbsp; Whether you do that in the router or not depends on your router.&nbsp; Some will let you assign a specific and static IP address in their DCHP server based on the MAC address of the target host.&nbsp; Then you can define port forwarding in the router to go to a specific IP address because that IP address is always assigned by the router's DHCP server to go to the same host with that MAC address.&nbsp; Some routers don't permit assigning static IP address by MAC address in their DHCP server, so you have to go to the host and configure its TCP properties to use a static IP address (not in the same range as the DHCP server for the router) instead of DHCP.

You might also have to configure a rule in the router for that forwarded port.&nbsp; Normally the router's firewall will allow inbound connects if there was an outbound request to match with it; i.e., the router's firewall will normally block unsolicited inbound connects.&nbsp; However, your P2P software probably has to accept unsolicited inbound connects. Since those connects come from an indefinite number of external hosts with varying IP addresses, you cannot filter the inbound connects based on their IP address.

Since P2P program punish their users that don't actually share their bandwidth, that is why you got the slow file transfer speeds.&nbsp; You need to open you router to grant access to your intranetwork host (and hence the loss of security by punching holes in your router's firewall).&nbsp; You could configure your P2P host into a DMZ if the router supports that. As to what you can, well, that depends entirely on WHAT is your router which was never identified.
Sweex broadband router

the ipconfig give these results
ipaddress 192.168.2.100
subnet mask 255.255.255.0
Standard gateway 192.168.2.1

the router these
ipaddress 192.168.1.33
subnet mask 255.255.255.0
default gateway 192.168.1.254
mac address 00.02.44.36.AA.5A
primary dns 192.168.1.254

Zyxel prestige modem
IP Address: 82.168.202.49 IP Subnet Mask: 255.255.240.0 Default Gateway: 82.168.207.254

So you see i am lost in what to forward

"Han Lubach" <(E-Mail Removed)> wrote in message
news:42babd93$0$1339$(E-Mail Removed) .nl...
> Vanguard schreef:
> "Han Lubach" <(E-Mail Removed)> wrote in message
> news:42b72d33$0$1357$(E-Mail Removed) .nl...
>
> Vanguard schreef:
>
>
> "Han Lubach" <(E-Mail Removed)> wrote in message
> news:42b6cc79$0$1378$(E-Mail Removed) .nl...
>
>
> When had cable there were no problems with downloading and
> uploading torrent files.
> But now I have a asdl modem and router and now the upload stays
> very low.
> I will explain te situation
>
> Internet ----> asdlmodem ------> one pc
> ext ip address 82.168.202.249 ip
> 192.172.1.33
>
> Now the same situation but with router and two pc's
> Internet --------->asdl
> modem------------->router ------------------> two pc's
> ext ip address 82.168.202.249 ip
> 192.172.1.33 ip 192.168.2.100 and 101
>
> he question is what to configurate the modenm or the router and
> whit what kind of address so i will be seen by the Net
>
> Han Lubach
>
>
> That isn't the problem the torrent users can not see me so i have
> to do something with portforwarding or port triggering to make me
> visible but the problem is where to do this router or modem anfd what
> kid of addresses
>
>
> Han
>
>
> Cable broadband is asynchronous regarding upload and download
> speed, as well as for aDSL (hence the "a" in that acronym). Cable and
> DSL differ not only in download speed (which is fastest) but also in
> upload speed (which is slowest). Did you compare the "promised"
> upload speed between your cable and DSL providers? Could be the
> upload speed with DSL is severely less than what you had with cable.
>
>
>
>
>
> You need to port forward to a static IP address. Whether you do that
> in the router or not depends on your router. Some will let you assign
> a specific and static IP address in their DCHP server based on the MAC
> address of the target host. Then you can define port forwarding in
> the router to go to a specific IP address because that IP address is
> always assigned by the router's DHCP server to go to the same host
> with that MAC address. Some routers don't permit assigning static IP
> address by MAC address in their DHCP server, so you have to go to the
> host and configure its TCP properties to use a static IP address (not
> in the same range as the DHCP server for the router) instead of DHCP.
>
> You might also have to configure a rule in the router for that
> forwarded port. Normally the router's firewall will allow inbound
> connects if there was an outbound request to match with it; i.e., the
> router's firewall will normally block unsolicited inbound connects.
> However, your P2P software probably has to accept unsolicited inbound
> connects. Since those connects come from an indefinite number of
> external hosts with varying IP addresses, you cannot filter the
> inbound connects based on their IP address.
>
> Since P2P program punish their users that don't actually share their
> bandwidth, that is why you got the slow file transfer speeds. You
> need to open you router to grant access to your intranetwork host (and
> hence the loss of security by punching holes in your router's
> firewall). You could configure your P2P host into a DMZ if the router
> supports that. As to what you can, well, that depends entirely on WHAT
> is your router which was never identified.
>
> Sweex broadband router
>
> the ipconfig give these results
> ipaddress 192.168.2.100
> subnet mask 255.255.255.0
> Standard gateway 192.168.2.1

External hosts cannot use that private IP address to connect to your
host. You need to supply them the WAN-side IP address of your router.
Somehow your Torrent client has to report the WAN-side IP address of
your router to their server so other Torrent users know to which
external IP address to connect. I don't use P2P software so I don't
know how the Torrent client running on your host could find out what is
the WAN-side IP address of your router (unless you were getting assigned
a static IP address by your ISP).

> the router these
> ipaddress 192.168.1.33
> subnet mask 255.255.255.0
> default gateway 192.168.1.254
> mac address 00.02.44.36.AA.5A
> primary dns 192.168.1.254

That is the LAN side of the router. The IP address on the WAN-side of
the router, the one that it got from your ISP's DHCP server, is what you
need to have your P2P software report to their server as your IP
address. You need the router to forward connects on whatever ports the
Torrent client uses (unless you want to forward from one port on the
router to a different port on the Torrent client host).

> Zyxel prestige modem
> IP Address: 82.168.202.49
> IP Subnet Mask: 255.255.240.0
> Default Gateway: 82.168.207.254

Its external IP address is useless for external requests trying to
connect to your intranetwork hosts.

> So you see i am lost in what to forward

Define a port forwarding definition may include it in the firewall
rules. If not, you need to add a firewall rule that allows unsolicited
inbound connects through that port. Somehow you need to tell your
Torrent client what is the WAN-side IP address of your router.
http://userpages.umbc.edu/%7Ehamilto...entconfig.html might help you
in setting up your Torrent client.

Just to throw some paranoia into the discussion, read
http://www.vitalsecurity.org/2005/06...d-and-175.html.
P2P opens up your system to outsiders. You are also helping others to
distribute porn, some of which is kiddie porn
(http://www.dallasnews.com/sharedcont...02ffe5a6.html).
Since you don't control the content of what passes through your P2P
client, you might even be [re]distributing viruses. You like the
advantages of using P2P but then neglect or disavow any responsibility
in the content delivered by YOUR server. Although there might be some
cooperation between the P2P makers and the police, remember that you are
still legally liable for the content on your computer, so if the cops
find child pornography on your system, you'll be presumed guilty until
you prove your ignorance (yes, your Honor, I really am that stupid).
Besides the security problems with P2P
(http://p2pjournal.com/main/security.htm), there is the problem of the
content being distributed.

Vanguard schreef:

> "Han Lubach" <(E-Mail Removed)> wrote in message
> news:42babd93$0$1339$(E-Mail Removed) .nl...
>
>> Vanguard schreef:
>> "Han Lubach" <(E-Mail Removed)> wrote in message
>> news:42b72d33$0$1357$(E-Mail Removed) .nl...
>>
>> Vanguard schreef:
>>
>>
>> "Han Lubach" <(E-Mail Removed)> wrote in message
>> news:42b6cc79$0$1378$(E-Mail Removed) .nl...
>>
>>
>> When had cable there were no problems with downloading and
>> uploading torrent files.
>> But now I have a asdl modem and router and now the upload
>> stays very low.
>> I will explain te situation
>>
>> Internet ----> asdlmodem ------> one pc
>> ext ip address 82.168.202.249 ip
>> 192.172.1.33
>>
>> Now the same situation but with router and two pc's
>> Internet --------->asdl modem------------->router
>> ------------------> two pc's
>> ext ip address 82.168.202.249 ip
>> 192.172.1.33 ip 192.168.2.100 and 101
>>
>> he question is what to configurate the modenm or the router
>> and whit what kind of address so i will be seen by the Net
>>
>> Han Lubach
>>
>>
>> That isn't the problem the torrent users can not see me so i
>> have to do something with portforwarding or port triggering to make
>> me visible but the problem is where to do this router or modem anfd
>> what kid of addresses
>>
>>
>> Han
>>
>>
>> Cable broadband is asynchronous regarding upload and download
>> speed, as well as for aDSL (hence the "a" in that acronym). Cable
>> and DSL differ not only in download speed (which is fastest) but also
>> in upload speed (which is slowest). Did you compare the "promised"
>> upload speed between your cable and DSL providers? Could be the
>> upload speed with DSL is severely less than what you had with cable.
>>
>>
>>
>>
>>
>> You need to port forward to a static IP address. Whether you do
>> that in the router or not depends on your router. Some will let you
>> assign a specific and static IP address in their DCHP server based on
>> the MAC address of the target host. Then you can define port
>> forwarding in the router to go to a specific IP address because that
>> IP address is always assigned by the router's DHCP server to go to
>> the same host with that MAC address. Some routers don't permit
>> assigning static IP address by MAC address in their DHCP server, so
>> you have to go to the host and configure its TCP properties to use a
>> static IP address (not in the same range as the DHCP server for the
>> router) instead of DHCP.
>>
>> You might also have to configure a rule in the router for that
>> forwarded port. Normally the router's firewall will allow inbound
>> connects if there was an outbound request to match with it; i.e., the
>> router's firewall will normally block unsolicited inbound connects.
>> However, your P2P software probably has to accept unsolicited inbound
>> connects. Since those connects come from an indefinite number of
>> external hosts with varying IP addresses, you cannot filter the
>> inbound connects based on their IP address.
>>
>> Since P2P program punish their users that don't actually share their
>> bandwidth, that is why you got the slow file transfer speeds. You
>> need to open you router to grant access to your intranetwork host
>> (and hence the loss of security by punching holes in your router's
>> firewall). You could configure your P2P host into a DMZ if the
>> router supports that. As to what you can, well, that depends entirely
>> on WHAT is your router which was never identified.
>>
>> Sweex broadband router
>>
>> the ipconfig give these results
>> ipaddress 192.168.2.100
>> subnet mask 255.255.255.0
>> Standard gateway 192.168.2.1
>
>
> External hosts cannot use that private IP address to connect to your
> host. You need to supply them the WAN-side IP address of your router.
> Somehow your Torrent client has to report the WAN-side IP address of
> your router to their server so other Torrent users know to which
> external IP address to connect. I don't use P2P software so I don't
> know how the Torrent client running on your host could find out what
> is the WAN-side IP address of your router (unless you were getting
> assigned a static IP address by your ISP).
>
>> the router these
>> ipaddress 192.168.1.33
>> subnet mask 255.255.255.0
>> default gateway 192.168.1.254
>> mac address 00.02.44.36.AA.5A
>> primary dns 192.168.1.254
>
>
> That is the LAN side of the router. The IP address on the WAN-side of
> the router, the one that it got from your ISP's DHCP server, is what
> you need to have your P2P software report to their server as your IP
> address. You need the router to forward connects on whatever ports
> the Torrent client uses (unless you want to forward from one port on
> the router to a different port on the Torrent client host).
>
>> Zyxel prestige modem
>> IP Address: 82.168.202.49
>> IP Subnet Mask: 255.255.240.0
>> Default Gateway: 82.168.207.254
>
>
> Its external IP address is useless for external requests trying to
> connect to your intranetwork hosts.
>
>> So you see i am lost in what to forward
>
>
> Define a port forwarding definition may include it in the firewall
> rules. If not, you need to add a firewall rule that allows
> unsolicited inbound connects through that port. Somehow you need to
> tell your Torrent client what is the WAN-side IP address of your
> router. http://userpages.umbc.edu/%7Ehamilto...entconfig.html
> might help you in setting up your Torrent client.