tech-airman wrote: » Instead of configuring the second WAP as a non-root bridge, try configuring the second WAP as a repeater.
SWM wrote: » My problem is the non-root bridge device keeps showing :software hardware status disabled when I select non root bridge. If i configure this interface as a AP it enables fine....
SWM wrote: » encryption mode ciphers tkip
SWM wrote: » parent 1 001c.0ed1.c3d0
SWM wrote: » antenna gain 22
SWM wrote: » parent 1 001c.0ed1.d9b0 parent timeout 65535
tiersten wrote: » It wouldn't bridge the two LANs if you set it as repeater.
tiersten wrote: » No AES support in your AP?
tech-airman wrote: » tiersten, I was just trying to deal with the equipment that already exists which is a pair of WAPs.
SWM wrote: » I am happy to tighten security once the two waps are talking. hey I would even use WEP just to get bi directional communication happening, and then increase security.
SWM wrote: » I used the GUI interface to configure and its put the same SSID on both the A and G radio !
SWM wrote: » Do i need a different SSID on each but a matching SSID on both A's at each site that match each other?
tiersten wrote: » Okay? SWM is trying to replicate the original configuration. If there isn't a wired LAN in the 2nd building then a repeater would work. If there is one then you'd need to use a bridge.
tech-airman wrote: » tiersten, At the time of my post, the above was unknown information based on the OP at the time.
SWM wrote: » So you are saying both external 802.11a interfaces have the SAME SSID. Is this how the non-root bridge knows who it is allowed to communicate with?
SWM wrote: » If so what prevents another WAP from attempting to connect to my root-bridge WAP if it can see and copies my SSID ?
SWM wrote: » Thanks for all the replies [HTML] Quote:Originally Posted by tech-airman Instead of configuring the second WAP as a non-root bridge, try configuring the second WAP as a repeater.It wouldn't bridge the two LANs if you set it as repeater. [/HTML] Correct, thats why a repeater is not a option. Each WAP needs to provide local Wireless and ethernet access.
SWM wrote: » [HTML] Quote:Originally Posted by SWM parent 1 001c.0ed1.c3d0[/HTML] I was clutching at straws when I entered that. The event log on the non root bridge indicated it cannot associate, so I gave it the root-bridge mac address.
Cisco Aironet Access Point FAQ wrote: Q: Which devices can associate with an AP? AP to client AP to AP (in repeater mode) AP (in repeater mode) to base station (in AP mode) AP to workgroup bridge
SWM wrote: » [HTML] Quote:Originally Posted by SWM antenna gain 22You do have a directional antenna with gain?[/HTML] Yes each site has a 22db external roof mounted antenna [HTML] Quote:Originally Posted by SWM encryption mode ciphers tkipNo AES support in your AP? [/HTML] I am happy to tighten security once the two waps are talking. hey I would even use WEP just to get bi directional communication happening, and then increase security. I used the GUI interface to configure and its put the same SSID on both the A and G radio ! Do i need a different SSID on each but a matching SSID on both A's at each site that match each other? The Cisco help and documentation is very vague.
tech-airman wrote: » Note that "AP (in non-root bridge mode)" is NOT listed. The purpose of using an AP (in non-root bridge mode)" is so that the AP can associate with a wireless bridge in root bridge mode. You cannot associate an AP in non-root bridge mode with an AP in root bridge mode as you learned.
SWM wrote: » I will give it a go over the next day or so, because I have external antenna, I cannot configure it on my workbench, have to connect the antenna and both device in each building.
SWM wrote: » So until I get the WAP's working I have no phone
SWM wrote: » or Internet access.
tiersten wrote: » It does work and that is how you're supposed to do it.
tech-airman wrote: » tiersten, Show me where "...you're supposed to do it?" While we're at it, show me where "...it does work....?" The OP clearly shows that it does NOT work.
SWM wrote: » Hi tech-airman Questions: Where does Ethernet access in Building 1 go to? Where does Ethernet access in Building 2 go to? How and why does the network in Building 1 need to be connected with the network in Building 2? Does any building have a WAN/upstream link and if so, which building(s)? Answers 1. Ethernet in main building is our main LAN, i,e servers, printers DSL router etc, workstations etc 2. Ethernet is second office is used for offsite data backup, and the odd workstation (second building is a warehouse) 3 User need to take laptops from Building one and connect to server infrastructure in building 1 whilst using wireless when in building two. 4 As I said building one has all the infrastructure. The end result needs to be laptops or desktops can be connect either via ethernet cable or wireless in the second office (a tad slower) but have full connectivity... Hope this make sense
tech-airman wrote: » For the WAP in Building 2, set the Dot11Radio1 interface to "station-role workgroup bridge"
SWM wrote: » Thanks tiersten for all your help, its working perfectly. Once I created the SSID that matched on both "A" External intefaces and the required security, the interface on the "non-root-bridge" automatically became "enabled and up" as it could associate with the "root-bridge"
EricO wrote: » I'm glad your issue got resolved. If you ever need to trunk multiple vlans across these things let me know. I've got a couple of configs where the g side is the AP, and the A side is trunking multiple vlans from one building to another.
EricO wrote: » I'm glad your issue got resolved. If you ever need to trunk multiple vlans across these things let me know. I've got a couple of configs where the g side is the AP, and the A side is trunking multiple vlans from one building to another. Hi all I am having the same problem linking two Cisco 1262 AP in 2 seperate buildings with multiple Vlans..One AP in root bridge mode and the second AP in non root bridge mode.. Any config to asist me in setting the APs up so the non root bridge AP can see the Vlans