SAP 1602 Wireless bridge issue. Non root bridge loses it's configuration

[EvaldasOu]

Hi guys,

Today I tried to configure wireless link between two autonomous AP 1602 APs.

There is a problem with Non-root bridge. I configured it with this command:

AP2(config-if)#station-role non-root wireless-clients

Non-root bridge successfully joins the root bridge (root AP). Anyway, this configuration does not work, if I reload my non-root bridge. Even without reload, If I check my non-root bridge configuration it looks like this:

interface Dot11Radio1

no ip address

no ip route-cache

!

encryption vlan 1 mode ciphers aes-ccm

!

ssid WiFi-Bridge

!

antenna gain 0

stbc

beamform ofdm

Command "station-role non-root wireless-clients" is missing here. But I just configured it few seconds ago... Does anyone know, where could be a problem?

[Rasika Nayanajith]

Try without "wireless-client" keyword (ie station-role non-root bridge) & see command show in the running config.

Also try with 2.4GHz interface & see whether it accpet the command & show it in running config.

What is the IOS image you are having?

HTH

Rasika

*** Pls rate all useful responses ****

[EvaldasOu]

Hi Rasika,

Yes, it works. Command "station-role non-root bridge" survives after the reload, I'm also able to see it in my interface radio config.

I'm running:

Cisco IOS Software, C1600 Software (AP1G2-K9W7-M), Version 15.2(4)JA1, RELEASE SOFTWARE (fc2) (on Root AP)

Cisco IOS Software, C1600 Software (AP1G2-K9W7-M), Version 15.2(2)JB2, RELEASE SOFTWARE (fc1) (on Non-Root AP)

No problem with software, I can upgrade/downgrade it if necessary. The solution I'm trying to achieve looks like this:

Serve WiFi clients on both sides of the bridge link.

[EvaldasOu]

Rasika,

I found a great write-up on your blog: http://mrncciew.com/2013/01/13/autonoumous-ap-wireless-bridges/

However, command "station-role non-root wireless-clients" does not appear on radio 0 and on radio 1.

Clients are not able to connect, because configuration does not work. Non-root bridge can't accept wireless clients.

[Rasika Nayanajith · Accepted solution]

Command should looks like "station-role non-root bridge wireless-client" & I can see bridge keyword is missing in your above command. Try that & see.

In my post I have used 12.2(25d)JA2 & those commands were accepted.

By the way thanks for read my blog & for the good feedback

HTH

Rasika

**** Pls rate all useful responses ****

[EvaldasOu]

Hi Rasika,

Good catch! You are right!

Now the configuration works! But only with Windows devices... If I try to connect with Android device, on root AP I see this:

*Mar  2 08:00:46.801: %DOT11-6-ADD: Interface Dot11Radio0, Station 9c02.986d.9675 Associated to Parent 34db.fde0.c890

*Mar  2 08:00:47.165: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 9c02.986d.9675

*Mar  2 08:00:48.013: %DOT11-6-ADD: Interface Dot11Radio0, Station 9c02.986d.9675 Associated to Parent 34db.fde0.c890

*Mar  2 08:00:48.397: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 9c02.986d.9675

*Mar  2 08:00:48.577: %DOT11-6-ROAMED: Station 9c02.986d.9675 Roamed to 34db.fde0.c890

*Mar  2 08:00:48.577: %DOT11-6-ADD: Interface Dot11Radio0, Station 9c02.986d.9675 Associated to Parent 34db.fde0.c890

*Mar  2 08:00:48.925: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 9c02.986d.9675

*Mar  2 08:00:49.005: %DOT11-6-ADD: Interface Dot11Radio0, Station 9c02.986d.9675 Associated to Parent 34db.fde0.c890

It looks like Android device roams, between root and non-root AP... connection is not stable. Both APs sents beacons on Channel 6.

Client is even unable to get IP address by DHCP, because the deauthentication.

Is there any tips, how could I configure roaming between root and non-root APs?

By the way, your blog is one of the best for CCIE Wireless studies!

[EvaldasOu]

Now I think that's not related with roaming... Android devices can't connect even if SSID is turned off on Non-Root AP.

[EvaldasOu]

Okay... Everything works with OPEN ssid. Not with my WPA 2 configuration.

On both APs configuration looks like this:

