About BrechtSchamp

BrechtSchamp

I'm with @NolanHerring . Exact values are documented here: https://documentation.meraki.com/MR/Radio_Settings/EU_Compliance_Information

BrechtSchamp

For Apps, check this documentation: https://documentation.meraki.com/SM/Tags_and_Policies/App_white%2F%2Fblacklisting_in_security_policies For Websites, for iOS there's this: https://documentation.meraki.com/SM/Profiles_and_Settings/Web_content_filtering_on_iOS_devices_in_Systems_Manager For Android there's no content filtering on the SM side I think. If you have a full-stack you could do it in your MX or your MR of course.

BrechtSchamp

As a small addition to what @MerakiDave wrote above. You may want to look into the option of serving multiple VLANs over one SSID. More info about that here: https://documentation.meraki.com/MR/Client_Addressing_and_Bridging/VLAN_Tagging#Per-User_VLAN_Tagging

BrechtSchamp

@UlrichSchulz wrote: Is there a chance that mesh will get a standard industry protocol so that it will work with all vendors? I think that's highly unlikely. Mixed vendor Wi-Fi deployments are not recommended. Let alone meshing between different vendors.

BrechtSchamp

Your understanding is correct. The SKU's are the same for PDL and co-term. The difference is the behavior when they're applied. (Also, small detail, the MR advanced licenses can only be used in the PDL model) The result would've been different when applying the licenses first and then converting vs converting and applying afterwards. Maybe that's the issue? Also as @PhilipDAth already mentioned, in the co-term model it's very important that you understand the difference between renewal and addition. Renewal effectively resets all your "allowed number of devices per type" to the numbers on that specific order. This is often overlooked by customers.

BrechtSchamp

@NolanHerring wrote: Pretty sure there are only 2 WAN links regardless of model Yup.

BrechtSchamp

@PawelG wrote: Looking at the specs the only difference is that 46/56 offer uplink/downlink OFDMA, while 45/55 offer only downlink OFDMA. Br, Pawel. Yup, I think that's the difference between the two. @davidvan any news on full Wi-Fi 6 certification for these? I still see "802.11ax compatible" in the datasheet? Also, any news about WPA3?

BrechtSchamp

Lol, I should've refreshed before putting the effort for the debugging in. At least we came to the same conclusion @boomi .

BrechtSchamp

For me it works fine in Postman when just specifying a lng and a lat. But as for you @PhilipDAth it fails with the SDK. After some debuging I found that there are multiple issues. First error: "moveMapMarker must be a boolean. So the SDK is putting moveMapMarker as null in the params if you don't specify it. The server is expecting true or false. It shouldn't even be specifying that param imo if you don't. But okay, I put in False in python which is then translated into false further on in the request params. Upon running with that change we arrive at the second error. Second error: "Device's network must be bound to a configuration template (that supports switches) to allow for switch profile binding". Again, even though no switch_profile_id is specified in the device object, the SDK adds it into the parameters with a null value. The server doesn't accept that. At this point I stopped debugging as there is no sensible value I can put in in the switch_profile_id... None gets translated to null as well so that won't help. This smells like SDK bug.

BrechtSchamp

Oops, late to the party. Congratulations and celebrations to all you fine people! Literal celebrations are so good 😍

BrechtSchamp

@Seshu Well I didn't open a ticket as I was just trying to help @Ozgur . I can tell you that the issue is still there for me though. @bly and @Ozgur , I think you opened cases, can you share the case IDs with @Seshu ?

BrechtSchamp

Probably hard to spot, but the white spot right across near the ceiling is an MR33 🤓 🔍

BrechtSchamp

To get full Wi-Fi 6 certification WPA3 will be required iirc. So I fully expect Meraki to add it soon.

BrechtSchamp

I can't seem to access any of my networks with it. The following error keeps popping up: Anyone else with that issue?

BrechtSchamp

No 😛 But I like investigating.

BrechtSchamp

Duomo in Milan? Edit: Leftmost door

BrechtSchamp

Thanks for sharing that! I'm sure lots of people would've broken their heads over this.

BrechtSchamp

That number 50 is not a hard stop. It's a guideline. Aaron Willette (SE at Meraki) has actually written a great blog post for MX sizing: https://www.willette.works/meraki-mx-sizing/ Looking at your numbers I honnestly think you're fine.

BrechtSchamp

It's while doing support you learn the most I'd say. That's why I'm on the community! Great to have you, sharing is caring. Here's a community challenge, juggle Meraki swag and record it with an MV (hint: socks).

BrechtSchamp

Evangelism aye, so when is your bible due 🤓 ? I never knew what detasseling corn meant, thanks for that.

BrechtSchamp

Hello and welcome John! I know there are some other people on the community that are grilling fanatics *cough* @MeredithW *cough*. You'll feel right at home!

BrechtSchamp

Welcome Pero! There is some more info about that incident type here: https://www.snort.org/rule_docs/1-45265 Basically your MX has detected someone accessing a website that had some mining javascript code embedded. It likely purged the request from it. If it happens often, go talk to the person causing it.

BrechtSchamp

I don't think we have BWW here. Okay, I'm in need of some Meraki "training". We'll have lunch at the nearest BWW... Oh snap.

BrechtSchamp

@PhilipDAth wrote: I like holding hands and going for walks in the park under the moonlight. Crap, wrong profile. Force of habit 😂

BrechtSchamp

Glad to have you!

BrechtSchamp

Community Record

Badges