You must have access to a binary executable of ampr-ripd that is compatible with the CPU in your OpenWrt device (e.g. i386, i586, x86_64, MIPS, PPC, etc.). If you do not, you must compile ampr-ripd yourself, or 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

That you intend to configure your OpenWrt-based (version 14.07 or greater) AMPRNet Gateway to be a 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 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)

Lastly, that the user:

can navigate the default OpenWrt LuCI web-based graphical user interface locally; and that they are using a device capable of having the packages installed

REMINDER: In OpenWrt 14.07 or lower - be sure to enable connection tracking if you will not masquerade.

Interfaces

Create an unmanaged Interface instance for tunl0 (AMPRWAN) - set to not bring up on boot, adding it to a new own firewall zone amprwan using

Input: Drop (or Reject)

Output: Drop (or Reject)

Forward: Drop (or Reject)

Create an interface instance for a new VLAN and bridge (AMPRNET). Assign an IP from your allocation to this interface - this will become the the Default Route/Gateway IP used on other 44 clients in your VLAN - add it to its own new firewall zone using

Input: Accept (if you wish for you AMPRLAN devices to reach the router)

Output: Accept; and

Forward: Drop (or Reject, depending if you have other downstream routers in this VLAN)

reboot

General Firewalling

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)