How can I diagnose why my ampr-ripd is not receiving the broadcast? Any tools?
Likely your problem is caused by a kernel bug that was introduced some time ago, I don't know if it has been fixed in the meantime or if it was defined as 'desirable behaviour' and left that way.
Some time ago I faced the same problem, and I could only fix it by adding the -r flag ("Use raw socket instead of multicast") to ampr-ripd. In multicast mode, which used to work fine, it simply did not work anymore on the Pi.
Rob
Thanks for the replys. I woke up this morning, checked, and saw the table 44 now filled with routes. So, the gateway is working again. I didn't do anything. Maybe someone activated or sent me the broadcast.
I have this RPI2 updated with all the latest updates available and maybe that can cause some problem if a bug is introduced. A few months back, on my other RPI2 I remember installing the updates and causes my RPI2 to freezed initiating an internal linbpq forward. Maybe some problem with socat. So, in that RPI2 decided not to install any more updates and working fine for now.
I will add the -r flag. Thanks for the tip.
Jose / HP2AT
----- Original Message ----- From: "Rob Janssen" pe1chl@amsat.org To: 44net@hamradio.ucsd.edu Sent: Tuesday, March 15, 2016 4:44 AM Subject: Re: [44net] Help Not receiving ampr-ripd encap route broadcast
(Please trim inclusions from previous messages) _______________________________________________
How can I diagnose why my ampr-ripd is not receiving the broadcast? Any tools?
Likely your problem is caused by a kernel bug that was introduced some time ago, I don't know if it has been fixed in the meantime or if it was defined as 'desirable behaviour' and left that way.
Some time ago I faced the same problem, and I could only fix it by adding the -r flag ("Use raw socket instead of multicast") to ampr-ripd. In multicast mode, which used to work fine, it simply did not work anymore on the Pi.
Rob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
If it works without it, don't.
The -r flag will make ampr-ripd receive ALL interface traffic and filter out multicasts in user space, while in regular operation mode that's left to the kernel and is more efficient. While on a big system it probably doesn't make much difference, on a limited resource device like the PI it could.
Marius, YO2LOJ
-----Original Message----- From: Jose Ng Lee Sent: Tuesday, March 15, 2016 16:48 To: AMPRNet working group Subject: Re: [44net] Help Not receiving ampr-ripd encap route broadcast _______________________________________________ I will add the -r flag. Thanks for the tip.
Jose / HP2AT
-
Jose Ng Lee -
Marius Petrescu -
Rob Janssen