1310 root bridge w/ wireless clients

I am having an issue with a 1310 in root bridge with wireless clients mode. I have the bridge connected to another bridge in non-root bridge mode and everything is working fine on that end on ethernet.
My issue is the wireless one the frirst bridge. I have an SSID on our wireless VLAN, and set that SSID as single guest mode. We can see the SSID and associate with it, but we are not getting DHCP. We have several APs that are set up the same way and users can connect and obtain IP addresses fine. Those APs are on the same wireless VLAN as the SSID, jsut programmed on the switch. The radios are in trunk ports.
Any ideas on what could be the issue.
Thansk.

Can you post your config?

Similar Messages

AP1200 as Root Bridge: Accept wireless clients or not?

Cisco's docs precisely contradict themselves on this topic. In some places they state clearly that configuring an AP1200 as a root bridge means it will NOT accept connections from normal wireless clients. In other places they state just as clearly that in root bridge mode an AP1200 WILL accept connections from both non-root bridges and normal wireless clients.
Which is correct?

Yes, I discovered that after setting up several units and running some experiments. At first all I saw were the options offered in the "express setup" area. The root-bridge choice there says nothing about wireless clients, and the help screen it invokes says it won't work. But on the radio interface config screen the option you mention is offered and ITS help screen notes wireless clients will be accepted (as its name implies).
The telnet interface offers all the options as well.
I can confirm that it does work: In root-bridge with wireless client mode the unit will accept associations from non-root bridges, other AP1230's in WGB mode, and even non-Cisco clients.
The testing continues... thanks!

1310 Root Bridge will not Authenticate with 350 Non Root Bridge

I've exhausted myself solving this issue.
I have a 1310 set as a root bridge using WEPS. I have a 350 set as a non root bridge/without clients, also using WEPS (they both use the same SSID)
The 350 will not authenticate to the 1310. After doing a Carrier Busy Test, it is clear the 350 see's the 1310 with signal strengh of 100 percent.
(I have a test lab setup in my office)
If I make the 350 the Root Bridge and the 1310 the Non Root, The 1310 will authenticate to the 350.
I hoping someone else has seen this problem and can enlighten me.
Thank you.

I have successfully configured a 1310 Bridge as a Root Bridge and a BR350 Bridge and a Non Root Bridge/with Clients. I also had to force the 1310 to operate at 11MB only.
As soon as I make the BR350 Bridge a Non Root Bridge/without Clients, the authentication is dropped between the two.
I was hoping I could transition to the 1310 one unit at a time since I have over a dozen 350's to replace.

Aironet 1310 non-root with wireless clients

I have two 1310s. One set as a root-bridge with wireless clients, another as a non-root bridge with wireless clients. The wireless side of things is working fine, but I'm having trouble when I try to connect a windows work station to the non-root bridge via ethernet. I'm getting an IP address from the router attached to the root bridge via DHCP, and I am able to connect to the configuration page of both 1310 APs, but I'm not getting any internet connectivity. Have I misunderstood what 'non-root bridge with wireless clients' means? If not, is there an obvious problem which might cause the wireless clients to work fine, but interfere with a wired client? Thanks.

Thanks Seth,
It's good to know that this is how it is supposed to work. The thing that has me scratching my head is that the wireless clients are working fine from this bridge--it is only the client hooked up to the ethernet interface that is not getting out.
I'll take a look at the gateway settings and see what I can find. I appreciate the tip.

Root Bridge+Clients with Non-Root Bridge+Clients Howto?

Hi, i have two 1242AG access points. I would like to setup a bridge between the two to bridge ethernet lan segments, furthermore i would like to be able to connect wireless clients to either of the access points so i can get maximum range.
I did what i thought was correct, created the first access point a 'root bridge with wireless clients', and assigned the ssid.
I set the second access point to 'non-root bridge with wireless clients' amd set the same ssid as the first access point.
I cant even get the root bridge to work, i turn it on, it brings the radio interface up but i cannot connect with my wireless clients, infact i cannot even see the SSID!
Do i need to 'Set Single Guest Mode SSID' for the radios? What does that command do?
Any ideas? A link to config example would be much apreciated.
Thanks,
Chris

