From: Spyros Kranis (skranis@algosystems.gr)
Date: Tue Jul 12 2005 - 08:43:48 GMT-3
BB1 advertise routes default metric
R1 has them with metric 1.
I labbed it up again and again with offset in and out list and understood
the following:
The offset is added to the already hop-count/metric that a route has,
plus the hopes ( 1 hop-if is directly connected ) to the router that
receives the route.
In my example
R1 add an offset of 13
plus the hop/metric of 1 that it has in its routing table for these routes,
plus the 1 hop in order to reach R2.
So I get the routes in r2 with a metric of 15.
Thanks for your help
Skra
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Schulz, Dave
Sent: Tuesday, July 12, 2005 2:38 PM
To: Spyros Kranis ; nobody@groupstudy.com; ccielab@groupstudy.com
Subject: RE: Rip issues - offset list
Skra -
What metric is R2 advertising the route as in your first case? This should
tell the story.
Dave
-----Original Message-----
From: nobody@groupstudy.com
To: ccielab@groupstudy.com
Sent: 7/12/2005 6:59 AM
Subject: RE: Rip issues - offset list
Maybe the offset is added to the already offset/metric that a route has
-
plus the hopes ( 1 hop-if is directly connected ) to the router that
receives the route.
Am I correct?
TIA
Skra
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Spyros Kranis
Sent: Tuesday, July 12, 2005 1:37 PM
To: ccielab@groupstudy.com
Subject: Rip issues - offset list
Hi group,
I found an issue regarding rip.
BB1 - R1 - R2
the question:
Configure R1 such that R2 would not advertise any networks to any of its
neighboring routers.
I thought that the following with an access-list should work
in order R2 to get routes with a metric of 15.
R1
Router rip
Offset-list 2 out 14 F0/0
Access-list 2............
But I found that the following is working with an offset of 13 at r1
in order R2 to get the routers with a metric of 15
R1
Router rip
Offset-list 2 out 13 F0/0.
Any thoughts?
TIA
Skra
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:00:29 GMT-3