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.
So, assuming a point to multipoint interface, if there is let's say an announcement 188.8.131.52/24 via 184.108.40.206 coming from 220.127.116.11 on the ipip0 interface, regular RIPv2 would translate this to:
18.104.22.168/24 via 22.214.171.124 if ipip0
while ampr rip would translate this to:
126.96.36.199/24 via 188.8.131.52 if ipip0
In the first case, traffic to 184.108.40.206/24 is sent directly to the gateway (the RIP sender), while in the second case it is encapsulated to 220.127.116.11.
On a mikrotik router it even goes a step further: it creates a ipip tunnel interface, ampr-18.104.22.168 to 22.214.171.124 and creates a route
126.96.36.199/24 via ampr-188.8.131.52
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 184.108.40.206/24 via 220.127.116.11 there are 2 route set:
18.104.22.168 via default-gw (which is autodetected), and 22.214.171.124/24 via 126.96.36.199 if ipip0 to do the encapsulation
So, while the information structure in both cases conforms to the RIPv2 specifications, its usage is completely different.
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:
- Slackware Linux
- Ubuntu/Debian Linux
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) : look here http://wiki.ampr.org/wiki/Setting_up_a_gateway_on_Cisco_Routers at the "Making the route commands automatically" section
- MikroTik : look here http://www.yo2loj.ro/hamprojects/ at the "Mikrotik RIPv2 AMPR Gateway Setup Script 3.0"
- Ubiquiti OS