RIP: Difference between revisions
Jump to navigation
Jump to search
added OSes that ampr-ripd has been compiled for |
|||
| Line 23: | Line 23: | ||
The devices below do not possess a known, end-user method to install additional software (i.e. ampr-ripd). Operators have developed scripts to parse inbound routing packets to make them compatible for usage on AMPRNet: | The devices below do not possess a known, end-user method to install additional software (i.e. ampr-ripd). Operators have developed scripts to parse inbound routing packets to make them compatible for usage on AMPRNet: | ||
* Cisco IOS | * Cisco IOS (a separate machine must run the script) | ||
* JunOS | * JunOS | ||
* MikroTik | * MikroTik | ||
* Ubiquiti OS | * Ubiquiti OS | ||
= See Also = | = See Also = | ||
Revision as of 00:14, 24 May 2017
Information about other AMPRNet gateways can now be received dynamically via modified RIPv2 advertisements. Previously, routes were obtained by creating a munge script that parsed Encap.txt.
RIP44 Daemons
Two programs are available for GNU/Linux to utilize these updates:
Availability/Compatibility
The RIP44 daemons have been tested and known to work on the following operating systems:
- BSD
- OpenWRT/LEDE
- Raspbian
- Slackware Linux
- Ubuntu/Debian Linux
- Vyatta/VyOS
Non-RIP44 Workarounds
The devices below do not possess a known, end-user method to install additional software (i.e. ampr-ripd). Operators have developed scripts to parse inbound routing packets to make them compatible for usage on AMPRNet:
- Cisco IOS (a separate machine must run the script)
- JunOS
- MikroTik
- Ubiquiti OS
See Also
- startampr - a script that loads the routing daemon on boot on Linux server-type devices
- Instructions for setting up a tunnel gateway on Linux
- Instructions for setting up a gateway on OpenWRT