09-24-2018 12:28 PM
09-25-2018 08:17 AM - edited 09-25-2018 08:19 AM
If your controller is public facing, then yes you can do as you suggest, but for many of us, the wifi network we manage sits behind a public facing router that someone else manages.
It's true that my suggestion only works if you have a USG managing your internet connection.
But the AP itself doesn't have a public IP address. The public IP is assigned by the NAT device (typically the router). If you don't have a way to ask the router what it is, then you have to ask something on the public internet to tell you what address it is seeing as your source address.
After a little googling, I found web site htttp://ipv4.me which seems intended to give you exactly that. However, when I try it, while it gives a plausible address, it isn't the same address that the controller tells me. (They are both in the the 24.62.x.x range.) I don't know the reason for the difference.
01-24-2019 04:43 PM
I tried the terminal solution, but I've only ever had the controller terminal work a handful of times to AP's. However, I was able to download what looks like the info that used to be available in the file by clicking on the AP -> Config then at the very bottom download device info. Near the top of the json file is a line called "connect_request_ip". That is the external IP that the AP is trying to connect from. So if your controller and AP are internal it will likely show the local IP, but if the controller is external then it will show what IP the AP is trying to connect from which is the external IP.
3 weeks ago - last edited 3 weeks ago
Hi, just in case folk were looking on a linux system or cloud key, you need to go to /user/lib/unifi/logs and look at the server.log file, you will identify the AP by its alias name, and you will also see its local lan address and the wan address its coming from. Might need to get a root shell to get there, ie sudo /bin/bash