cancel
Showing results for 
Search instead for 
Did you mean: 

AP-7522 Client Bridging Isn't Working

AP-7522 Client Bridging Isn't Working

Aaron_Wright
New Contributor

I have two AP-7522 access points. Both have version 5.9.1.4-004R. Both receive their power and network through a Symbol AP-PSBIAS-2P2-AFR "brick". I set the country name to "United States-us" on both because I read the radios will not turn on until you do.

AP#1 - This is the "host" access point connected to the wired LAN with access to the internet. The internal network is 192.168.1.0/24. I've given this AP the IP address 192.168.1.101. I configured a wireless network with SSID "myWireless", Secure-PSK, WPA2-CCMP, and the key is "myWirelessKey". Radio 1 is 2.4GHz, radio 2 is 5GHz.

AP#2 - This is the "client" access point that I want to bridge to AP#1. I have AP#2 connected to an unmanaged 5 port switch, which also connects a desktop PC. It's this desktop PC that needs access to the internet. I've given this AP the IP address 192.168.1.101. For the bridging configuration I followed the directions here (https://extremeportal.force.com/ExtrArticleDetail?an=000082884)

  • en
  • conf t
  • profile
  • interface radio 2
  • rf-mode bridge
  • bridge ssid myWireless
  • bridge vlan 1
  • bridge encryption-type ccmp
  • bridge authentication-type none
  • bridge wpa-wpa2 psk 0 myWirelessKey
  • no bridge eap username
  • no bridge eap password
  • bridge eap type peap-mschapv2
  • bridge roam-criteria missed-beacons 20
  • bridge roam-criteria rssi-threshold -75
  • bridge channel-list 5GHz 36,40,44,48
  • bridge channel-list 2.4GHz
  • comm wr

However when I run "show wireless bridge candidate-ap" it reports 0 candidate APs. AP#1 shows no wireless clients. The workstation can successfully ping AP#2 and vice versa. I am able to reach the web interface and ssh on AP#1 on the 192.168.1.0/24 network. But AP#1 can't ping AP#2 and vice versa. Nothing on the 192.168.1.0/24 network can ping AP#2 or the desktop PC. The desktop PC cannot reach anything on the 192.168.1.0/24 network.

Right now both APs are in the same room, 10 feet from each other, no physical obstacles between them.

In my searching I also found (https://extremeportal.force.com/ExtrArticleDetail?an=000063492) I tried the solution there but it didn't help.

Does anyone know what I'm doing wrong, or what I'm missing?

Additional questions:
1 - Do I have to configure any bridging properties on the AP#1 that is connected to the wired network with internet access? None of the guides I've read mention anything about configuration on the "host" AP, but since I can't get this working I'm wondering if some configuration is necessary on AP#1.

2 - Do I have to load a special firmware version to be able to access bridging configuration in the web GUI? Right now none of those configuration options are there and I have to do everything through ssh/command line. I know this was the case for some APs in the past that didn't have a web GUI at all and you had to download the firmware that included the GUI.

Thanks for any help you can provide!
Aaron

44 REPLIES 44

Aaron_Wright
New Contributor
I log in via ssh, then enter the commands "en", then "self", then "show context". Below is the output. I'm typing this by hand, not copy/paste, as this is the desktop PC connected to AP#2 and it doesn't have internet access. Might be typos, I'll do my best to proofread.

I gave the wired interface ge1 the IP address 192.168.1.102/24. Is that going to conflict with anything we're adding to this profile PROFILE-AP7522 ?

  • ap7522 B8-50-01-A8-19-50
  • use profile PROFILE-AP7522
  • use rf-domain default
  • hostname ap7522-A81950
  • ip default-gateway 192.168.111.1
  • interface vlan1
  • description "WAN Interface"
  • ip address 192.168.111.102/24
  • no ip dhcp client request options all
  • no shutdown
  • no virtual-controaller
  • rf-domain-manager capable
  • ip dns-server-forward
  • ip nat inside source list default-B85001A81950-nat precedence 1 itnerface vlan1 overload
  • no adoption-mode

ckelly
Extreme Employee
I should've remembered that too.
Any time you create a new Profile....it doesn't come pre-populated with VLAN-1. You need to manually add it if you need it on the AP.

In this case, you need to go into the Profile and create the VLAN-1 entry:

    en config t profile ap7522 PROFILE-AP7522 interface vlan 1 commit write optionally - ip address 192.168.1.102/24 (you could also enter this address in the override section) commit wr
This missing VLAN-1 entry shouldn't stop the AP from being able to discover candidate APs though.
What other entries are there in the self (override) section?

What is the output of:

show wireless radio

Aaron_Wright
New Contributor
Update: I issued the command "use profile PROFILE-AP7522" and now "show context" reports that profile is being used. Still have zero candidate APs though.

I'm looking at the output of "show running-config" and PROFILE-AP7522 doesn't have any "vlan 1" entries in it. I entered the vlan commands from the bulleted list though. Is this an issue?

ckelly
Extreme Employee
Aha...so there's the issue then.

Command to change this:

  • en
  • self
  • use profile PROFILE-AP7522
  • commit write
As long as you're in the override section, what else is in there? Just want to make sure there's nothing else that is going to mess things up.

Aaron_Wright
New Contributor
The entry says "use profile default-ap7522". How can I switch it to use PROFILE-AP7522?

How can I perform a factory reset to get back to the default configuration? Do I log in as user "reset" and password "FactoryDefault" ? I've tried so many things, one of my previous attempts to fix the problem might actually be causing me problems at this point and I need to start from a clean slate.

GTM-P2G8KFN