Revision as of 17:13, 8 January 2021 by Cross (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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.

What's the difference?

There is a big difference in how the packets are processed.

The regular RIPv2 sets a route to a specific subnet via the sender and interface where the RIP broadcast was received on. The gateway information is used only as an optimization element, in case a route with to that gateway already exists so that the one with the lower metric gets chosen.

In our case, we use the RIP announcements to transport the subnet AND gateway information.

Detailed description

So, assuming a point to multipoint interface, if there is let's say an announcement via coming from on the ipip0 interface, regular RIPv2 would translate this to: via if ipip0

while ampr rip would translate this to: via if ipip0

In the first case, traffic to is sent directly to the gateway (the RIP sender), while in the second case it is encapsulated to

On a mikrotik router it even goes a step further: it creates a ipip tunnel interface, ampr- to and creates a route via ampr-

This is the processing in the usual case, for 44 subnets having a 44net gateway we assume that the gateway is published by BGP and is directly reachable, so for a announcement like via there are 2 route set: via default-gw (which is autodetected), and via if ipip0 to do the encapsulation

So, while the information structure in both cases conforms to the RIPv2 specifications, its usage is completely different.

RIP44 Daemons

Two programs are available for GNU/Linux to utilize these updates:

A program is also available for OpenBSD:


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