Current connection issues (problems with setup)
Current connection issues (problems with setup)
This setup seems unusual. If your PC is handling the software, it should stay active continuously (unless there’s a major issue). Using an older laptop or Raspberry Pi might be practical. Ensure the controller can run on Linux. Since both devices share the same network, they should locate the APs if the software functions correctly. Verify there are no manual steps like buttons or modes required for discovery. If needed, operate the APs as standalone units with identical SSID and password temporarily.
I just finished a small project and it works well for my home even with thin walls. I’m planning to set up an rPi with an Ubuntu server to run the Omada Controller. I’ve discovered some guides from the past year that match my setup needs. I’m still confused why my PC isn’t functioning as a host, but it’s puzzling. My goal was to use my PC and the controller for configuration, leaving things as they are. I don’t need constant monitoring, so I only have to start Omada to adjust or troubleshoot later. Still, I see that keeping the controller running 24/7 would improve reliability.
The Omada hardware controllers can be quite tricky to configure. They automatically assign themselves an IP address within the 192.168.1.X network. Since I’m unfamiliar with the software side, but it seems there are no VLANs in place—you can ping the individual access points—and you could reset them to check if they appear online and can be connected.
The Omada system oversees all access points and ensures smooth communication between them. You can operate each AP independently without a controller, but using the controller improves coordination during transitions. The controllers—whether software or hardware—offer ongoing monitoring, making it essential to keep the software active around the clock.
The issue is that nothing I do makes them show up in Omada. A fresh hard reset plus a PC and software reboot, along with resetting the APs and router, didn’t bring anything into view. They’re still there but pingable individually, which explains it. I thought once the hardware was configured as a mesh network, the APs would manage the switch based on performance, but they weren’t acting when the change should have happened.