Date: Mon, 14 Mar 2005 21:38:52 +0800 From: sam wun <sam.wun@authtec.com> To: freebsd-current@freebsd.org Subject: Re: dhcpdiscover ... not responding. Message-ID: <423593EC.5090106@authtec.com>
next in thread | raw e-mail | index | archive | help
Hi,
I installed another copy (same version) of the isc-dhpcd service to a new freebsd 5.4 PR system. The old server was runnig 5.4 as well. While the isc-dhcpd running perfectly in the old server, but it failed to release IP in the new server. I heard that may be problem wiht freebsd tcp/ip stack, but I m not sure.
I just found out how to prints debug message from dhcpd. Just append a
-d to the end of the dhpcd commandline.
The message shown that dhcpd clearly has problem on a network interface:
failover peer dhcp: I move from recover to startup
failover peer dhcp: I move from startup to recover
DHCPDISCOVER from 00:09:6b:8d:b2:67 via em0: not responding (recovering)
DHCPDISCOVER from 00:09:6b:8d:b2:67 via em0: not responding (recovering)
DHCPDISCOVER from 00:09:6b:8d:b2:67 via em0: not responding (recovering)
...
But I m not able to immediate identify where the problem is. Here is
the ifconfig message:
# ifconfig
xl0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
options=9<RXCSUM,VLAN_MTU>
ether 00:0a:5e:51:9b:b7
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=b<RXCSUM,TXCSUM,VLAN_MTU>
inet 192.168.1.200 netmask 0xffffff00 broadcast 192.168.1.255
inet6 fe80::20e:cff:fe05:8229%em0 prefixlen 64 scopeid 0x2
ether 00:0e:0c:05:82:29
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
fxp0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=8<VLAN_MTU>
inet 192.168.4.200 netmask 0xffffff00 broadcast 192.168.4.255
inet6 fe80::211:11ff:fe0f:9543%fxp0 prefixlen 64 scopeid 0x3
ether 00:11:11:0f:95:43
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
plip0: flags=108810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
pflog0: flags=41<UP,RUNNING> mtu 33208
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6
pfsync0: flags=41<UP,RUNNING> mtu 1348
pfsync: syncif: xl0 maxupd: 128
carp0: flags=41<UP,RUNNING> mtu 1500
inet 192.168.4.1 netmask 0xffffff00
carp: MASTER vhid 1 advbase 1 advskew 0
carp1: flags=41<UP,RUNNING> mtu 1500
inet 192.168.1.1 netmask 0xffffff00
carp: MASTER vhid 2 advbase 1 advskew 0
The isc-dhcpd.sh start up script start with the following option lines:
#! /bin/sh
dhcpd_enable="YES"
dhcpd_ifaces="em0"
dhcpd_chroot_enable="YES"
. /etc/rc.subr
name=dhcpd
paranoia=YES # compiled in paranoia?
jail=YES
..
The dhcpd.conf.master file is written as below:
ddns-update-style none;
one-lease-per-client on;
option domain-name "myhome.com";
option domain-name-servers 192.168.4.254;
option subnet-mask 255.255.255.0;
default-lease-time 600;
max-lease-time 7200;
authoritative;
subnet 192.168.1.0 netmask 255.255.255.0 {
option routers 192.168.1.1;
option broadcast-address 192.168.1.255;
pool {
failover peer "dhcp";
range 192.168.1.20 192.168.1.40;
deny dynamic bootp clients;
}
}
The Windows client is at the em0 side.
Thanks
Sam.
sam wun wrote:
> *** From dhcp-server -- To unsubscribe, see the end of this message.
> ***
>
> Simon Hobson wrote:
>
>
>
>> *** From dhcp-server -- To unsubscribe, see the end of this message.
>> ***
>>
>> sam wun wrote:
>>
>>
>>
>>
>>
>>> I duplicated the dhcpd.conf and dhcpd.conf.master file into another
>>> FreeBSD system, but the same windows client failed to receive any IP
>>> leased from the new server. There is only one thing is different
>>> between the new server with the old server, that is the time zone.
>>> In the new machine it is UTC, but the old one is AU. While my
>>> windows is set to AU, does it matter for a AU windows client request
>>> dhcpd servcie from a UTC server? The previous dhcpd server is
>>> configured in UTC time zone.
>>>
>>>
>>
>> No the time zone does NOT matter.
>>
>> When you say "same windows client failed to receive any IP leased
>> from the new server", what exactly do you mean ? If you are simply
>
>
>
>> going to the client and doing an ipconfig /renew, then it will
>> attempt to contact the server which initially issued the lease to ask
>> for a renewal. IIRC, the same will occur at startup/waking from
>> sleep/bringing up an interface when a cable is plugged in.
>>
>>
>>
>>
>
> I tried a manual setup of the network configuraiton in this Windows
> machine, and verified this Windows system can logoin the new server,
> so it is not the network problem.
>
>
>
>> Only when it has failed to contact the old server and it's lease is
>> almost expired (7/8th of the lease time IIRC) will it start to
>> broadcast to find another server.
>>
>> If you do an ipconfig /release, followed by ipconfig /renew, then it
>> should broadcast for a server.
>>
>>
>>
>>
>
> I have done this many times.
>
>
>
>> If this is not the case, then you'd better post whatever logs the
>> dhcp server is producing.
>>
>>
>>
>>
>
> How can I configure dhcpd print out debug messages?
>
> Thanks
> Sam
>
>
>
>> Simon
>>
>>
>>
>>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?423593EC.5090106>