LDAP Subclasses in dynamic mode
Jason Brandt
jbrandt at fsmail.bradley.edu
Wed May 22 00:26:42 UTC 2013
Thank you for the clarification, I will research more and make the appropriate changes to conform to standards.
Jason K. Brandt
Sent from my iPad
On May 21, 2013, at 5:06 PM, Peter Rathlev <peter at rathlev.dk> wrote:
> On Tue, 2013-05-21 at 16:56 -0500, Jason Brandt wrote:
>> We're using IP Helpers to point to the server. So in effect yes it's
>> only broadcasting on one VLAN.
>
> That's not what shared-network does. Shared-network means that the
> server expects all those networks to be just one broadcast domain. It
> doesn't matter if the networks in question are local or remote. From the
> man pages of dhcpd.conf:
>
> : If any subnet in a shared network has addresses available
> : for dynamic allocation, those addresses are collected into
> : a common pool for that shared network and assigned to
> : clients as needed. There is no way to distinguish on which
> : subnet of a shared network a client should boot.
>>
> If all clients explicitly match a class via CI/MAC then you will
> probably not see the effect of shared-network, but using shared-network
> when the networks do not in fact share a broadcast domain is technically
> wrong.
>
>> However, I did just figure out the problem. For whatever reason, the
>> subclass entry starting with 1:xx:xx:xx:xx:xx:xx works fine in static
>> mode, upon getting the LDAP debugging working, i discovered it was
>> querying for 01:xx:xx:xx:xx:xx:xx, which is why it was not finding a
>> match. I corrected my entry in LDAP, and everything started working
>> properly!
>
> Good thing that's solved. :-)
>
> --
> Peter
>
>
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
More information about the dhcp-users
mailing list