Sounds like your static IP addressing is incomplete, make sure you have the correct addressing, subnet mask, gateway and dns.   Secondly, when on DHCP mode, your internal network is not accessing the internet. Make sure your MX is set to NAT mode, and that the connection does not drop traffic that you need, since MX will drop untagged traffic by default. ... View more

Depending on your MX version, MX 13.x allows  you to assign a static IP address via Uplink tab.   In previous version, you connect via management port or directly and use a web browser to http://mx.meraki.com/   In there, you choose Configure tab, enter username and password as setup in Network General setting (or if you haven't connect to the cloud yet, device serial number and blank password). You can set a static IP address for the Uplink ports afterwards. ... View more

Glad you were able to solve your network issue! ... View more

It would be wise not to throw your email out on the world wide Internet, so I recommend you use direct message to share your email address privately. ... View more

Depending on how your network topology is set up.   If its a flat network, I assume you have a network setup to hold over 700 IP addresses such as a class B network, then the MX's DHCP will give out addresses within that subnet. All you have to do is turn on DHCP for that VLAN holding the 700 computers.   If you're using /24 subnet, then you can only have 253 addresses (one is the MX and the other two unusable by hosts). If your network is flat, then you probably need a /22 which hold 1022 hosts.   However, you might want to consider creating VLANs to better manage those 700 computers in an organized way. You can have a DHCP server for each VLAN on the MX. ... View more

The onus to provide security of the devices falls on you, the administrator. Meraki provides security over what they control, the cloud. So its up to you, to set up the default password for device login when they pull configurations from the cloud. The serial number can be gotten from the dashbord or from the hardware device, thus requiring you to physically secure your device, which is your responsibility, nothing Meraki can do about.   However, a reminder for setting password is a good idea. ... View more

Then that will be correct, if set up that way.   I would advise you to make sure the trunk port on the TP-Link switch is configured correctly. ... View more

@PhilipDAth is correct, your VLAN gateway is misconfigured for VLAN 2 and VLAN 3. A gateway must be within the same subnet as the network. The MX84 can be a gateway for multiple VLAN. It creates an interface for each VLAN, which has its own IP address, thus a gateway for that VLAN. ... View more

For your trunk, adding tagged vlan is basically what vlan you allow on the link. Untagged means they remove the tag when they traverse the port. So if you have untagged on all vlan on that port, then they are losing the VLAN ID after they enter the trunk port. Which is why you could do inter-vlan route still but not go out to the internet since the MX could not return the traffic to the right VLAN.   So you want to make sure that the port connecting to the MX84 is "tagged' with the 3 vlans you want. I had a similar experience with Brocade switches. Untagged is best for access/edge ports. So you might have to remove the untagged configuration. ... View more

Are you saying you have the following setup:   MX80 ---> TP-Link Switch ---> Patch bay?   If so, did you confirm the TP-Link switch's port to the MX80 is set up as a dot1q trunk and all vlans allowed?   That may be why only vlan 1 is getting internet and the rest not. ... View more

The quarterly update confirms that they are aware of the increasing request for IPv6. Some regions are becoming exclusively or dominantly IPv6 and a team is working on it but no projections at this time.   Its recommended to provide a use case so they can optimize their development process to fulfill our wishes. ... View more

I will be attending the quarterly update webinar. We'll see if anything being said there. ... View more

The main thing is IPv6 is supported on the CIsco platform, its adapting it for the Meraki Dashboard that takes an effort and they haven't informed us of their time/effort on this.   I really strongly recommend IPv6 implementation since more and more web resources are efficient via IPv6 due to NAT traversal that IPv4 has to perform. ... View more

Once you set the port to Access, you can set the policy to Sticky whitelist. That will bring up two fields. One is whitelist size limit. You can put down the limit there.   This may be what you're looking for. ... View more

@PhilipDAth is correct. If the ISP route the /28 pointing to your MX, even if its a /30 network connection, it will work.   If you have one server per public IP, then you can use 1:1 NAT. If you have multiple servers sharing IP address, you can use 1:Many NAT.. This allows you to define ports to internal IP address and the internal ports as well. Just as long as the ISP route the /28 network to your MX, it will work. ... View more

 No cage can hold the gnome. Any attempts to do so is pure folly! ... View more

I do not have experience with Meraki's Site to Site VPN yet but according to the documentation, you can define if you want the Hub to send default route or not.   https://documentation.meraki.com/MX-Z/Site-to-site_VPN/Site-to-site_VPN_Settings#Default_Route   I hope this helps you. ... View more

Part of the problem for decryption is where does it take place? If it takes place in the cloud, then that'll violate privacy, especially for HIPPA and PCI compliance. If its on the devices itself, which may be possible, then the result can be fed to the cloud. Again, it depends on what the data is being sent to the cloud to enable this feature. ... View more

Unfortunately, it an intended design setup: https://documentation.meraki.com/MX-Z/Wireless/Adding_a_Z1_or_Wireless_MX_to_a_Wireless_Network_or_Mesh   MXxxxW is meant to be a very small office or home based setup, so a wireless network infrastructure was not designed into it. ... View more

You got most of it right. The last part, the UnTangle being the router, gateway, needs to have an IP for each subnet associated with each VLAN. That way it can route traffic to each other and the internet. If you use one Ethernet port to do this, you will need a trunk to the UnTangle set up.   The guest wireless vlan needs to have a rule to prevent it from seeing others on the network but full access to the Internet. ... View more

Nice, so swagplease!   Looking forward to it. ... View more

Unreachable just means it cannot communicate to the cloud for some reason. Make sure you have no ACL or firewall rules blocking the management IP address of the switch. Try pinging it from upstream. The fact that your AP downstream can connect to the cloud means it still forwarding traffic, just not able to communicate with the cloud.   You can open a support ticket to have the team look at it and see why its an issue. ... View more

You can use a small switch in between the provider's equipment and your 2 MX. Assuming you get a /29 or higher block of public IP address, you can then set each MX on its own ip addressing and connect to the ISP that has only one link.   No need for port forwarding or other setup since the switch is unmanaged. ... View more

Unfortunately, you cannot monitor Meraki's CPU/Memory information via API or SNMP. However, you can monitor ports traffic and sample over time to do performance monitoring, which the dashboard does in the cloud.   For example, you monitor a switch uplink port every 60 seconds and gather total packets in/out and measure them over time. This way you can see how much traffic every minute. ... View more