Client VPN to Non-Meraki VPN peers routing

Solved
PaulinBeer
Conversationalist

Client VPN to Non-Meraki VPN peers routing

Hi... I have read loads on this but nothing that seemed clear cut in its resolution. 

 

So we have a local subnet of 192.168.3.0/24 with a Non-Meraki VPN to 172.29.40.0/25, this is working and pings to the Non-Meraki VPN peers respond. 

 

We have a client vpn subnet on 192.168.7.0/24 and can ping devices on the local 192.168.3.0/24 network but cant ping anything on the 172.29.40.0/25 network. My question is what needs to be done to allow traffic from the client vpn 192.168.7.0/24 through the Non-Meraki VPN to 172.29.40.0/25?

 

 

1 Accepted Solution
ww
Kind of a big deal
Kind of a big deal

Does the other end of the non meraki vpn has a route to 192.168.7.0/24?

View solution in original post

7 Replies 7
Jwiley78
Building a reputation

Under Site 2 Site config tab make sure your client VPN subnet is allowed through Site 2 Site tunnel.

PaulinBeer
Conversationalist

Hi, if you mean to enable it below then I have already enabled it. 

 

PaulinBeer_0-1668008653460.png

 

Jwiley78
Building a reputation

Yeah, that's what I was referring to.  I've missed that step a few times in the past.  If that's set and no ACLs are blocking then I would reach out to support.  They can help with packet captures to assist.

ww
Kind of a big deal
Kind of a big deal

Does the other end of the non meraki vpn has a route to 192.168.7.0/24?

PaulinBeer
Conversationalist

I suspect not, will that be needed?

ww
Kind of a big deal
Kind of a big deal

Yeszz

PaulinBeer
Conversationalist

Hi, that solved it... so simple. 

 

Thanks for you help. 

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels