What's new

Meraki Limits firewall throughput

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

this is a terrible move for Meraki

Wow... in some ways though, it sounds like a bug fix gone awry... QoS is supposed to be a minimum committed bandwidth, not a maximum...

Between the conversations on Reddit and Spiceworks, I'm sure they'll figure it out...

@L&LD - I'm told by a couple of sources that Cisco has been fairly benign - it's not a core market, similar to what they did with Linksys - reporting P&L to the mothership, and getting some front time with their sales team, other than that, the Meraki business pretty much stands on it's own..
 
min/max bandwidth... I've always seen the term "bandwidth management" to mean limiting the peak and average rate for a flow (TCP or UDP/RTSP). To prevent hogging, get fairness per admin policy. QoS I think of in VoIP terms where a min is what's important.
 
@L&LD - I'm told by a couple of sources that Cisco has been fairly benign - it's not a core market, similar to what they did with Linksys - reporting P&L to the mothership, and getting some front time with their sales team, other than that, the Meraki business pretty much stands on it's own..

I worked with Meraki about 18 months ago on a big financial solution and at that time they were operating almost exactly like you've stated.
 
@L&LD - I'm told by a couple of sources that Cisco has been fairly benign - it's not a core market, similar to what they did with Linksys - reporting P&L to the mothership, and getting some front time with their sales team, other than that, the Meraki business pretty much stands on it's own..
I worked with Meraki about 18 months ago on a big financial solution and at that time they were operating almost exactly like you've stated.


What they present to outsiders is not what necessarily happens internally. I do not have facts one way or another except that part of me that says 'what would common sense' indicate.

And that says they do not operate as independently as they would like us to think.
 
Well common sense with indicate they're going to do whatever they can to maximize profits. Cisco is pretty good at that.

What Cisco provides (at least to my knowledge) at this point is financial backing, marketing, and engineering insight (from a business standpoint). To me, the original issue falls under the third heading - it certainly seems to be something that could have come from Cisco. Of course, I'm a little biased - I've been dealing with Cisco for 25 years and I believe them to be some of the shadiest m*****-f****** on the planet.

Meraki is still being operated like a wholly-owned subsidiary other than those things.
 
When you pay for hardware and then pay a subscription fee to use it, the company that made the product will be more likely to make business decisions that are not in the customer's best interest.
From a psychological standpoint, a user will be more willing to accept a little screwing over if the alternative means turning their hardware into a paperweight.

Cloud reliance allows more for this type of business to consumer relationship.

vJXqv3f.png


While it seems that they may have backtracked on that decision, it really seems like it was done on purpose. From my experience with alpha and beta level firmware, it is rare to push one out without verifying that the performance has not been negatively impacted.

They may have been testing the waters to see how much they can screw people over.
 
Last edited:

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top