Hey Jon,
I saw both of your emails and I think this great work and your
observation of the missing AX.25 device like "ax0" from the output
of "netstat -A ax25 -an" is an interesting one.? I'll look for
that as well.?
Beyond that, if you're looking for a solid AX.25 stack for your
Raspberry Pi 1 or Raspberry Pi 2 hardware, I'd have to recommend
using a VERY old release like Jessie with the 4.14 kernel.? Making
that recommendation really pains me as it's EOL, known insecure,
etc. but bad patches started getting integrated into the Linux
kernel around the 4.17 time frame.
You can see some of this hardware compatibility vs. OS version
detail captured here:
??
--David
KI6ZHD
On 01/31/2024 09:43 PM, Jon Bousselot
KK6VLO wrote:
toggle quoted message
Show quoted text
Mike and David,? all great input and I didn't consider
32/64 for application stability.? I chose 32 because if anyone in
our club has a Pi-1 or Pi-2, they will be choosing the 32 bit
release and rmsgw is such a light weight app and compiles from
source...? I started with the most compatible release.???
The Pi-1 is a pilot project for our club, and the gateway and
client radios are all within my house.? I've told others to finish
soldering their TNC kit and connect, but so far I'm the only one.?
I will attempt to monitor the number of ax25 packets that travel
through the host.? I am usually checking winmail twice a day, and
don't always have a lot of mail to get/send.? The quantity of
packets on that interface are probably small, even for 1200 baud.
The Pi-1 crashed on its own today without the beacon app, after 1d
3h 47m uptime.? Here is what it cried out when going down.
[100075.375841] CPU: 0 PID: 3001 Comm: netstat Tainted: G????????
C???????? 6.1.0-rpi7-rpi-v6 #1? Raspbian 1:6.1.63-1+rpt1
Netstat, while not part of the ax25 tools, does query the ax25
interface statistics.? You might be onto something with the ax25
packet count theory.? I wasn't home when it crashed so I did not
run netstat.
The rmsgw_aci is set to run on cron and it does call the netstat
command several times, one specifically for the ax25 protocol.???
See for yourself.??? The -o is the output log file.
strace -ormsgw_aci.strace-log -fvtTq -s1024
/usr/local/bin/rmsgw_aci
I'm going to downgrade the Pi-1 to Bullseye, patch it thoroughly,
and drop this config on it again and include beacon running every
35 minutes.?
I'll re-image my Pi-3 and load a 64bit Bookworm release and get it
queued up for a second round of tests.? The two Pi's will swap
roles for monitoring the serial console to catch the panic strings
when the other goes crazy
We're collecting quite a few variables to test here.? This could
take a while if crashes only happen every few days.
32 or 64 bit?
Bullseye or Bookworm?
How many ax25 packets until the system becomes unstable?
Beacon or no-beacon?