Can you verify that in the Office-Wifi Firewall & traffic shaping you do not have Layer 2 LAN Isolation? Layer 2 LAN isolation only allows traffic to the default gateway MAC address hence it will disable connectivity to any other devices on the wired LAN if they are in that same VLAN. ... View more

Hola,  Si, es posible comprar licencias de equipos que están en EoS.  Esta licencia continuará habilitando el uso del dashboard pero no será posible hacer un RMA de un equipo que se encuentra en estado EoS. La recomendación es intentar hacer una renovación del HW para tener HW actual, con las nuevas capacidades que aporta y con el nivel de soporte adecuado.   ... View more

Hello,   To my knowledge this feature is working as expected.  I have several customers using it.  If it does not work on your environment I kindly suggest you open a support case to check what might be happening.     ... View more

Correct, I guess a better way to put it is that all WiFi6E AP, except the C9136i (only WLC) and MR57 (only Meraki), are dual personas APs and can be fully managed by Meraki Dashboard or Cisco WLC/Catalyst Center. Those are the ones with the CW916X nomenclature.  See above to choose the right SKU for your desired persona.  For the c9136i, most of the Cisco WiFi6 and WiFi5 APs controlled by physical Catalyst WLCs will be able to be monitored (not fully managed) by Meraki Dashboard in the near future. This exciting capability is now in Beta and was announced in Cisco Live Amsterdam 2024.  ... View more

Yes, the CW916x family can run in Meraki Dashboard the same way MRs do.  Upon ordering make sure you get the right SKU so they come from factory ready to be used in Meraki Dashboard:   CW916Xi-MR comes ready for Meraki Dashboard. Aka Meraki Persona CW916Xi-E/A/B or other terminations come ready for Cisco WLC/Catalyst center. Aka Catalyst persona  Any SKU can be changed from one persona to the other.    ... View more

You might be hitting the condition discussed in this thread:   https://community.meraki.com/t5/Wireless-LAN/Firmware-Network-Issue-MR30-5/m-p/220995#M30594     ... View more

You can do several things. Amongst them:   1. Create a group policy and assign a VLAN that does not have DHCP and does not go anywhere. Their devices will be place on that VLAN and it will give them a failure as they will not obtain an IP.  2. Increase your DHCP pool, create a policy that has very limited Bandwidth (10s of Kbps) and assign it to mobile devices. This will make the WiFi for mobile phones so slow that they will prefer to use the LTE connection.  3.  Stop using PSK and start using a radius server to authenticate. This will not allow their mobiles, which are not in the Radius server, to connect.  4.  Similar to option 2. Increase your DHCP pool, set the SSID with  very limited Bandwidth (10s of Kbps) and put a splash page telling them not to use WiFi. Assign to your corporate devices a whitelist policy.  This will make any device that connects to WiFi go really slow and get a splash message about their non compliant behaviour. The corporate devices that you whitelist will not be BW limited nor get the splash page.  it is Friday. I encourage you to play with all of the Dashboard options and see how the users react!   Happy weekend.   ... View more

You are right, same process for CWs or Catalyst Switches.  You need to open a support case, they will check conditions are met and will start the process from their side. ... View more

Hello,    You can assign VLAN per AP (using TAGs) or via Group Policy to clients.   https://documentation.meraki.com/MR/Client_Addressing_and_Bridging/VLAN_Tagging_on_MR_Access_Points#Setting_Per-SSID_VLAN_Tagging_in_Dashboard   https://documentation.meraki.com/MR/Client_Addressing_and_Bridging/VLAN_Tagging   Hello,   Pablo   ... View more

In addition to that, which is entirely correct, each DHCP request has a transaction ID which is included in the replies by the servers (however many different servers reply). So, it is really easy for MRs/Dashboard to follow the whole DHCP process even when getting replies from diff servers.   ... View more

Hello,   The reason why it is not supported is because of the mechanism that the MRs use to determine if they can reach Dashboard via the wired network or they need to form a mesh connection to other MRs.   Like is says in the documentation not only it is not supported but the behaviour will be unpredictable.  Make sure you have some short of layer 3 device as mentioned in the documentation, if a 24 port switch does not fit maybe you can use an MX75 or similar.   Regards, Pablo     ... View more

It is supported in Windows 10 versions 2004 and above but also you need to have compatible Wireless NIC cards and drivers.   Use this powershell command: systeminfo | findstr /B /C:"OS Name" /B /C:"OS Version" ... View more

Please, make sure you are running MR software version 29 or above.  MR30.5 is current stable.   There is a dashboard connectivity method change in these new versions.  With the newer versions Dashboard connectivity uses TCP port 443, prior to this was UDP port 7351 which could improve your connectivity issue. ... View more

Hola Mexico!! Bienvenido. ... View more

You may use an MX terminating a Teleworker VPN from an MR36H. This would be a Layer 2 extension, however this is not the recommended use of that technology.   https://documentation.meraki.com/MR/Client_Addressing_and_Bridging/MR_Teleworker_VPN     ... View more

Hello Lena,   Please open a support case. We should be able to find out the SN from the MAC address. Regards,   Pablo ... View more