dot11 ssid Private

   vlan 10

   authentication open

   authentication key-management wpa version 2

   guest-mode

   wpa-psk ascii 7 01100F175804575D72

interface Dot11Radio0

!

encryption vlan 10 mode ciphers aes-ccm

!

ssid Private

!

infrastructure-client ( on Root AP)

!

station-role root bridge wireless-clients ( on Root AP)

Few debugs:

*Mar  2 09:57:30.554: %DOT11-6-ASSOC: Interface Dot11Radio0, Station  9c02.986d.9675 Reassociated KEY_MGMT[WPAv2 PSK]

*Mar  2 09:57:30.938: dot11_auth_client_abort: Received abort request for client 9c02.986d.9675

*Mar  2 09:57:30.938: dot11_auth_client_abort: No client entry to abort: 9c02.986d.9675 for application 0x1

*Mar  2 09:57:30.938: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 9c02.986d.9675 Reason: Sending station has left the BSS

*Mar  2 09:57:30.986: %DOT11-6-ASSOC: Interface Dot11Radio0, Station  9c02.986d.9675 Reassociated KEY_MGMT[WPAv2 PSK]

*Mar  2 09:57:31.350: dot11_auth_client_abort: Received abort request for client 9c02.986d.9675

*Mar  2 09:57:31.350: dot11_auth_client_abort: No client entry to abort: 9c02.986d.9675 for application 0x1

*Mar  2 09:57:31.350: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 9c02.986d.9675 Reason: Sending station has left the BSS

*Mar  2 09:57:31.398: %DOT11-6-ASSOC: Interface Dot11Radio0, Station  9c02.986d.9675 Reassociated KEY_MGMT[WPAv2 PSK]

*Mar  2 09:57:31.766: dot11_auth_client_abort: Received abort request for client 9c02.986d.9675

Everything works with android device and WPA2 if I change configuration to this:

dot11 ssid Private

   vlan 10

   authentication open

   authentication key-management wpa version 2

   mbssid guest-mode

   wpa-psk ascii 7 01100F175804575D72

interface Dot11Radio0

!

encryption vlan 10 mode ciphers aes-ccm

!

ssid Private

!

station-role root

!

mbssid

[EvaldasOu]

Guys...

I think it an issue with android device... It works with Windows laptops, works with Apple Iphone.

Tried with few different android mobile phones, with samsung galaxy tab, - can't even get dhcp. Client associates/dissoaciates...

[Rasika Nayanajith]

Glad to see you get this basic bridging working...

Typically wireless bridge solution is not for connecting wireless clients on the same SSID/band where non-root-bridge associate.(as it effectively reduce bridge backhaul bandwidth)

Try to associate clients on another SSID & other radio band. Also look at WGB options as well.(in that case root will be just Root Access point, not a bridge)

HTH

Rasika

**** Pls rate all useful responses ****

[EvaldasOu]

Hi Rasika,

I was using different SSIDs (one for Client access, one for the bridge backhaul. Configuration output was omitted).

The best solution would be:

• Client access , - 2.4 GHz band;
• Bridge backhaul, 5 GHz band.

Bridge over 5 GHz band works, with root, non-root bridge configuration.

AP1:

interface Dot11Radio1

no ip address

no ip route-cache

!

encryption vlan 1 mode ciphers aes-ccm

!

ssid WiFi-Bridge

!

no dfs band block

stbc

beamform ofdm

channel dfs

station-role root bridge wireless-clients

AP2:

interface Dot11Radio1

no ip address

no ip route-cache

!

encryption vlan 1 mode ciphers aes-ccm

!

ssid WiFi-Bridge

!

antenna gain 0

stbc

beamform ofdm

station-role non-root bridge wireless-clients

Could you give me a tip, how does the 2.4 GHz band configuration should look like? How will non-root AP know, that he needs to send 2.4GHz data over 5 GHz backhaul?

[EvaldasOu]

Okay guys! It's done. I managed how we should configure everything.

As I said:

• Client access , - 2.4 GHz band;
• Bridge backhaul, 5 GHz band.

There is two links to the configuration files. I hope it will help for someone today or tomorrow

Root AP : http://pastebin.com/dj6neKci

Non-Root AP : http://pastebin.com/TcsyEsv3