Why destination tunnel address of ipsec-GRE tunnel is not

From: jeremy co <jeremy.cool14_at_gmail.com>
Date: Fri, 7 May 2010 12:16:11 +0700

Hi,

I have a working scenario of GRE+ipsec tunnel, every thing works fine but
Id I ping other end tunnel interface address sourced from tunnel interface
address of my side I cannot each that!

Anybody have any idea why tunnels interface addresses are not pingable?

interface Tunnel2
 ip address 10.98.201.9 255.255.255.0
 ip nhrp map 10.98.201.17 10.98.17.11
 ip nhrp map multicast 10.98.17.11
 ip nhrp network-id 201
 ip nhrp nhs 10.98.201.17
 ip tcp adjust-mss 1300
 delay 2000
 tunnel source Loopback2
 tunnel mode gre multipoint
 tunnel key 201
 tunnel protection ipsec profile DMVPN
!

on the other side:

interface Tunnel0
 ip address 10.98.201.17 255.255.255.0
 no ip redirects
 ip mtu 1400
 no ip next-hop-self eigrp 101
 ip nhrp map multicast dynamic
 ip nhrp network-id 201
 ip tcp adjust-mss 1300
 no ip split-horizon eigrp 101
 delay 30000
 tunnel source Loopback10
 tunnel mode gre multipoint
 tunnel key 201
 tunnel protection ipsec profile DMVPN

 ping 10.98.201.17 source 10.98.201.9 fails!

but everything else is working , routes exchanged and tunnels are up.

Cheers,

jeremy

Blogs and organic groups at http://www.ccie.net
Received on Fri May 07 2010 - 12:16:11 ART

This archive was generated by hypermail 2.2.0 : Tue Jun 01 2010 - 07:09:52 ART