Aruba Instant & Cloud Wi-Fi

Reply
Occasional Contributor I
Posts: 9
Registered: ‎09-18-2015

Disabling legacy client devices

Hi,

 

In IAP225, I would like to block legacy clients connecting to the SSID's. The arubas document suggests to use 'legacy-mode' command to control the legacy clients. As per the document, all non 802.11n devices are considered as 'legacy devices'. The document description is as given below.

 

legacy-mode - Enables the IAPs to run the radio in non-802.11n mode.

 

According to the above description, when disabled, any 802.11 a/b/g devices should NOT be able to connect to the network however it does not seem working. Please have a look at the below logs:

 

Configuration:

  IAP225# show radio config

 

  2.4 GHz:

  Legacy Mode:disable

  Single Chain Legacy:disable

  Beacon Interval:100

  802.11d/802.11h:enable

  Interference Immunity Level:2

  Channel Switch Announcement Count:0

  MAX Distance:600

  Channel Reuse Type:disable

  Channel Reuse Threshold:0

  Background Spectrum Monitor:disable

  Max Tx Power:0

  Min Tx Power:0

  5.0 GHz:

  Legacy Mode:disable

  Single Chain Legacy:disable

  Beacon Interval:90

  802.11d/802.11h:enable

  Interference Immunity Level:2

  Channel Switch Announcement Count:0

  MAX Distance:600

  Channel Reuse Type:disable

  Channel Reuse Threshold:0

  Background Spectrum Monitor:disable

  Standalone Spectrum Band:5ghz-upper

  Max Tx Power:0

  Min Tx Power:0

  IAP225#

 

Connected Clients:

 

IAP225# show ap association

 

The phy column shows client's operational capabilities for current association

 

Flags: A: Active, B: Band Steerable, H: Hotspot(802.11u) client, K: 802.11K client, R: 802.11R client, W: WMM client, w: 802.11w client V: 802.11v BSS trans capable

 

PHY Details: HT   : High throughput;      20: 20MHz;  40: 40MHz; t: turbo-rates (256-QAM)

             VHT  : Very High throughput; 80: 80MHz; 160: 160MHz; 80p80: 80MHz + 80MHz

             <n>ss: <n> spatial streams

 

Association Table

-----------------

Name               bssid              mac                auth  assoc  aid  l-int  essid          vlan-id  tunnel-id  phy              assoc. time  num assoc  Flags  DataReady

----               -----              ---                ----  -----  ---  -----  -----          -------  ---------  ---              -----------  ---------  -----  ---------

18:64:72:c8:51:56  18:64:72:05:15:72  cc:fa:00:a9:12:9a  y     y      1    10     Q_streaming_1  4092     0x0        a-VHT-20sgi-1ss  1m:30s       1          W      Yes (Implicit)               

18:64:72:c8:51:56  18:64:72:05:15:72  c8:f9:f9:34:13:8e  y     y      2    12457  Q_streaming_1  4092     0x0        a                52s          1                 Yes (Implicit)

18:64:72:c8:51:56  18:64:72:05:15:63  5c:50:15:24:f0:21  y     y      2    12457  Q_streaming_2  4092     0x0        g                1m:16s       1                 Yes (Implicit)

18:64:72:c8:51:56  18:64:72:05:15:63  18:af:61:68:e0:f8  y     y      1    20     Q_streaming_2  4092     0x0        g-HT-20sgi-1ss   20s          1          WK     Yes (Implicit)               

Num Clients:4

IAP225#

 

 

Question: Is 802.11b device only considered as legacy device[a/g are not]? It could be  a case that information  documents is not correct. Need clarification on this.

        or

controlling the legacy devices functionality not working in IAP225?

 

Please let me know.

 

Regards,

Shiva

 

 

Guru Elite
Posts: 8,322
Registered: ‎09-08-2010

Re: Disabling legacy client devices

You cannot currently disallow 11a and 11g clients from associating. You can however remove the data and basic rates under 12 to stop 11b clients from associating.


Tim Cappalli | Aruba Security TME
@timcappalli | timcappalli.me | ACMX #367 / ACCX #480
Occasional Contributor I
Posts: 9
Registered: ‎09-18-2015

Re: Disabling legacy client devices

Thank you for your quick response. I will change the data rate and test again.

 

Thanks,

Shiva

 

 

Search Airheads
Showing results for 
Search instead for 
Did you mean: