About PhilipDAth

PhilipDAth · ‎08-08-2018

Ideally you should only need to put in a username and password. Meraki use a public certificate, so it should already be trusted by the printer.

PhilipDAth · ‎08-08-2018

You should use PEAP.

PhilipDAth · ‎08-08-2018

I don't know the answer. However I would try running the stable release candidate 10.31. It resolves a lot of issues.

PhilipDAth · ‎08-08-2018

1. Enabling the "Scanning API" allows Meraki to send location data to a server you have setup, so you can collect/analyze the data yourself. https://documentation.meraki.com/MR/Monitoring_and_Reporting/Scanning_API The anayltics is what you see in the dashboard under Organization/Location Analytics. 2. I don't think you can only get a hash of the MAC address. I'm not sure that really addresses GPDR either - since you are still using a unique identifier for each individual. You can read how to address GPDR compliance here: https://meraki.cisco.com/gdpr There is some kind of opt-out system for end users as well. 4. If you sign up as a developer at create.meraki.io you can get a sandbox account. Note that if you are an IT professional and attend selected webinars you can often get an AP for free. https://meraki.cisco.com/webinars

PhilipDAth · ‎08-08-2018

You wont be able to terminate an OpenVPN client connection directly on an MX. OpenVPN is an SSL based VPN solution. You would need to setup your own OpenVPN server behind the MX to get this to work. If you can wait to the end of the year I suspect you might see an extra client CPN option appear.

PhilipDAth · ‎08-08-2018

You shouldn't need to do that (run a script). The "connect to to a more preferred network" option should be all that is required. Once it has seen the beacons for the primary network it should change over.

PhilipDAth · ‎08-08-2018

The vMX can only have one interface. The decrypted traffic goes to the default gateway - which is usually the VPC.

PhilipDAth · ‎08-08-2018

Put the ISP traffic in one VLAN and present it to the WAN ports, and management traffic in another VLAN and present it to the LAN ports.

PhilipDAth · ‎08-08-2018

That does not sound like you are using group policy to me. It should look something like the below. Note how the second SSID has the option ticked to connect to a more preferred SSID.

PhilipDAth · ‎08-08-2018

But in group policy you configure the order of the SSIDs to use. The first in the list is the preferred SSID. Have you placed the configuration for the SSIDs into a single group policy?

PhilipDAth · ‎08-07-2018

In that case you just need basic IGMP snooping enabled. https://documentation.meraki.com/zGeneral_Administration/Other_Topics/Multicast_support

PhilipDAth · ‎08-07-2018

I'm guessing this is for a security purpose, and maybe you are familiar with the Cisco Country of Origin tool used to validate this. There is no such Meraki tool.

PhilipDAth · ‎08-07-2018

The ASA's have considerably more configuration flexibility. They can do tricky site to site VPNs and handle complex user VPN requirements. They can also do complex NAT configurations. The MX is very basic at all of these. As long as your ASA configuration is simple you can replace them with MX.

PhilipDAth · ‎08-07-2018

This is nothing to do with Meraki. On your clients you need to configure the preferred order of the SSIDs.

PhilipDAth · ‎08-07-2018

With the switches make you you are using 10.x code as they have a lot of improvements. Do you want to only using multicast within a single VLAN, or across VLANs?

PhilipDAth · ‎08-07-2018

Port 1 (the ISP links) does not need to be tagged. Just put it into a VLAN and present that to the WAN ports of the MX.

PhilipDAth · ‎08-07-2018

Meraki MX does not support WISP and is unlikely to get such support.

PhilipDAth · ‎08-07-2018

The WAN interfaces each need their own IP address, and if there is a common subnet, you can also enable a Virtual IP. Using a virtual IP on the WAN interfaces is an optional configuration. https://documentation.meraki.com/MX-Z/Other_Topics/Warm_Spare#Virtual_IP

PhilipDAth · ‎08-07-2018

The WAN ports can be tagged, but can only belong to a single VLAN. You configure this via the local status page. https://documentation.meraki.com/zGeneral_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Meraki_Device_Local_Status_Page#MX-Z_Series_with_Multiple_Dedicated_WAN_Links The MX will use its WAN IP to talk to the Meraki cloud, and does not need a seperate management network. If you have other devices needing to talk to the Internet that are attached to VLAN11, then you can connect those via the LAN ports and configure a VLAN11 there. Note this would be using private IP address space. https://documentation.meraki.com/MX-Z/Networks_and_Routing/Configuring_VLANs_on_the_MX_Security_Appliance

PhilipDAth · ‎08-06-2018

That used to be an old bug. It sounds like it has slipped back into the code again.

PhilipDAth · ‎08-06-2018

Another option you could consider changing is the RX-SOP threshold. This allows you to tell the access point to ignore weak signals (such as those driving by). https://documentation.meraki.com/MR/Radio_Settings/RF_Profiles#RX-SOP You could either get someone to come in who can measure it for you, or maybe get some machines placed just a little further away than where you want coverage, and adjust RX-SOP until they just get chopped off.

PhilipDAth · ‎08-06-2018

Thank you for my latest swag @CarolineS. I think I'll use these in my vehicle. I have several charging cords, but someone always asks for one I don't have, and this will solve that problem.

PhilipDAth · ‎08-06-2018

On the MX side, I don't think you can statically configure DNS servers which at the same time having DHCP enabled.

PhilipDAth · ‎08-06-2018

It isn't written very well. The MX's use VRRP, which in essence is a virtual IP. The IP address is always serviced by the primary MX. The spare takes over the VRRP IP address if the primary fails.

PhilipDAth · ‎08-06-2018

You would probably need to go and buy your own high efficiency power supplies. You'll probably find this tricky to do at such low power levels. I've only seen good efficiency power supplies for things that draw much higher power loads. You also need to consider what you are doing to feed the power supplies. Are you given them good power with a power factor ratio of 1 - or poor quality power with a low power factor of 0.8 - making it hard for them to be efficient. You can't expect them to perform well if you are feeding them badly. A solar panel and storage battery could be fun to play with ...

PhilipDAth

Community Record

Badges