hex prepend?

[Allie Hopkins]

I played around with this setting for our Cisco AP's for a short while.
I then discovered that they first look for the hostname
"cisco-lwapp-controller.your.domain" via DNS and then look for the DHCP
options if that name does not resolve.  We took this route since it was
getting tedious with option 43.  Have you looked into this option?

Allie

On Mon, 2007-02-19 at 16:41 -0700, Mike A. Hale wrote:
> I am trying to send option 43 to specific Access Points. I have setup my
> dhcpd.conf as the following:
> 
> option space Cisco_LWAPP_AP;
> option Cisco_LWAPP_AP.server-address code 43 = string;
> 
> subnet 170.87.57.0 netmask 255.255.255.0 {
>   option broadcast-address 170.87.57.255;
>   option routers 170.87.57.1;
>   range dynamic-bootp 170.87.57.176 170.87.57.179; # testing
>   pool {
>     range 170.87.57.75 170.87.57.175;  # 101
>   }
>   min-lease-time 28800;
>   max-lease-time 28800;
>   default-lease-time 28800;
>   option dhcp-renewal-time 3600;
>   class "Cisco AP c1240" {
>     match if option vendor-class-identifier = "Cisco AP c1240";
>     option vendor-class-identifier "Cisco AP c1240";
>     vendor-option-space Cisco_LWAPP_AP;
>     option Cisco_LWAPP_AP.server-address f1:04:AA:57:D0:0C; }
> }
> 
> Option 43 is correctly sending however it has values prepended. Instead
> of sending f1:04:AA:57:D0:0C it is sending
> 2b:08:2b:06:f1:04:aa:57:d0:0c. After some searching it looks like these
> prepended values are somehow related to the length of the string. How do
> I get it to send only the string I need?
> 
> -Mike 
>