@Vincent-TP Hi Vincent TP,.
Without going into to much detail about my application, it is super critical that I have no unnecessary traffic on these networks. FWIW I have over 30 EAP245s!
So yes I do have a networking issue now using the EAP 245s with the latest firmware. My application doesn't work correctly.
1, The behavior has changed with the latest firmware, which I can not downgrade to previous anymore.
2, The only reason why I upgraded was hoping that there will be a "stand alone" mode. Joke on me for not doing testing and research prior to flashing all of them.
3, The omada address in the config is 127.0.01 but id doesn't matter what it is.
First it will do a DNS query, if that is blocked, it will then send a broadcast to x.x.x.255
If I kill the MAC in the DHCP server it will then send broadcast to x.x.x.255:67 and 68.
So with the latest firmware I have no ability to kill this omada searching for home feature, and with the number of EAP245s on the network this adds up and my time critical application does not work properly. Please test this in your lab to ensure you are fully understanding what I am talking about.
Clearly you have made an effort in development to make the OMADA call home function much more resilient in the latest firmware, which may be ok for those who are using your APs with a controller, but devastating for those who just want to use it as a standalone device.
All you need to do is add a switch in the firmware that is "Stand Alone Mode vs OMADA mode" and in standalone mode there should be no looking for omada controller in any fashion. Till then I need a solution (a hack over SSH or whatever) to make all this stop!
FWIW I even tried to turn of L3 management and then use your Omada Discovery Utlity, which is basically useless as it only allows you to set Omada controller address and does not have the ability to l2 manage the AP.
Again the trick I used previously that worked well, was to change the last 2 cotet of the MAC address in DHCP so tha AP did not get an IP at all. This turned off all broadcasts.
When I needed to manage the AP for whatever reason I then put the correct mac in DHCP waited for lifetime experation and I was able to manage. Then set DHCP back to incorrect mac and the APs were quiet. This no longer works as now there is endless DHCP boradcasts from all these APs degrading my time sensitive network.
