What are the differences between RIP44 and RIP v2? Is the RIP44 protocol documented anywhere? I'm learning more and would like to crack into the differences between the protocols.
--tom n2xu
RIP44 is pretty much RIP v2 sent over encapsulated tunnels to the various gateways. This is done in this manner because there is no concept of broadcasting in the world of tunnels. It requires special software or setup on the receiving end at the gateways in order to decapsulate the RIP packets and process them. Once decapsulated, the RIP packets are handled much like ordinary RIPv2 would be, except that the data in them is used to build an encapsulation routing table of tunnel endpoints rather than Ethernet routes. - Brian
On Thu, Dec 21, 2017 at 01:53:00PM -0600, Tom Cardinal wrote:
What are the differences between RIP44 and RIP v2? Is the RIP44 protocol documented anywhere? I'm learning more and would like to crack into the differences between the protocols.
--tom n2xu _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
What Brian said. And to put a finer point on it, RIP44 is bit-for-bit identical to the RIPv2 wire format. The differences are in how the data are interpreted, now how it is represented.
On Thu, Dec 21, 2017 at 2:53 PM, Tom Cardinal ki4szj@gmail.com wrote:
What are the differences between RIP44 and RIP v2? Is the RIP44 protocol documented anywhere? I'm learning more and would like to crack into the differences between the protocols.
--tom n2xu _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Thanks for the response to Brian and Dan. Dan you were helping me last year... I bailed on you for a linux install when I got new hardware... I'm working on pfSense again.
--tom/n2xu
On 12/21/17 3:06 PM, Dan Cross wrote:
What Brian said. And to put a finer point on it, RIP44 is bit-for-bit identical to the RIPv2 wire format. The differences are in how the data are interpreted, now how it is represented.
On Thu, Dec 21, 2017 at 2:53 PM, Tom Cardinal ki4szj@gmail.com wrote:
What are the differences between RIP44 and RIP v2? Is the RIP44 protocol documented anywhere? I'm learning more and would like to crack into the differences between the protocols.
--tom n2xu _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Tom, a little deeper insight on this, because some may be curious :-)
The RIPv2 actually transfers just a list of destination network/netmask, gateway and distance data from one host to another.
e.g. from 44.0.0.1 (ampr-gw) to 224.0.0.2 (multicast) network: 44.182.21.0/255.255.255.0 gateway: 89.122.215.236 distance: 1
The difference appears in how the routes are interpreted.
From a point of view of a regular RIPv2 processing, the router will know that the specific network is reachable via THE SENDER'S IP AND RECEIVE INTERFACE that sent the announcement. So in a regular RIPv2 system this will translate this to:
route 44.182.21.0/255.255.255.0 via 44.0.0.1 dev ampr-gw metric 2
which is obviously wrong in our case, and would send all traffic via the ampr gateway. The gateway information is used only to mitigate between routing decisions in some implementations, if there are multiple routes with the same distance.
Our routing daemons interpret this in a different way, using the gateway information to get the remote tunneling endpoint and relies on some specific behavior of the linux kernel tunnel driver: route 44.182.21.0/255.255.255.0 via 89.122.215.236 dev tunl0 metric 2 This tells the kernel to encapsulate traffic to 44.182.21.0/24 via the IPIP tunnel tunl0 using 89.122.215.236 as the encap endpoint, which is exactly what we want.
This technique is available ONLY for the linux tunnel driver. E.g. for the mikrotik implementation, the scripts create an individual tunnel to the gateway for each link partner based on the RIP data. The user space implementation done in amprd offers a virtual network interface for all 44.0.0.0/8 traffic and solves all routing issues inside its code, without using the kernel routing tables or the tunnel driver, using the same RIPv2 information.
(Maybe this shoul actually land in the Wiki)
Marius, YO2LOJ
On 21.12.2017 21:53, Tom Cardinal wrote:
What are the differences between RIP44 and RIP v2? Is the RIP44 protocol documented anywhere? I'm learning more and would like to crack into the differences between the protocols.
--tom n2xu _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
-
Brian Kantor -
Dan Cross -
Marius Petrescu -
Tom Cardinal