cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1488
Views
0
Helpful
13
Replies

Cant ping GRE destination

DanielAbergel
Level 1
Level 1

Hello All,

i start a new lab with tunnels i set up everything(EIGRP + Tunnel0) but i cant ping from R1 to R2 GRE ip dest.

i set up eigrp and one loopback for every router.

R1 config :

 

interface Loopback1

ip address 1.1.1.1 255.255.255.0

!

interface Tunnel0

ip address 10.1.1.1 255.255.255.0

mtu 1476

tunnel source Loopback1

tunnel destination 2.2.2.2

!

!

interface FastEthernet0/0

ip address 172.12.123.1 255.255.255.0

duplex auto

speed auto

!

interface FastEthernet0/1

no ip address

duplex auto

speed auto

shutdown

!

interface Vlan1

no ip address

shutdown

!

router eigrp 1

network 172.12.123.0 0.0.0.255

network 1.1.1.0 0.0.0.255

auto-summary

!

 

R2 config :

interface Loopback2

ip address 2.2.2.2 255.255.255.0

!

interface Tunnel0

ip address 10.1.1.2 255.255.255.0

mtu 1476

tunnel source Loopback2

tunnel destination 1.1.1.1

!

!

interface FastEthernet0/0

ip address 172.12.123.2 255.255.255.0

duplex auto

speed auto

!

interface FastEthernet0/1

no ip address

duplex auto

speed auto

shutdown

!

interface Vlan1

no ip address

shutdown

!

router eigrp 1

network 172.12.123.0 0.0.0.255

network 2.2.2.0 0.0.0.255

auto-summary

!

i add the diagram here.

at the end i want to ping 10.1.1.2 from R1 and from R2 to 10.1.1.1 and its fails.

someone knows what the problem ?

 

1 Accepted Solution

Accepted Solutions

Hello,

 

I just tested your original setup (below) on two real routers, it works perfectly. I am pretty sure it is one of the many flaws in Packet Tracer, which does not feature real, full IOS versions, but rather subsets of commands, with unpredictable results...

 

R1


interface Loopback1
ip address 1.1.1.1 255.255.255.0
!
interface Tunnel0
ip address 10.1.1.1 255.255.255.0
mtu 1476
tunnel source Loopback1
tunnel destination 2.2.2.2
!
interface FastEthernet0/0
ip address 172.12.123.1 255.255.255.0
duplex auto
speed auto
!
router eigrp 1
network 172.12.123.0 0.0.0.255
network 1.1.1.0 0.0.0.255
auto-summary


R2

 

interface Loopback2
ip address 2.2.2.2 255.255.255.0
!
interface Tunnel0
ip address 10.1.1.2 255.255.255.0
mtu 1476
tunnel source Loopback2
tunnel destination 1.1.1.1
!
interface FastEthernet0/0
ip address 172.12.123.2 255.255.255.0
duplex auto
speed auto
!
router eigrp 1
network 172.12.123.0 0.0.0.255
network 2.2.2.0 0.0.0.255
auto-summary

View solution in original post

13 Replies 13

Sergey Lisitsin
VIP Alumni
VIP Alumni

DanielAbergel,

 

First thing you need to check that your EIGRP neighbour relationships have established and that you have both loopbacks learned by the routers. Check the following output:
show ip eigrp nei

show ip route

show ip int brief

and see if anything is not in order. If you want, post the outputs and we can troubleshoot further.

 

Hello,

 

if that is a Packet Tracer project, post the (zipped) .pkt file here...

i attach my packet tracer lab here.

Hello,

 

I just tested your original setup (below) on two real routers, it works perfectly. I am pretty sure it is one of the many flaws in Packet Tracer, which does not feature real, full IOS versions, but rather subsets of commands, with unpredictable results...

 

R1


interface Loopback1
ip address 1.1.1.1 255.255.255.0
!
interface Tunnel0
ip address 10.1.1.1 255.255.255.0
mtu 1476
tunnel source Loopback1
tunnel destination 2.2.2.2
!
interface FastEthernet0/0
ip address 172.12.123.1 255.255.255.0
duplex auto
speed auto
!
router eigrp 1
network 172.12.123.0 0.0.0.255
network 1.1.1.0 0.0.0.255
auto-summary


R2

 

interface Loopback2
ip address 2.2.2.2 255.255.255.0
!
interface Tunnel0
ip address 10.1.1.2 255.255.255.0
mtu 1476
tunnel source Loopback2
tunnel destination 1.1.1.1
!
interface FastEthernet0/0
ip address 172.12.123.2 255.255.255.0
duplex auto
speed auto
!
router eigrp 1
network 172.12.123.0 0.0.0.255
network 2.2.2.0 0.0.0.255
auto-summary

sanju
Level 1
Level 1

Hi Daniel

 

please share output to troubleshoot further, configuration looks fine.

 

R1:

sh ip eigrp neighbors

