[NCLUG] permanent IP addresses on a home LAN?

Stephen Warren swarren at wwwdotorg.org
Wed Aug 1 09:53:48 MDT 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

dlc at frii.com wrote:
>   Perhaps the quick and easy way to accomplish this is to just set your
> systems up with a fixed IP address and ignore the DHCP.  Since DHCP
> seems to assign starting with the low numbers first...

Benson Chow wrote:
> Don't overlook the cheesy way out: hardcode IP addresses of machines
> that you normally ssh to.  ...  DHCPds should
> automatically avoid 'used' addresses if they're implemented
> correctly - I've seen a lot of implementations from scanning the
> subnet to simply  checking the IP for a response before assignment.

Ick. Both of the above sound like relying on the internal implementation
details of the DHCP server in question, which will soon lead to problems
once the DHCP server is changed out with something else.

Fortunately, there's a simpler way that seems to be implemented on even
the most simple DHCP servers I've seen - i.e. if you have 192.168.1.0/24
as your network, tell the DHCP server to assign e.g.
192.168.1.32-192.168.1.64, and hard-code your static IPs outside this
range, e.g. 192.168.65-192.168.128. This will guarantee that there's
never a clash.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGsKyMhk3bo0lNTrURArYKAKCSWhDuO8oxgeO3VZjyBlX9sCtEZgCeK4km
y6FN1xwmIXFbKNjZdK0vzMA=
=lIEU
-----END PGP SIGNATURE-----



More information about the NCLUG mailing list