Enable and rename the Guest and Internal SSIDs appropriately. For the Name section of each SSID, click the rename link.ģ. In Dashboard, navigate to Wireless > Configure > SSIDs.Ģ.– Another good point to add to Meraki WiFi best practices – deploy no more than 3 SSIDs per Access Point. The process to create the SSIDs is the same regardless of their use. Meraki makes it simple to create and deploy WiFi networks (SSIDs) from the dashboard management console. Meraki WiFi Best Practices – Creating a Guest and Internal network. It’s part of Meraki WiFi best practices to segregate network access, and administrators can use different types of technical and administrative controls to ensure Guest Wifi users don’t have access to the corporate network and vice versa.Īre you a Cisco Meraki Shop? This article “5 Cisco Meraki to improve WiFi performance” may be useful to you. You can create a Guest WiFi network to provide your visitors with internet access without allowing them to access the internal company resources. As you can imagine, you wouldn’t want unauthorized users accessing your internal network for all the administrative, security, and compliance reasons. They are designed to provide access to internal resources such as servers, printers, shared drivers, etc in other words, it’s simply an “extension” of the LAN. What makes the difference is the configuration settings that you apply to it. Although the process to create the networks is the same, there are some Meraki WiFi best practices you can implement to take advantage of Meraki’s wireless features.Īll SSIDs are configured the same way, and there’s nothing special when it comes to configuring a Guest SSID. I don't want to overstate this, since not all devices support these standards in the first place, but for devices that do, it's pretty nice to have the devices switch from 2.4GHz to 5GHz when they get close enough, and from one 5GHz access point to another 5GHz access point as they move around the home.One of the most common types of WiFi access deployments is to create at least two Wireless networks, in other words, an internal WiFi network for the company’s employees and another one for Guest Access. So, devices that support those specifications will be more likely to get 'stuck' to an access point or band that is still working, even when a better one is available. Not only will you lose the features described on that support page, but you will also lose the 802.11k and 802.11v handoff support. Olav's suggestion of creating multiple parallel bridge mode Google WiFi units can work, but there are some really important caveats to understand with that approach as well. Using it as a single bridge mode device may work, but you're losing a lot of the features. It allows Google WiFi to be a router+firewall as well as create the multi-unit wireless mesh that supports multiple remote Google WiFi units to expand coverage. Generally speaking, putting your ISP router+modem in bridge mode will be a better fit for the way Google WiFi is intended to be used. Here's a help article with more details on bridge mode:

Wired client meraki wireless bridge