Rip44d - Revision history

KI5QKX: mw push

2026-04-30T18:52:53Z

mw push

← Older revision		Revision as of 18:52, 30 April 2026
Line 94:		Line 94:
	The daemon was written by Heikki Hannikainen, OH7LZB.		The daemon was written by Heikki Hannikainen, OH7LZB.

			[[Category:How-To]]
	[[Category:How-To Guides]]		[[Category:How-To Guides]]
	[[Category:Infrastructure]]		[[Category:Infrastructure]]
	[[Category:Routing]]		[[Category:Routing]]

KI5QKX: mw push

2026-03-01T00:14:53Z

mw push

← Older revision		Revision as of 00:14, 1 March 2026
Line 96:		Line 96:

	[[Category:How-To Guides]]		[[Category:How-To Guides]]
			[[Category:Infrastructure]]
			[[Category:Routing]]

KI5QKX at 20:36, 12 December 2024

2024-12-12T20:36:53Z

← Older revision		Revision as of 20:36, 12 December 2024
Line 93:		Line 93:

	The daemon was written by Heikki Hannikainen, OH7LZB.		The daemon was written by Heikki Hannikainen, OH7LZB.


			[[Category:How-To Guides]]

KC8QBA: Change in url for content hosted at github.

2024-06-13T16:48:05Z

Change in url for content hosted at github.

← Older revision		Revision as of 16:48, 13 June 2024
Line 36:		Line 36:
	Download the daemon		Download the daemon

	curl -O https://raw.~~github~~.com/hessu/rip44d/master/rip44d		curl -O https://raw.githubusercontent.com/hessu/rip44d/master/rip44d

	Make it executable		Make it executable

Kb9mwr: /* Links */

2017-07-05T19:59:59Z

Links

← Older revision		Revision as of 19:59, 5 July 2017
Line 93:		Line 93:

	The daemon was written by Heikki Hannikainen, OH7LZB.		The daemon was written by Heikki Hannikainen, OH7LZB.

	~~= Links =~~

	* [http://www.qsl.net/kb9mwr/wapr/tcpip/rip44d.html Alternative installation instructions by KB9MWR]

Kb3vwg at 09:26, 3 August 2015

2015-08-03T09:26:11Z

← Older revision		Revision as of 09:26, 3 August 2015
Line 73:		Line 73:
	/usr/local/sbin/rip44d -p PasswordGoesHere < /dev/null &		/usr/local/sbin/rip44d -p PasswordGoesHere < /dev/null &

	That should be all. Really. The downside of this configuration is that it will take up to 5 minutes for the gateway to receive a routing update and become operational after a reboot. The daemon should really be improved to store the current routing table in a local file and load it from there when starting up.		That should be all. Really. The downside of this configuration is that it will take up to 5 minutes for the gateway to receive a routing update and become operational after a reboot. The daemon should really be improved to store the current routing table in a local file and load it from there when starting up. '''(See: [[startampr]] about configuring reload of the AMPR routing table upon reboot with rip44d.)'''

	The above route add command will cause packets destined to 44.255.259.* to be dropped on the floor, unless a more specific route (such as 44.255.259.0/25) exists. If you route the whole /24 subnet to your radio interface, the blackhole route should not be used. If you have smaller subnets or per-host routes for each user host, the blackhole route will prevent packets destined to unused addresses from getting into a loop between your gateway and the Amprgw.		The above route add command will cause packets destined to 44.255.259.* to be dropped on the floor, unless a more specific route (such as 44.255.259.0/25) exists. If you route the whole /24 subnet to your radio interface, the blackhole route should not be used. If you have smaller subnets or per-host routes for each user host, the blackhole route will prevent packets destined to unused addresses from getting into a loop between your gateway and the Amprgw.

Kb3vwg: /* Notes */

2015-08-03T09:04:39Z

Notes

← Older revision		Revision as of 09:04, 3 August 2015
Line 82:		Line 82:
	* It expects that your tunnels are configured on tunl0. Use the -i <if> option to change to another. The tunnel interface must be up and configured before rip44d starts up.		* It expects that your tunnels are configured on tunl0. Use the -i <if> option to change to another. The tunnel interface must be up and configured before rip44d starts up.
	* Old encap routes may be present, the daemon will overwrite them as necessary (it won't touch more specific routes, or ones which are not found in the route advertisements). You don't need to "clean" the routing table before running rip44d if you have populated it from encap.txt.		* Old encap routes may be present, the daemon will overwrite them as necessary (it won't touch more specific routes, or ones which are not found in the route advertisements). You don't need to "clean" the routing table before running rip44d if you have populated it from encap.txt.
			* rip44d does not automatically start, see [[startampr]] for more information about running on boot

	= Support, bug reports and improvements =		= Support, bug reports and improvements =

Kb3vwg: /* Run it for the first time */

2015-08-03T09:03:00Z

Run it for the first time

← Older revision		Revision as of 09:03, 3 August 2015
Line 61:		Line 61:
	Within 5 minutes it should receive the new routing table and take it into use. For added fun, use -v (verbose) or -d (debug, really verbose) to see what it does.		Within 5 minutes it should receive the new routing table and take it into use. For added fun, use -v (verbose) or -d (debug, really verbose) to see what it does.

	After confirming that it works, move it to /usr/local/sbin (or something) and put it in your boot scripts (~~sorry, no sysv init script provided yet~~). At minimum, the following lines in /etc/rc.local should do the required tricks to bring Amprnet routing up. The IP addresses are intentionally invalid – you'll need to replace them with your own.		After confirming that it works, move it to /usr/local/sbin (or something) and put it in your boot scripts '''(see: [[startampr]])'''. At minimum, the following lines in /etc/rc.local should do the required tricks to bring Amprnet routing up. The IP addresses are intentionally invalid – you'll need to replace them with your own.

	# Route my own subnet to blackhole, just to make sure I don't accidentally		# Route my own subnet to blackhole, just to make sure I don't accidentally

Kb3vwg at 20:59, 7 April 2014

2014-04-07T20:59:42Z

← Older revision		Revision as of 20:59, 7 April 2014
Line 17:		Line 17:
	install perl, and IO::Socket::Multicast, a Perl module used for receiving the RIP multicast packets		install perl, and IO::Socket::Multicast, a Perl module used for receiving the RIP multicast packets

	sudo apt-get install perl libio-socket-multicast-perl		sudo apt-get install perl libio-socket-multicast-perl libio-interface-perl

	install something to download the daemon, if needed		install something to download the daemon, if needed

Njohnson at 03:45, 5 April 2014

2014-04-05T03:45:46Z

← Older revision		Revision as of 03:45, 5 April 2014
Line 1:		Line 1:
	Technically, rip44d is a custom RIPv2 daemon which receives periodic routing table updates from the [[AMPRNet]] routing service ~~([[Amprgw]])~~, and inserts them in the Linux routing table.		Technically, rip44d is a custom RIPv2 daemon which receives periodic routing table updates from the [[AMPRNet]] routing service, 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]] [[Gateway]], 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).		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]] [[Gateway]], 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).