From: Feliz, Edgar (Edgar.Feliz@xxxxxxxx)
Date: Fri Oct 27 2000 - 01:22:18 GMT-3
Thanks to all that replied.
Here is the routing table entry for the path to r1 from r2, and then from r3
with the Ethernet interface on r2 being redistributed as connected. r3 shows
a better metric back to r1 then r2 does.
r2#D 10.1.20.0/28 [90/2195456] via 172.30.1.1, 07:32:51, Serial0
r3#O E1 10.1.20.0/28 [110/84] via 172.32.10.1, 05:24:52, Serial1
Thanks,
EF
-----Original Message-----
From: Nnanna Obuba [mailto:obuba@bellatlantic.net]
Sent: Thursday, October 26, 2000 10:14 PM
To: Feliz, Edgar; 'Ccielab
Subject: Re: Asymmetric routing (CCBOOTCAMP 16
Actually, redistributing the connected ethernet interface into EIGRP did the
trick for me..
----- Original Message -----
From: "Feliz, Edgar" <Edgar.Feliz@BTNA.com>
To: "'Ccielab" <ccielab@groupstudy.com>
Sent: Thursday, October 26, 2000 7:52 PM
Subject: Asymmetric routing (CCBOOTCAMP 16
> I am working on CCBOOTCAMP lab #16, but I am not getting something on task
#
> 2 Q. #2. It goes like this;
>
> Setup asymmetric routing so that when r1 pings r4's Ethernet interface its
> original path is through r2, but its return path is through r3. If I
> understanding this correctly then I should have be able to put a static
> route on r4 to send packets coming from r1 back to r3. If someone has e
> better idea please give me a clue.
>
> r1---F/R-EIGRP--r2---LAN------r4 static route here?
> l l
> l--F/R---OSPF---r3-OSPF-HDLC--l
>
>
> Thanks,
>
>
> Edgar Feliz
>
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:31 GMT-3