Home • Using RIP updates from AMPRgw

IMPORTANT NOTE - this configuration is designed for JNOS systems that have the luxury of a static internet ip address, and where JNOS itself does the 44 encapsulation, and where your system has an entry in the gateways file. In other words, you are running a registered AMPRnet gateway. That is the way my system has been setup for many years now. IF you are doing the 44 encapsulation in linux, then this configuration simply does not apply to you. I am also assuming you are not currently using the RIP client for anything else.

Just recently, the AMPRnet gateway system has started offering RIP (Version 2) updates through the IPIP tunnel. Like alot of NOS users, I too have been using the 'encap.txt' to keep my routes current, but one usually restarts NOS each time a new 'encap.txt' becomes available. It isn't necessary, but old routes will not get purged if you don't. I've decided to switch over to the RIP client built into the JNOS software - my routes are now updated online and in realtime, no more 'encap.txt', no more restarting JNOS each time there is an update to encap.txt.

NOTE : If the RIP updates stop, you WILL loose your routes - you've been warned !

You will need the latest official JNOS 2.0h + a software patch to use this feature, OR you can download the latest JNOS source using the rsync system (see linux downloads section for information on how you can do this), in which case the patch is not required. Click here for the patch file, gunzip it, extract the contents to your JNOS 2.0h source directory.

Edit your config.h file, '#define RIP' and '#define RIPAMPRGW', then do a 'make'. Keep in mind that the 'RIP' definition is actually part of the older JNOS definitions further down the file. Some people have put both '#define' entries at the top of the file, and completely forgot about the '#undef RIP' entry in the older section, which of course will cancel out the entry at the top. Just keep that in mind, when editing your config.h file.

# a 'new' command - allow jnos to recognize multicast used in RIP update
ip upstairs 224.0.0.9
# purging of old routes depends very much on route expiry. I am
# experimenting with 1/2 day for my route lifes
rip ttl 43200
# start the rip client
start rip
# accept RIP update from the AMPRgw system
rip accept 44.0.0.1
# uncomment this entry to debug or trace the RIP update process
# rip trace 9 rip.log 

Restart JNOS and give it a few minutes, the routes should start coming in.