Accessing FAP221C web interface

[Frosty]

We have a number of FAP221C units managed through our Fortigate FG200E.

I would like to connect to the web interface of each AP, just to see what's going on with each unit.

I created a policy to allow traffic to the IPs of the APs in the wireless subnet.  I can ping the units on their IP, but I can't access the web interface.

So I suspect that I might actually need to get a longer ethernet cable and connect directly to the units up in the roof space.  Does anyone happen to know if that is required in order to see the web interface?  I read elsewhere that the default IP of each AP would be 192.168.1.2 (or something like that).  

[Toshi_Esumi]

Did you allow "https" access to the APs at the profiles? In GUI, "Administrative Access" checkboxes. In CLI, under "config wireless-controller wtp-profile" then edit the profile name, and "set allowaccess https".

[Frosty]

Interesting. 

I'm running FortiOS v5.6.11 and there is no option for "Administrative Access" anywhere in the GUI.  I checked with both Chrome and IE just to be sure that something wasn't rendering right.

Have been able to set it via CLI though ... thanks!

Will need to reboot APs tomorrow morning to pick up the change.

[Toshi_Esumi]

An GUI example found on the internet:

https://amyengineer.files.wordpress.com/2018/09/createap-profile.jpg

[Frosty]

Yep, I can see that in the screenshot, just under the AP Login Password line, near the top.

But that doesn't show up in v5.6.11 running on my FG200E.

[Dave_Hall]

If you need to connect to the AP GUI (and you do not have/see those admin connection options in the AP profiles) you should be able connect to it before it discovers/connects to the Wifi controller - either reboot it and/or temporary deauthorize it from the 200E - both options are really not good in my opinion.

If you need to monitor/troubleshoot the APs/wifi issues, you should be able to do it from the Wifi Health monitor

A couple things I do like to do on the APs though is set a default static IP on them (from 192.168.1.2?) in the event they are unable to obtain an IP from the network they are connected to, and add a static IP for the wifi controller (setting).

[Frosty]

Thanks for the extra info and suggestions.

After a reboot of the WiFi APs this morning, I can now access their web interface fine, so the CLI commands did the trick.

One less thing on my "to do" list!