From: Joe Mama (jsmith1234550@gmail.com)
Date: Wed Dec 12 2007 - 15:43:54 ART
All - Thanks again for your input and help. Below are 5 solutions to
the issue that I just tested.
Joe
Solution 1.
In RIP v1 or 2, with or without neighbors, the combination of 'no
validate-update-source' and 'encap ppp' on an interface will correct
the issue.
Solution 2.
'ip unnumbered' without the use of PPP will work.
Solution 3.
'secondary' IP address on R2 and R3 that are on the same subnet.
Ensure that the primary address (which have networks do not match) is
not using RIP.
The 'no validate-update-source' is not needed as long as the primary
interfaces are not running RIP.
Solution 4.
!
interface Serial1/1
ip address 33.33.33.34 255.255.255.252 secondary
ip address 22.22.22.22 255.255.255.240
serial restart-delay 0
end
+
do not use the 'no validate-update-source'
router rip
version 2
network 2.0.0.0
network 5.0.0.0
network 22.0.0.0
network 24.0.0.0
no auto-summary
The primary network does not have to match the secondary network (in RIPs case).
You could even include both the primary and secondary in the network statement.
Solution 5.
Use static routes (no viable for the lab) to ensure that the routes
point to a interface.
On 12/12/07, AKHILESH THAKUR <akhi_thakur@hotmail.com> wrote:
> Joe
>
> Use encapsulation ppp b/w r2 and r3.
> it works
>
> Akhilesh
>
>
> > From: akhi_thakur@hotmail.com
> > To: jsmith1234550@gmail.com; ccielab@groupstudy.com
> > Subject: RE: RIP Issue - related to link that have diff. networks on each
> side
> > Date: Wed, 12 Dec 2007 08:37:48 +0000
>
> >
> > Joe,
> > secondary address could be tried.
> >
> > Akhi> Date: Tue, 11 Dec 2007 21:47:25 -0500> To: ccielab@groupstudy.com>
> From:
> > jsmith1234550@gmail.com> Subject: RIP Issue - related to link that have
> diff.
> > networks on each side> > The setup> > r1-----r2------r3------r4> > > On
> the
> > link that connects r2 to r3, each interface has different networks subnet
> > masks (22.22.22.22/28 for r2 and 33.33.33.33/30 for r3). All other links
> have
> > normal ips that are on the same network and work fine.> > Requirement: all
> > routers are to run rip. r2 and r3 must pass routing info between each
> other as
> > well as you must be able to route traffic from r1 to r4 and vice-versa.
> 'ip
> > unnumbered' cannot be used. no static / default routes of any kind can be
> > used.> > > Where I'm at: All routers can see routes from each other (used
> the
> > no validate-update-source to get the routes passed along....). However, r1
> for
> > example cannot route to a network on r3 because full route recursion is
> not
> > happening because the next hop for r2 is 33.33.33.33 (the interface
> directly
> > connected to r3) and when doing a route lookup for 33.33.33.33, there is
> no
> > recursion to an interface. a static route pointing traffic destined for
> the
> > netx hops of 22.22.22.22, etc. to the serial interface can fix this but i
> > cannot use statics for this.> > Any ideas would be greatly appreciated. >
> >
> > Joe> >
> >
> _______________________________________________________________________>
> > Subscription information may be found at: >
> > http://www.groupstudy.com/list/CCIELab.html
> >
> _________________________________________________________________
> > Post free property ads on Yello Classifieds now! www.yello.in
> > http://ss1.richmedia.in/recurl.asp?pid=219
> >
> >
> _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
>
> ________________________________
> Post free auto ads on Yello Classifieds now! Try it now!
This archive was generated by hypermail 2.1.4 : Tue Jan 01 2008 - 12:04:30 ARST