Anyone here use DHCP?

  • Thread starter Thread starter Deleted member 651465
  • Start date Start date

Deleted member 651465

Deleted member 651465

Hey all,

I've always used static ips on my networks, but recently I'm getting bored with the effort of adding devices to the network so I'm considering switching back to DHCP (with static modem and access point, of course! :p)

Am I in the minority by using static IPs?
 
Use both - my main machine / NAS / Xbox etc all use static then allocate a small DHCP range so the little things like mobile and kids laptops etc can all jump on as and when
 
I'd say so, even where I use static I use reservations rather than hard coding and I have public IPs for everything in my home office. May be unique to me - I use laptops primarily these days and going to a different site and having to reconfigure my network card is just annoying and silly, static reservations fix that and allow me to use DHCP elsewhere without any hassle.
 
EVH said:
Am I in the minority by using static IPs?
Click to expand...

Yes.

Use DHCP and then add in static reservations for the computers that you want to have static IP's :)


Having said that... I'm not even running NAT, this network setup is so old it's hilarious :o
 
Ok guys, great.

Will configure some static reservations later. Also want to jig the modem IP around (not liking 192.168.1.254) and start again.

:cool:
 
bit of both, dhcp for laptop and phones, static for the rest. As said, it's a pain going somewhere else and the laptop not liking it...
Not really bothered with static reservations, still on a BT Homehub and the dns is pants, with static ip's at least it resolves most times...
 
I tend to use (in small setups)

.254 as the DG / internet router
.253 and down as additional routers

.220 as static for printers (2nd, 3rd etc printers will be .221,.222 etc)

.200 for the server or nas box (201, 202 etc if there are several)

dhcp .10 - .199 (leaving the first few free for no real reason, some times a new device will start as .1 static (if you used a common range)
.
 
Some routers will allow Static DHCP (not always called this)

This means normal DHCP for most clients, and you can specify certain MAC addresses to be assigned a static IP. This means all of the config is done on the router side, so no need to manually enter IP details on any of the machines. Quite a neat feature, all network machines have their IP config set as Auto.

If you don't have this feature, just set your DHCP range from 1-50 or something, and then manually assign from 51 upwards on each client that you want a static IP for
 
paradigm said:
Why?

Pretty standard to have your gateway at .254
Click to expand...

I always used to think that, but increasingly you see gateways at .1 or .2.

I think the idea behind it is that if you need to split the subnet at a later date it would be harder if your hosts are under .128 and you gateway is over .128.
So keeping everything under .128 means it can be split later.
 
PistolPete said:
I always used to think that, but increasingly you see gateways at .1 or .2.

I think the idea behind it is that if you need to split the subnet at a later date it would be harder if your hosts are under .128 and you gateway is over .128.
So keeping everything under .128 means it can be split later.
Click to expand...

Much of a muchness, most routers/switches support multinetting and if you have more than 128 hosts or you don't want to split 50:50 you'll have problems anyway. Keeping it relevent to the OP, dishing gateways out via DHCP makes this a non issue :)

One of the subnets here was set up by a software solution vendor initially. Server was at .1 and gateway was at .100! and still is because routers don't support multiple interface IPs within the same subnet and there's some Diagnostic imaging kit statically assigned that we can't change. :(

Moving to 172. from 10. soon though so will all be back to OCD pleasing order :)
 
Static for the NAS and Wireless AP but then just have DHCP starting from .10. Don't see the point or need for having static on the computers/consoles/freesat box.
 
DHCP with long reservations. I also have IPv6 where the same nic can have multiple addresses - so I have some static addresses in addition to the autoconfigured on those nics. fe80::1, fe80::2 etc is easy to remember and quick to type.
 
bledd. said:
Some routers will allow Static DHCP (not always called this)

This means normal DHCP for most clients, and you can specify certain MAC addresses to be assigned a static IP. This means all of the config is done on the router side, so no need to manually enter IP details on any of the machines. Quite a neat feature, all network machines have their IP config set as Auto.

If you don't have this feature, just set your DHCP range from 1-50 or something, and then manually assign from 51 upwards on each client that you want a static IP for
Click to expand...

This is spot on. I've worked this way for last few years, its great cuz when you take your 'statically assigned' devices (configured on your router) to another location you don't need to configure them again (if there is a dhcp on the destination network that is).
 
I've set static IPs for all the permanent desktops/laptops in the house, including the printer. But DHCP is is still turned on for friend's/guest's WiFi needs.
 
dhcpj.png


Here we go.

Assigned static IP reservations for the HP switch and Wi Fi access (AirPort Extreme), all the rest are left to auto assign until I get all the computers up and running.

:)
 
You must log in or register to reply here.
Back
Top Bottom