ArubaOS and Controllers

Reply
Highlighted
MVP

Advertise 802.11d and 802.11h Capabilities

Why would you have this setting disabled? Is there any downside to having it enabled? If not, why is it disabled by default?

Asking because I ran into an upgrade where a bunch of hand-scanners would no longer work after upgrading from 2.5 to 3.4. Differentiator between the working scanners and those that didn't was a setting 802.11d on those scanners.

From Google I gather both are extensions to meet regulations so again.. why disabled per default?

http://en.wikipedia.org/wiki/IEEE_802.11d-2001
http://en.wikipedia.org/wiki/IEEE_802.11h-2003

Koen (ACMX #351 | ACDX #547 | ACCP)

-- Found a post helpful or important? Click the "Thumbs Up" icon to give kudos.
-- Problem Solved? Click "Accept as Solution" in a post.
Highlighted
MVP

Re: Advertise 802.11d and 802.11h Capabilities

Anyone got an idea?

Koen (ACMX #351 | ACDX #547 | ACCP)

-- Found a post helpful or important? Click the "Thumbs Up" icon to give kudos.
-- Problem Solved? Click "Accept as Solution" in a post.
Highlighted
Guru Elite

Re: Advertise 802.11d and 802.11h Capabilities

Aruba

Advertise 802.11d and 802.11h Capabilities

Having these settings enabled(or rather these 'standards' advertised out
by the network that is) has caused me issue in the past. Not all
devices are compliant with these pieces of the 802.11 family.

In one example, some HP/Compaq laptops would refuse to associate, at
all, with these parameters activated. The same laptop associated
immediately with these parameters off. It would seem that some pre-N
laptops geared for the "Home Market" can have this issue whereas the
devices geared for the "Enterprise" (e.g. barcode scanners like yours)
do not.

As newer clients (802.11n) have been increasingly replacing 802.11g
clients (with good drivers or other wise) I think this will be less of
an issue, and it will make more sense to enable the fields.
Highlighted
Occasional Contributor II

Re: Advertise 802.11d and 802.11h Capabilities


Having these settings enabled(or rather these 'standards' advertised out
by the network that is) has caused me issue in the past. Not all
devices are compliant with these pieces of the 802.11 family.




Seconding this. We deployed 802.11d and saw the same problem with Intel 2200 chipsets. Disabling it fixed the problem immediately.

Moral of the story: Deploy in controlled manner, see if it breaks things.