Option 43 and scopes

[Mike Richardson-2]

Apologies if this has been asked and answered but I'm struggling to find the
right information.

I'm trying to configure up option 43 for Aruba APs and Siemens VOIP phones.

The Aruba APs require this approach to option 43:

"
option serverip code 43 = ip-address;

shared-network wireless_APs_setuproom
{
  option serverip X.X.X.X;
}
"

This configuration appears only to be valid in the global scope (BICBW).

The VOIP config is sub option based:

"
option space VOIP;
option VOIP.siemens code 1 = text;
option VOIP.vlan code 2 = integer 32;
option VOIP.dls code 3 = text;

class "OptiIpPhone"
{
  match if option vendor-class-identifier = "OptiIpPhone";

  vendor-option-space VOIP;
  option VOIP.siemens "Siemens";
}

"

Either of these work fine on their own but as soon as I mix them then the
VOIP stuff stops working and doesn't send back any option 43 data.

My completely uneducated guess is that the global nature of each clash with
each other. I'm a bit stuck now as to how to make both work together.

Any help would be appreciated.

Thanks,

Mike

--
Mike Richardson
Networks ([hidden email])
IT Services, University of Manchester
*Plain text only please - attachments stripped on arrival*
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

[Anderson, Charles R]

On Fri, Nov 25, 2016 at 10:39:06AM +0000, Mike Richardson wrote:
> Apologies if this has been asked and answered but I'm struggling to find the
> right information.
>
> I'm trying to configure up option 43 for Aruba APs and Siemens VOIP phones.

You can try using an option space for Aruba as well:

option space Aruba;
option Aruba.ControllerIP code 43 = ip-address;

class "ArubaAP" {
        match if option vendor-class-identifier = "ArubaAP";
        vendor-option-space VOIP;
        option Aruba.ControllerIP x.x.x.x;
}
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

[Mike Richardson-2]

On Fri, Nov 25, 2016 at 12:52:57PM -0500, Chuck Anderson wrote:

> On Fri, Nov 25, 2016 at 10:39:06AM +0000, Mike Richardson wrote:
> > Apologies if this has been asked and answered but I'm struggling to find the
> > right information.
> >
> > I'm trying to configure up option 43 for Aruba APs and Siemens VOIP phones.
>
> You can try using an option space for Aruba as well:
>
> option space Aruba;
> option Aruba.ControllerIP code 43 = ip-address;
>
> class "ArubaAP" {
> match if option vendor-class-identifier = "ArubaAP";
> vendor-option-space VOIP;
> option Aruba.ControllerIP x.x.x.x;
> }

Thanks for the response. I probably should have said that I've tried this
and it doesn't work. The Aruba APs expect a single valued reply.

https://lists.isc.org/pipermail/dhcp-users/2010-December/012824.html

Mike
--
Mike Richardson
Networks ([hidden email])
IT Services, University of Manchester
*Plain text only please - attachments stripped on arrival*
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

[glenn.satchell]

Ok, so it's time for the ugly hacks to come out... :(

The option space notation helps set up the encoding for multiplevalues in
option 43.

So it should be possible to define the value of your option 43 usng the
colon separated hexadecimal list. You will need to manually work out the
values so that they will be decoded properly. This is defined in RFC2132.
Essentially it is sort of looks like option number, length of value,
option value, repeat as required.

regards,
-glenn

On Mon, November 28, 2016 7:38 pm, Mike Richardson wrote:

> On Fri, Nov 25, 2016 at 12:52:57PM -0500, Chuck Anderson wrote:
>> On Fri, Nov 25, 2016 at 10:39:06AM +0000, Mike Richardson wrote:
>> > Apologies if this has been asked and answered but I'm struggling to
>> find the
>> > right information.
>> >
>> > I'm trying to configure up option 43 for Aruba APs and Siemens VOIP
>> phones.
>>
>> You can try using an option space for Aruba as well:
>>
>> option space Aruba;
>> option Aruba.ControllerIP code 43 = ip-address;
>>
>> class "ArubaAP" {
>> match if option vendor-class-identifier = "ArubaAP";
>> vendor-option-space VOIP;
>> option Aruba.ControllerIP x.x.x.x;
>> }
>
> Thanks for the response. I probably should have said that I've tried this
> and it doesn't work. The Aruba APs expect a single valued reply.
>
> https://lists.isc.org/pipermail/dhcp-users/2010-December/012824.html
>
> Mike
> --
> Mike Richardson
> Networks ([hidden email])
> IT Services, University of Manchester
> *Plain text only please - attachments stripped on arrival*
> _______________________________________________
> dhcp-users mailing list
> [hidden email]
> https://lists.isc.org/mailman/listinfo/dhcp-users
>

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

[Mike Richardson-2]

On Mon, Nov 28, 2016 at 10:35:29PM +1100, Glenn Satchell wrote:

> Ok, so it's time for the ugly hacks to come out... :(
>
> The option space notation helps set up the encoding for multiplevalues in
> option 43.
>
> So it should be possible to define the value of your option 43 usng the
> colon separated hexadecimal list. You will need to manually work out the
> values so that they will be decoded properly. This is defined in RFC2132.
> Essentially it is sort of looks like option number, length of value,
> option value, repeat as required.

Thanks,

That worked. Not pretty but it's functional.

Mike

--
Mike Richardson
Networks ([hidden email])
IT Services, University of Manchester
*Plain text only please - attachments stripped on arrival*
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users