Right... Just mistyped on small touchscreen; correct is RIPv2. Best regards. --- Tom - SP2L Sent from Xperia Z1 with AquaMail http:/​/​www​.​aqua-mail​.​com

Brian, this is actually not quite accurate. Quagga and other RIP routing daemons understand the messages, if the interface is set to an 44net IP with an /8 netmask. They just handle it wrong, sending all routes to the originator of the RIP message (as it should be in standard RIP). So for an entry like 44.182.21.0/24 via 89.122.215.236 sent by 44.0.0.1 ampr-ripd will generate the route: 44.182.21.0/24 via 89.122.215.236 dev tunl0 while quagga will give us: 44.182.21.0/24 via 44.0.0.1 dev tunl0 This is a cause of some confusions, but this can be used to actually get the RIP data into a router, but needs to be processed further to create higher priority routes based on the gateway info, not the originator (and this is how my miktrotik script actually works). Marius, YO2LOJ -----Original Message----- From: Brian Kantor Sent: Wednesday, March 09, 2016 14:35 To: AMPRNet working group Subject: Re: [44net] Is there raceroutre machine on 44 net available forpublic ? (Please trim inclusions from previous messages) _______________________________________________ Well, it uses the RIPv2 packet format but because it's not actually broadcast and because it's carried over the IPIP tunnels it's not really RIP. I just used the packet format because it's well understood and serves a similar purpose. But quagga and other routing software doesn't understand it because it's transported differently. We really don't have an IPIP broadcast capability. - Brian

Actually, in case of completely missing broadcasts, one can replace the saved route files in /var/lib/ampr-ripd with a downloaded standard encap.txt at it will setup the routes (just shut it down before the overwrite and start it again).