I found the gnome! https://community.meraki.com/t5/Smart-Cameras/rename-camera/m-p/254157#M3947 ... View more

I would start with a packet capture on the network while you connect one of the devices and see if there are any dhcp responses coming from a device you don't recognize, or that isn't your MX. Are the IPs in the same subnet just below 11 or above 200? or completely different subnet? ... View more

I've had this happen once with Spectrum, we had a random routing issue, we had to provide them with traceroutes to show that it was failing to reach the other end. You can required connections for the cloud if you go to Help->Firewall Info and check the traceroutes that way ... View more

When trying to do something like this it would probably be better to use Point-to-Point radios instead of wireless access points. If you can get the distance between the 2 buildings you'll also get that distance to the sides leaving a huge footprint of your wireless network. ... View more

They are generally setup wired behind your router. Then you can either hard wire your work laptop in or use the wireless, if that model supports wireless.   For that to work the other side must be public facing. So the VPN concentrator used would need a public IP, or IP/port forwarding configured ... View more

While I haven't used the W1850, I've used the Cradlepoint CBA850 & L950 models, and I have also used an MG41.   Simply, they both do roughly the same thing, they bring in a cell connection, and they are cloud managed.   Cost wise, from what I've seen, the Cradlepoint is cheaper.   BUT When trying to do dual SIM and have it work on your network, the MG works so much better and easier. We had issues trying to get the Cradlepoint device to failover and route properly. The MG, no configuration needed, it just works.   Updates on the MG vs Cradlepoint, Meraki wins hands down, so much easier. You don't update devices with Cradlepoint, you update groups, so you have to setup those groups first, not horrible, but not as easy as Meraki.   Having the MG in the same dashboard as the rest of your network(s) simplifies the management.   My personal pick would be the MG, but figured I'd give you the information I had. ... View more

My recommendation, leave it as an access port. Set your ssid that you want on local lan to bridge mode and don't enter a vlan tag. That should work ... View more

So the quickest way to do what you're looking to do would be to change the SSID you want to be part of the LAN to bridge mode. Do not add a VLAN ID. Everything else will continue to work the same way. If you are going to want to add other VLANs eventually, you are going to want to change that to a trunk, but not required for what you are currently doing. ... View more

The OfficeWiFi will continue to use Meraki NAT. Does your AP use a static IP or DHCP? By changing that to a Trunk you will have to add in the VLAN you want the AP to use for the management IP if you use static, originally VLAN 20. If it's set to DHCP it will try to get an IP from the native VLAN (generally VLAN 1) ... View more

Do you have the switchport set to trunk or access? If you're using a trunk then you need the vlan tagged, if you're using an access port don't add a tag. Do you have the SSID set to layer 3 roaming or bridge mode? ... View more

That doc was what I needed. Thank you ... View more

That's what I was seeing as well. My concern is the link I shared says it's AES-128, and since we have to adhere to PCI requirements, it has to be a minimum AES-256. ... View more

I think I submitted this to feedback about 4 years ago. Maybe one day lol ... View more

Started working for me just now ... View more

I'm trying to create a new SSID on n561 and it's just spinning. Tried to refresh and configure it again and the same issue is happening. ... View more

I think you misunderstood what I was saying. If you run the api call https://api.meraki.com/api/v1/organizations/{orgid}/apiRequests?version=0, you get a recent list of v0 api calls, if you change it to version=1, you get a recent list of v1 api calls. As explained here: https://community.meraki.com/t5/Developers-APIs/Identify-API-v0-usage-the-easy-way-0%EF%B8%8F%E2%83%A3/m-p/150274/thread-id/6006   ... View more

That's what I was hoping, just wanted to make sure I wasn't missing something that I should check.   Thanks ... View more

We are actually replacing a lot of the old copper lines at our remote locations with new desk phones. Gas stations and service shops will probably have desk phones for a long time ... View more

You don't have to run an ethernet connection, but you will need power. If it doesn't have a direct ethernet connection it will Mesh with another AP that it can reach and the traffic will move to another AP wirelessly to reach the internet.    The downside of doing this, if it can only reach one other AP and that one goes down due to power loss, upgrade, other issues then you lose that AP as well.    Here is some documentation on wireless mesh: https://documentation.meraki.com/MR/Wi-Fi_Basics_and_Best_Practices/Wireless_Mesh_Networking   ... View more

We were able to do the upgrade last night, and that did fix the issue, thanks again! ... View more

yep that is our exact issue, we are currently running 3.0. I'll try to get approval to move to 3.101 but may have to wait until it's 'stable'.   Thanks @javalins  ... View more

This is our first site that has the MG. We are using Verizon as the primary carrier on it and AT&T as the backup. We have paid to not have the CG-NAT.    When we ping from outside of that network we can see the pings hit the MX and the MX responds but we don't see the response in the packet capture on the MG.   Data Center -> MG -> MX looks fine but the packet captures only show MX -> nothing coming from the MX on the MG ... View more