IPIP Mesh/OpenWrt - Revision history

KI5QKX: Organize IPIP Mesh documentation and navigation

2026-09-29T19:08:40Z

Organize IPIP Mesh documentation and navigation

KI5QKX: KI5QKX moved page Setting up a gateway on OpenWRT to IPIP Mesh/OpenWrt: Group IPIP Mesh documentation under IPIP Mesh

2026-09-29T19:08:39Z

KI5QKX moved page Setting up a gateway on OpenWRT to IPIP Mesh/OpenWrt: Group IPIP Mesh documentation under IPIP Mesh

← Older revision	Revision as of 19:08, 29 September 2026
(No difference)

KI5QKX: mw push

2026-09-28T22:28:10Z

mw push

← Older revision		Revision as of 22:28, 28 September 2026
Line 195:		Line 195:
	[[Category:Infrastructure]]		[[Category:Infrastructure]]
	[[Category:Gateways]]		[[Category:Gateways]]
			[[Category:Device and platform guides]]

KI5QKX: mw push

2026-04-30T18:52:40Z

mw push

← Older revision		Revision as of 18:52, 30 April 2026
Line 46:		Line 46:
	* opkg update		* opkg update
	* opkg install ampr-ripd		* opkg install ampr-ripd


	'''Configure:'''		'''Configure:'''
Line 192:		Line 191:
	* https://openwrt.org/docs/guide-user/network/start		* https://openwrt.org/docs/guide-user/network/start

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

KI5QKX: mw push

2026-03-01T00:14:38Z

mw push

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

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

KI5QKX: mw push

2026-02-28T23:20:24Z

mw push

← Older revision		Revision as of 23:20, 28 February 2026
Line 98:		Line 98:
	# Dynamic filter, -s argument creates encap.txt		# Dynamic filter, -s argument creates encap.txt
	'''# ./etc/config/ampr-ripd -p <PASSWORD> -s -t 44 -a <44.xxx.xxx.xxx/xx> -x ./etc/config/load_ipipfilter.sh &'''		'''# ./etc/config/ampr-ripd -p <PASSWORD> -s -t 44 -a <44.xxx.xxx.xxx/xx> -x ./etc/config/load_ipipfilter.sh &'''
	## Allows traceroute to respond using ~~44net~~ IP of tunl0 or br-amprlan ##		## Allows traceroute to respond using 44Net IP of tunl0 or br-amprlan ##
	echo 1 > /proc/sys/net/ipv4/icmp_errors_use_inbound_ifaddr		echo 1 > /proc/sys/net/ipv4/icmp_errors_use_inbound_ifaddr

Line 144:		Line 144:
	option lookup '44'		option lookup '44'

	### You must add an IP rule for all ~~44net~~ IPs residing on the device		### You must add an IP rule for all 44Net IPs residing on the device
	config rule		config rule
	option src '44.xxx.xxx.0/24		option src '44.xxx.xxx.0/24
Line 185:		Line 185:
	* '''reboot'''		* '''reboot'''

	== See ~~Also~~ ==		== See also ==

	* [[ampr-ripd]]		* [[ampr-ripd]]

K2IE: Fix typo

2025-09-16T15:41:30Z

Fix typo

← Older revision		Revision as of 15:41, 16 September 2025
Line 52:		Line 52:
	In this example, 44.127.255.1 is the address assigned to your OpenWrt host. 255.255.255.0 is the associated netmask. 44.127.255.0 is your assigned network number.		In this example, 44.127.255.1 is the address assigned to your OpenWrt host. 255.255.255.0 is the associated netmask. 44.127.255.0 is your assigned network number.

	* /etc/init.d/ampr-ripd ~~configre~~ 44.127.254.1 255.255.254.0 44.127.254.0		* /etc/init.d/ampr-ripd configure 44.127.254.1 255.255.254.0 44.127.254.0
	* /etc/iit.d/ampr-ripd restart		* /etc/iit.d/ampr-ripd restart
	* /etc/init.d/network restart		* /etc/init.d/network restart

K2IE at 15:40, 16 September 2025

2025-09-16T15:40:48Z

