ip address on lan getting hijacked

[Rashkae]

chris dunn wrote:
> On Sat, 31 May 2008 23:48:53 -0300S Derek Broughton <news at pointerstop.ca> 
> wrote:
> 
> 
>> chris dunn wrote:
> 
>>> All works well until 9.30 a.m. every morning when 192.168.1.2 is taken
>>> down and reset to 192.168.1.100, apparently by dhclient accessing the dhcp
>>> server running on the wap. Any nxclient connections crash as the nxserver
>>> ip address has changed.
> 
>>> To those suggesting a change to dhcp from static addresses, I don't think
>>> this is a workable option for me, unless maybe going into the router and
>>> linking machine names to the mac addresses is the way to go. I need to
>>> know the addresses of the machines on the lan.
> 
>> That's exactly why you link IPs (not names) to MAC addresses.
>> --
>> derek
> 
> Removing dhclient (and dhcdbd) from the box seems to have cured my problem. At 
> 9.30 a.m. on Sunday there was no connection breaking event, and no messages 
> in syslog.
> 

I'm glad you were able to get your system running.. however, removing
dhclient, generally an essential component of the network stack, is
somewhat like cutting off your left hand to cure a hangnail because you
see no use for your left hand at the moment.

I don't know how you ended up in this situation, but to be clear, having
dhclient and ahavi installed was not the cause the problem.