The local status page of any Meraki device is accessible via the web browser of a host machine. By default, users are required to log in to pages that provide configurable options. The local status page uses digest authentication with Message Digest Algorithm 5 (MD5) hashing for the connection between the administering computer and the Meraki device to protect these sensitive settings.
The authentication credentials for a device that uses the default authentication credentials or a device that has not fetched configuration will depend on the firmware version the device is running.
MX devices running MX 19+ firmware, MS devices running MS 17+ firmware and MS390/Catalyst devices running CS 17+ firmware will use the username admin and the password will be the serial number of the device (upper case letters and dashes).
All devices running other firmware versions will use the serial number of the device (upper case letters and dashes) as the username with no password.
Authentication credentials should be changed to have a strong password after their initial use. Please see the Changing Log-In Credentials section below.
To reach MR devices, the client must be wirelessly connected to the access point (AP) using a configured service set identifier (SSID) or one of the SSIDs mentioned in the Default SSIDs section, such as "meraki-setup" SSID. However, MS and MX devices can be accessed by any device with access to their LAN IP. This is done by entering the LAN IP address in the URL bar of a web browser. Additionally, each device can be accessed by DNS name if the client traffic passes through the device while browsing the following URLs. This can be useful for determining which AP/switch/firewall a client's traffic is going through to reach the internet.
If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
