Re: Ethernet Secondary Address and ping/Rip

From: P729 (p729@xxxxxxx)
Date: Sat Jul 13 2002 - 17:41:44 GMT-3


   
You might also want to try having R1 RIP source a default route
('default-information originate') or policy routing on R2, just for drill.

Regards,

Mas Kato
https://ecardfile.com/id/mkato
----- Original Message -----
From: "Yakout esmat" <yesmat@iprimus.com.au>
To: "Matt Mullins" <dahlene@aros.net>; <ccielab@groupstudy.com>
Sent: Saturday, July 13, 2002 3:25 AM
Subject: RE: Ethernet Secondary Address and ping/Rip

> When you have secondary ip address running RIP or IGRP/EIGRP you will need
> to disable ip split horizon on that interface, otherwise the secondary
> address will not be advertised.
>
> In your wcenario: when you ping from R2, source address is 172.19.35.0,
> which is known by R1, that's why you are getting responce.
>
> When you ping from R1, source address is 192.168.10.0, which is not known
by
> R2 hence not getting any responce.
>
> Try to disable ip split horizon on ethernet interface on R1 and see what
> happens, it should work.
>
> HTH
>
> Yakout
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Matt Mullins
> Sent: Saturday, July 13, 2002 4:25 PM
> To: ccielab@groupstudy.com
> Subject: Ethernet Secondary Address and ping/Rip
>
>
> I am trying to do the following:
>
> Ping from R1 to R2 and have R2 learn rip routes via R1
>
> R1--------Ethernet--------R2
>
> Config router 1
> interface Ethernet0
> ip address 172.19.35.15 255.255.255.128 secondary
> ip address 192.168.10.33 255.255.255.240
> Rip is also configured
> IOS Version 12.1(5)T9
>
> Config router 2
> interface Ethernet0
> ip address 172.19.35.2 255.255.255.128
> Rip is also configured
> IOS Version 12.2(1d)
>
> I can ping from router 2 to router 1 no problems. R1 also learns routes
> from
> R2 via rip no problems.
>
> Problem:
> I cannot ping from R1 to R2 or to any subnets off of R2. The routes are
> being
> learned via rip but they are not pingable. If I turn on an IP Packet
Detail
> I
> get the following output on R2 while pinging from R1
> 00:42:47: ICMP type=8, code=0
> 00:42:47: IP: s=172.19.35.2 (local), d=192.168.10.33, len 100, unroutable
> 00:42:47: ICMP type=0, code=0
> 00:42:49: IP: s=192.168.10.33 (Ethernet0), d=172.19.35.2 (Ethernet0), len
> 100,
> r
> cvd 3
> 00:42:49: ICMP type=8, code=0
> 00:42:49: IP: s=172.19.35.2 (local), d=192.168.10.33, len 100, unroutable
> 00:42:49: ICMP type=0, code=0
> 00:42:51: IP: s=192.168.10.33 (Ethernet0), d=172.19.35.2 (Ethernet0), len
> 100,
> r
> cvd 3
> 00:42:51: ICMP type=8, code=0
> 00:42:51: IP: s=172.19.35.2 (local), d=192.168.10.33, len 100, unroutable
> 00:42:51: ICMP type=0, code=0
> 00:42:53: IP: s=192.168.10.33 (Ethernet0), d=172.19.35.2 (Ethernet0), len
> 100,
> r
> cvd 3
>
> Should this work?
>
> I can make it work by configuring R2 as follows but did not think this was
> required



This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:28 GMT-3