dhcpd on Solaris 10

[Ward, Martin]

Just to throw a little more data into the mix, I am happily running dhcpd v3.1.1 on a Solaris 10 box running SPARC.

I don't recall doing anything strange to the sources to get it up and running, v3 ran pretty much straight out of the archive. 

V4 had lots of problems though...

|\/|artin

> -----Original Message-----
> From: dhcp-users-bounces at lists.isc.org [mailto:dhcp-users-
> bounces at lists.isc.org] On Behalf Of Jason Penton
> Sent: 26 April 2009 08:31
> To: Users of ISC DHCP
> Subject: Re: dhcpd on Solaris 10
> 
> 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.
> 
> 
> Cheers
> JAson
> 
> 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 0.0.0.0 siaddr.
> >>
> >>regards,
> >>-glenn
> >>
> >>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
> >>>server????
> >>>
> >>>Cheers
> >>>Jason
> >>>
> >>>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 the
> >>'next server in the bootstrap process', eg a tftp server. The siaddr
> field is
> >>now left zeroed unless next-server is configured.
> >>>>
> >>>>
> >>>> alan
> >>>> _______________________________________________
> >>>> dhcp-users mailing list
> >>>> dhcp-users at lists.isc.org
> >>>> https://lists.isc.org/mailman/listinfo/dhcp-users
> >>>>
> >>>_______________________________________________
> >>>dhcp-users mailing list
> >>>dhcp-users at lists.isc.org
> >>>https://lists.isc.org/mailman/listinfo/dhcp-users
> >>
> >>_______________________________________________
> >>dhcp-users mailing list
> >>dhcp-users at lists.isc.org
> >>https://lists.isc.org/mailman/listinfo/dhcp-users
> >
> > _______________________________________________
> > dhcp-users mailing list
> > dhcp-users at lists.isc.org
> > https://lists.isc.org/mailman/listinfo/dhcp-users
> >
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users


*************************************************************************************
The message is intended for the named addressee only and may not be disclosed to or used by anyone else, nor may it be copied in any way. 

The contents of this message and its attachments are confidential and may also be subject to legal privilege.  If you are not the named addressee and/or have received this message in error, please advise us by e-mailing security at colt.net and delete the message and any attachments without retaining any copies. 

Internet communications are not secure and COLT does not accept responsibility for this message, its contents nor responsibility for any viruses. 

No contracts can be created or varied on behalf of COLT Telecommunications, its subsidiaries or affiliates ("COLT") and any other party by email Communications unless expressly agreed in writing with such other party.  

Please note that incoming emails will be automatically scanned to eliminate potential viruses and unsolicited promotional emails. For more information refer to www.colt.net or contact us on +44(0)20 7390 3900.