← Older revision		Revision as of 15:40, 16 September 2025
Line 3:		Line 3:
	TL;DR		TL;DR

	~~Skip~~ to [[#Express setup \| Express setup]]		Most readers will want to skip to [[#Express setup \| Express setup]]

	== Running the [[RIP\| RIP44 protocol]] ==		== Running the [[RIP\| RIP44 protocol]] ==

K2IE: Changes to document OpenWrt ampr-ripd package installation process

2025-09-16T15:39:45Z

Changes to document OpenWrt ampr-ripd package installation process

@@ Line 1: / Line 1: @@
 This Wiki provides operators a straightforward method of configuring your OpenWrt device for use with the [[ARDC]] network.
 == Running the [[RIP| RIP44 protocol]] ==
@@ Line 10: / Line 13: @@
 ''Therefore:''
-* '''You must have access to a binary [https://en.wikipedia.org/wiki/Executable executable] of [[ampr-ripd]] that is compatible with the [https://en.wikipedia.org/wiki/Central_processing_unit CPU] in your OpenWrt device (e.g. i386, i586, x86_64, MIPS, PPC, etc.). If you do not, you must [https://en.wikipedia.org/wiki/Compiler compile] ampr-ripd yourself, or install the packages necessary to run [[rip44d]].'''
+* '''You must have access to a binary [https://en.wikipedia.org/wiki/Executable executable] of [[ampr-ripd]] that is compatible with the [https://en.wikipedia.org/wiki/Central_processing_unit CPU] in your OpenWrt device (e.g. i386, i586, x86_64, MIPS, PPC, etc.). An OpenWrt package is available to install and configure ampr-ripd (see Express setup below).  Alternatively, install the packages necessary to run [[rip44d]].'''
 * '''[[ampr-ripd]]''' (written in C by YO2LOJ) is used in this Wiki example, as fewer prerequisite software are required (e.g. C++ library), compared to [[rip44d]]
 * ''There is also an experimental [[RIP44.lua]] daemon which should run with standard packages''
@@ Line 33: / Line 36: @@
 ** familiar with entering OpenWrt UCI (Unified Configuration Interface) commands by serial console or SSH.'''
-== Setup and configuration of OpenWrt ==
+== Express setup ==
 '''Install:'''
 * [https://openwrt.org/packages/pkgdata/kmod-ipip kmod-ipip]
-* [https://openwrt.org/packages/pkgdata/ip-full ip-full]
+* [https://openwrt.org/packages/pkgdata/ip-full ip-tiny]
 * [https://openwrt.org/packages/pkgdata/libstdcpp libstdcpp] (depending on version, it may now be named [https://openwrt.org/packages/pkgdata/libstdcpp6 libstdcpp6])

KI5QKX at 20:20, 12 December 2024

2024-12-12T20:20:10Z

← Older revision		Revision as of 20:20, 12 December 2024
Line 156:		Line 156:
	* [[RIP44.lua]]		* [[RIP44.lua]]
	* https://openwrt.org/docs/guide-user/network/start		* https://openwrt.org/docs/guide-user/network/start


			[[Category:How-To Guides]]

← Older revision		Revision as of 19:08, 29 September 2026
Line 1:		Line 1:
			{{Section nav\|hub=IPIP Mesh\|title=IPIP Mesh\|category=IPIP Mesh}}

	This Wiki provides operators a straightforward method of configuring your OpenWrt device for use with the [[ARDC]] network.		This Wiki provides operators a straightforward method of configuring your OpenWrt device for use with the [[ARDC]] network.

Line 5:		Line 7:
	Most readers will want to skip to [[#Express setup \| Express setup]]		Most readers will want to skip to [[#Express setup \| Express setup]]

	== Running the [[RIP\| RIP44 protocol]] ==		== Running the [[IPIP Mesh/RIP\| RIP44 protocol]] ==
	'''NOTE:'''		'''NOTE:'''

	* To operate a [[Gateway]] on [[AMPRNet]], you must run software to obtain up-to-date route information - a variant of [https://en.wikipedia.org/wiki/Routing_Information_Protocol RIP version 2] protocol named [[RIP\| RIP44]] is used		* To operate a [[IPIP Mesh/Gateways\|Gateway]] on [[AMPRNet]], you must run software to obtain up-to-date route information - a variant of [https://en.wikipedia.org/wiki/Routing_Information_Protocol RIP version 2] protocol named [[IPIP Mesh/RIP\| RIP44]] is used
	* The implementation of [https://en.wikipedia.org/wiki/Routing_Information_Protocol RIP version 2] and RIP44 '''[[RIP#What's the difference?\|are not the same]]'''		* The implementation of [https://en.wikipedia.org/wiki/Routing_Information_Protocol RIP version 2] and RIP44 '''[[IPIP Mesh/RIP#What's the difference?\|are not the same]]'''

	''Therefore:''		''Therefore:''

	* '''You must have access to a binary [https://en.wikipedia.org/wiki/Executable executable] of [[ampr-ripd]] that is compatible with the [https://en.wikipedia.org/wiki/Central_processing_unit CPU] in your OpenWrt device (e.g. i386, i586, x86_64, MIPS, PPC, etc.). An OpenWrt package is available to install and configure ampr-ripd (see Express setup below). Alternatively, install the packages necessary to run [[rip44d]].'''		* '''You must have access to a binary [https://en.wikipedia.org/wiki/Executable executable] of [[IPIP Mesh/Ampr-ripd\|ampr-ripd]] that is compatible with the [https://en.wikipedia.org/wiki/Central_processing_unit CPU] in your OpenWrt device (e.g. i386, i586, x86_64, MIPS, PPC, etc.). An OpenWrt package is available to install and configure ampr-ripd (see Express setup below). Alternatively, install the packages necessary to run [[IPIP Mesh/Rip44d\|rip44d]].'''
	* '''[[ampr-ripd]]''' (written in C by YO2LOJ) is used in this Wiki example, as fewer prerequisite software are required (e.g. C++ library), compared to [[rip44d]]		* '''[[IPIP Mesh/Ampr-ripd\|ampr-ripd]]''' (written in C by YO2LOJ) is used in this Wiki example, as fewer prerequisite software are required (e.g. C++ library), compared to [[IPIP Mesh/Rip44d\|rip44d]]
	* ''There is also an experimental [[RIP44.lua]] daemon which should run with standard packages''		* ''There is also an experimental [[IPIP Mesh/RIP44.lua\|RIP44.lua]] daemon which should run with standard packages''
	* ''For information about compiling for OpenWrt devices, see:''		* ''For information about compiling for OpenWrt devices, see:''
	** [https://openwrt.org/docs/guide-developer/crosscompile Cross Compile - OpenWrt]		** [https://openwrt.org/docs/guide-developer/crosscompile Cross Compile - OpenWrt]
Line 24:		Line 26:
	'''NOTE - ''' ''these instructions assume:''		'''NOTE - ''' ''these instructions assume:''

	* That you have been assigned AMPRNet IP address allocations that are properly claimed; and your [[Gateway]] IP or hostname configured on your account in the [[Portal]]		* That you have been assigned AMPRNet IP address allocations that are properly claimed; and your [[IPIP Mesh/Gateways\|Gateway]] IP or hostname configured on your account in the [[Portal]]
	* ''While not a requirement, that the allocation is /30 (preferablly /29) or larger - that you have enough usable IPs for: tunl0, AMPRLAN and for downstream client usage''		* ''While not a requirement, that the allocation is /30 (preferablly /29) or larger - that you have enough usable IPs for: tunl0, AMPRLAN and for downstream client usage''
	** NAT is not used on the AMPRLAN side of this example		** NAT is not used on the AMPRLAN side of this example
	* '''That you have properly enabled DNS PTR records with your AMPRNet regional coordinator - this enables global IP addresses usage'''		* '''That you have properly enabled DNS PTR records with your AMPRNet regional coordinator - this enables global IP addresses usage'''
	* That you intend to configure your OpenWrt-based (version 14.07 or greater) AMPRNet [[Gateway]] to be a [https://en.wikipedia.org/wiki/Stateful_firewall stateful firewall] for your AMPRNet allocations (i.e. enabling connection tracking). If you prefer to forward all traffic to your allocated AMPRNet IP addresses, you may follow these instructions; but configure your Firewall Zones to forward all traffic to/from AMPRLAN to AMPRWAN		* That you intend to configure your OpenWrt-based (version 14.07 or greater) AMPRNet [[IPIP Mesh/Gateways\|Gateway]] to be a [https://en.wikipedia.org/wiki/Stateful_firewall stateful firewall] for your AMPRNet allocations (i.e. enabling connection tracking). If you prefer to forward all traffic to your allocated AMPRNet IP addresses, you may follow these instructions; but configure your Firewall Zones to forward all traffic to/from AMPRLAN to AMPRWAN
	* These instructions configure your AMPRNet Tunnel and AMPRNet Local Interfaces in their own [https://en.wikipedia.org/wiki/Policy-based_routing policy-based routing] scenario; and places all local AMPRNet allocations in the main routing instance (you must provide routing rules for your local AMPR subnets to reach local subnets, if you desire)		* These instructions configure your AMPRNet Tunnel and AMPRNet Local Interfaces in their own [https://en.wikipedia.org/wiki/Policy-based_routing policy-based routing] scenario; and places all local AMPRNet allocations in the main routing instance (you must provide routing rules for your local AMPR subnets to reach local subnets, if you desire)
	* Since the OpenWrt Kernel is aware that your AMPRNet allocations exist locally (and are populated on the MAIN ROUTING TABLE), you must provide routing rules for AMPRLAN to reach these local subnets, or omit those rules (not permitting your AMPRLAN to route to your local subnets)		* Since the OpenWrt Kernel is aware that your AMPRNet allocations exist locally (and are populated on the MAIN ROUTING TABLE), you must provide routing rules for AMPRLAN to reach these local subnets, or omit those rules (not permitting your AMPRLAN to route to your local subnets)
Line 77:		Line 79:
	'''Paste:'''		'''Paste:'''

	* '''[[ampr-ripd]]''' to '''/etc/config/''' (always run [[RIP\| RIP44]] software in console mode FIRST after installation to verify execution and obtain the password, the execution of the file is commented-out below)		* '''[[IPIP Mesh/Ampr-ripd\|ampr-ripd]]''' to '''/etc/config/''' (always run [[IPIP Mesh/RIP\| RIP44]] software in console mode FIRST after installation to verify execution and obtain the password, the execution of the file is commented-out below)
	* ''optional'' - dynamic firewall script to /etc/config/load_ipipfilter.sh (see the [[Firewalls#ipset\|ipset]] section of the firewall wiki)		* ''optional'' - dynamic firewall script to /etc/config/load_ipipfilter.sh (see the [[IPIP Mesh/Firewalls#ipset\|ipset]] section of the firewall wiki)
	* the following to /etc/rc.local or on web GUI at'''System > Startup > Local Startup:'''		* the following to /etc/rc.local or on web GUI at'''System > Startup > Local Startup:'''

Line 171:		Line 173:
	* Permit forwarding from AMPRLAN to AMPRWAN and WAN (you must masquerade this traffic when using WAN)		* Permit forwarding from AMPRLAN to AMPRWAN and WAN (you must masquerade this traffic when using WAN)
	* Permit forwarding from LAN to AMPRLAN (as desired, NOTE: you must make an IP Rule for the AMPRLAN to use the LAN's route on the Main Routing Table)		* Permit forwarding from LAN to AMPRLAN (as desired, NOTE: you must make an IP Rule for the AMPRLAN to use the LAN's route on the Main Routing Table)
	* ''For IPENCAP in'' - create Traffic Input rule to allow IPv4 IPENCAP (IP protocol type 4) from Any IP on WAN to any IP on Router ''(or configure optional dynamic script above, see [[Firewalls#OpenWrt\|Firewalls - OpenWrt]])''		* ''For IPENCAP in'' - create Traffic Input rule to allow IPv4 IPENCAP (IP protocol type 4) from Any IP on WAN to any IP on Router ''(or configure optional dynamic script above, see [[IPIP Mesh/Firewalls#OpenWrt\|Firewalls - OpenWrt]])''
	** specify WAN IP instead of ''Any'' - if statically assigned by ISP		** specify WAN IP instead of ''Any'' - if statically assigned by ISP
	* ''For [[RIP\| RIP44]] packets in'' - create Traffic Input rule to allow IPv4 udp/520 from 44.0.0.1 in AMPRWAN to 224.0.0.9 at port udp/520 IP on Router		* ''For [[IPIP Mesh/RIP\| RIP44]] packets in'' - create Traffic Input rule to allow IPv4 udp/520 from 44.0.0.1 in AMPRWAN to 224.0.0.9 at port udp/520 IP on Router
	* Create Traffic Forward rules for any inbound services (as desired)		* Create Traffic Forward rules for any inbound services (as desired)
	* assign the new VLAN to any switch/trunk ports (as desired)		* assign the new VLAN to any switch/trunk ports (as desired)
Line 186:		Line 188:
	== See also ==		== See also ==

	* [[ampr-ripd]]		* [[IPIP Mesh/Ampr-ripd\|ampr-ripd]]
	* [[Firewalls#OpenWrt\|Firewalls - OpenWrt]]		* [[IPIP Mesh/Firewalls#OpenWrt\|Firewalls - OpenWrt]]
	* [[RIP44.lua]]		* [[IPIP Mesh/RIP44.lua\|RIP44.lua]]
	* https://openwrt.org/docs/guide-user/network/start		* https://openwrt.org/docs/guide-user/network/start