How do you keep users from stealing other user's ip??
tedm at toybox.placo.com
Sun Mar 26 10:05:57 UTC 2006
The only way you can really lock it down is to statically assign
everything (either with a DHCP server that has a table of mac addresses)
and maintain an accurate list of mac addresses, and use managed switches
that have filtering capabilities.
We do this on bridged DSL networks (except for the managed switch part)
and it's actually a lot easier to manage that most people think.
What you have to do is when a new person hooks into the network,
you give them a test IP address, you ping that, get their MAC for that,
then hard code that into your DHCP server and tell them to switch
over to DHCP to get their permanent address. Once they do that, hard-
code the IP address and mac in the router ARP table, and install a
filter on the switch port going to them that ignores any traffic
that originates from a different MAC than the one that you probed
>From: owner-freebsd-questions at freebsd.org
>[mailto:owner-freebsd-questions at freebsd.org]On Behalf Of Mark Jayson
>Sent: Thursday, March 23, 2006 10:26 PM
>To: questions at freebsd.org
>Subject: How do you keep users from stealing other user's ip??
> We are trying to reorganize our local area network and I need
>some tips on how you are managing your own lan...
> We have a vanilla pc router with interface facing our private
>lan and interface facing the Internet.
> One problem which we are experiencing right now is that any
>user from private lan can use any ip address he wants. If he
>boots his computer with a stolen ip address, the poor owner of
>that machine(not active at the moment) will give automatically
>up his ip address to this user. The same scenario for public ip
>addresses. Basically, we need to track down the users through
>their ip address.. But this is trivial as of now since anyone
>can use any ip he wants. Even if there is a solution out there
>to tie up his mac address to his ip address..(sort of checking
>the mac first before giving him an ip, possibly through dhcp..)
>still, users can just download applications which will enable
>him to change his mac address....
> Now, where thinking about authenticating users before he is
>allowed to use a particular network service(internet proxy,
>mail etc.) because I guess it is a clever way of keeping the
>bad users from doing something bad within your network when
>after all, the reason why he is plugging his lancard to the
>network is to use a particular service. However, it still
>doesn't keep them from playing around and steal other ip
>addresses or mac addresses and thus denying network access to
>those legitimate owners. I'm thinking about tying dhcp with
>authentication, and freeradius comes to mind.. I just need some
>more tips from you. User's workstations are mixed Windows and
>*nixes. Some have laptops with wireless interfaces.
> Any idea how to handle this situations??
>New Yahoo! Messenger with Voice. Call regular phones from your
>PC and save big.
>freebsd-questions at freebsd.org mailing list
>To unsubscribe, send any mail to
>"freebsd-questions-unsubscribe at freebsd.org"
>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.1.385 / Virus Database: 268.3.1/292 - Release Date: 3/24/2006
More information about the freebsd-questions