04-10-2020 02:39 PM
Hello All,
I am trying to set up a VPN between our Router(iS5 Raptor) and Cisco. I can see that the IPSec tunnel is up but traffic is not pushed into the tunnel on the Cisco side. I do not have any NAT.
My setup is given below:
(PC1) 192.168.9.3 -- 192.168.9.1 (Router 1) 172.16.31.1 --- 172.16.31.3 (Router 2) 172.16.21.3 --- 172.16.21.1 (CISCO) 10.10.9.1 -- 10.10.9.3 (PC2)
Tunnel between 172.16.31.1 == 172.16.21.1
Ping form PC2 (10.10.9.3) to 192.168.9.3 (PC1)
The packets reach Cisco (Src: 10.10.9.3, Dest: 192.168.9.3: Interesting traffic)
But instead of being pushed into the tunnel, they end up on the default route.
I am expecting to see an ESP packet pushed into the tunnel for the ic
I'm guessing that some routing config is missing. But cannot figure it out.
Would highly appreciate if someone can point out the mistake in my configuration.
Thanks for looking at my query.
Details below:
The IPSec tunnel is up:
Solved! Go to Solution.
04-13-2020 09:21 AM
The issue was a routing issue on the Cisco router. I found a previous post which pointed to the resolution:
The resolution in my case was the following route:
ip route 192.168.9.0 255.255.255.0 gi 1/0/1
This forces traffic towards the gi 1/0/1 and th
04-10-2020 02:48 PM
Hi,
You can tell from your output that the cisco router is encrypting traffic, but not decrypting. Therefore you should check the configuration on the other router. Confirm whether on not traffic is received, whether traffic could be natted, check routing, check the crypto ACL etc.
#pkts encaps: 5, #pkts encrypt: 5, #pkts digest: 5
#pkts decaps: 0, #pkts decrypt: 0, #pkts verify: 0
HTH
04-11-2020 06:49 AM
Good morning,
Thanks for your response.
My mistake. I did not explain the issue good enough.
Doing a ping from the Cisco router with a proper source works great. The packets are encrypted and decrypted as expected.
The problem is when PC2(10.10.9.3) sends a ping request to 192.168.9 over the tunnel. Cisco router receives the packet as it is the default GW for PC2. But instead of pushing it into the tunnel it sends it to it's default GW 172.16.21.3. I can see unencrypted pings coming to 172.16.21.3.
Would highly appreciate some pointers which will allow the Cisco router to push routed traffic coming in from end device into the tunnel.
The routes on my Cisco routers are as follows:
S* 0.0.0.0/0 [1/0] via 172.16.21.3
10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C 10.10.9.0/24 is directly connected, GigabitEthernet1/0/2
L 10.10.9.1/32 is directly connected, GigabitEthernet1/0/2
172.16.0.0/16 is variably subnetted, 3 subnets, 2 masks
C 172.16.21.0/24 is directly connected, GigabitEthernet1/0/1
L 172.16.21.1/32 is directly connected, GigabitEthernet1/0/1
S 172.16.31.0/24 [1/0] via 172.16.21.3
Switch#
Some logs of correct encryption/decryption:
Counter values at start:
04-13-2020 09:21 AM
The issue was a routing issue on the Cisco router. I found a previous post which pointed to the resolution:
The resolution in my case was the following route:
ip route 192.168.9.0 255.255.255.0 gi 1/0/1
This forces traffic towards the gi 1/0/1 and th
04-16-2020 12:47 PM
Hello All,
The solution for some reason is not working anymore.
Cisco router is sending out an ARP for the interesting traffic on the default route of the interface.
who has 192.168.9.3 tell 172.16.21.1 <-- This is comes out on the middle router.
Something does not seem right here. The ICMP request should just enter the tunnel, I think without triggering an ARP.
Am not getting anywhere. Any inputs would be highly appreciated.
Tx.
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