[Xorp-users] RIP configuration

[Frederic Gilloteau]

Ok, I did a mistake!

No cable was plugged on my eth1 interface (In fact, a cable was but ethernet
negotiation failed and the link was down)
So the RIP route concerning this interface was not propagated (good
functionnality)

With a good ethernet connection on eth1, RIP is working well!

Anyway, thanks for your help

Fred



-----Original Message-----
From: Pavlin Radoslavov [mailto:pavlin at icir.org] 
Sent: lundi 23 juillet 2007 20:18
To: Frederic Gilloteau
Cc: xorp-users at xorp.org
Subject: Re: [Xorp-users] RIP configuration 

> I try to configure RIP on two interfaces :
> Eth0 : 192.168.92.1 (with vif eth0)
> Eth1 : 172.20.0.90 (with vif eth1)
> 
> I have configured these interfaces in the 'interfaces section' and in 
> the 'RIP section'.
> 
> My problem is that RIP is propagated on eth0 with success (seen with 
> tcpdump -i eth0) but no route about the network associated to eth1 
> (172.20.0.0) is propagated through RIP.
> 
> Using 'show rip status all' I can read :
> 
> RIP on eth0 eth0 192.168.92.1
> Status: enabled
> 
> RIP on eth1 eth1 172.20.0.90
> Status: enabled [gated by disabled FEA interface/vif/address]
> 
> I have activated the fea section ...
> 
> Moreover, in the logs of xorp_rtrmgr, I can sometimes read INFO : 
> Detected iftree change on eth1 eth1 172.20.0.90 setting transport enable
false .
> 
> Do you have any idea ?

I think you need to explicitly export the connected routes into RIP:

policy {
    /* Describe connected routes for redistribution */
    policy-statement connected {
        term export {
            from {
                protocol: "connected"
            }
        }
    }
}

protocols {
    rip {
        export: "connected"
        ...
    }
}


Regards,
Pavlin


> Thanks in advance
> 
> Regards
> 
> Fred
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users