[Xorp-users] Trouble with RIP

[Venketesan]

Hi,
Actually the error message was just an example error message which 
appears in all the normally operational nodes except node D. for 
example say we have nodex(eth1)---(eth0)nodey. eth1=10.0.15.1/24; 
eth2=10.0.15.2/24
In a normall operational RIP nodex, i wud see a error message: "  RIP 
port eth1/eth1/10.0.15.1 received bad route from 10.0.15.2:520 - 
loopback route"
and in nodey, i wud see a error message: "  RIP port 
eth0/eth0/10.0.15.2 received bad route from 10.0.15.1:520 - loopback 
route"
This does not affect the operation in any way as i have observed so 
far.

And such a message is received for each of the interfaces in any node 
which is configured with RIP and has RIP neighbor.

The node D that is erroneous is the only one that does not show this 
error message.
I will send the config files when i get back to the machine.

I am using XORP 1.2.

Thanks and regards,
Venkat


----- Original Message -----
From: Atanu Ghosh <atanu at icsi.berkeley.edu>
Date: Wednesday, September 6, 2006 11:10 am
Subject: Re: [Xorp-users] Trouble with RIP

> Hi,
> 
> The configuration file for NodeD may help to analyse the problem. In
> your diagram NodeD does not have eth2 configured yet the error 
message
> is from eth2, this seems a little odd.
> 
>   Atanu.
> 
> >>>>> "Venketesan" == Venketesan  <venkthi1 at iit.edu> writes:
> 
>    Venketesan> Hi, I am having trouble iwth RIP in one of the routers
>    Venketesan> in my setup. i have the following setup:
>    Venketesan> (eth0)NodeA(eth1)----(eth1)NodeB(eth0)----
> (eth1)NodeD(eth0)-----(eth0)
>    Venketesan> nodeE(eth1)
> 
>    Venketesan> The problem is node D. It is not showing any 
> routes by
>    Venketesan> RIP.Although i think D is sending the RIP responses
>    Venketesan> correctly, i.e in NodeB i can see the route to the 
> eth0    Venketesan> for NodeD. Similarly Node E can see route to 
> eth1 in
>    Venketesan> nodeD.
> 
>    Venketesan> One difference between the behaviour of node D 
> than the
>    Venketesan> other nodes that i see in the log messages is in all
>    Venketesan> other nodes (except nodeD) message like :
> 
>    Venketesan> RIP port eth2/eth2/10.0.15.2 received bad route from
>    Venketesan> 10.0.15.1:520 - loopback route
> 
>    Venketesan> Also i saw in ethereal traces that node D does receive
>    Venketesan> RIP responses from neigbors node B and node E about
>    Venketesan> various routes. Node D sends them out correctly too.
> 
>    Venketesan> could anyone guide me how shud proceed to debug the
>    Venketesan> issue. shud i attach config files and log messages?
> 
>    Venketesan> Thanks a lot.
> 
>    Venketesan> regards, Venkat
> 
>    Venketesan> _______________________________________________
>    Venketesan> Xorp-users mailing list Xorp-users at xorp.org
>    Venketesan> 
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>