Rip44d: Difference between revisions
No edit summary |
Putting in the original rip44d page |
||
| Line 1: | Line 1: | ||
Technically, rip44d is a custom RIPv2 daemon which receives RIP updates from the 44/8 routing service ([[Amprgw]]), and inserts them in the Linux routing table. | |||
RIP ([http://en.wikipedia.org/wiki/Routing_Information_Protocol Routing Information Protocol]) is a method to dynamically update IP routing tables. In practice, on the [[AMPRNet]] gateways, it removes the requirement to periodically download the tunnel routing table ([[encap.txt]]) using FTP and apply it to the routing table. It transmits changes quicker and should be simpler to set up. Amprgw transmits the RIP routing table updates every 5 minutes, while the encap.txt has traditionally been only updated once per day. Some operators have even done the downloads manually (and not very often). | |||
The RIP protocol is used in a slightly unconventional way on the Amprnet, and the standard IP routing daemons such as zebra/quagga are not able to process these packets. Until those daemons are modified to support Amprnet routing updates, a custom implementation such as rip44d can be used. | |||
rip44d is written in the Perl programming language. C might be the conventionally right language to implement daemons such as this, but the author happened to have a good bunch of perl code that could be easily reused in the implementation of rip44d. The routing table is relatively small, so the performance or memory consumption of this daemon isn't very critical. | |||
= Requirements = | |||
# You'll need a Linux computer, which has been added in the Gateways file using the [[Portal]], so that it is know as an AMPRnet gateway and will receive RIP updates from the [[Amprgw]]. It will take some time before Amprgw will learn about new gateways. | |||
# If you have been running the gateway before, and you have already set up a cron job to automatically update the routing table by downloading encap.txt, you need to disable that cron job so that there's only one updating method running at a time. | |||
https://github.com/hessu/rip44d | https://github.com/hessu/rip44d | ||
| Line 13: | Line 25: | ||
http://evvk.com/evvktvh.html#english | http://evvk.com/evvktvh.html#english | ||
INSTALLATION | |||
http://www.qsl.net/kb9mwr/wapr/tcpip/rip44d.html | http://www.qsl.net/kb9mwr/wapr/tcpip/rip44d.html | ||
Revision as of 04:46, 8 May 2013
Technically, rip44d is a custom RIPv2 daemon which receives RIP updates from the 44/8 routing service (Amprgw), and inserts them in the Linux routing table.
RIP (Routing Information Protocol) is a method to dynamically update IP routing tables. In practice, on the AMPRNet gateways, it removes the requirement to periodically download the tunnel routing table (encap.txt) using FTP and apply it to the routing table. It transmits changes quicker and should be simpler to set up. Amprgw transmits the RIP routing table updates every 5 minutes, while the encap.txt has traditionally been only updated once per day. Some operators have even done the downloads manually (and not very often).
The RIP protocol is used in a slightly unconventional way on the Amprnet, and the standard IP routing daemons such as zebra/quagga are not able to process these packets. Until those daemons are modified to support Amprnet routing updates, a custom implementation such as rip44d can be used.
rip44d is written in the Perl programming language. C might be the conventionally right language to implement daemons such as this, but the author happened to have a good bunch of perl code that could be easily reused in the implementation of rip44d. The routing table is relatively small, so the performance or memory consumption of this daemon isn't very critical.
Requirements
- You'll need a Linux computer, which has been added in the Gateways file using the Portal, so that it is know as an AMPRnet gateway and will receive RIP updates from the Amprgw. It will take some time before Amprgw will learn about new gateways.
- If you have been running the gateway before, and you have already set up a cron job to automatically update the routing table by downloading encap.txt, you need to disable that cron job so that there's only one updating method running at a time.
https://github.com/hessu/rip44d
LICENSE AND COPYRIGHT
Copyright (C) 2011 Heikki Hannikainen, OH7LZB
Packaging Copyright (C) 2012 C.J. Adams-Collier, KF7BMP
This program is released under the following license: EVVKTVH / ICCLEIYSIUYA http://evvk.com/evvktvh.html#english
INSTALLATION