RIP: Difference between revisions

From 44Net Wiki
Jump to navigation Jump to search
← Older editNewer edit →
4Z4ZQ (talk | contribs)
90 edits
mNo edit summary
4Z4ZQ (talk | contribs)
90 edits
mNo edit summary
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 (a separate machine must run the script)
* Cisco IOS (a separate machine must run the script) : look here http://wiki.ampr.org/wiki/Setting_up_a_gateway_on_Cisco_Routers  at the "Making the route commands automatically" section"
* JunOS
* JunOS
* MikroTik : look here  http://www.yo2loj.ro/hamprojects/ at the "Mikrotik RIPv2 AMPR Gateway Setup Script 3.0"
* MikroTik : look here  http://www.yo2loj.ro/hamprojects/ at the "Mikrotik RIPv2 AMPR Gateway Setup Script 3.0"

Revision as of 16:29, 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:

See Also

Retrieved from "https://wiki.ampr.org/w/index.php?title=RIP&oldid=702"