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!

Similar Messages

  • 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?

  • I cannot get my Airport Express to accept wireless clients.

    I cannot get my Airport Express to accept wireless clients. After resetting to factory default and reconfiguring, it works briefly but then stops again.
    The Airport Express is on the second floor of my house and is seen by Airport Utility. Using a LAN cable with the Express works no problem.
    My network is created by an Airport Extreme (ground floor) and extended by a Time Capsule (first floor)
    Have run through all settings repeatedly and as I said I can get it to work briefly by resetting and then reconfiguring, but after a short while again my iOS devices can no longer connect and revert to cellular.

    I cannot get my Airport Express to accept wireless clients. After resetting to factory default and reconfiguring, it works briefly but then stops again.
    The Airport Express is on the second floor of my house and is seen by Airport Utility. Using a LAN cable with the Express works no problem.
    My network is created by an Airport Extreme (ground floor) and extended by a Time Capsule (first floor)
    The issue is most likely due to the fact that the AirPort Express may be too far from the AirPort Extreme to properly extend it with enough bandwidth to be useful.
    It is important to understand that with Apple 802.11n or 802.11ac base station an extended network works in a wheel-like fashion with the base station to be extended at the hub and each extending base station along one of the spokes. This type of configuration does not allow for daisy chaining the base stations. That is, in your case, both the Time Capsule and AirPort Express are attempting to extend the AirPort Extreme.
    Each extending base station must be within a certain signal quality range in order to extend the network properly. Please check out the following AirPort User tip for details.

  • Extending wireless network - allow wireless clients or not?

    Hi,
    sorry if this is a stupid question but I cannot find the answer on the internet.
    I have a setup with 3 level house, 3 airport extremes, the one in the middle connected via ethernet to router and acting as DHCP server.
    The other two are setup to 'extend network'
    Question I have is should I check "allow wireless clients" or not because when I do it seems to make the main AP extreme a client of the other two as well. This seems strange to me. any help would be appreciated.

    do you work in entertainment industry at all? I know a bob timmons...
    That would not be me.
    any ideas why my extension airport extremes see the main DHCP extreme as clients?
    This is normal. The "main" base station is a client of the "extending" Airport....and the "extending" AirPort is a client of the "main" base station.  You would not have any extension if they were not clients of each other. In simple terms, they are communicating with each other at all times.
    also any idea of the actual range of the AP extremes?
    They usually check out at about 45-50 meters or 150 feet or so....but range measurements are made in "free air" in a large space....like an airplane hangar......with no obstructions in the signal path. Most homes are laid out a bit differently.
    I've seen installations where the signal would barely go through one wall to a computer that was no more than 10 feet away from the router.  The wall was metal lathe and plaster, so in effect the very weak signal was being asked to power though metal. Not much signal was getting through.
    In very general terms, a typical wall of sheetrock or wallboard and 2 x 4s will absorb on average 15-20% of the wireless signal. A ceilng will absorb much more because it is much thicker.  In most homes, after 3 or 4 walls, or a ceiling and a wall, there won't be much signal left.
    Now, if you  have adobe walls or cement walls or ceilings, everything changes dramatically. You get the idea.
    My home is about 2400 sq ft, single level, of typical construction.  I use 3 AirPort Extremes....all connected by Ethernet....not wireless....to get full speed, fast coverage virtually everywhere.  I use an AirPort Express to "extend"....using wireless only....if I want to take my laptop out on the patio.
    Older iPhones can connect at maximum 54 Mbps if they are literally right on top of the router. Typically,they might be at 25-35 Mbps or so with a good signal in the next room.  The 180 and 270 numbers signify that these connections are 5 GHz...probably a newer Mac laptop or iMac.
    If you have a Mac laptop and don't mind a $3 investment to get a good utility, WiFi Explorer can reveal some very useful things about your network.  Post back if you are interested and we will take this up on Thursday.

  • The master extreme does not seem to be able to accept wireless clients.

    I have a roaming network setup with several extremes/express devices. The probem I am having is the master extreme which is in the garage does not want to accept new wireless clients. I have 3 other devices which work just fine. They hand off clients as you move around the house. You can see the wireless network on your device and when you select it you get a pop up window prompting you for the password??? You enter the passwork/key and nothing seems to happen.

    Yes all of my base stations have the same network name, same password and same security setting. I have Comcast as my network provider. I have the latest airport extreme connected directly to the cable modem in the garage. I have 2 other base stations of the previous verison in house. One in my office and one in the living room. If I am moving around in the house I can use the airport utilitiy to look at those base stations and see which wireless clients they have. If I go out into the garage and try and connect to the wireless network the device appears to be trying (spinning dial icon) and then comes back with the pop up requesting a password. I have tried entering it and again it will appear to try and connect for a few seconds and then the pop up will appear again. I I walk into the house the device will connect with one of the other base stations.
    Also all of the base stations are connected via ethernet cable to the main base station in the garage. They are connected directly with no switch or router between them.

  • Network Policy Server windows 7 non domain wireless clients could not connect (Event id 6273 reason code 265)

    Hi,
    We have successfully configured network policy server on windows server 2012 and all wireless clients could connect to our network except windows 7 and xp non domain clients.The clients that are successfully authenticated includes windows 8,mobile users
    (andriod + iOS) domain as well as non domain clients.If we join windows 7 pc to the domain it  successfully connects but non domain clients could not connect.We have large number of windows 7 users that have their own laptop machines and we dont want
    each laptop to join the domain.
    On server event 6273 generated with reason code 265 "The certificate chain was issued by an authority that is not trusted".Plz help how to resolve this issue.I have searched on the internet but no proper solution found.

    Hi,
    According to the error message, it seems that you used certificate-based authentication methods and the non-domain computers has no Trusted Root Certificate for the CA that enrolled the certificate for the NPS.
    For more detailed information, please refer to the links below:
    Certificates and NPS
    Manage Trusted Root Certificates
    Best regards,
    Susie
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Flexconnect AP(Local Switching) Wireless clients are not able communicate eachother

    Hi,
      Scenario :  We are deployed the WLC in Corparate Office and Access Points are placed in Branch Office with FlexConnect Local Switching mode.
    In this case, I am not able to Ping the Wireless clients eachother . Peer to Peer Block Option also Disabled.
    Some time Wireless clients Ping eachother & some times not. Both Wireless clients  are associated with Same AP & Same WLAN SSID.
    Please help me urgent ..
    Devices :
    1)WLC 2500 series , Software 7.2
    2)Cisco 1400 series APs
    3)CISCO ACS server for AAA authentication
    Regards,
    Shanmugam Nachimuthu

    Hi Shanmugam,
    Please apply following steps to configure P2P setting for WLAN:
    Step 1 Choose WLANs to open the WLANs page.
    Step 2 Click the ID number of the WLAN for which you want to configure peer-to-peer blocking.
    Step 3 Choose the Advanced tab to open the WLANs > Edit (Advanced) page.
    Step 4 Choose one of the following options from the P2P Blocking drop-down list:
    • Disabled — Disables peer-to-peer blocking and bridges traffic locally within the controller whenever possible. This is the default value.
    NOTE: Traffic is never bridged across VLANs in the controller.
    • Drop—Causes the controller to discard the packets.
    • Forward - Upstream — causes the packets to be forwarded on the upstream VLAN. The device above the controller decides what action to take regarding the packets.
    NOTE: To enable peer-to-peer blocking on a WLAN configured for FlexConnect local switching, select Drop from the P2P Blocking drop-down list and select the FlexConnect Local Switching check box.
    Step 5 Click Apply to commit your changes.
    Step 6 Click Save Configuration to save your changes.
    Thanks,
    Prashant Gondaliya

  • Why do some devices show up as wireless clients and not DHCP clients

    When looking at the 'Logs and Statistics' section it shows me the MAC addresses of 3 wireless devices I have on my W/LAN (Macbook and 2 wireless PVR's) in the 'wireless clients' section but no info on the 2 wireless PVR's in the DHCP clients section. Only the Macbook appears there with its ip address shown. Can anyone tell me how to find out the ip addresses of these 2 other devices. I tried connecting one of the PVR's via a cat 5 but that one still doesn't show up in the DHCP clients section.

    Esterhazyinoz wrote:
    Can anyone tell me how to find out the ip addresses of these 2 other devices. I tried connecting one of the PVR's via a cat 5 but that one still doesn't show up in the DHCP clients section.
    Try scanning with WakeOnLan to get a list of all devices and their IP addresses. If the devices got fixed IP addresses at the factory, they won't show up under DHCP.

  • "add wireless clients" functionality --not working

    I'm hoping someone can help me figure out the Add Wireless Client functionality in the AirPort utility. I can't seem to get it to work, and even Apple support appears to be stumped.
    I have tried using the "add wireless clients" functionality in the Base Station menu of Airport Utility. When the "Wireless Client Setup Assistant" window opens, there are two choices: PIN or First attempt. Neither option seems to work. In fact, if I try to enter a PIN, I am able to enter a series of numbers, but the continue button does not become enabled.
    Is anyone able to get this to work? I called Apple support and they were supposed to get back to me but they as of yet haven't offered a solution.
    I have an airport extreme 802.11n and express configured in a WDS. Everything else is working perfectly.

    James,
    This topic has been previously discussed - the URL to one such thread which may assist you is http://discussions.apple.com/thread.jspa?threadID=855971
    Regards,
    Chris

  • WAP4410N stops accepting wireless clients

    I have two WAP4410N. One of he accesspoints is connected to our wired LAN, called by now AP1. The other accesspoint is connected to the first accesspoint by WDS (Client mode) called now by AP2. I have upgraded both accesspoints to firmware 2.0.4.2. Both accesspoints are set to the same SSID and channel (6) and are set to mixed mode (B/G/N). After I two weeks they started to fail. When I connect to AP1 I don't reveive an IP-address of our DHCP server from our LAN. I'm able to connect to AP1 from our LAN. When I SSH to the box and I do an dmesg command, I see the following messages:
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    I'm still testing these devices and I hope I can use these devices in our production environment,which is not possible with these errors and outages.
    I can't connect to AP2 right now. I think the whole wireless interface isn't working anymore, unless I power off/power on the box. But it's hard testing when it works ok for two weeks and then stops.
    Message was edited by: Sander Cornelissen

    After your advice I did a factory reset of both AP's. From 17 october until today it worked fine. Today it crashed and the connection to the device isn't usable.
    In the dmesg, from the SSH console to the AP, I did notice the following text:
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    Going to erase from sector 00000085 to 00000086..
    erasing bf7e0000...
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    I have to power off and power on again to make the device work.

  • New Wireless clients certificate not verified

    Whenever a new clients login using SSID Green,using cisco WLC 4404, there is a prompt saying certificate is not valid. No doubt, clients can connect once they accept the certificate. Is there anyway I can remove this prompt? We have ACS doing authentication.The certificate is signed by authorized bodies? Please advice

    I have indeed.
    Pushing the profile can happen a few ways. If you use ISE you can push a profile in auto enrollment. Whereby you create the wireless profile (SSID, Security, Add Cert). This is delivered to the user automatically during enrollment.
    Another way to make profiles and manually push is with the Apple Configurator.
    https://itunes.apple.com/us/app/apple-configurator/id434433123?mt=12
    You can also use a tool like Jamf for MACs to make and push profiles.
    Hope this helps ..
    "Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
    ‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."
    "Im like bacon, I make your wireless better"

  • 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.

  • 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.

Maybe you are looking for