Static IP addresses

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › Static IP addresses

Rickles

3109 posts

Uber Geek
+1 received by user: 448

Trusted

#136745 7-Dec-2013 16:57

I've noticed that both a router and individual devices on the network can be used to define a static IP address.

For example, my NAS can be set to have a static address (e.g. xxx.xxx.1.x), and the (DHCP on) router also can be set to reserve this address for that particular device, yet both settings appear to do the same job.

Is there any benefit in setting both devices (sort of doubling up), or just using one of them (and which one)?

R.

chevrolux

4962 posts

Uber Geek
+1 received by user: 2638
Inactive user

#947150 7-Dec-2013 17:22

If you set a static address on the device it won't look for DHCP when starting.

I personally prefer to use static DHCP mappings for devices that require a static address. It's just simpler to manage overall if there are a lot of them.

At the end of the day each method does the same thing it's just what you prefer. Some times though DHCP is required to include things like option 66 for example - not likely in the home network though.

Zeon

3926 posts

Uber Geek
+1 received by user: 759

Trusted

#947164 7-Dec-2013 17:50

I would recommend a DHCP mapping as its easier to manage. I use that at work for things like printers, security cameras etc. Not a good idea for a critical system though as it will go offline if the DHCP server fails.

IPv6 SLAAC is where its at, every device by its nature has a unique address.

Speedtest 2019-10-14

Rickles

3109 posts

Uber Geek
+1 received by user: 448

Trusted

#947179 7-Dec-2013 18:20

Thanks guys.

R.