wrote: You can still populate your routing table using a munge script and you have several ways to get the encap file: FTP, Email or via the portal’s API. The easier way though, is to use the RIP44d to automatically do it for you. More details on the Wiki: https://wiki.ampr.org <https://wiki.ampr.org/> Chris _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net

The "best practice" is to run ampr-ripd with a patched kernel if yours is a 4.x one. If you choose JNOS, none of that is necessary and all the settings need to be done in jnos. Marius, YO2LOJ On 16.12.2020 14:04, Chris Maness via 44Net wrote: > I tried rip44d and it failed with an error message. Something about a non > configured tun device. That was with and without JNOS running, so I am > thinking it needs to be fixed for my kernel version. > > On Wed, Dec 16, 2020 at 4:00 AM G1FEF via 44Net &lt;44net(a)mailman.ampr.org&gt; > wrote: > >>> On 16 Dec 2020, at 00:11, Chris Maness via 44Net &lt;44net(a)mailman.ampr.org&gt; >> wrote: >>> I have been inactive for a long time, and I am trying to get my >>> Raspberry Pi to talk to 44 net the way I did with my slackware boxes >>> 10-15 years ago. I am not having a lot of luck doing things the way I >>> did back in the day. Maybe a bruit force munge script is the way to >>> go. What is the current way to pull the encap.txt? >> You can still populate your routing table using a munge script and you >> have several ways to get the encap file: FTP, Email or via the portal’s API. >> >> The easier way though, is to use the RIP44d to automatically do it for you. >> >> More details on the Wiki: https://wiki.ampr.org <https://wiki.ampr.org/> >> >> Chris >> >> >> >> _________________________________________ >> 44Net mailing list >> 44Net(a)mailman.ampr.org >> https://mailman.ampr.org/mailman/listinfo/44net >> > _________________________________________ > 44Net mailing list > 44Net(a)mailman.ampr.org > https://mailman.ampr.org/mailman/listinfo/44net

Our experience is that the munge script is the most reliable. When there have been disruptions at the main gateway, whether it was down or not sending routes or not sending all routes, or problems with RIP44d, our connectivity has been unaffected. Granted, those problems have been few - perhaps a couple/few times a year. But 0 problems is better than >0. When we download the file, we perform a couple of checks: -- if the download fails or the result is not readable, then send an email to the sysop and continue using the old routes -- if the number of changes in the file is large, then send an email to the sysop and continue using the old routes. This has saved us a couple of times when the gateways file put out for download was corrupted and missing a bunch of routes. 12 years now, and I can't think of an outage. The only disadvantage I can see is that we don't learn instantaneously about new routes. That's OK. I think we download/munge 4 times a day. In 12 years, that's been fine. And if we need it now, perhaps because we're trying to connect to a new forwarding partner who is brand new on AMPRnet, the script can always be run on demand. But we've never needed to do that. Michael N6MEF -----Original Message----- You can still populate your routing table using a munge script and you have several ways to get the encap file: FTP, Email or via the portal’s API. The easier way though, is to use the RIP44d to automatically do it for you. More details on the Wiki: https://wiki.ampr.org <https://wiki.ampr.org/> Chris _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net