Hi can some one please clarify the following:1. For new Catalyst APs for use with 9800 WLC, for the UK should these still be ordered as E domain or RoW?2. For Catalyst APs for management by the Meraki Dashboard, again should these be RoW/E or is this...
Hi is it now possible to configure MX appliances in SSID VPN termination mode to act as a client DHCP server, this was not supported last time I looked. Thanks
Hi, I don't normally specify security products and would welcome clarification re the below in reference to the ASA5516-X with Firepower (ASA5516-FPWR-K9) 1. In a HA (active/standby) deployment is it mandatory that I need to purchase a L-ASA5516-TAMC...
I have a client who wishes to utilise a "mobile" WiFi platform to provide temporary coverage within differing WiFi RF regulatory regions i.e. Europe, Japan, North and South America, Australia/Asia PAC. The solution would be purchased in Europe but wo...
The reason for wanting the MX to provide DHCP is simply this is the case for the clients legacy on-prem wireless LAN controller. Effectively the client will need to provision a DHCP server for the Meraki solution as this functionality is not supporte...
Hi thanks for coming back, all I'm looking for is for the MX to be a DHCP server when used to terminate SSID tunnels, Meraki's validated design says use one-arm pass through mode but does not mention DHCP capabilities
Hi thanks for the reply. I was lead to believe the MX in VPN concentrator mode (one arm) was not capable of running client DHCP services. I'm struggling to find anything official in writing
I think this is saying that the MX receives its IP address via DHCP, the documentation does not refer to the MX been able to run DHCP services to facilitate client addressing
Hi, yes I have seen this guide thanks, but there is no reference to DHCP capabilities. All that is required is for the MX to support DHCP for clients connecting to an SSID which terminates its tunnel on the MX
.jpg "VIP Advocate"){kind=icon}
