I fail to see the similarity. Ignoring the fact that I only enquired about the difference of calling ubus command vs ifup and ifdown, that thread is about interfaces, my question is about physical devices.
And yet making changes in Web UI does not necessarily disconnect all clients. I can't find that piece of code tho and looking for help, not random replies from people who "didn’t do a deep dive on your posts".
Flakey wireless is a very general problem with an unknown source, not the kind of thing that one can fix without completely reseting wifi (and kicking clients in the process). In order to have a hope of fixing it without completely reseting wifi you'd need to know more specifically what the problem is.
Each change would do something different. Unless a specific change to the web UI temporarily improves your wifi, then there is nothing there that can help.
I think that the current code does disconnect all clients from that wifi device that you are reloading but not from the other radio. The "wifi" command always runs down+up, in order to get all changes reflected to the radio that you are configuring.
So, if you make config changes to just one radio, it is likely possible to maintain clients connected to the other radio when you reload the config of the first radio..
Thanks! I believe there also was a thread on the old forum, it probably had the same information.
No, I'm not sure. But it's either trying that while keeping the router plugged and possibly capturing enough information for driver developers or unplugging the router and being no help at all for future development.
By trial and error, at least on my device, wifi does not disconnect majority of existing clients if none of the radio's channel is set to auto. Otherwise, radios enter promiscuous mode on restart to search for underused channels and that is noticeable on clients.