QUOTE(azbro @ Sep 11 2024, 09:36 AM)
Firstly thank you for the feedback, I might to study more on this tplink omada. It's kind of interested of the capabilities.
QUOTE(razr_sped @ Sep 11 2024, 10:05 AM)
» Click to show Spoiler - click again to hide... «
just in time as mine today it broke 32 devices and i'm seeing unstable networrk issue
using zytel from digi, though it mention 128 simultaneous device on 2.4Ghz but the setup onli allow 32 max.
have tried to put guest network (which doesnt seems to have limit) as same SSID still having issue, need to consider more powerful unit that can handle more devices on the 2.4G single SSID
QUOTE(gerald7 @ Sep 11 2024, 10:46 AM)
wah, thats quite detailed, I was looking at omada stuff yesterday and wondering whats s 'sample' setup would look like, today saw your post. I think you have shown the path for many~
I was always wondering why my IoT devices online offline online offline. Some IP cam also, eventho its within same room of the router. Maybe is the SSID thing.
it's not so much about the 1 SSID vs many SSID.I was always wondering why my IoT devices online offline online offline. Some IP cam also, eventho its within same room of the router. Maybe is the SSID thing.
it just so happened that when i was using Maxis' mesh LG8245X6-10, which is capable of creating multiple SSID, the issue almost disappeared - ALMOST - when i divide into 20-odd per SSID on same mesh network.
i would attribute the problem to these:-
- consumer wifi devices are only capable of handling limited number of concurrent clients. processors just fast enough to turn around a limited number of clients, not to mention having to fight for limited aurtime slot against other APs in hostile vicinity.
- IoT devices are still on the 802.11bg protocol, so they can't benefit from newer, efficient time-sharing protocol.
- IoT don't transmit huge packet, and most of the time idling and sleeping to conserve batteries and what not; probably can't wake up soon enough for their allted transmission slot.
- the flapping issue becomes prevalent if a network has been left running too long, that eventually even my static IP reserved for CCTVs and anything will become not responding. this is educated guess:- when IoT devices reconnect, they'll request new dhcp address, not reuse what was previously already assigned, and my dhcp server kindly and foolishly dish a new address. so to make sure there is always an address available, i shortened my dhcp lease time to 2hrs, which helped to further mitigate the issue.
Sep 11 2024, 11:59 AM

Quote
0.0238sec
0.33
6 queries
GZIP Disabled