@Paul_H I appreciate you taking a stab at answering, and also can appreciate that you have once felt my pain before being brainwashed. 😉 Listen, I know it isn't easy; and I understand the Meraki MO of "simplicity". But I think you have to ask "simple for who"? I can tell you there is nothing simple about a 60 min call (on hold) to get Meraki to enable DH 14. There is nothing simple about the fact that none of my engineers can tell that DH 14 is enabled on a firewall without ANOTHER 60 min call to Meraki support. There is nothing simple about the fact that most of us don't even know WHICH phantom options even exist - no publicly documented list that I'm aware of. I know managing features across different hardware models isn't easy. But have you ever heard of a little company called Ubiquiti? They have figured it out. ...AND they don't even charge a licensing fee. ...AND their hardware is a fraction of the cost. So, with all due respect to someone who was once in the trenches with me... I have two points: 1. Meraki may look at feature requests, but until that feature request dashboard is public and we can all vote on them and see the rankings, I don't believe that it has the development weight that it is proclaimed to have. There are too many features that people have had to beg for too long to have implemented (or are still waiting for). 2. You have the budget to figure this out. Simple doesn't have to mean "dummy proof". Simple doesn't have to mean "one size fits all". It isn't like you are Apple selling an iPhone to a wide audience from senior citizens to children - needing to assume there is no IT knowledge. You ONLY sell through resellers. Most of your equipment goes to large enterprise or goes through some IT consultant channel. I'm trying to tell you what "simple" looks like for us - and I think that should influence your development decisions!
... View more