- 1. Can I configure a Controller for Captive Wi-Fi without having a Captive router attached?
- 2. I have a Wi-Fi client device connected to my Captive router. Why does the Controller display this as a wired client?
- 3. When I try to log into my Controller, I log into the Captive router instead. How do I fix this?
1. | Can I configure a Controller for Captive Wi-Fi without having a Captive router attached? | ||
Yes.
| |||
2. | I have a Wi-Fi client device connected to my Captive router. Why does the Controller display this as a wired client? | ||
This is expected. What you will see: When the Controller GUI is used to inspect the status of attached client devices (Status > Clients), those devices will appear in the Wired Clients table instead of the WiFi Clients table. When the Controller console CLI is used to inspect the status of attached client devices (via the client's command), those devices appear in the Connection Type: all table, but not in the Connection Type: wlan table. Why you see it: The client connection status is reported from the Controller’s point of view. All traffic coming to the Controller from the Captive router arrives through the Ethernet cable connecting them. Thus, the controller sees the Captive, and everything attached to it, as a wired device. | |||
3. | When I try to log into my Controller, I log into the Captive router instead. How do I fix this? | ||
Take the Captive router offline for a few minutes (disconnect it from the Controller, reboot it, or do a factory_reset). While the Captive is offline, refresh DHCP addresses on the client device. This should route those addresses to the Controller instead of the Captive router. The new routing should persist after the Captive router is reconfigured. This problem has been seen to occur under the following set of conditions:
Before a router in accessory mode is captured, it can serve DHCP addresses. This ability is disabled as part of the capture process. If the (soon-to-be) Captive router issues a DHCP address to the client device before the Controller does, then commands like ssh admin@192.168.0.1 will be directed to the Captive router rather than the Controller. This is technically not a bug: the internal network switch in the Controller is doing what it is supposed to do. Run the following commands to find out if this is the case: ping 192.168.0.1 arp -a # Look at the MAC address for 192.168.0.1 and if it is the captive, # you know the DHCP is served incorrectly. A short-term solution to this problem is to reboot the Captive router (or for a little more time do factory_reset). While the Captive is rebooting, refresh DHCP addresses on the client device. This should cause 192.168.0.1 to be directed to the Controller. You can then work as normal. This problem has not been seen on a Controller once it has been configured to capture a router in accessory mode. |