|
|
|
If you've got a managed switch, check the logs. I see looped packet errors accompanied by brief traffic storms when it happens. Can see it with 1.0.25.1, .3 and .7. I don't think it's an actual loop (i.e. back through a mesh link) as it can be reproduced with a single connected AP running the affected firmware.
RunningMan:
If you've got a managed switch, check the logs. I see looped packet errors accompanied by brief traffic storms when it happens. Can see it with 1.0.25.1, .3 and .7. I don't think it's an actual loop (i.e. back through a mesh link) as it can be reproduced with a single connected AP running the affected firmware.
I have the grandstream router so I will jump in and have a poke around and see waht I can find, the logs probably won't be much help to me as I don't really know what I'm looking at.
RunningMan:
If you've got a managed switch, check the logs. I see looped packet errors accompanied by brief traffic storms when it happens. Can see it with 1.0.25.1, .3 and .7. I don't think it's an actual loop (i.e. back through a mesh link) as it can be reproduced with a single connected AP running the affected firmware.
I do not have these problems with my GWN APs. However, I have implemented various rules, for example, which prohibit IP-TV multicast messages to become broadcast messages entering the WLAN via the AP ports so as not to clutter up my entire WiFi. If IGMPv3 is not supported or enabled by the switch(es), the multicast becomes a broadcast to all devices in the network. With a single HD stream at 10 Mbit/s and 20 devices in the network, you would generate 200 Mbit/s load. Maybe this hint will help you?
- NET: FTTH & VDSL, OPNsense, 10G backbone, GWN APs
- SRV: 12 RU HA server cluster, 0.1 PB storage on premise
- IoT: thread, zigbee, tasmota, BidCoS, LoRa, WX suite, IR
- 3D: two 3D printers, 3D scanner, CNC router, laser cutter
Well, 1.0.25.10 has been released a few days ago, and seems to have finally resolved the network loop bug.
Avoid 1.0.25.1, 1.0.25.3, 1.0.25.7 as they all seem to cause this issue. In certain circumstances they are creating a storm at the link line rate for a second, having sent a packet with the wrong MAC source address.
michaelmurfy:
better than Ubiquiti in my books ;)
Anything is better than Ubiquiti, I remember when they messed up the meshing and created network loops if a device was wired.
Any views expressed on these forums are my own and don't necessarily reflect those of my employer.
I've only just found this thread - I've been having some random network issues at home with my three APs over the last couple of weeks. Things have seemed stable again over the last couple of days, and this thread explains why!
And as a further update 1.0.25.15 was released a couple of weeks ago. This seems stable as well.
Perhaps it should also be mentioned that the Grandstreams firmware upgrade server's references to model-specific paths have changed.
- NET: FTTH & VDSL, OPNsense, 10G backbone, GWN APs
- SRV: 12 RU HA server cluster, 0.1 PB storage on premise
- IoT: thread, zigbee, tasmota, BidCoS, LoRa, WX suite, IR
- 3D: two 3D printers, 3D scanner, CNC router, laser cutter
Yeah, instead of people not turning on the auto-update function, they went for the nuclear option of changing the upgrade path for each version. PITA.
RunningMan:
Yeah, instead of people not turning on the auto-update function, they went for the nuclear option of changing the upgrade path for each version. PITA.
Sure is. I wish they'd allowed both options myself. Some places will want stability (arguably just dont put in the path) and others will want the latest when its available. Can only assume they were getting too many support complaints about it. But then why not just recommend "dont add the auto update path"?
Actually think they're possibly opening themselves up to more hassles later on. When some vulnerability is discovered, but no one updates because they're not paying attention to patches coming, someone will be compromised. It wont look good for Grandstream when its reported they disabled updates by default.
It stemmed from a few releases back that were very buggy. It seems people had entire sites set up to auto update as soon as new firmware became available then had major issues.
Kind of their own fault really for allowing firmware installation without checking, the fix is to just not turn on auto update. Now Grandstream have made it both difficult to update manually and impossible to update automatically. Overkill.
|
|
|