sh ip route 2.2.2.2

ping 2.2.2.2 source 1.1.1.1

 

R2 :

sh ip eigrp neighbors

show ip route 1.1.1.1

ping 1.1.1.1 source 2.2.2.2

 

regards

 

 

 

I agree that the partial configs posted look appropriate. Perhaps there is something in the remaining parts of the config that we do not see that contribute to the issue. But I suspect there is some basic connectivity issue that causes the issue. So the suggested outputs (show ip interface brief, show ip route, show ip eigrp neighbor) might be helpful in diagnosing the problem. 

 

I also note that the diagram shows a switch connecting the routers. It might be helpful if we had some information about that switch, perhaps starting with the output of show interface status.

HTH

Rick

Hey all,

thanks for try to help,

here the outposts from the commads:

 

R1#sh ip route 2.2.2.2
Routing entry for 2.0.0.0/8
Known via "eigrp 1", distance 90, metric 156160, type internal
Redistributing via eigrp 1
Last update from 172.12.123.2 on FastEthernet0/0, 00:01:26 ago
Routing Descriptor Blocks:
* 172.12.123.2, from 172.12.123.2, 00:01:26 ago, via FastEthernet0/0
Route metric is 156160, traffic share count is 1
Total delay is 5100 microseconds, minimum bandwidth is 100000 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 1

 

R1#sh ip eigrp neighbors
IP-EIGRP neighbors for process 1
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 172.12.123.2 Fa0/0 10 00:01:52 40 1000 0 3

 

Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds:
Packet sent with a source address of 1.1.1.1
!!!!!

 

R2:

 

R2#sh ip eigrp neighbors

IP-EIGRP neighbors for process 1

H Address Interface Hold Uptime SRTT RTO Q Seq

(sec) (ms) Cnt Num

0 172.12.123.1 Fa0/0 11 00:05:14 40 1000 0 3

 

Routing entry for 1.0.0.0/8

Known via "eigrp 1", distance 90, metric 156160, type internal

Redistributing via eigrp 1

Last update from 172.12.123.1 on FastEthernet0/0, 00:05:20 ago

Routing Descriptor Blocks:

* 172.12.123.1, from 172.12.123.1, 00:05:20 ago, via FastEthernet0/0

Route metric is 156160, traffic share count is 1

Total delay is 5100 microseconds, minimum bandwidth is 100000 Kbit

Reliability 255/255, minimum MTU 1500 bytes

Loading 1/255, Hops 1

 

Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds:

Packet sent with a source address of 2.2.2.2

!!!!!

 

 

 

and the switch show ip status:

 

Switch#show interfaces status

Port Name Status Vlan Duplex Speed Type

Fa0/1 connected 1 auto auto 10/100BaseTX

Fa0/2 connected 1 auto auto 10/100BaseTX

Fa0/3 notconnect 1 auto auto 10/100BaseTX

Fa0/4 notconnect 1 auto auto 10/100BaseTX

Fa0/5 notconnect 1 auto auto 10/100BaseTX

Fa0/6 notconnect 1 auto auto 10/100BaseTX

Fa0/7 notconnect 1 auto auto 10/100BaseTX

Fa0/8 notconnect 1 auto auto 10/100BaseTX

Fa0/9 notconnect 1 auto auto 10/100BaseTX

Fa0/10 notconnect 1 auto auto 10/100BaseTX

Fa0/11 notconnect 1 auto auto 10/100BaseTX

Fa0/12 notconnect 1 auto auto 10/100BaseTX

Fa0/13 notconnect 1 auto auto 10/100BaseTX

Fa0/14 notconnect 1 auto auto 10/100BaseTX

Fa0/15 notconnect 1 auto auto 10/100BaseTX

Fa0/16 notconnect 1 auto auto 10/100BaseTX

Fa0/17 notconnect 1 auto auto 10/100BaseTX

Fa0/18 notconnect 1 auto auto 10/100BaseTX

Fa0/19 notconnect 1 auto auto 10/100BaseTX

Fa0/20 notconnect 1 auto auto 10/100BaseTX

Fa0/21 notconnect 1 auto auto 10/100BaseTX

Fa0/22 notconnect 1 auto auto 10/100BaseTX

Fa0/23 notconnect 1 auto auto 10/100BaseTX

Fa0/24 notconnect 1 auto auto 10/100BaseTX

Gig0/1 notconnect 1 auto auto 10/100BaseTX

Gig0/2 notconnect 1 auto auto 10/100BaseTX

 

DanielAbergel
Level 1
Level 1
now i try to make other tunnel from fa0/0 172.12.123.1 to 172.12.123.2 its working but when i try to make tunnel with the loopbacks its not working.

Thanks for the additional information. I still do not see a reason why your tunnel between loopback interface addresses is not working. Please post the output of the commands show ip interface brief and show ip route from both routers. Also perhaps the complete config of the routers.

HTH

Rick