Hi, first, thanks for the help.
Second, this incompatibility is only valid
for RFC1042 or it is valid for 802.11g?
Third, If I configure my 1242 as Acess Point, and the 340 series as Client or Brigde_only, they should not talk too?
Sorry for the bad english...

Root-bridge non-root bridge security

Using AP1231, I have a point-to-point configuration with the option "without wireless clients". I have enabled WPA2-PSK/AES-CCMP to the infrastructureSSID/nativeVLAN.
Does this security automatically apply to the other SSID/VLAN I have configured? Or do I need to configure additional security on the other SSID/VLAN? Please advise. Thanks!

From your diagram, AP3 is the root bridge because it is connected to ISP, so AP2 will be a repeater, but 1242 can't work both as repeater and AP. So the diagram won't work. you have 3 alternative options:
1. not let AP2 to connect wireless clients, only configure AP2 as a repeater.
2. If AP1 can connect to AP3 directly, then configure AP3 as root-bridge with wireless clients, configure both AP1 and AP2 as non-root bridge withe wireless clients.
3. If AP1 can't connect to AP3 directly, you need to add an additional AP4 to have back-to-back connection with AP2, configure AP1 and AP4 as non-root bridge with wireless clients, configure AP2 and AP3 as root-bridge with wireless clients; ap1 peered with AP2, AP4 peered with AP3, AP2 and AP4 are interconnected by ethernet port.

1310 Non-Root Bridge Accessing Different Subnets

