DHCP OFFER issues (to relay client)

Glenn Satchell Glenn.Satchell at uniq.com.au
Tue Jun 26 13:31:45 UTC 2007


What filtering are you using on your packet capture? It may be that the
responses are being sent, but not captured in your trace.

A full decode of oneof the discover packets might also suggest something.

regards,
-glenn

>From: "Tim Preston" <Tim.Preston at vecimanetworks.com>
>
>LOL - thought you would ask that... it's a proprietary router/radio I'm doing 
integration testing and research for; Waverider CCU3100. As mentioned, the relay 
works fine with other makes of DHCP server software.
>________________________________
>
>From: dhcp-users-bounce at isc.org on behalf of Gideon Viator
>Sent: Mon 25/06/2007 10:19 AM
>To: dhcp-users at isc.org
>Subject: RE: DHCP OFFER issues (to relay client)
>
>
>
>Tim,
>
>What device is relaying the DHCP requests?
>
>Gideon Viator
>IT Administrator
>Kaplan Telecommunications
>337-643-7171
>
>
>
>-----Original Message-----
>From: dhcp-users-bounce at isc.org [mailto:dhcp-users-bounce at isc.org] On Behalf
>Of Tim Preston
>Sent: Monday, June 25, 2007 10:58 AM
>To: dhcp-users at isc.org
>Subject: DHCP OFFER issues (to relay client)
>
>Hi there - I'm new to the list so I hope I'm using it right ; ) - sorry for
>the length!
>
>I'm trying to get DHCPd version 3.0 hand out IPs to hosts through a relay
>client. Other DHCP servers (Windows, Cisco, HaneWin) have no problem doing
>this with the exact same network config, so I figure I must be doing
>something wrong with ISC DHCPd.
>
>My config is simple:
>
>------------192.168.1.x/24------------
>        |                                  |
>    DHCPd                 DHCP relay agent
>(192.168.1.205)        (192.168.1.100 eth0)
>                               ( 3.11.1.254 eth1)
>                                           |
>                      -------------3.11.1.x/24---------------
>                                           |
>                                   DHCP client
>
>Everything can ping everything else with the DHCP client configured staticly
>with a 3.11.1.x/24 address.
>
>dhcpd.conf is even simpler:
>----------------------------------------------------------------------------
>---------------------------
>subnet 192.168.1.0 netmask 255.255.255.0 {
>}
>
>subnet 3.11.1.0 netmask 255.255.255.0 {
>   option routers 3.11.1.254;
>   option subnet-mask 255.255.255.0;
>   range 3.11.1.1 3.11.1.9;
>}
>----------------------------------------------------------------------------
>---------------------------
>
>At the Linux box, the DHCP DISCOVER is being received:
>Jun 25 10:42:34 dualboot dhcpd: DHCPDISCOVER from 00:90:c8:61:1c:1e
>(eum61-1c-1e) via 3.11.1.254
>
>...and subsequently answered with a DHCP OFFER (so it says):
>Jun 25 10:42:34 dualboot dhcpd: DHCPOFFER on 3.11.1.9 to 00:90:c8:61:1c:1e
>(eum61-1c-1e) via 3.11.1.254
>
>However, a packet capture on the Linux switch port shows no sign of the
>offers DHCPd says it's sending out; only 'discovers':
>
>
>
>No.     Time        Source                Destination           Protocol
>Info
>      1 4.688431    3.11.1.254            192.168.1.205         DHCP
>DHCP Discover
>
>      2 4.823431    3.11.1.254            192.168.1.205         DHCP
>DHCP Discover
>
>      3 4.993382    3.11.1.254            192.168.1.205         DHCP
>DHCP Discover
>
>
>
>Has anyone run across this before??
>
>
>
>Thanks,
>
>Tim
>
>
>
>
>
>
>
>
>
>
>
>


More information about the dhcp-users mailing list