So, I got this working. The problem was due to me not properly combining the client cert and the client key into a a .pfk file. Worked like a charm after that. ... View more

You will need to line up the mobile data connection for that MX via wired uplink, beforehand.   It's not possible to do ZTP via LTE connection only. The modem in that MX supports up to 300 Mbps, I believe, with the very best of coverage etc.    In practise the chances are you may not get that, but I gather the limiting factor is often the capability / flexibility of the carrier's infrastructure to support all the relevant standards. If you need VPN to work, this can be limited/prevented by carrier grade NAT implemented on the carrier's network;   a SIM designed for a data-specific plan is usually the best approach. ... View more

Awesome. Glad it resolved your issue.   Good luck with the rest of your project ... View more

In the EU you follow the ETSI rules and these are as following: For the 2.4 GHz ISM band you are allowed 20 dBm EIRP. For the 5 GHz bands it's a little more complicated: UNII-1 and UNII-2 (channels 36 through 64) are allowed 23 dBm EIRP. UNII-2e (channels 100 through 140) are allowed 30 dBm EIRP. The power levels you configure in Meraki and Cisco gear for that matter are the IR values (intentional radiator) so the antenna gain is not added to it to come to the EIRP. So in case of a MR45 which has in 2.4 GHz a gain of 5.4 dBi, you would be able to go no higher than 14 dBm Tx power. And for 5 GHz there is a gain of 6 dBi so if your channel is below 100 you would not be able to set it higher than 17 dBm TX but go up to 24 dBm if using channels 100 and above. However in a good Wi-Fi design you should keep your AP Tx power as close as possible to the Tx power most of the Wi-Fi clients have which usually varies between 12 and 14 dBm for 5 GHz clients.  And since you want 2.4 GHz to be less desirable you usually keep that one at least 5 dB lower so 8 dBm is a good value there. ... View more