AP 120 not publishing SSID
Sorry if I'm in the wrong forum. But I have a WG AP 120 I'm trying to use again. Its paired through Gateway Wireless Controller via the gui and I have SSID assigned to it.
But I don't see the SSID even though its published. I see this on traffic monitor for the AP's IP. It says SSL handshake error.
0
Sign In to comment.
Comments
This is how the AP is connected. Its connected to a Netgear PoE smart managed switch on VLAN 1. Also the 2.5 and 5.0 GHz lights are not lit, but power is on.
I found this. Looks like I need to allow the AP (10.0.0.154) access to these?
HTTP port 80
HTTPS port 443
UDP port 3851
UDP port 3852
*.cloudwifi.com
redirector.online.spectraguard.net**
https://www.watchguard.com/help/docs/help-center/en-us/Content/en-US/Wi-Fi-Cloud/getting_started/connect_device.html
That link is not for the older AP models including AP120.
"As of Fireware v12.11 and higher, only AP125, AP225W, AP325, AP327X, AP420 devices that run the latest v11.0.0-36-4 firmware are supported by the Gateway Wireless Controller on a Firebox."
from here:
Cannot connect to APs after Firebox upgrade to Fireware v12.11
https://techsearch.watchguard.com/KB?type=Article&SFDCID=kA1Vr0000009EuzKAE&lang=en_US
So what are my options if I still want to use the AP 120? I don't really want to downgrade the Fireware version.
Can I not connect it to Gateway Wireless Controller and use it as a stand alone AP? When I first turned it on, I could ssh into it, but I couldn't figure out the default password. But now I can't ssh either. This is going to be used as a temporary AP.
The only option to use it is to use a Fireware version lower than 12.11 to control it.
Ok so that means its unstable unfortunately.