Multiple vendor-encapsulated option spaces?
sar at isc.org
Thu May 28 05:12:01 UTC 2015
> On May 27, 2015, at 3:23 PM, Peter Rathlev <peter at rathlev.dk> wrote:
> On Wed, 2015-05-27 at 14:16 -0700, Shawn Routhier wrote:
>>> On May 27, 2015, at 1:20 PM, Peter Rathlev <peter at rathlev.dk> wrote:
>>> The option space configuration that I can't get to work is:
>>> option space Cisco-WLC;
>>> option Cisco-WLC.ControllerIP code 241 = ip-address;
>>> option Cisco-WLC-encapsulation code 43 = encapsulate Cisco-WLC;<-----------------
>>> option space ASCOM;
>>> option ASCOM.servicediscovery code 10 = text;
>>> option ASCOM-encapsulation code 43 = encapsulate ASCOM; <-----------------
>> Try removing the lines stating that option 43 is encapsulating things.
> Ah, thanks! That was it! Everything works as intended now.
> I'm not sure exactly why we had these in the configuration, but I'm
> pretty sure I've looked at several examples on teh Intarnetz that
> include a similar line. But then there are a lot of terrible examples
> out there…
I’ve seen some indications that they were needed in some older versions
of DHCP, but I’ve never felt the desire to figure out if they really were needed
or somebody was confused.
> Reading the man pages I can now see that this "= encapsulate" thing is
> only meant for options above 224 (or 128 or whatever) that the DHCP
> server doesn't already know how to encapsulate.
> And a nod to Doug, who was right if not elaborate. :-) That line isn't
> mentioned in Ciscos (old-ish) LWAPP documentation.
> Cheers all around!
More information about the dhcp-users