01-28-2017 05:12 PM - edited 06-04-2019 02:28 AM
Hello,
I'm connected to devnetsandboxlabs.cisco.com/rave35 and was assigned IP 192.168.235.12. However, the route is misconfigured so I'm not able to ping 192.168.235.12.
Secured Routes (IPv4)
10.10.20.0/24
192.168.223.0/24
Thank you!
Solved! Go to Solution.
01-30-2017 08:55 AM
No Problem. I misread you initial mail. Just corrected the defined split VPN route.
Joe
01-29-2017 05:28 AM
Hi Peter
can you ping the sandboxes servers in your lab? i.e 10.10.20.1, 10.10.10.100 etc from your own pc. where are you pinging the 192.168 address from?
Joe
Sent from my Samsung Galaxy smartphone.
01-30-2017 05:24 AM
Hi Peter,
Any update on your question above? If you like, We can have a webex to bring you through the routing.\\
Regards,
Joe
01-30-2017 08:37 AM
Hi Joe,
I'm able to ping 10.10.20.10, 10.10.20.1 but not 10.10.10.100 and my vpn assigned IP address 192.168.235.13.
Secured Routes (IPv4)
10.10.20.0/24
192.168.223.0/24
Thank you,
Peter
01-30-2017 08:41 AM
Peter,
My apologies. I meant 10.10.20.100. All of the sandbox servers live on the 10.10.20.0/24 subnet.
Regards,
Joe
01-30-2017 08:45 AM
yes, I'm able to ping 10.10.20.10, 10.10.20.100 but not my own IP assigned by the VPN client 192.168.235.13. The route is for the wrong subnet. It should be 192.168.235.0/24 instead of 192.168.223.0/24
Secured Routes (IPv4)
10.10.20.0/24
192.168.223.0/24
Thanks!
01-30-2017 08:53 AM
it's working now...thanks for resolving it so quickly.
01-30-2017 08:55 AM
No Problem. I misread you initial mail. Just corrected the defined split VPN route.
Joe
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide