Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About Juraj7
Juraj7
Here to help
Member since Mar 12, 2023
May 9 2023
Community Record
12
Posts
0
Kudos
1
Solution
Badges
Apr 26 2023
3:40 AM
thanks for assistance all. The issue was that there was no vMX template in a second region so we used AWS site-to-site VPN and VPC peering to get the connectivity going at the beginning. This has interfered with Meraki's routing and was the cause of the issues. After removing all site-to-site VPNs and VPC peering I've changed all the routing back to respective vMXs and it all started to flow beautifully.
... View more
Apr 25 2023
4:39 PM
It's already defined correctly there...
... View more
Apr 19 2023
6:49 PM
by IP. As mentioned above, when I have the Meraki IP set as the device, it doesn't NAT out due to one-arm configutration. If I set it to outside of AWS subnet, it routes correctly for the client VPN users but my office device only sends to that subnet, which is outside of 10.50.0.0/16 and 10.0.0.0/16 respectively. So this is what I'm trying to square primarily...
... View more
Apr 19 2023
6:39 PM
also enabled
... View more
Apr 19 2023
6:36 PM
I have that enabled.
... View more
Apr 19 2023
6:28 PM
But the system won't let me accept no entry or empty entry - I need to have value. Can you post screenshot from your setup? Seems unlikely that you were able to do it...
... View more
Apr 19 2023
6:22 PM
Meraki says that I do need it.. if you have vMX, what did you put in? Same IP as the device, different but same AWS subnet or something outside of your AWS subnet?
... View more
Apr 19 2023
5:57 PM
I did not and when I enquired with support (ticket still opened) they said it's not necessary. VPN connectivity seems fine.. I understood that as a single exit which we don't want. Not all traffic is routed via VPN, only VPN traffic (split tunnel)
... View more
Apr 19 2023
5:39 PM
I don't believe I said that.. I have mesh VPN between all Meraki devices.
... View more
Apr 19 2023
4:42 PM
Scenario:
I got one MX68 in the office and 2 vMX in AWS cloud in different regions. There are servers in each region that I'm trying to connect to. All devices are in routed mode.
Devices connect via VPN without any issues.
Problem:
One arm configuration of vMX has me assigning IP address outside of the AWS subnet. This works for AnyConnect VPN and users can dial in to either vMX and authenticate via AD (routing to servers works). Issue now is that the site office is sending any traffic to the servers via internet, instead of VPN. When trying to add route, it complaints that there's no subnet defined and simply refuses.
How to go about it?
for better visualisation:
MX68 (office): 192.168.0.0/24 (device 192.168.0.1)
vMX region1: 10.0.0.0/16 (device AWS assigned IP: 10.0.12.143)
vMX region2: 10.50.0.0/16 (deice AWS assigned IP: 10.50.1.42
I've tried to set the Meraki IP in Addressing & VLAN to the same IP as AWS assigned but it wasn't routing to my AD for authentication.
I've set it to outside of any AWS subnet which works for AD authentication and client VPN but then running into issues described above - office traffic routes via internet
I've set the Meraki IP within AWS subnet but different IP that's not AWS assigned to 10.0.12.144. It wasn;t routing correctly and I got no responses and no VPN users authenticated via AD
thanks
... View more
Mar 12 2023
6:41 PM
But I don't need AnyConnect if I'm just using Windows built-in VPN client
... View more
Mar 12 2023
5:21 PM
Hi all, I'm new here so hopefully this is the correct place to post. Got vMX in AWS and I can connect to it from a PC without Umbrella client without any issues (we aren't using AnyConnect). With Umbrella client however I never get prompted for credentials. I spoke with Umbrella support, they suggested making few changes but none helped. Was anyone successful in making it work or does Cisco just require AnyConnect licensing? thanks
... View more
Labels:
- Labels:
-
AWS
-
Client VPN
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 9598 | Apr 26 2023 3:40 AM |
© 2025 Cisco Systems, Inc.
