Hi all,
Following on from my Ax.25 amateur radio on Linux thread, I've still not solved this problem.
I have got kind people from the debian-hams mailing list helping me, but I've got to a stage where I reckon the problem is so deep and so general that someone who is just very good with Linux might be able to help.
Background: it's an embedded ARM machine running Debian. Kernel is 2.4.26. A port called ax0 is created that is the tx/rx place for traffic, it acts just like a normal port as far as the Linux system is concerned. ax25d is a copy of inetd, but modified for AX.25 traffic. The ax25d program listens on this port for connections:
Netstat -i shows that data is being rx/tx'd from this port:
But for some reason the listening daemon cannot hear it. Some other programs that are built to "watch" AX.25 traffic on the port CAN hear the data. Programs are called "listen" and "ax25spy". I'm wondering if there's some obscure kernel option that might be stopping it?
I'm not expecting any responses really, but if anyone has a clue I'd be grateful. Can anyone think of any reasons why the traffic might not be getting through to the daemon?
Cheers guys,
Jon
Following on from my Ax.25 amateur radio on Linux thread, I've still not solved this problem.
I have got kind people from the debian-hams mailing list helping me, but I've got to a stage where I reckon the problem is so deep and so general that someone who is just very good with Linux might be able to help.
Background: it's an embedded ARM machine running Debian. Kernel is 2.4.26. A port called ax0 is created that is the tx/rx place for traffic, it acts just like a normal port as far as the Linux system is concerned. ax25d is a copy of inetd, but modified for AX.25 traffic. The ax25d program listens on this port for connections:
Code:
root@ts7000:root# netstat --ax25
Active AX.25 sockets
Dest Source Device State Vr/Vs Send-Q Recv-Q
* M6VXO-1 ax0 LISTENING 000/000 0 0Netstat -i shows that data is being rx/tx'd from this port:
Code:
root@ts7000:root# netstat -i
Kernel Interface table
Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg
ax0 230 0 11 0 0 0 7 0 0 0 BRUBut for some reason the listening daemon cannot hear it. Some other programs that are built to "watch" AX.25 traffic on the port CAN hear the data. Programs are called "listen" and "ax25spy". I'm wondering if there's some obscure kernel option that might be stopping it?
I'm not expecting any responses really, but if anyone has a clue I'd be grateful. Can anyone think of any reasons why the traffic might not be getting through to the daemon?
Cheers guys,
Jon