From this non-root 1310 bridge, we are connecting to an old BR500 root bridge via wireless.
Clients inside the non-root bridge are able to access devices anywhere on the subnet (servers, workstations, etc.) via the bridge (wireless connection) with no problems. But, these clients cannot access the default gateway of the subnet or pass through the router (I can't even ping the default gateway router interface from the 1310 bridge; yet from the bridge, I can ping anything else on the same subnet).
Of course, clients on the wired LAN are able to browse the Internet, etc. -- it is only clients behind this bridge that cannot seem to "get out" so to speak.
This is a small LAN -- so everything is VLAN1 with a router at the boundary.
I have even ran a "sh ip arp" on the 1310 to ensure that a MAC entry is in the table for the default gateway IP, and it is there.
Any ideas?

Make sure there is no access list confiugred on the router blocking the access. Save the configurations and restart the bridge .

1310 Root with two non-root bridges

I have a Cisco 1310 root bridge and a 1310 non-root bridge . it worked fine for a year, I then installed one more 1310 as a non-root bridge now I?m seeing both of my non-root bridges dropping offline more and more. I checked my first non-root bridge today and the radio is down and I can?t seem to bring it back up. I have recently upgraded the tar to see if that would fix the problem. This problem started when I added my second non-root bridge. Did I miss some setting or something

Make sure the spanning tree protocol is disabled on Vlan interfaces

Root-Bridge and Non-Root Bridge Support

I was wondering if the ISR Routers (Cisco 1811w) support the root-bridge and non-root-bridge feature. If not is there another device apart from the 1310 and 1410 bridges that support this feature?
Thank You,
VT

Hi VT,
The ISR AP supports both of these roles;
Access Point Link Role Flexibility
Access Point Link Role Flexibility allows access point radios to operate in a combination of radio roles,
such as access point root, bridge root (with or without clients), bridge nonroot (with or without clients).
This provides a more flexible deployment scheme to support the various applications requirement. Note
that the ISR AP does not support access point repeater and WGB.
Wireless Non-Root Bridge
The wireless non-root bridge allows the access point radio to operate as the remote node in a point to
point or point to multi-point network.
Wireless Root Bridge
The wireless root bridge role provides support for both point-to-point or point to multi-point bridging.
http://www.cisco.com/en/US/docs/ios/12_4/12_4x/release/notes/rn1800xj.html
Hope this helps!
Rob

1242AG How to set a password on wireless client

Listen I wasn't able to get these woking as a Root-Bridge & Non-Root Bridge but was able to get them to work as Root-Bridge with Wireless. Ok I'm out here in the middle of nowhere in Iraq so i say fine just put a password on the wireless client but it seem no matter what I do I cant get to the place to just secure it with a password.
Please any help much appreciated.
Thanks
Danny

From your query I understand that you are trying to configure some form of authentication for Wireless clients accessing the wireless bridge. Read the following document which explains how to configure the AP/Bridge as a local radius server to authentication clients.
http://www.cisco.com/en/US/products/hw/wireless/ps4570/products_configuration_example09186a00801c0912.shtml

Root Bridge vs. Non-Root Bridge

Hi,
I want to understand the Root Bridge vs. the Non-Root Bidge when using Autonomous 1131 AP's on the same /24 network. Does that command matter in Autonomous? I have many devices working without issues on the same /24 network and all have the Root Bridge set,
Clearly confused...
Thanks,

The command is used on point to point links deployments
A non root bridge becomes a client and connect to another ap in order to do wireless bridging.
Sent from Cisco Technical Support iPhone App

Wireless Root Bridge - Non Root Bridge

I've been reading a lot about bridge configuration for wireless AP but i cannot make it work the following scenario:
PC -- ethernet port --> Non-Root-Bridge -----------> Root Bridge ---------> Switch
vlan111                     native 18 - vlan111           native 18 - vlan111      vlan native 18,111
Its pinging fine between switch and Non-Root. But when i put vlan111 on Non-Root the two AP's stop responding to the network.
What am i doing wrong? Plz i need some help!! I have two 1242.
------------------------ Root Config ----------------------
dot11 syslog
dot11 vlan-name JGS111 vlan 111
dot11 vlan-name JGS18 vlan 18
dot11 ssid WGB
   vlan 18
   authentication open
   guest-mode
   infrastructure-ssid
username Cisco password 7 047802150C2E
bridge irb
interface Dot11Radio0
no ip address
no ip route-cache
ssid WGB
station-role root bridge
infrastructure-client
interface Dot11Radio0.18
encapsulation dot1Q 18 native
no ip route-cache
bridge-group 1
bridge-group 1 spanning-disabled
interface Dot11Radio0.111
encapsulation dot1Q 111
no ip route-cache
bridge-group 111
bridge-group 111 spanning-disabled
interface Dot11Radio1
no ip address
no ip route-cache
shutdown
dfs band 3 block
channel dfs
station-role root
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
bridge-group 1 spanning-disabled
interface FastEthernet0
no ip address
no ip route-cache
duplex auto
speed auto
interface FastEthernet0.18
encapsulation dot1Q 18 native
no ip route-cache
bridge-group 1
bridge-group 1 spanning-disabled
interface FastEthernet0.111
encapsulation dot1Q 111
no ip route-cache
bridge-group 111
bridge-group 111 spanning-disabled
interface BVI1
ip address 10.1.8.50 255.255.255.0
no ip route-cache
ip default-gateway 10.1.8.254
ip http server
no ip http secure-server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
bridge 1 route ip
------------- Non-Root-Bridge -------------
ot11 syslog
dot11 vlan-name JGS111 vlan 111
dot11 vlan-name JGS18 vlan 18
dot11 ssid WGB
   vlan 18
   authentication open
   guest-mode
   infrastructure-ssid
username Cisco password 7 14341B180F0B
bridge irb
interface Dot11Radio0
no ip address
no ip route-cache
ssid WGB
station-role non-root bridge
infrastructure-client
interface Dot11Radio0.18
encapsulation dot1Q 18 native
no ip route-cache
bridge-group 1
bridge-group 1 spanning-disabled
interface Dot11Radio0.111
encapsulation dot1Q 111
no ip route-cache
bridge-group 111
bridge-group 111 spanning-disabled
interface Dot11Radio1
no ip address
no ip route-cache
shutdown
dfs band 3 block
channel dfs
station-role root
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
bridge-group 1 spanning-disabled
interface FastEthernet0
no ip address
no ip route-cache
duplex auto
speed auto
interface FastEthernet0.18
encapsulation dot1Q 18 native
no ip route-cache
bridge-group 1
bridge-group 1 spanning-disabled
interface FastEthernet0.111
encapsulation dot1Q 111
no ip route-cache
bridge-group 111
bridge-group 111 spanning-disabled
interface BVI1
ip address 10.1.8.51 255.255.255.0
no ip route-cache
ip default-gateway 10.1.8.254
ip http server
no ip http secure-server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
bridge 1 route ip

Try this:
interface Dot11Radio0.18
encapsulation dot1Q 18 native
no ip route-cache
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
bridge-group 1 spanning-disabled
interface Dot11Radio0.111
encapsulation dot1Q 111
no ip route-cache
bridge-group 111
bridge-group 111 subscriber-loop-control
bridge-group 111 block-unknown-source
no bridge-group 111 source-learning
no bridge-group 111 unicast-flooding
bridge-group 111 spanning-disabled
interface FastEthernet0.18
encapsulation dot1Q 10 native
no ip route-cache
bridge-group 1
no bridge-group 1 source-learning
bridge-group 1 spanning-disabled
interface FastEthernet0.111
encapsulation dot1Q 111
no ip route-cache
bridge-group 111
no bridge-group 111 source-learning
bridge-group 111 spanning-disabled
Make sure your switchort is setup similar
interface GigabitEthernet0/7
description 1242 AP Bridge
switchport trunk encapsulation dot1q
switchport trunk native vlan 18
switchport trunk allowed vlans 18,111
switchport mode trunk
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"

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

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?

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

Bridge does not work for wireless clients - connecting to existing network.

Hi - I really hope somebody can help out here, after hours of trial & error, I have finally given up
I need to connect my Airport Extreme Base Station to my existing network. I have a linksys router (192.168.15.1) connected to my modem and this linksys router acts as DHCP server too.
I suppose I have to use "bridge mode" for that to work. But should the linksys be connected to the AEBS using the AEBS's WAN or LAN port?
If I use "bridge mode", then wired computers to the AEBS works fine - getting an IP from the linksys etc. BUT, the wireless clients will have a self-assigned IP and not get through to the internet. It's like the AEBS will not allow wireless clients to "get through" unless AEBS itself is handing out IP addresses.
Page 36 of this manual ( http://manuals.info.apple.com/en/DesigningAirPort_Networks10.5-Windows.pdf ) shows the setup I want. But in the picture, it says "Ethernet WAN port" but the text says: "The Apple wireless device (in this example, a Time Capsule) uses your Ethernet network to communicate with the Internet through the Ethernet LAN port ( <--> )." I don't know which one to use, WAN or LAN - they show WAN but say LAN?
When I set it up as "share an IP address", the AEBS status tells me "double nat" and to change from "shared IP" to "bridge mode". I do that, and everything seems fine - for the wired clients. Now the wireless clients cannot connect, Airport on the MacBook Pro just say "Connection failed" and the MacBook says "Invalid password" (translated from danish), even though I set the Airport Utlity to save the password in keyring, so it should be correct... If I disable wireless encryption, the wireless clients will connect but get a self-assigned IP, and therefor not work (cannot get online)...
It seems the only way I can get wireless to work, is if I set AEBS up as DHCP, but then it won't be on the "same network" as the linksys (192.168.15.1), but rather on 10.0.x.x as I select. If I select 192.168.x.x within AEBS, I'm also getting some error messages, conflict/subnet thing.
Anyway - I really hope somebody knows how to get wireless clients to get an IP address from existing ethernet when connected to the AEBS.
Thanks!!

I've given up and had to go back to running "Double NAT" which also reports as a "problem" within the AEBS, but I just "ignore" it so the light will always be green.
It still ***** though, as "Double NAT" is also a reason for "Back to my Mac" not working properly, but how the ** am I supposed to avoid Double NAT when the wireless will not work in bridged mode?!

Bridge Mode and Wireless Clients

I have my network up and running fine, but I am now thinking I may need to tweak it a bit. I have an AEBS(n) and an Airport Express both set up with WDS. The Extreme is the base station and the Express is set in WDS Remote and in Bridge mode under the internet tab. The Express is hooked up via a wired ethernet connection to my PS3. Everything works.
I am wondering if in bridge mode, the express accepts wireless clients as well as providing net access to my PS3 over the ethernet cable. Both the extreme and express stations are close enough together that I am not sure which one I am connecting to when I use my laptop wifi.
Thanks in advance for your help.

I am wondering if in bridge mode, the express accepts wireless clients as well as providing net access to my PS3 over the ethernet cable.
Yes if you enable that option.

1310 root bridge w/ wireless clients

Similar Messages

Maybe you are looking for