I think it's expected that you can access only the AP that you are connected to. If that is the VC, you should be able to access the WebUI as well.
I'm not sure if that can be changed, as it probably has to do with a separation of the datapath and control path within the AP infrastructure.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------
Original Message:
Sent: Oct 12, 2024 07:01 PM
From: Kevin Rice
Subject: IAP-325 GUI unreachable via Wi-Fi side (but Wi-Fi Internet access works)
I find this very odd. I'm a bit stumped.
I have a pair of IAP-325 (v8.10.0.14) installed in a fire station for non-business use:
INTERNET --> ROUTER --> SWITCH --> IAP-325 (x2)
- I cannot access the GUI or even ping the APs when connected via Wi-Fi, but can do both from the wired side (either remotely or from the router).
- Similarly, I cannot ping the SWITCH from the Wi-Fi side, but can ping the switch from the router and the Internet.
- From the same Wi-Fi connection, I can ping and access the router GUI and the entire Internet. Just not the APs and switch.
How could I possibly be able to ping and access the router (and entire Internet) via Wi-Fi, but not the switch or APs? At the same time, everything works fine from the wired side! Everything has been rebooted.
Any ideas?