Re: Validate Update source command - RIP

In this case how did you configure your static route. Does it points to
the nexthop ip or the outgoing interface?

R1-----e0/0-------------------------------------------e0/1----BB1
            1.1.1.1/24
2.2.2.2/24
In this scenario you need to use two static routes as below

R1
  ip route 2.2.2.2 255.255.255.255 e0/0

BB1
  ip route 1.1.1.1 255.255.255.255 e0/1

not only the above, you need to configure no validate-update-source on
both R1 and BB1.

Then you should receive all the rip routes from BB1 --> R1 and R1--->BB1.
So no matter how many routers connected to R1, they should be able to
reach BB1 connected interfaces if all are advertised by rip.

Nethan

On 6/6/2012 2:30 PM, Mohammed Aftab Memon wrote:
> Hello All,
>
> I am stuck and need your help.
>
> BB1---connected to R1 and is configured with a different subnet. Both run
> Rip v2 but are not reachable. I did configure no validate source command
> and I was able to see all the routes from BB1 in R1 routing table. When I
> ping from R1 to those routes they were not reachable so I created a static
> route and I was able to reach those ips.
>
>
> Now in the network where R1 is connected to other routers, from those
> devices I am able to reach R1 ip address at the same time I do see all the
> routes in the routing table which come from BB1. But those IPs are not
> reachable. When I did a traceroute the packet goes till R1 but there is no
> response from there on.
>
> I am not sure what needs to be done and I am failing here.
>
> Please assist.
>
> Mohammed Aftab Memon
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Thu Jun 07 2012 - 07:13:53 ART