I think using badly outdated software is the answer here.? I never thought I make that recommendation for stuff.
? No doubt, it definitely feels wrong. ?But, I think you have a different objective than I do, so it sounds like the best thing to do for your use case.
? Just a quick update, I did more testing and was able to crash the setup between RMS and PAT twice yesterday, so this is definitely repeatable. ?In a crash cycle, once I can demonstrate "kernel weirdness" with netstat output, it usually takes two ax.25 commands to crash the RMS Pi. ?In one instance I ran axcall twice, in another instance I ran beacon twice.
? I'm going to be away from the console of these test Pis for a few days, so it's a bit pointless to test a crash that only takes a few hours to happen. ?Instead, I'm going to remove rmsgw from ax25d and let the test cycle run while I'm away. ?PAT will try to connect to RMS, but fail; that's ok. ?If I don't see any "kernel weirdness" when I return, then it's safe to conclude that rmsgw is a required element of the crash.
? Cheers
? Mike
