9 replies to this topic

[King Mustard]

I want to use DMZ mode but my IP address seems to change every few days (only the last two digits, e.g. 192.168.1.78), which stops DMZ mode working.

How can I stop my IP address from changing?

[+littleneutrino]

Internal IP you can just setup a static IP address on your computer, or do it on the router. with Windows 7 it is very easy, go into the properties on your network adapter and manually enter a static IP address.

Attached Images

• 

[Biohead]

If its an internal network address, set either a static ip within the device itself, OR use the DHCP reservation table in the router to reserve a certain IP address for the device in question as it will identify its MAC address.

[SuperKid]

I'd do it in the router though by assigning an IP to your Mac address so you don't get any IP conflicts.

[Detection]

littleneutrino, on 29 December 2012 - 14:54, said:

Internal IP you can just setup a static IP address on your computer, or do it on the router. with Windows 7 it is very easy, go into the properties on your network adapter and manually enter a static IP address.

^^ This

SuperKid, on 29 December 2012 - 14:55, said:

I'd do it in the router though by assigning an IP to your Mac address so you don't get any IP conflicts.

DHCP shouldn't assign an IP to any device if another device on the network has that IP, be it static or Automatically Assign

I have static on my PC and Automatic on just about everything else and never get a conflict

[King Mustard]

I just found an tick box on my router that says "Always use the same IP address".

I'll use that

[+BudMan]

"DHCP shouldn't assign an IP to any device if another device on the network has that IP, be it static or Automatically Assign"

It shouldn't no - but its a VERY VERY BAD idea to setup static IPs on the host that fall within the dhcp scope.

So for example if your dhcp server hands out 192.168.1.100 to .150, and you want to setup a static on the host itself then it is better option to use 192.168.1.1 to 99, or .151 to .254

Keeping in mind whatever other statics you might have set, your routers static IP, etc.

Yes depending on your dhcp server and and even dhcp client, you should not hand out dupe IPs. Your dhcp server could check for them before it hands out, or even the client when gets an offer for specific IP can check to see if any other host has that IP and then send the dhcp server a decline message

DHCPDECLINE
Sent by a client to a specific server in response to a DHCPACK message, which contain parameters which the client has determined are not in fact valid. For example, the client might test an IP address it has received by sending an ARP (Address Resolution Protocol) message on its shared LAN to see if any other host has been assigned this address; if it discovers that another host is in fact using this address, it must send a DHCPDECLINE message to the server which supplied the address. This both allows the server to release the resources it has allocated to this client, and inform a system administrator of the problem. (Such a problem might arise in a situation in which a host has been manually configured by an administrator with an IP address, but the DHCP server hasn’t been informed that this address is no longer available in its pool. Though it is suggested that a server test an address before allocating it to a client [1, section 3.1, point 2], for example by “pinging” the address to see if another host is using it, it may be that the test or the response to it is lost, incorrectly suggesting to the server that the address is available.)

But not all dhcp clients support this, nor do all dhcp servers -- the dhcp servers in soho routers are normally very limited in features, etc..

Normally its a better idea to setup a reservation on your dhcp server to always hand out same IP to host normally based on its mac yes. This way host can get other updated info you might hand out in dhcp, dns, gateway, local domain, ntp server, etc. etc. But either works be it you set the static on the host or setup a reservation.

[Detection]

BudMan, on 29 December 2012 - 16:51, said:

"DHCP shouldn't assign an IP to any device if another device on the network has that IP, be it static or Automatically Assign"

It shouldn't no - but its a VERY VERY BAD idea to setup static IPs on the host that fall within the dhcp scope.

So for example if your dhcp server hands out 192.168.1.100 to .150, and you want to setup a static on the host itself then it is better option to use 192.168.1.1 to 99, or .151 to .254

Keeping in mind whatever other statics you might have set, your routers static IP, etc.

Yes depending on your dhcp server and and even dhcp client, you should not hand out dupe IPs. Your dhcp server could check for them before it hands out, or even the client when gets an offer for specific IP can check to see if any other host has that IP and then send the dhcp server a decline message

DHCPDECLINE
Sent by a client to a specific server in response to a DHCPACK message, which contain parameters which the client has determined are not in fact valid. For example, the client might test an IP address it has received by sending an ARP (Address Resolution Protocol) message on its shared LAN to see if any other host has been assigned this address; if it discovers that another host is in fact using this address, it must send a DHCPDECLINE message to the server which supplied the address. This both allows the server to release the resources it has allocated to this client, and inform a system administrator of the problem. (Such a problem might arise in a situation in which a host has been manually configured by an administrator with an IP address, but the DHCP server hasn’t been informed that this address is no longer available in its pool. Though it is suggested that a server test an address before allocating it to a client [1, section 3.1, point 2], for example by “pinging” the address to see if another host is using it, it may be that the test or the response to it is lost, incorrectly suggesting to the server that the address is available.)

But not all dhcp clients support this, nor do all dhcp servers -- the dhcp servers in soho routers are normally very limited in features, etc..

Normally its a better idea to setup a reservation on your dhcp server to always hand out same IP to host normally based on its mac yes. This way host can get other updated info you might hand out in dhcp, dns, gateway, local domain, ntp server, etc. etc. But either works be it you set the static on the host or setup a reservation.

Thanks for the explanation, just realised that I have done exactly that, DHCP from .100 with maximum 50 clients, main PC static on .3

Also running DD-WRT so hopefully had I not done that, would have been slightly more advanced than the average firmware and managed to avoid my static

[+Crisp]

As mentioned already, you need to give your device in the DMZ a static address.

What are you putting in your DMZ? Game console?

[+remixedcat]

My router has something called "static DHCP" accessed from the following RCP area:
More settings>Network Settings>LAN settings>Set Static DHCP>

It has the following options:

• IP Address:
  
• MAC Address:
  
• Comment:

Quote

Description: Reserve an IP address for a specific user. Enter the IP Address that you would like to use and enter the MAC Address for the user that will be associated to this IP address .