Skip to contentSkip to conversation

axctl utility

DISCUSSION Manfred Haertel, DB3HM 2 participants 3 messages Sep 8, 2003 – Sep 9, 2003

lore
Share & tools
lore
#0 lore raw

When I try to use the axctl utility on an AX.25 connection that runs over a digipeater, I get an error message:

axctl: SIOAX25CTLCON: Transport endpoint is not connected

This is because there is no direct connection between the source and the destination call sign and it seems as if there is no way to specify a digipeater on the command line.

I have read the source of the utility, it's actually very simple, just passes the parameters to an ioctl call with SIOCAX25CTLCON as the second parameter.

Is there a chance to specify a digipeater in the ioctl() call? I have not found a documentation of this call yet.

Thanks for any help!

73 de DB3HM

Signature · 7 lines
Manfred Härtel, DB3HM    mailto:[email protected]
                         http://rz-home.de/mhaertel

-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#1 lore raw
Quoted 6 lines · On Mon, 2003-09-08 at 23:15, Manfred Haertel, DB3HM wrote:

I have read the source of the utility, it's actually very simple, just passes the parameters to an ioctl call with SIOCAX25CTLCON as the second parameter.

Is there a chance to specify a digipeater in the ioctl() call? I have not found a documentation of this call yet.

The ioctl call is passing a "struct ax25_ctl_struct" to the kernel. That structure has the fields digi_count and digi_addr (see netax25/axlib.h) that should probably be filled in. The argument parsing should be modified to accept a digi path in addition to to dest call (maybe use ax25_aton() to fill in a temporary "struct full_sockaddr_ax25" and copy the digi stuff from there to the ax25_ctl_struct).

Signature · 3 lines
Tomi Manninen           Internet:  [email protected]
OH2BNS                  AX.25:     [email protected]
KP20ME04                Amprnet:   [email protected]
#2 lore raw
Quoted 6 lines · Tomi Manninen

The ioctl call is passing a "struct ax25_ctl_struct" to the kernel. That structure has the fields digi_count and digi_addr (see netax25/axlib.h) that should probably be filled in. The argument parsing should be modified to accept a digi path in addition to to dest call (maybe use ax25_aton() to fill in a temporary "struct full_sockaddr_ax25" and copy the digi stuff from there to the ax25_ctl_struct).

Hmm, I tried adding the following lines before the ioctl() call:

ax25_ctl.digi_count = 1;
if (ax25_aton_entry(mydigi, (char *)&ax25_ctl.digi_addr[0]) == -1)

        return 1;

but I still get the "Transport endpoint is not connected" message... :-(

It seems that there is no problem with ax25_aton_entry(), the error message comes from the ioctl() call...

Signature · 7 lines
Manfred Härtel, DB3HM    mailto:[email protected]
                         http://rz-home.de/mhaertel

-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html