The only proper way to deal with a squatter is find them and kick them off
the net. You can eliminate the ability for others to do this kind of damage
by being on a separate VLAN than the person trying to squat on your IP, and
have appropriate anti-spoofing on the router. However that is a (somewhat)
extreme way to avoid this issue and not one that we are willing to do on a
regular basis at the current time.
From: MSU Network Administrators Group [mailto:[log in to unmask]] On
Behalf Of David McFarlane
Sent: Thursday, February 26, 2009 4:30 PM
To: [log in to unmask]
Subject: Re: [MSUNAG] How to force a new IP address from DHCP?
>Perhaps someone from Hostmaster could offer more specific details, but
>my understanding is that those IPs will be a subset of the DHCP assigned
>For example each building has a dedicated DHCP range(s). Out of that
>dedicated range, you could specify a few machines that would always get
>same IPs from campus DHCP.
OK, but I still must be missing something. Suppose Hostmaster
assigns the range 184.108.40.206-220.127.116.11 for just one set of rooms
in our building. What stops a rogue in our building, or even from
that very set of rooms, from grabbing, say, 18.104.22.168 for their
static IP, and thereby creating a conflict with the rightful dynamic
user of that IP?