4 replies
Dear Friend
you can do it with Linux with MCA Address Filtering
Niladri
by sbotsford
I strongly recommend that you split your production system from your test system by using different subnets.
If you have a problem in your test system, it has less effect on your corporate environment.
It doesn't take much extra hardware to do this. You can either dual home your dhcp server, adding another card, or you can add a second server just for the test group.
I do all of my dhcp services with static addressing. It's a touch trickier to set up, but since IP maps to a constant host archival log files have a lot more meaning. And when I'm dealing with the switches, which work by IP and MAC only, I don't have to keep looking up the IP.
At present my setup has:
1 server that is dual homed. One line connects to the "quarantine switch" This server has all my installation files on it, but does not bridge between the Q switch and the rest of the network. I plug into this switch when I'm doing an install, so that it cannot get infected while installing. (I had a nasty network worm here last month -- average clean time was under a minute.)
Regular machines get a fixed IP for the reasons mentioned above.
Any other machine connecting to the network gets a dhcp address from a small pool. That pool of addresses cannot access either our servers, except for certain read only shares, nor the internet.
In this way, no one can casually connect their laptop to my network and do something nasty.
I'm considering setting up my switches to be in 'disable on changed mac' so that if someone tried to set up their machine to mimic an existing machine, but didn't also mimic the mac address it would get caught.
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending