From: Justin Menga (Justin.Menga@xxxxxxxxxxxxxxxxxx)
Date: Sat Feb 03 2001 - 10:04:05 GMT-3
Hi,
You shouldn't need to worry with RIP, assuming you are using a lower
distance protocol for your main routing (e.g. OSPF), because the RIP route
to the destination tunnel endpoint won't override your lower distance route.
As I remember in the bootcamps, the problem occurred when using OSPF at the
source, and IGRP across the tunnel. Since IGRP has a lower admin distance
than OSPF (good on you Cisco), of course, bang - recursive route....the
solution to this was to filter routes - not to use passive interface...
If you are asked to exchange routes across the tunnel, how can you set that
to be passive? Then, no routes are exchanged at all......the only solution
I see is to filter out your 'physical' interface from being exchanged across
the tunnel. I can only see passive working if the other end does not
require any of your routes, but the passive end does need to learn some
routes.
e.g.
R1 ----------Tunnel ----------- R2
| |
Net A Net B
| |
-----------OSPF Domain---------
Here, you would filter Net A at R1 and filter Net B at R2 to stop recursive
routes.....if you used passive interface on either R1 or R2 on the tunnel,
no routes will be exchanged......
Regards,
Justin Menga CCIE #6640 MCSE+I CCSE
WAN Specialist
Computerland New Zealand
PO Box 3631, Auckland
DDI: (+64) 9 360 4864 Mobile: (+64) 25 349 599
mailto: justin.menga@computerland.co.nz
-----Original Message-----
From: Robert DeVito [mailto:robertdevito@hotmail.com]
Sent: Saturday, 3 February 2001 7:06 a.m.
To: ccielab@groupstudy.com
Subject: recursive routing for OSPF/EIGRP
I was working on ccbootcamp lab 16 last night and it specifies to use rip
across the tunnel. What I did to avoid link flapping on the tunnel
interface, under rip, on R8 i made the tunnel interface passive. My question
is, if I use a different protocol like EIGRP or OSPF, where if I make one
side passive, I will not be able to receive any routing information because
they won't be able to form adjacency. The only thing that I can think of is
to use a distribute-list or route-map telling EIGRP/OSPF not to advertise
the tunnel's network and to send everything else. Am i thinking on the
correct terms?
Thank you,
Robert
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:28:35 GMT-3