Bill Moran 写道:
I have followed Jeffrey's suggestion and reconfigured dhcpd.conf to make
sure no host with specified IP address is within dynamic assigned IP
range. I was mislead by my previous experience with Microsoft DHCP
server configuration where a host with fixed IP address should be within
the range. After updated dhcpd.conf I haven't see an IP conflict yet,
I'll watch a few days.
In response to Zhang Weiwu <[EMAIL PROTECTED]>:
P.S. In recent days we some times got another network problem and I'm
not sure if it's related to this DHCP server behavior. It happens on
both Linux and Windows hosts that a host suddenly is no longer
accessible (Ping no response). Check 'arp -a' on other hosts shows the
host being accessed have wrong Mac Address. e.g. yesterday
22.214.171.124 suddenly become in-accessible, this host is Linux and we
got this behavior on a nearby host:
sappho # arping 126.96.36.199
Unicast reply from 188.8.131.52 [00:0F:EA:4B:82:58] 0.638ms
Unicast reply from 184.108.40.206 [00:0F:EA:4B:82:58] 0.637ms
Sent 113 probes (1 broadcast(s))
Received 113 response(s)
sappho # arp -a 220.127.116.11
? (18.104.22.168) at 00:02:2A:C1:53:87 [ether] on eth0
arping reply is different from arp cache. This host become accessible
the next day. Strange. Are these two problems related?
You have something seriously wrong somewhere. They may be related but
there's not enough information here to be sure. Consider installing
arpwatch on one or more systems and see if the reports it sends narrow
down the problem.
For the ARP issue, thanks for suggesting arpwatch. I'd like to take a
deeper look into how ARP works later. Thanks!
email@example.com mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"