[nos-bbs] RIP configuration woes
Maiko Langelaar
maiko at pcs.mb.ca
Tue Nov 5 11:37:17 EST 2013
Hi Michael,
Check this link out : RIP for NOS users (dated, but probably helpful)
http://wetnet.net/pipermail/seatcp/2003-March/002900.html
I've never heard of quagga, so I looked it up, and I'm sure you're not
talking about the extinct subspecies of the plains zebra that lived in
South Africa, I see it's a software routing suite. Never heard about
it before (till now) and certainly never used it before. Sorry.
The first thing I think you need to do is compile the RIP in JNOS as
it used to be long before any of this AMPR RIP stuff was implemented,
in other words, in your config.h, make sure RIPAMPRGW is #undef, and
that #define RIP (and possible #define RIP98) are there. I see refs
to RIP98 in some of the searchs I did for quagga. The bottom line,
don't use the RIPAMPRGW for this. The problem with that however is
you will not be able to use the AMPR rip stuff and you'll have to
go back to your encap.txt. I know, I know, should have been better
thought out, but anyways it's just the way it is right now.
> 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
You'll have to play with this on your own. Get your JNOS into the
original RIP configuration as explained, and just start from there,
I don't know how conforming the implementation is, never used it.
> But no matter what I try, JNOS doesn't seem to listen
Of course ethreal/tcpdump/whatever should help you out.
Maiko
More information about the nos-bbs
mailing list