ip address on lan getting hijacked

[Derek Broughton]

Bart Silverstrim wrote:

> OR you do it the way I do it here...
> 
> You have a home router with DHCP. You set the router to a set address,
> like 192.168.1.1. You tell the DHCP configuration part of the firmware
> to hand out a bank of addresses at a particular point, like, say,
> 192.168.1.100 to 150 or 200. You *statically assign* addresses to key
> devices...printers, your primary workstations, etc...in another "bank",
> like 192.168.10 to 20 for printers, and 20 to 99 for your workstations,
> only you don't use them in the DHCP server at all. You put them on the
> devices themselves.

Yeah, but he's doing that and he's still ending up getting a DHCP assigned
address.

> The DHCP can handle just your transient devices. Keep organized banks of
>   IP's set aside to assign *on the devices* you're not going to change
> so you can keep track of them and not have to reconfigure a new router
> if something happens to them, as inevitably happens to home/SOHO

Reconfigure?  Don't you have backups of the settings?  Get a Linux router,
and treat it just like your PCs.  If mine fails, I'll just drop the config
files from this one onto the next one.

-- 
derek