My kernel is a 5.x on a Raspberry Pi.
On Wed, Dec 16, 2020 at 4:45 AM Marius Petrescu <marius(a)yo2loj.ro> wrote:
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 <44net(a)mailman.ampr.org>
> wrote:
>
>>> On 16 Dec 2020, at 00:11, Chris Maness via 44Net
<44net(a)mailman.ampr.org>
>> 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