Vendor Encapsulated Options Bug?
Jiann-Ming Su
sujiannming at gmail.com
Fri Dec 7 23:28:46 UTC 2007
Using 3.0.4. Trying to pass option 43 to Aruba APs. Their doc
suggests the following config:
class "vendor-classes" {
match option vendor-class-identifier;
}
option option43 code 43 = ip-address;
subnet 192.168.122.0 netmask 255.255.255.0 {
subclass "vendor-classes" "ArubaAP" {
option vendor-class-identifier "ArubaAP";
option option43 192.168.33.179;
}
}
The above config works. I trace the traffic and the option43 section
shows up as 0x2b04c0a821b3.
However, if I modify the config a little bit as suggested in the
dhcp-options man page:
class "vendor-classes" {
match option vendor-class-identifier;
}
option space ARUBA;
option ARUBA.option43 code 43 = ip-address;
subnet 192.168.122.0 netmask 255.255.255.0 {
subclass "vendor-classes" "ArubaAP" {
vendor-option-space ARUBA;
option vendor-class-identifier "ArubaAP";
option ARUBA.option43 192.168.33.179;
}
}
The option43 shows up as 0x2b062b04c0a821b3 and is rejected by the client.
Why would using the "option space..." directives cause the server to
add the addition 2 bytes (0x2b06)?
Do I have something misconfigured, or is this a bug? Thanks for any insights.
--
Jiann-Ming Su
"I have to decide between two equally frightening options.
If I wanted to do that, I'd vote." --Duckman
"The system's broke, Hank. The election baby has peed in
the bath water. You got to throw 'em both out." --Dale Gribble
"Those who vote decide nothing.
Those who count the votes decide everything." --Joseph Stalin
More information about the dhcp-users
mailing list