![]() To confirm, I also disabled all firewall rules and set a permit any any inbound on both the IoT VLAN and the Management VLAN just to make sure everything was wide open, and the SDN Controller software still failed to detect my APs across the subnets.Īm I missing something? Are my ports incorrect? I'm about to start doing packet captures, but I don't know how to tell the SDN software to initiate a scan for APs, so I'm just going to let it run for 10-15 minutes and then filter for the SDN Controller IP.ĮDIT: We have a working solution!! As recommended here by u/D3v01d, DHCP Option 138 was enough to signal my APs in the other VLAN to find my Omada SDN Controller for adoption! Thank you also to u/jcsuperfly in this comment for pointing me to the Omada SDN Controller software manual which highlights this exact issue on. Here's what I have on my firewall:ĭespite those rules applied to my firewall, I cannot seem to get the Omada SDN Controller software to detect my APs. I've reviewed my firewall policies and confirmed with TP-Link documentation. Install ubiquiti device discovery tool by searching for it after you log into. I've confirmed that the device where the controller software lives is able to ping both APs. The size can be slightly different for players depending on the devices. Ubiquiti devices will include more information such as MAC address and documentation such as Quick Start Guides and Datasheets. Tap each device to see its IP address and start a port scan to verify which ports are open. Once I had it set, I moved the device with the SDN Controller software to an IoT subnet, but the controller cannot communicate with the APs any longer. Discover devices Refresh to see devices connected to this network. Earlier today, I set up the Omada SDN Controller application in the same subnet and VLAN as the EAPs just to test out its functionality. ![]() I previously had a Ubiquiti Unifi setup with the Unifi Controller, but I've moved over to EAPs this week.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |