On Thu, Apr 29, 2010 at 8:54 AM, Andrew McNabb <[email protected]> wrote:
> On Wed, Apr 28, 2010 at 09:30:36PM -0600, Aaron Toponce wrote: > > > > Any network engineer worth his salt better be able to locate one > > extremely quickly, and cut it from the network, until the one in charge > > of the rogue box has disabled it. After all, it isn't that difficult to > > chase a cable from the port in question on the switch to the box running > > the rogue DHCP server. > > It's not always that simple. I had one time where the rogue DHCP server > was giving out correct information for almost everything. The only > thing it was getting wrong was next-server, so certain machines weren't > PXE booting correctly. Sure, sometimes it's easy to track down a rogue > DHCP server, but at times the effects can be incredibly subtle. > I think I remember that..... :P James -- "And very early in the morning the first day of the week, they came unto the sepulchre at the rising of the sun..." (Mark 16:2) Web: http://james.jlcarroll.net
-------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list
