dhcpd on Solaris 10

[Jason Penton]

Hi Glenn,

Thanks, well the problem has something to do with the siaddr as you
pointed out. However, I had no idea how to set this option. It seems
that dhcpd on solars doesnt serve clients correctly unless this option
is set to the IP address of the DHCP server. I may have done it the
long way around but I added the following lines to the OFFER dhcp
reply in servers/dhcp.c: (everything works perfectly after this
change)

char * hackip = "10.31.3.40";
struct hostent * record = gethostbyname(hackip);
struct in_addr* myip = (struct in_addr *)record->h_addr;
raw.siaddr = *myip;

I'd imagine that on other OS's (linux) the siaddr is set
automatically. Seems that on Solaris 10 update 6, it does not.
Tomorrow when I get time I will see why siaddr is not set by default
on my OS. At least for now it is working for me (albeit a hack :) )

Cheers
Jason

On Sat, Apr 25, 2009 at 2:32 PM, Glenn Satchell
<Glenn.Satchell at uniq.com.au> wrote:
> Hi Jason
>
> One other thing. The server identifier is shown in the Options part of
> the snoop output, like this (snoop -v)
>
> DHCP: ----- (Options) field options -----
> DHCP:
> DHCP: Message type = DHCPOFFER
> DHCP: DHCP Server Identifier = 192.168.14.28
> ...
> DHCP: ----- (Options) field options -----
> DHCP:
> DHCP: Message type = DHCPREQUEST
> DHCP: DHCP Server Identifier = 192.168.14.28
> ...
> DHCP: ----- (Options) field options -----
> DHCP:
> DHCP: Message type = DHCPACK
> DHCP: DHCP Server Identifier = 192.168.14.28
>
> Note that this is different to
>
> DHCP: Next server address (siaddr) = 0.0.0.0
>
> which is the option set by next-server, typically where a tftp service
> is running to download the next stage of booting, eg PXE or Jumpstart.
>
> regards,
> -glenn
>
>>Date: Sat, 25 Apr 2009 09:44:48 +0200
>>Subject: Re: dhcpd on Solaris 10
>>From: Jason Penton <jason.penton at gmail.com>
>>
>>Hi Glenn, *
>>
>>I've tried many version - in both release 3 and 4, but exactly the
>>same symptoms. I've stripped down my dhcpd.conf to the bare minimum as
>>follows:
>>
>>server-identifier <dhcp server IP>;
>>option dhcp-server-identifier <dhcp server IP>;
>>option domain-name "domain.com";
>>option domain-name-servers <DNS server IP>;
>>default-lease-time 14440;
>>ddns-update-style none;
>>deny bootp;
>>shared-network NetworkName {
>>        subnet X.X.X.0 netmask 255.255.255.0 {
>>                option routers X.X.X.X;
>>                option subnet-mask 255.255.255.0;
>>                pool {
>>                        range X.X.X.Y X.X.X.Z;
>>                }
>>        }
>>}
>>
>>Any help would be greatly appreciated.
>>
>>Another thing. The clients do get the OFFER but obv. dont respond
>>because of the server-ip-address being 0.0.0.0
>>
>>BTW, DHCP server has 4 NICs configured (dont know if this has any effect)
>>
>>Cheers
>>Jason
>>
>>On Sat, Apr 25, 2009 at 9:26 AM, Glenn Satchell
>><Glenn.Satchell at uniq.com.au> wrote:
>>> What version of dhcpd are you using? I've had problems with 4.0.0. In
>>> that case it works with a relay but not for directly attached
>>> networks.  I haven't tried 4.1.0 yet. All of the 3.x versions work fine
>>> with Solaris 10.
>>>
>>> Otherwise can you post your dhcpd.conf.
>>>
>>> regards,
>>> -glenn
>>>
>>>>Date: Sat, 25 Apr 2009 07:08:41 +0200
>>>>Subject: dhcpd on Solaris 10
>>>>From: Jason Penton <jason.penton at gmail.com>
>>>>To: dhcp-users at lists.isc.org
>>>>X-BeenThere: dhcp-users at lists.isc.org
>>>>
>>>>Hi *,
>>>>
>>>>I am pulling my hair out trying to serve the simplest of setups using
>>>>ISC dhcpd on Solaris 10.
>>>>
>>>>The problem is that the DISCOVERS come in.
>>>>dhcpd responds with OFFER.
>>>>Client never sends REQUEST.
>>>>
>>>>The exact same config on a linux box works as predicted.
>>>>
>>>>Packet trace of differences between the 2 OFFERS (sent by linux and
>>>>Solaris) is that the Solaris offer has:
>>>>
>>>>server-ip-address set to 0.0.0.0,
>>>>while linux,
>>>>server-ip-address set to (x.x.x.x ip of dhcpd server)
>>>>
>>>>I have tried every option to get the solaris box to correctly set this
>>>>option (even server-identifier) but to noavail.
>>>>
>>>>Could someone please shed some light?
>>>>
>>>>Kind regards
>>>>Jason
>>>>_______________________________________________
>>>>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
>