[nos-bbs] FW: RIP configuration woes

Michael E. Fox - N6MEF n6mef at mefox.org
Mon Nov 4 16:19:12 EST 2013



More info:

Apparently, JNOS RIP doesn't listen to unicast.  

I tried a new build with #define RIPAMPRGW (normally I have it undefined)

This allowed me to use the ip upstairs command.  That caused it to actually
start receiving the rip updates.  But then "rip trace 2" shows errors that
the incoming packets are not IPIP and it ignores the routes.


So, again, how do I get JNOS to accept regular RIPv2 updates using either
the multicast or a unicast address?

And how do I restrict it to only listen to specific neighbors on specific







From: nos-bbs-bounces at tapr.org [mailto:nos-bbs-bounces at tapr.org] On Behalf
Of Michael E. Fox - N6MEF
Sent: Sunday, November 03, 2013 8:06 PM
To: 'TAPR xNOS Mailing List'
Subject: [nos-bbs] RIP configuration woes


I'm trying to create the following RIP configuration in JNOS:


Accept RIP v2 updates on interface tun0 from linux quagga ripd

Don't accept RIP in on any other interface

Don't send RIP out on any interface 


I have quagga configured with a neighbor entry for the JNOS address so it
will send unicast since JNOS doesn't accept multicast.

I can see the routes going out on the tun0 interface.

But no matter what I try, JNOS doesn't seem to listen to what quagga is
sending out.  "rip status" shows 0 rec'd and "rip trace 2" shows nothing. 


What is the proper JNOS configuration?





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20131104/900c7a05/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Untitled attachment 00082.txt
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20131104/900c7a05/attachment.txt>

More information about the nos-bbs mailing list