3 ms·

I experience basically the same level of problems on our office's Cisco Meraki gateway/firewall. A couple months ago we had to do a support ticket to get them t

I experience basically the same level of problems on our office's Cisco Meraki gateway/firewall. A couple months ago we had to do a support ticket to get them to fix their spanning-tree implementation because it configured loops in our simple dual-master crossover switch configuration, forcing us to disable one of the masters. Then there was a spurious packet loss problem in one of the default configuration parameters. Now it just randomly stalls TCP connections open until the local node closes them, but allows the remote node to continue receiving packets(!), which is probably the worst thing a TCP system can do aside from simply not connecting. I quite literally had to attempt this post twice before giving up and connecting to a UDP VPN. I have watched my colleagues cancel and refresh webpage loads for the last few months.

jonatron 10y ago
I've had all sorts of problems with Meraki APs. They claim to hop around to find the clearest channel, but they all always chose channel 44. Manual channel selection was limited to non DFS channels, otherwise they'd switch back to channel 44. There was no insight into CPU usage, so we were suspicious that some QoS settings made everything grind to a halt, but we couldn't confirm. Switched to high end Ruckus APs and a Juniper router/firewall and it's now working properly.