Hi Richard,

R1 :

R1#show run

Building configuration...

 

Current configuration : 996 bytes

!

version 12.4

no service timestamps log datetime msec

no service timestamps debug datetime msec

no service password-encryption

!

hostname R1

!

!

!

!

!

!

!

!

ip cef

no ipv6 cef

!

!

!

!

!

!

!

!

!

!

!

!

spanning-tree mode pvst

!

!

!

!

!

!

interface Loopback1

ip address 1.1.1.1 255.255.255.0

!

interface Tunnel0

ip address 10.1.1.1 255.255.255.0

mtu 1476

tunnel source Loopback1

tunnel destination 2.2.2.2

!

!

interface Tunnel1

ip address 11.1.1.1 255.255.255.0

mtu 1476

tunnel source FastEthernet0/0

tunnel destination 172.12.123.2

!

!

interface FastEthernet0/0

ip address 172.12.123.1 255.255.255.0

duplex auto

speed auto

!

interface FastEthernet0/1

no ip address

duplex auto

speed auto

shutdown

!

interface Vlan1

no ip address

shutdown

!

router eigrp 1

network 172.12.123.0 0.0.0.255

network 1.1.1.0 0.0.0.255

network 10.0.0.0

network 11.0.0.0

auto-summary

!

ip classless

!

ip flow-export version 9

!

!

!

!

!

!

!

!

line con 0

!

line aux 0

!

line vty 0 4

login

!

!

!

end

 

ip rotue:

 

Gateway of last resort is not set

 

1.0.0.0/8 is variably subnetted, 2 subnets, 2 masks

D 1.0.0.0/8 is a summary, 00:04:08, Null0

C 1.1.1.0/24 is directly connected, Loopback1

D 2.0.0.0/8 [90/156160] via 172.12.123.2, 00:03:36, FastEthernet0/0

10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks

D 10.0.0.0/8 is a summary, 00:03:36, Null0

C 10.1.1.0/24 is directly connected, Tunnel0

11.0.0.0/8 is variably subnetted, 2 subnets, 2 masks

D 11.0.0.0/8 is a summary, 00:04:08, Null0

C 11.1.1.0/24 is directly connected, Tunnel1

172.12.0.0/16 is variably subnetted, 2 subnets, 2 masks

D 172.12.0.0/16 is a summary, 00:04:08, Null0

 

R2:

 

R2#show run

Building configuration...

 

Current configuration : 996 bytes

!

version 12.4

no service timestamps log datetime msec

no service timestamps debug datetime msec

no service password-encryption

!

hostname R2

!

!

!

!

!

!

!

!

ip cef

no ipv6 cef

!

!

!

!

!

!

!

!

!

!

!

!

spanning-tree mode pvst

!

!

!

!

!

!

interface Loopback2

ip address 2.2.2.2 255.255.255.0

!

interface Tunnel0

ip address 10.1.1.2 255.255.255.0

mtu 1476

tunnel source Loopback2

tunnel destination 1.1.1.1

!

!

interface Tunnel1

ip address 11.1.1.2 255.255.255.0

mtu 1476

tunnel source FastEthernet0/0

tunnel destination 172.12.123.1

!

!

interface FastEthernet0/0

ip address 172.12.123.2 255.255.255.0

duplex auto

speed auto

!

interface FastEthernet0/1

no ip address

duplex auto

speed auto

shutdown

!

interface Vlan1

no ip address

shutdown

!

router eigrp 1

network 172.12.123.0 0.0.0.255

network 2.2.2.0 0.0.0.255

network 10.0.0.0

network 11.0.0.0

auto-summary

!

ip classless

!

ip flow-export version 9

!

!

!

!

!

!

!

!

line con 0

!

line aux 0

!

line vty 0 4

login

!

!

!

end

 

 

R2 ip route:

D 1.0.0.0/8 [90/156160] via 172.12.123.1, 00:05:02, FastEthernet0/0

2.0.0.0/8 is variably subnetted, 2 subnets, 2 masks

D 2.0.0.0/8 is a summary, 00:05:34, Null0

C 2.2.2.0/24 is directly connected, Loopback2

10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks

D 10.0.0.0/8 is a summary, 00:05:01, Null0

C 10.1.1.0/24 is directly connected, Tunnel0

11.0.0.0/8 is variably subnetted, 2 subnets, 2 masks

D 11.0.0.0/8 is a summary, 00:05:34, Null0

C 11.1.1.0/24 is directly connected, Tunnel1

172.12.0.0/16 is variably subnetted, 2 subnets, 2 masks

D 172.12.0.0/16 is a summary, 00:05:34, Null0

 

DanielAbergel,

 

Can you please turn on packet debugging and try to ping the tunnel IP address from R1 to R2. The debugging is turned on by 

"debug ip packet detail" command.

 

Thanks all for help seems its problem with the packet tracer client.

Review Cisco Networking for a $25 gift card