Re: Kernel 6.9.1 AX.25 Crash

["Dave Hibberd" <hibby@debian.org>]

Can you use other libax25 dependent packages or is it only Uronode?

axcall for netrom would be a reasonable starter to see if it's a libax25 problem or not. 

LinFBB, from what I remember, uses its own internal state machine/etc once it's bound to the socket.

Cheers,

-- 
  Hibby
  Debian Developer
  Packet Radioist
  MM0RFN

On Tue, 21 May 2024, at 4:07 AM, Chris Maness wrote:
> Ok, the only thing not working so far is UROnode in this system.  I am
> thinking it needs to be updated to the newer kernel.  I am getting:
>
> ERROR; connect_to: bind: Cannot assign requested address
>
> When I try to connect to a NETROM node from UROnode (AX.25 only works tho).
>
> I can connect from LinFBB with NETROM directly to other nodes using my
> NETROM port in LinFBB.
>
> -Chris KQ6UP
>
>
> On Mon, May 20, 2024 at 7:12 PM Dan Cross <crossd@gmail.com> wrote:
>>
>> On Mon, May 20, 2024 at 9:06 PM Lars Kellogg-Stedman <lars@oddbit.com> wrote:
>> > On Mon, May 20, 2024 at 05:11:39PM GMT, Chris Maness wrote:
>> > > Your patch seems to have fixed the issue so far.
>> >
>> > That's great! I'm glad it helped.
>> >
>> > > How come this patch is not included in the mainline source?
>> >
>> > Well, partly because you're the first person to confirm that it works
>> > for someone besides me :). Dan (Cross) has offered to test it out as
>> > well; if I can get a couple of confirmations that it's working, I'll
>> > probably go ahead and submit it to netdev.
>>
>> I am running this as of today, and so far so good.
>>
>> > The bigger issue has been that there are very few people interested in
>> > the ax.25 support in the kernel; there's not a real maintainer, so it's
>> > difficult to get code approved. There were some concerns expressed that
>> > maybe this isn't the *correct* fix, but I would argue that even if it's
>> > not the most correct fix we should try to get it in anyway, since
>> > otherwise ax.25 is completely broken.
>>
>> Agreed: what's there now is objectively broken. Please, let's not let
>> the perfect be the enemy of the good here.
>>
>>         - Dan C.
>
>
>
> -- 
> Thanks,
> Chris Maness