From: MADMAN (dmadlan@xxxxxxxxx)
Date: Tue May 21 2002 - 17:11:58 GMT-3
You had to build maps for pings because by default the ping packets
source is the interface from which it departs the router. Do an
extended ping sourcing the LAN and it's a non-factor.
I'll admit I'm going off of long term memory, not always the most
reliable;), don't build multipoint RIP networks anymore but it should
work fine without neighbor statements for LAN to LAN connectivity.
Keeping in mind of coarse RIP is a classful protocol and it's
limitations therein.
Dave
"Wright, Jeremy" wrote:
>
> i know for ping purposes i would have to build frame maps for end to end but
> what about as far as rip updates.
>
> -----Original Message-----
> From: MADMAN [mailto:dmadlan@qwest.com]
> Sent: Tuesday, May 21, 2002 3:01 PM
> To: Wright, Jeremy
> Cc: 'ccielab@groupstudy.com'
> Subject: Re: rip & split horizon
>
> The hub to spoke communication will work fine, no knobs needed, it's
> the spoke to spoke where you have issues in the multipoint scenerio. If
> your talking frame relay, when you enable frame relay encap you disable
> split horizon by default. To get to the remote spoke from another spoke
> you need to build a map to the spoke via the hub if you want to ping
> spoke A's serial interface sourcing spoke B's serial interface.
>
> dave
>
> "Wright, Jeremy" wrote:
> >
> > i understand the concept of rip and split horizon. if you have a hub and
> > spoke setup and if you do neighbor statements at the hub pointing to the 2
> > spokes will the update get there with split horizon turned on? i dont have
> > the equipment in front of me to simulate this right now. thanks.
> >
> >
> >
> >
> > ************************
> > Jeremy Wright
> > Network Analyst
> > Archer Daniels Midland
> > ja_wright@admworld.com
> > (217)451-4063
> >
> > ************************
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:59:03 GMT-3