From: Tim Chan (timanji@yahoo.com)
Date: Tue Aug 22 2006 - 06:54:24 ART
Thanks Peter, it makes sense now. Because the router was seeing networks as host routes and
not /24 routes, it would reject updates it was receiving from those networks.
Thanks!
-tim
----- Original Message ----
From: Peter Plak <plukkie@gmail.com>
To: Tim Chan <timanji@yahoo.com>
Cc: ccielab@groupstudy.com
Sent: Tuesday, August 22, 2006 2:33:47 AM
Subject: Re: validate-update-source
try "no peer neighbor-route" on the interface, cause it's creating a /32
route for the neighbor.
On 8/22/06, Tim Chan <timanji@yahoo.com> wrote:
>
> My understanding of the RIP "validate-update-source" command was that the
> router will assure that the source IP address of incoming updates matches
> the network of the received interface, right?
>
> So can someone explain why this is needed when one side of a PPP link is
> getting it's IP address
> from a dhcp server? (Or even being assigned from the remote peer?) It's
> the same subnet, so why
> is the update source validation failing?
>
> Until I add the "no validate-update-source" command, R4 will send RIP
> routes to R5, but refuses
> accept any.
>
> R4:
> interface serial 0/0
> encap ppp
> ip address negotiated
> !
> router rip
> ver 2
> network 139.1.0.0
>
> R5:
> interface serial 0/0
> encap ppp
> ip add 139.1.45.5 255.255.255.0
> peer default ip address 139.1.45.4
> !
> router rip
> ver 2
> network 139.1.0.0
>
> In case you're interested, this is from IEWB Vol I - Lab 13.
>
> Please explain....thanks!
> -tim
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Fri Sep 01 2006 - 15:41:58 ART