Bug 2039199

Summary:	axcall always fails with AX25_WINDOW
Product:	[Fedora] Fedora	Reporter:	Bastian <main.delegate>
Component:	ax25-apps	Assignee:	Richard Shaw <hobbes1069>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	35	CC:	bobjensen, hobbes1069
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-12-13 16:17:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bastian 2022-01-11 08:28:19 UTC

Description of problem:
Whenever I try to use axcall, after having attached to my virtual Kiss TNC node (direwolf), I get the following error: 

$ axcall -r radio db0xx
GW4PTS AX.25 Connect 2.0.1
AX25_WINDOW: Invalid argument

Even if I explicitly set the window with -w 2 I get the same error.


Version-Release number of selected component (if applicable):
2.0.0-5.fc35

How reproducible:
Anytime I use axcall I get the error message as long as I have attached a device. Additional command line arguments were not able to make a difference (e.g. setting the -w parameter).


Steps to Reproduce:
1. Set up a TNC (I use direwolf), which is exposed on e.g. /dev/pts/2
2. Add the following line to /etc/ax25/axports (use tabs instead of spaces):
radio dl1xxx-5 1200 255 2 144.800 MHz 1200
3. Run kissattach: 
# kissattach /dev/pts/2 radio
4. Run axcall
$ axcall -r radio db0xx

Actual results:
GW4PTS AX.25 Connect 2.0.1
AX25_WINDOW: Invalid argument

Expected results:
axcall tries to connect to db0xx

Additional info:

Comment 1 Richard Shaw 2022-01-14 02:11:17 UTC

I'm not sure what to do, I switched to the fork at https://github.com/ve7fet/linuxax25 a few years ago because the main source had not been updated in some time. Now it seems the fork is suffering for the same reason. 

The last commit was in 2019.

Comment 2 Richard Shaw 2022-01-14 04:15:29 UTC

For posterity here's a thread for the same issue on Debian, looks to be a change made in the kernel so no quick fixes here.

https://lists.debian.org/debian-hams/2022/01/msg00106.html

Comment 3 Ben Cotton 2022-11-29 17:38:06 UTC

This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Ben Cotton 2022-12-13 16:17:39 UTC

Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.