dhcpd on Solaris 10

Glenn Satchell Glenn.Satchell at uniq.com.au
Mon Apr 27 02:21:18 UTC 2009

Hi Jason

Ok, been testing with dhcp version 4.1.x

4.1.0 does not work for me. I see the dhcpdiscover packets come in,
dhcpd logs that it sent an offer, but nothing further. Using snoop to
capture traffic on udp ports 67 and 68 shows the discovers, but the
offer is not transmitted.

4.1.1b1 does work for me. I think it is this bug that was fixed:

- A bug in DLPI packet transmission (Solaris, HP/UX) that caused the server
  to stop receiving packets is fixed.  The same fix also means that the MAC
  address will no longer appear 'bogus' on DLPI-based systems.

siaddr is zero in all cases. Using the exact same dhcpd.conf in all cases.

So make sure of the version you are using (dhcpd --version).

Also I have smf scipts if you'd like to manage dhcpd that way and I'll
send them to you, or the list if there's more than two enquiries.

# svcs dhcpd
STATE          STIME    FMRI
online         11:57:24 svc:/site/dhcp/server:dhcpd


>Date: Mon, 27 Apr 2009 00:09:09 +1000 (EST)
>From: Glenn Satchell <Glenn.Satchell at uniq.com.au>
>Subject: Re: dhcpd on Solaris 10
>To: dhcp-users at lists.isc.org
>Hi Jason
>I can confirm that dhcp-3.1.2 works for me with Solaris 10 sparc.
>siaddr is zero, client recieves the address ok.
>Can you try setting siaddr using next-server command to see if this
>makes any difference?
> next-server a.b.c.d;
>>Date: Sun, 26 Apr 2009 23:33:38 +1000 (EST)
>>From: Glenn Satchell <Glenn.Satchell at uniq.com.au>
>>Subject: Re: dhcpd on Solaris 10
>>Hmm, interesting. I have Solaris 10 update 6 on sparc 64 bit (Ultra 10,
>>cough), and my clients all seem to work fine when the siaddr is zero.
>>I'm only running 3.1.1 atm, but will upgrade to 3.1.2 to see what I
>>get. I only have 32 bit x86, but I can also try one of those as the
>>>Date: Sun, 26 Apr 2009 09:30:40 +0200
>>>Subject: Re: dhcpd on Solaris 10
>>>From: Jason Penton <jason.penton at gmail.com>
>>>To: Users of ISC DHCP <dhcp-users at lists.isc.org>
>>>X-BeenThere: dhcp-users at lists.isc.org
>>>X-MIME-Autoconverted: from quoted-printable to 8bit by mail.uniq.com.au id 
>>>Hi Glen, *
>>>Solaris x86 64-bit.
>>>Solaris and linux boxes running same version of dhcpd (tested 3.1.2
>>>and 4), same config, and same network segment! Also, made sure that
>>>exactly the same requests were coming in from the clients. I have
>>>eliminated all the 'variables' and at this stage im only left with the
>>>OS. Seems Solaris 10 update 6 is doing something strange.
>>>On Sun, Apr 26, 2009 at 7:49 AM, Glenn Satchell
>>><Glenn.Satchell at uniq.com.au> wrote:
>>>> Hi Jason
>>>> Are you using Solaris 10 on Sparc or x86? 64 or 32 bit?
>>>> regards,
>>>> -glenn
>>>>>Date: Sun, 26 Apr 2009 12:33:51 +1000 (EST)
>>>>>From: Glenn Satchell <Glenn.Satchell at uniq.com.au>
>>>>>You can fill in the siaddr using:
>>>>>  next-server a.b.c.d;
>>>>>in an appropriate scope.
>>>>>What version(s) of dhcpd is running on your linux box? What version are
>>>>>you testing with on the Solaris box?
>>>>>Are there any other options set or not set in the packets you sniff?
>>>>>Is the Linux box on the same segment as the Solaris dhcp server?
>>>>>siaddr is not required to be set to get an IP address. I have Windows
>>>>>XP, 98, Linux and Solaris clients all working with a siaddr.
>>>>>PS Note to everyone, please reply only to the list, I do not need to
>>>>>see the message twice.
>>>>>>Date: Sat, 25 Apr 2009 18:54:08 +0200
>>>>>>Subject: Re: dhcpd on Solaris 10
>>>>>>From: Jason Penton <jason.penton at gmail.com>
>>>>>>To: Users of ISC DHCP <dhcp-users at lists.isc.org>
>>>>>>Cc: Glenn Satchell <Glenn.Satchell at uniq.com.au>
>>>>>>Hi Alan
>>>>>>So why is it that when a client receives an OFFER with a zeroed
>>>>>>siaddr, it never sends out the DHCP REQUEST (as if it was unhappy with
>>>>>>the OFFER). I tested with Windows, linux and solaris clients??????? On
>>>>>>a linux box, the EXACT same code with the EXACT same config (i.e. no
>>>>>>next-server setting) the siaddr is set to the ip address of the DHCP
>>>>>>On Sat, Apr 25, 2009 at 6:39 PM,  <A.L.M.Buxey at lboro.ac.uk> wrote:
>>>>>>> Hi,
>>>>>>>> I'd imagine that on other OS's (linux) the siaddr is set
>>>>>>>> automatically. Seems that on Solaris 10 update 6, it does not.
>>>>>>> to quote the post 3.0.2 changelog
>>>>>>> The siaddr field was being improperly set to the server-identifier when
>>>>>responding to DHCP messages. RFC2131 clarified the siaddr field as meaning 
>>>>>'next server in the bootstrap process', eg a tftp server. The siaddr field 
>>>>>now left zeroed unless next-server is configured.
>>>>>>> alan
>>>>>>> _______________________________________________
>dhcp-users mailing list
>dhcp-users at lists.isc.org

More information about the dhcp-users mailing list