On 6/25/22 8:13 AM, Harald Welte wrote:
Hi Grant,
Hi Harald,
unortunately not. However, I know that a number of HAM radio operators are still using the AX.25 in Linux. It has not received a lot of maintenance in the last 15+ years or so, but there's some new grant to get that fixed:
*nod*nod*
Unfortunately, despite being related, I think that X.25 and AX.25 are about as compatible as IPv4 and IPv6. If even that. At least IPv6 can have IPv4 addresses mapped into it and converted.
The net/x25 directory still exists. It looks like the application-side interface uses a sockets based API.
I saw on the linux-x25 mailing list that there were updates to the Linux kerenel earlier this year. So there's active development work.
I'm using this HDLC code (with frame relay on top, not X.25) even in production setups together with DAHDI on Digium and other cards. So at least up to that HDLC layer we know it works.
ACK
You could follow with the only difference that you have to use 'sethdlc hdlc0 x25' to tell the HDLC WAN code to put X.25 on top.
Interesting.
Though I suspect that's going to require specific hardware. Conversely X.25 over TCP or X.25 over Ethernet or X.25 over Async uses more generic hardware. :-)
* drivers/net/wan/lapbether.c
This is the LAPB-over-Ethernet driver you already hinted. I've never used it, but looking at the code it seems that it automatically creates a "lapb*" interface for each ethernet interface in your system.
I was thinking that a lapb0, et al., device was created per interface as you suggested.
I'm working to find the user space commands and utilities to bring the interface(s) up and how to use it (them).
I've not seen any XOT code in Linux, so there doesn't seem to be a straight-forward way to hook those two up.
I have found xotd.c 0.04 from 1999-01-08 by Stephane Fillod.
It naturally doesn't want to compile as is on contemporary systems. I've not yet tried to compile on older commensurate systems.
--
Grant. . . .
unix || die
