Dynamic IP, port fowarding...

[blackspawn]

Hey, a piolet user presented a problem to me that I wasn't able to resolve so I though I would access the great resource that is PCTT
Anyway the problem is this: In order to connect to mp2p network one needs to open a few ports (udp and tcp/ip) that's all fine and dandy, but what is someone supposed to do when the router attributes different IPs to one's computer (the Private IP) everytime you reboot? How can I do port fowarding knowing that my IP isn't always the same?

The router is a SpeedStream 5667 DSL Router.
User's Guide (pdf)

Edit: Sorry for the bad link, its working now.

[greffov]

uhm that user's guide doesn't work for me...

you got to forward some ports, if you're lucky you got a web based tool with your router to do that.

[Pasty901]

Routers should assign each machine a static ip thats usually how it works but i know of a program which will update every time u get a new ip and masks it with a host, its called No-ip, i use if myself
Can be found here: http://www.no-ip.com/index.php?sid=4...10f4fa90fd4864
Its free to sign up too!

[blackspawn]

Originally posted by Pasty901
Routers should assign each machine a static ip thats usually how it works but i know of a program which will update every time u get a new ip and masks it with a host, its called No-ip, i use if myself
Can be found here: http://www.no-ip.com/index.php?sid=4...10f4fa90fd4864
Its free to sign up too!

humm I've check no-ip's webpage but I don't think it will solve the problem. The thing is that the router is attributing diferent IP's after reboot so it's impossible to know the IP which to set port fowarding (cause it constantely changing). This No-IP prog is for public IP only, it doesn't work for Private IPs (which are assigned by the router).
What I want to know is if it's possible to make the router assign a static IP adress or if there is someway of doing port fowarding for a range of IPs...

Would it work If I set port fowarding for EVERY IP the router can atribute? (somehow I don't think this is the only option... this would create an insane amount of rules...)

[Cirga]

Blackspawn,

Most routers out there reserve a certain range of IP addresses to be used for static IP's.

If you look in your router setup it will show the range of IP's that are being used for DHCP each time your PC boots up.

The only way to fix this problem is to put your PC on a static IP address. Which means you need to do the following:

Boot up your PC and open a Dos Command Prompt. You can do this by going to Start > Run > cmd. Once the prompt is open type in ipconfig /all. This will list the following things which you should write down:

Gateway, Netmask, Primary DNS, Secondary DNS

Once you have that written down you need to find out what IP address you are aloud to use. Remember that on a default setting a router will use a scheme such as:

192.168.1.
10.10.10.

This is a full Class C or in otherwords 256 IP address (254 Useable).

If your DHCP address range is going from 192.168.1.101 - 254 then you are safe to use any ip address from 192.168.1.10 - 99.

Now you need to go to your control panel in Windows and open the networking panel. Find your TCP/IP local area connection and go to the properties. Then go to your Properties on the TCP/IP protocol. Once you are in there check the radio button that says "Specify IP address". Enter in all the fields it asks for. That is what you will need the info you wrote down for.

Then when you set your port forwarding you will always know what IP address you are set up on.

If you get lost just snag me in IRC or here

[greffov]

more beautiful solution: make static DHCP records, so your computer always gets the same IP from the DHCP server That way you can keep auto settings...

Cirga's solution works fine though.

[blackspawn]

Thanks for all the help, I'll try your solution Cirga (when I can... exams now have my undevoted attention...).

[blackspawn]

Well I tried your solution but somewhow the user wasn't able to connect, it doesn't seem to be the router problem... Anyway thanks for all the help (eh eh I can know make a static private IP )

[leopold]

Just a small thing that I think I'm not getting here...

You've set up the router to forward the ports for Piolet to your PC, yes? You shouldn't need a static address for that, all you need to do is tell your router to allow traffic on those ports and all should be well. It shouldn't need to pass the traffic to a specific IP address, as the NAT on the firewall will modify the socket (combination of IP and port) to work with it. I used Piolet quite successfully by just opening the ports on the router without any sort of forwarding.

Looking at your manual, it looks like that option (which is available on my Belkin and Linksys routers) isn't that configurable. You could try playing with the firewall settings.

[Cirga]

If you put the router up correctly blackspawn.. then it is something else blocking it. If they are using Windows XP it could be the XP Personal firewall. If its ZoneAlarm then you have to have it set at medium instead of High under firewall or it wont let Piolet connect either.

You did forward UDP 41170 correct?

[blackspawn]

Yes I explained "step-by-step" on how to open the ports (41170 UDP and the TCP/ip ports needed to download, the ones in piolet settings). But she (the user) told me her router gave her a diferent IP adress everytime she rebooted, and since from the default config the router's DHCP is set to attribute a range of IP's and in the port fowarding menu one needs to put an IP (... hummm this IP, needed to configure the port fowarding menu, is the machine's IP right? the Private IP? attributed by the router by DHCP... isn't it?) I thought the problem was the IP setting on the port fowarding set up.

She said XP's firewall was disabled... Anyway since I can't mess around with the settings (I have to PM all the intructions) I gave her pctechtalk's IRC adress and piolet's too so she *might* just come your way (or not)