I FOUND THE GNOME! https://community.meraki.com/t5/Smart-Cameras/rename-camera/td-p/254157 ... View more

Is it possible to do a test by changing the ports from trunk mode to access mode? Just to validate one thing. ... View more

If you want something even tighter, then you could use 802.1x and a RADIUS server on the LAN ports, and actually authenticate each device (or you could do it by MAC address).  This method would prevent a client from being able to do DHCP until authenticated.   https://documentation.meraki.com/MX/Access_Control_and_Splash_Page/MX_Access_Policies_(802.1X)   ... View more

Hi ,   But then how does the access points will be able to reach the radius servers lan? Both the radius servers and the APs are on different management networks. For instance, let's say that  the access points are on network 192.168.128.0/24 - VLAN X.  and the radius servers are on network 10.1.1.0/24 - VLAN Y.  both of the vlans are defined on the MX addressing and vlans and have gateways.    Yes the AP and the RADIUS server(s) need to have IP reachability.    Is the routing done by a MX / MS or something else ? if so you have to make sure that inter-vlan routing is enabled and that UDP 1812-1813 is allowed between these vlans/endpoints. ... View more

I forgot to update my comment. It did not work for my native vlan. Had to add it too. It was a mistake from my side. ... View more

And link for the mx https://documentation.meraki.com/MX/Other_Topics/Configuring_Bonjour_forwarding_for_the_MX_Security_Appliance ... View more

Yes that is why i stated "if the L2 protocol is ethernet" 😉 ... View more

I am looking for a solution to this as well.  Did you find one? As far as I can tell, Windows only sets a "custom name" for wireless connections using the SSID name.  it will use "Network #" for wired connections unless you have connected to a wireless network first that uses the same Gateway MAC address and offers the same option 15 domain name...which is probably how you got your KITLV_STAFF_FREE name to show up for the wired connection instead of "Network 2". The only other way I have found to change it is by editing the registry keys on each PC, or pushing a profile via Intune or a DC.   ... View more

Can you think of a good reason there's no an option to  alert for a port going to blocking state due to a loop / spanning tree issue?   ... View more

Why you dont want wan2 as primary? And set the flow pref for all lan traffic to wan1 https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/MX_Load_Balancing_and_Flow_Preferences#Flow_Preferences ... View more

Hi,   I just opened a case to have that clarification   And Meraki confirms that Bandwidth limit that is either applied by Group Policy on a vlan or applied by Traffic Shaping rule on a subnet is a per-flow/client limit, and not an entire vlan/subnet limit.   The only way to apply a ' per-vlan ' limit is on an SSID ... View more

Unlike Wi-Fi 5 (802.11ac) Wi-Fi 6 also supports the old 2.4 GHz band.  You can work in either band as you see fit. The usual use case I see for the 2.4 GHz band is for IoT devices.  And then use 5 GHz (and 6 GHz in Wi-Fi 6E) for all your bandwidth hungry devices.   Make sure to check your RF profiles in dashboard to see if the disable 802.11ax box is not checked. ... View more

Many thanks, that was it!   ... View more

Hi @Captain ,   Were you able to figure put how to do it? Because I am also facing the same issue and wondering if there is a way out. Thanks! ... View more

Sorry no need to reply...  I had something wrong configured on my end and now your solution is working!   ... View more

Hello,   This interface appears to be a pseudo interface (existing on an L2 switch), as the screenshot shows no field exists to configure a subnet mask.   Pseudo interfaces on L2 switches (MS120, MS220) are highly limited in scope of functionality. They only send or receive IGMP or DHCP packets and do not respond to ping/ICMP. For more details, see: https://community.meraki.com/t5/Switching/MS120-DHCP-relay-doesn-t-work/m-p/45320/highlight/true#M3787   As for IGMP version for IGMP snooping purposes, you cannot configure the IGMP version. Only version 3 is supported. However, IGMPv3 is backward compatible with IGMPv2. The only real IGMP packets you'll see transmitted by a switch performing IGMP snooping will be IGMP general query packets.   IGMPv3 query packets are processed in a fully backward compatible manner by IGMPv2 hosts. The only difference between an IGMPv3 general query versus IGMPv2 is that the IGMP payload of the v3 packet has some additional fields present in it not used by IGMPv2 hosts.   These are the fields that extend the IGMP payload beyond 8 bytes. However, this extra data is simply ignored by an IGMPv2 host, per IGMPv2 RFC 2236:   2.5. Other fields Note that IGMP messages may be longer than 8 octets, especially future backwards-compatible versions of IGMP. As long as the Type is one that is recognized, an IGMPv2 implementation MUST ignore anything past the first 8 octets while processing the packet. However, the IGMP checksum is always computed over the whole IP payload, not just over the first 8 octets.   The Type field is set as 0x11 for both an IGMPv2 and an IGMPv3 query -- meaning the IGMPv2 host will process the IGMPv3 query and respond in the correct manner. ... View more

You can do a bulk placement for devices on network per network basis via Network Wide -> Map and Floorplans -> Click Place devices on a map, mark all devices and choose "Edit" -> Geolocate -> Enter Address.   Don't forget to click "save device placements"  .   * Edit - this only moves the devices on the map to the correct map location, it does not set the address on the actual device.       ... View more