VPN clients connect to MX100, act as if they are split tunneled. We have most of our Meraki VPN clients connecting to the MX 100 just fine. But their traffic does not all flow through the VPN to the MX. The clients all have the default setting "Use default gateway on remote network" selected. I really need all traffic to flow through the VPN to the MX for filtering. Client VPN connections that have their local LAN subnet as 192.168.1.0/24 then cannot reach any resources on the corporate internal 192.168.1.0/24 subnet. Because the local LAN uses the DG of itself, most of the time its 192.168.1.1. How can I make the Meraki Client VPN settings on Windows 10 (1803) use only the VPN connection for all traffic? Example: Users log into their computers. Click on the “connect” to connect their computers to the Meraki MX100 through the configured Meraki Client VPN. They connect to all but one office and can use most resources on most subnets fine. Except when they have a matching subnet they use at home that matches with one at the other offices. Also their internet traffic also goes through the Home LAN network router instead of through VPN to tunnel. Acting like it is split tunnel but by settings on the client appear to be set for non-split tunnel. The Ipconfig /all on the client is: On the MX100 the client subnet is 192.168.3.0/24. Nameservers: 192.168.1.254 and 192.168.26.254 Active Directory authentication is turned on and authenticating with AD. There is a static route to the office that has 192.168.1.0/24 listed in the MX100 and all other subnets internally connect to that subnet without an issue. From the MX100 I cannot ping the 192.168.3.194 client either. However, on the Z3 teleworker appliances; I just select default route on the site-to-site and then done, they work fine.
... View more
