sending options from wrong subnet in shared-network

[Brian J. Murrell]

On Thu, 2013-12-05 at 10:31 -0500, Brian J. Murrell wrote: 
> On Thu, 2013-12-05 at 16:09 +0100, Sten Carlsen wrote: 
> 
> > If they are not,
> > inheritance will come from that subnet as well, overriding the options
> > in the subnet where the address eventually comes from.
> 
> Well, if that's a way to force the options from the proper subnet, then
> maybe that's my solution, despite this seeming wrong.

So, yeah.  Moving the host declarations up into the subnet declaration
forced dhcpd to send the right options.

I still think this feels wrong though and a hack against what appears to
be a dhcpd bug.  Not that I'm convinced that it's not a configuration
error.  I just have a difficult time imagining any configuration that
should result in getting an ip address from one subnet and the options
from another in a shared-network configuration.

Cheers,
b.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20131205/7d564e76/attachment.bin>