NAT mode with Meraki DHCP allows a MR Access Point to provide client addressing by running its own DHCP server to simplify management, allow guest access, and provide client isolation functionality.
Meraki.com Auto-tunneling VPN technology Leveraging the Meraki cloud architecture, site-to-site VPNs can be enabled via a single click without and command-line configurations or multi-step key permission setups. Complete with IPsec encryption, deploy the following architectural setups within minutes.
- MacOS Meraki VPN Setup Here are the basic steps: Open System Preferences Network from Mac applications menu. Click the “+” button to create a new service, then select VPN as the interface type, and choose L2TP over IPsec from the pull-down menu.
- Using the Clients List. Navigate to Network-Wide Clients, then check the boxes of the clients that you want to allow list or block.Click on the Policy drop down above the client list, and select blocked or allow listed.To apply the allow list or block on a per SSID basis or only on the MX Security Appliance, select Different policies by connection and SSID.
Client Addressing in NAT mode with Meraki DHCP
The DHCP server run by the Cisco Meraki AP provides addresses in the 10.0.0.0/8 subnet (10.x.x.x). Outbound connections will be initiated with the LAN IP address of the AP using Network Address Translation. Wireless clients that connect to the network will be given the following configuration via Meraki DHCP:
- An IP address in the 10.x.x.x range. The IP address is created by running the client’s MAC address through a hashing algorithm.
- A gateway address of 10.128.128.128
A wireless network using NAT Mode with Meraki DHCP can be seen below. When clients on the wireless network access resources upstream of the AP, their IP addresses will be translated to the IP address of the AP (192.168.1.1):
Client Isolation
NAT mode with Meraki DHCP isolates clients. Devices with a Meraki DHCP address will be able to access external and internal resources, such as the Internet and LAN (if firewall rules permit). However, connected clients will be unable to contact each other. The client isolation features of Merkai DHCP can be seen above in Figure 1. Client A and Client B can both access the Internet. When Client A wants to send traffic to Client B, the traffic will reach the AP. However, the AP will not forward this traffic to Client B. Therefore, the two clients are isolated from each other.
Since the client isolation function of NAT mode prevents wireless devices on the SSID from communicating with other wireless devices, NAT mode is not recommended for use with wireless peer-to-peer devices like a wireless printer or Google Chromecast.
Due to the implementation of client isolation, clients on a NAT mode SSID cannot talk to clients on a bridge-mode SSID when both clients are connected to the same AP.
Configuring NAT mode with Meraki DHCP
To configure NAT mode with Meraki DHCP on an SSID, follow the directions below:
- Navigate to Configure > Access control.
- Select the appropriate SSID from the SSID menu at the top of the page.
- Change the Client IP Assignment to NAT mode: Use Meraki DHCP under the Addressing and traffic section, as seen in the image below.
- Click Save Changes.
Common Problems
There are a few common problems that can arise when deploying NAT mode with Meraki DHCP to provide client addressing. These problems are outlined in detail below:
- Roaming - NAT mode with Meraki DHCP will use the IP address of the AP as the public IP address for wireless clients. When a client roams between APs with Meraki DHCP, TCP connections will drop and have to be re-established. This can cause problems with some applications and devices.
- Bonjour and multicasting protocols - The client isolation features of Meraki DHCP will prevent wireless clients from communicating with each other. This will prevent Bonjour, layer 2 discovery protocols, and multicasting protocols from working. This can cause problems in networks that use Bonjour among wireless clients, or have IP phones or applications that require multicasting.
- Inbound client connections - NAT mode with Meraki DHCP prevents inbound connections to a wireless client. This can cause problems if a wireless client needs to be accessible from a different network. The image below illustrates this problem. A connection, such as a remote desktop session, from the wired client to wireless client A will fail. Other common examples include failed wireless LAN connections to Chromecast devices, AirPlay enabled devices, printers or projectors.
The issues described above can be resolved by using bridge mode for client addressing. Bridge mode simply passes traffic between the wireless client and wired distribution system. An upstream DHCP server will be required to handle client addressing.
Additional Resources
For additional information about NAT mode with Meraki DHCP and client addressing, please consult the following documentation:
Configuring an IPSEC VPN using the MAC Built in Client to RV32x Series Router
Objective
The objective of this document is to show users how to use the MAC Built in client to connect to an RV32x Router.
Applicable Devices | Software Version
RV320 | 1.3.2.02
RV325 | 1.4.2.22
Introduction
An Internet Protocol Security Virtual Private Network (IPSEC VPN) allows you to securely obtain remote resources by establishing an encrypted tunnel across the internet. The MAC built-in client, is a built in Client available on all MACs that allows you to connect to the VPN using IPSEC. The RV32x routers work as IPSEC VPN servers and support the MAC built-in client.
This document has two parts:
Configure RV32x Series Router
Configure MAC built-in Client
Configure RV32x Series Router:
We will start by configuring the Client-to-Site VPN on the RV32x series router.
Step 1
Log in to the router using valid credentials.
Meraki Vpn Client Mac 10 12
Step 2
Navigate to VPN > VPN passthrough. Confirm IPSEC Passthrough is enabled and click Save.
Step 3
Navigate to VPN > Client to Gateway.
Step 4
Select the Easy VPN Option.
Step 5
Configure Tunnel Name, enter a Password, select the WAN interface, and enable the Tunnel and select Tunnel Mode. ClickSave to save the configurations.
Full tunnel mode chosen and password complexity has been disabled.
Step 6
Navigate to VPN > Summary and confirm VPN tunnel has been configured.
Step 7
Confirm the VPN tunnel has been configured.
Step 8
Navigate to User Management and select the add button under User Management table
Step 9
Meraki Vpn Client Setup
Enter Username,Password, select Group, Domain and click Save.
Configure MAC Built inClient
We will now configure the MAC Built in Client.
Step 1
Navigate to the apple icon in the tool bar. Choose System Preferences.
Step 2
Navigate to Network
Meraki Vpn On Mac
Step 3
Go to Add button and then select interface tab will appear.
Step 4
Select Interface as VPN, VPN Type as Cisco IPSec, and enter the Service Name to match the Tunnel name that was configured in your router. Click Create.
Step 5
Navigate to the VPN, enter Server Address, Account Name and Password.
The account name and password are those configured in User Accounts.
Step 6
Choose Authentication Settings button, the Machine Authentication tab will appear. Enter the Tunnel password key in Shared Secret and Tunnel name in Group Name, press OK.
Step 7
Press Connect, a warning will appear, press Apply.
Step 8
The connection status should show as Connected.
Conclusion
We have configured the Easy VPN tunnel using IPSEC IKEV1 between the RV32X series router and a MAC computer by using the MAC built-in client. It’s important to be sure the tunnel is configured on the router using Easy VPN for this connection and entering the same information on the client side to ensure a connection. Now you are able to connect to your VPN and access the information you may need to access.
Comments are closed.