howtogeek at January 15th, 2014 12:34 — #1
Originally published at: http://www.howtogeek.com/177648/how-to-force-your-pc-to-keep-its-private-ip-address/
There may be times when you need your PC to retain the same local IP address every time it boots up. Forwarding ports, sharing content on your network, and other things can all be made easier when your computer’s IP address never changes.
iszi at January 15th, 2014 14:10 — #2
A note regarding the older routers which do not support DHCP Reservations: You should probably upgrade your router anyway. Especially with regards to Wi-Fi, these routers very likely have security vulnerabilities which leave your local systems and network traffic open to attack by hackers.
wilsontp at January 15th, 2014 15:38 — #3
I am actually moving away from using reservations, and back to simply assigning IP's outside of my DHCP range. I actually hit the limit on the number of addresses my router would reserve the other day, thanks to the number of virtual machines on my network.
It's easier for me just to add a host to my spreadsheet, then manually assign an IP addres. That way I never have to enter the router's configuration screen.
iszi at January 15th, 2014 17:00 — #4
Why not just NAT the VMs at the host, and use DHCP reservations from there? How many of your VMs really need a reserved IP, anyway?
wilsontp at January 15th, 2014 17:34 — #5
They all do. They're development servers, and I have to connect to them from another PC. THAT PC is also VPN'd in to my office, with its own DNS, so I can't use hostnames to talk back and forth. (Or more correctly, I can, but the hostnames have to resolve to fixed IP addresses.)
The real issue that I was trying to point out is that routers often have a limit to how many hosts you can reserve an address for. Mine turned out to be around 15. That seems like a lot, but when you count all the cell phones, satellite boxes, media players, game consoles, and smart devices in the house (I have a weather forecaster that pulls data off the Internet), it's not hard to end up wit 30 or more IP-enabled devices in the house.
True, they don't all need static IP's. The reason I was reserving most of the IP's was to detect rogue devices.
Now I have fixed IP's for only a few devices:
- My router (no duh there)
- 2 networked printers
- My desktop gaming computer (so I can host game servers)
- VM Server hosting
- Work PC
In all, I have 12 or so things that need fixed IP addresses... so I have stopped reserving the IP addresses for things like my satellite boxes, game consoles, and portable devices.
Yes, it requires management... but you can't set up a complex environment with multiple servers, and multiple VPN's, and not have to do some work to set all that up and maintain it.
iszi at January 16th, 2014 13:49 — #6
I personally maintain a small-ish hardware list for all the devices which are (or recently have been) authorized on my home network, including guests, so I kinda know what you mean about managing the network. 15 is kinda weak for a DHCP reservations cap, though. I'm pretty sure all the ones I've used went up to around 32. That's about the same as the cap on MAC Address filtering, which I'm constantly having to adjust to kick off guests who haven't been around in awhile so new guests can get on.
Here's a thought: So long as you have that much of a home network going anyway, why not set up an actual DHCP server so that you're freed from the limitations of a SOHO router?
wilsontp at January 16th, 2014 14:53 — #7
Mostly because I don't need to. At some point, I'll probably install some sort of computer based router, but at the moment, I'm happy with my setup. I have no problem with manually configuring IP addreses, and the old maxim "if it ain't broke, don't fix it" would tend to apply here.
iszi at January 16th, 2014 15:42 — #8
True geeks heed no such admonishments.
wilsontp at January 16th, 2014 16:58 — #9
True geeks also have a house full of ticked off residents. I learned that lesson years ago.
system at January 25th, 2014 12:34 — #10
This topic was automatically closed after 10 days. New replies are no longer allowed.