cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
619
Views
10
Helpful
5
Replies

Could someone tell me why the gre tunnel is not working?

Translator
Community Manager
Community Manager

Kochundeagil_0-1666602781428.png

I'm writing because there was a problem while setting it up. I don't think the setting itself is difficult, and I think I set it up properly, but it doesn't work. 

Kochundeagil_5-1666603036978.png

Even if I try tracert, it doesn't seem to be using tunnel. 

It's the image of topology and settings. Did I do anything wrong? 

gre1 :

Kochundeagil_1-1666602947872.png

Kochundeagil_2-1666602956858.png

gre 2 :

Kochundeagil_4-1666602991610.png

Kochundeagil_3-1666602979571.png

 

1 Accepted Solution

Accepted Solutions

Hello
Looks like you may be incurring recursive routing, as stated by @MHM Cisco World  the tunnel and source/destination address shouldn’t be advertised with each other, as such the tunnel could see its own source destination addressing through its tunnel, also you are advertising the same network (192.168.1.0/24 from each rtr)

Try the following:

GRE1
router eigrp 100

no network 192.168.1.0
no network 192.168.6.0


ip route 192.168.5.0 255.255.255.0 tunnel 10 

GRE2
router eigrp 100
no network 192.168.1.0
no network 192.168.5.0

ip route 192.168.6.0 255.255.255.0 tunnel 10


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

View solution in original post

5 Replies 5

Because you config wrong net under each eigrp of both router.

Also you cant use same routing protocol for both, tunnel ip and tunnel source.

Correct network and also use no auto summary.

Richard Burts
Hall of Fame
Hall of Fame

We have only a little information to work with but not enough for us to understand the issue.As a first step can you tell us if gre1 is able to ping 3.3.3.2? And if gre 2 is able to ping 3.3.2.1?

HTH

Rick

Hello
Looks like you may be incurring recursive routing, as stated by @MHM Cisco World  the tunnel and source/destination address shouldn’t be advertised with each other, as such the tunnel could see its own source destination addressing through its tunnel, also you are advertising the same network (192.168.1.0/24 from each rtr)

Try the following:

GRE1
router eigrp 100

no network 192.168.1.0
no network 192.168.6.0


ip route 192.168.5.0 255.255.255.0 tunnel 10 

GRE2
router eigrp 100
no network 192.168.1.0
no network 192.168.5.0

ip route 192.168.6.0 255.255.255.0 tunnel 10


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

Thank you for your reply. As you said, it was a problem caused by an incorrect routing setting and was solved. Have a nice day.

Hello,

if this problem persists, post the zipped Packet Tracer project (.pkt) file...

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card