Cisco Meraki MX100

Security Appliance
Wikipedia	Cisco Systems
3rd Party Firmware
dd-wrt	Status Unknown
OpenWrt	Supported
Tomato any flavor	Incompatible
Gargoyle	Status Unknown
Platform
Brand • Model • Rev	Cisco Meraki MX100
Type	router
CPU1 N	Intel Xeon E3-1200
CPU1 Speed	1.5 GHz ( 2 cores )
Flash1 Chip	Brand? Model?
Flash1 Size	1 GiB 1,024 MiB <br />1,073,741,824 B <br />8,388,608 Kib <br />1,048,576 KiB <br />8,192 Mib <br /> (NAND)
RAM1 Size	4 GiB 4,096 MiB <br />4,294,967,296 B <br />33,554,432 Kib <br />4,194,304 KiB <br />32,768 Mib <br /> (DDR3 1600)
RAM1 Chip	Brand? Model?
ETH chip1	Brand? Model?
Ethernet Port Count	10-1GbE-LAN
Wired Standard	IEEE 802.3i/3u/3ab
Expansion IF types	SFP, USB 2.0
USB ports	1
SFP ports	2
USB Hub Compatible	Untested
Serial Port (UART)	yes
Other
3rd Party Firmware Support	OpenWrt • (List | Dev | DLs)
Retail
Availability	End of Life
End of Life date	2022
(Est.) release date	23 December 2014
ASIN	B00NY19H88

Intel Xeon not currently documented.

For a list of all currently documented Cisco devices with specifications, see Cisco.

Flashing

Flashing OpenWrt

On the OpenWrt ToH (techdata entry)

Target: x86
Subtarget: 64
Package architecture: x86_64
Supported Since Commit
Support started version: 22.03.0
Current supported version: 24.10.5

WLAN Hardware: none
WLAN Comment: No WLAN
Installation method(s):
see git-commit
Install Comment:
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=fe9e5fbd7527ad4ff4f5b955823216038a80557d
Recovery method(s):
see git-commit

UART:

The UART header is named CONN11 and is found in the
center of the mainboard. The pinout from Pin 1 (marked
with a black triangle) to pin 4 is below:
Pin 1: VCC
Pin 2: TX
Pin 3: RX
Pin 4: GND
Note that VCC is not required for UART on this device.

Booting:

1. Flash/burn one of the images from this repo to a
flash drive.
2. Take the top off the MX100, and unplug the SATA
cable from the HDD.
3. Hook up UART to the MX100, plug in the USB drive,
and then power up the device.
4. At the BIOS prompt, quickly press F7 and then
scroll to the Save & Exit tab.
5. Scroll down to Boot Override, and select the
UEFI entry for your jumpdrive.

Note: UEFI booting will fail if the SATA cable for
the HDD is plugged in.
The issue is explained under the Flashing instructions.

Flashing:

1. Ensure the MX100 is powered down, and not plugged
into power.
2. Take the top off the MX100, and unplug the SATA
cable from the HDD.
3. Using the Mini USB female port found by the SATA
port on the motherboard,
flash one of the images to the system. Example:
`dd if=image of=/dev/sdb conv=fdatasync` where sdb
is the USB device for the MX100's NAND.
4. Unplug the Mini USB, hook up UART to the MX100,
and then power up the device.
5. At the BIOS prompt, quickly press F7 and then
scroll to the Boot tab.
6. Change the boot order and set UEFI: USB DISK 2.0
as first, and USB DISK 2.0 as second.
Disable the other boot options.
7. Go to Save & Exit, and then select Save Changes and
Reset

Note that OpenWRT will fail to boot in UEFI mode when
the SATA hard drive is plugged in. To fix this, boot
with the SATA disk unplugged and then run the following
command:
`sed -i "s|hd0,gpt1|hd1,gpt1|g" boot/grub/grub.cfg`
Once the above is ran, OpenWRT will boot when the HDD
is plugged into SATA. The reason this happens is the
UEFI implementation for the MX100 will always set
anything on SATA to HD0 instead of the onboard USB
storage, so we have to accomidate it since OpenWRT's
GRUB does not support detecting a boot disk via UUID.