AX.25 on Linux - Revision history

KI5QKX: mw push

2026-05-01T02:01:22Z

mw push

← Older revision		Revision as of 02:01, 1 May 2026
Line 215:		Line 215:
	If your goal is specifically IP over AX.25, the range of options has narrowed.		If your goal is specifically IP over AX.25, the range of options has narrowed.

	The [[https://lore.kernel.org/netdev/20260421021824.1293976-1-kuba@kernel.org/ upstream discussion]] explicitly points out that IP over AX.25 can, in principle, be handled from user space via TUN/TAP integration rather than by requiring the historic kernel implementation.		The [https://lore.kernel.org/netdev/20260421021824.1293976-1-kuba@kernel.org/ upstream discussion] explicitly points out that IP over AX.25 can, in principle, be handled from user space via TUN/TAP integration rather than by requiring the historic kernel implementation.

	That does not mean there is one complete drop-in replacement ready for every old Linux AX.25 workflow today. It does suggest a long-term architectural direction:		That does not mean there is one complete drop-in replacement ready for every old Linux AX.25 workflow today. It does suggest a long-term architectural direction:

KI5QKX: mw push

2026-05-01T02:01:01Z

mw push

← Older revision		Revision as of 02:01, 1 May 2026
Line 215:		Line 215:
	If your goal is specifically IP over AX.25, the range of options has narrowed.		If your goal is specifically IP over AX.25, the range of options has narrowed.

	The upstream discussion explicitly points out that IP over AX.25 can, in principle, be handled from user space via TUN/TAP integration rather than by requiring the historic kernel implementation.		The [[https://lore.kernel.org/netdev/20260421021824.1293976-1-kuba@kernel.org/ upstream discussion]] explicitly points out that IP over AX.25 can, in principle, be handled from user space via TUN/TAP integration rather than by requiring the historic kernel implementation.

	That does not mean there is one complete drop-in replacement ready for every old Linux AX.25 workflow today. It does suggest a long-term architectural direction:		That does not mean there is one complete drop-in replacement ready for every old Linux AX.25 workflow today. It does suggest a long-term architectural direction:

KI5QKX: mw push

2026-04-30T23:09:35Z

mw push

← Older revision		Revision as of 23:09, 30 April 2026
Line 87:		Line 87:
	! Software		! Software
	! Current interface		! Current interface
	~~! Works in the new world?~~
	! Common migration target		! Common migration target
	\|-		\|-
	! colspan="4" \| All-in-one environments		! colspan="3" \| All-in-one environments
	\|-		\|-
	\| [https://www.cantab.net/users/john.wiseman/Documents/BPQ32.html LinBPQ / BPQ32]		\| [https://www.cantab.net/users/john.wiseman/Documents/BPQ32.html LinBPQ / BPQ32]
	\| Implements full stack and applications; provides KISS, AXIP/UDP, AGWPE interfaces		\| Implements full stack and applications; provides KISS, AXIP/UDP, AGWPE interfaces
	~~\| Yes~~
	\| Point applications at its KISS or AGWPE endpoint, or use its built-in applications		\| Point applications at its KISS or AGWPE endpoint, or use its built-in applications
	\|-		\|-
	\| [https://www.langelaar.net/projects/jnos2/ JNOS 2]		\| [https://www.langelaar.net/projects/jnos2/ JNOS 2]
	\| Implements full stack and applications; provides KISS and AGWPE interfaces		\| Implements full stack and applications; provides KISS and AGWPE interfaces
	~~\| Yes~~
	\| Point applications at its KISS or AGWPE endpoint, or use its built-in applications		\| Point applications at its KISS or AGWPE endpoint, or use its built-in applications
	\|-		\|-
	! colspan="4" \| Software TNCs and soundmodems		! colspan="3" \| Software TNCs and soundmodems
	\|-		\|-
	\| [https://github.com/wb2osz/direwolf Dire Wolf]		\| [https://github.com/wb2osz/direwolf Dire Wolf]
	\| KISS over TCP/serial; AGWPE over TCP		\| KISS over TCP/serial; AGWPE over TCP
	~~\| Yes~~
	\| Point your applications at its KISS or AGWPE endpoint		\| Point your applications at its KISS or AGWPE endpoint
	\|-		\|-
	\| [https://www.cantab.net/users/john.wiseman/Documents/QtSoundModem.html QtSoundModem]		\| [https://www.cantab.net/users/john.wiseman/Documents/QtSoundModem.html QtSoundModem]
	\| User-space modem/TNC; KISS and AGWPE host-side interfaces		\| User-space modem/TNC; KISS and AGWPE host-side interfaces
	~~\| Yes~~
	\| Point your applications at its KISS endpoint		\| Point your applications at its KISS endpoint
	\|-		\|-
	\| [http://uz7.ho.ua/packetradio.htm SoundModem]		\| [http://uz7.ho.ua/packetradio.htm SoundModem]
	\| User-space modem/TNC; KISS and AGWPE host-side interfaces		\| User-space modem/TNC; KISS and AGWPE host-side interfaces
	~~\| Yes~~
	\| Point your applications at its KISS or AGWPE endpoint		\| Point your applications at its KISS or AGWPE endpoint
	\|-		\|-
	! colspan="4" \| Endpoint applications and clients		! colspan="3" \| Endpoint applications and clients
	\|-		\|-
	\| [https://github.com/la5nta/pat Pat]		\| [https://github.com/la5nta/pat Pat]
	\| AX.25 support with pluggable engines; AGWPE support; can use Dire Wolf directly over TCP		\| AX.25 support with pluggable engines; AGWPE support; can use Dire Wolf directly over TCP
	~~\| Yes~~
	\| AGWPE		\| AGWPE
	\|-		\|-
	\| [https://github.com/Xastir/Xastir Xastir]		\| [https://github.com/Xastir/Xastir Xastir]
	\| Serial KISS, AGWPE, and optional Linux kernel AX.25 network ports		\| Serial KISS, AGWPE, and optional Linux kernel AX.25 network ports
	~~\| Depends~~
	\| KISS or AGWPE		\| KISS or AGWPE
	\|-		\|-
	\| [https://thelifeofkenneth.com/aprx/ aprx]		\| [https://thelifeofkenneth.com/aprx/ aprx]
	\| Serial KISS or kernel AX.25 interface		\| Serial KISS or kernel AX.25 interface
	~~\| Depends~~
	\| KISS		\| KISS
	\|-		\|-
	\| [https://sourceforge.net/projects/yetanotheraprsc/ YAAC]		\| [https://sourceforge.net/projects/yetanotheraprsc/ YAAC]
	\| User-space APRS client using external TNCs / serial interfaces		\| User-space APRS client using external TNCs / serial interfaces
	~~\| Yes~~
	\| KISS		\| KISS
	\|-		\|-
	\| [https://github.com/n2ygk/aprsdigi/ aprsdigi]		\| [https://github.com/n2ygk/aprsdigi/ aprsdigi]
	\| APRS digipeater software; commonly used with KISS TNCs		\| APRS digipeater software; commonly used with KISS TNCs
	~~\| Yes~~
	\| KISS		\| KISS
	\|-		\|-
	! colspan="4" \| Legacy patterns and kernel-bound tools		! colspan="3" \| Legacy patterns and kernel-bound tools
	\|-		\|-
	\| [https://www.ka9q.net/papers/kiss.html KISS-oriented legacy applications generally]		\| [https://www.ka9q.net/papers/kiss.html KISS-oriented legacy applications generally]
	\| Usually external TNC, pseudo-tty KISS, or TCP KISS		\| Usually external TNC, pseudo-tty KISS, or TCP KISS
	~~\| Depends~~
	\| KISS		\| KISS
	\|-		\|-
	\| [https://packages.debian.org/sid/ax25-tools ax25-tools]		\| [https://packages.debian.org/sid/ax25-tools ax25-tools]
	\| Tools for configuring Linux AX.25 / NET/ROM / ROSE ports		\| Tools for configuring Linux AX.25 / NET/ROM / ROSE ports
	~~\| No~~
	\| None directly; replace the workflow with user-space TNC tooling or keep only in a legacy environment		\| None directly; replace the workflow with user-space TNC tooling or keep only in a legacy environment
	\|-		\|-
	\| [https://packages.debian.org/sid/ax25-apps ax25-apps]		\| [https://packages.debian.org/sid/ax25-apps ax25-apps]
	\| User applications for AX.25 / NET/ROM / ROSE over the Linux stack, including <code>ax25d</code>		\| User applications for AX.25 / NET/ROM / ROSE over the Linux stack, including <code>ax25d</code>
	~~\| Mostly no~~
	\| Switch to something like LinBPQ, JNOS, Pat, or an APRS-specific tool		\| Switch to something like LinBPQ, JNOS, Pat, or an APRS-specific tool
	\|-		\|-
	\| [https://www.systutorials.com/docs/linux/man/8-net2kiss/ net2kiss]		\| [https://www.systutorials.com/docs/linux/man/8-net2kiss/ net2kiss]
	\| Converts a kernel AX.25 network interface into a pseudo-tty KISS stream		\| Converts a kernel AX.25 network interface into a pseudo-tty KISS stream
	~~\| No~~
	\| No direct equivalent; consider refactoring your stack		\| No direct equivalent; consider refactoring your stack
	\|}		\|}

	~~Some notes about reading the table:~~

	* '''Yes''' means the software already works without depending on the removed code.
	* '''Depends''' means “check the configured interface.” The software may work fine through KISS, AGWPE, serial, or TCP.
	* '''No''' or '''Mostly no''' means the software category is tightly coupled to the old Linux stack and will not work with future kernels.

	== Developing new user-space AX.25 tools ==		== Developing new user-space AX.25 tools ==

KI5QKX: mw push

2026-04-30T23:07:38Z

mw push

← Older revision		Revision as of 23:07, 30 April 2026
Line 88:		Line 88:
	! Current interface		! Current interface
	! Works in the new world?		! Works in the new world?
	~~! Next step to consider~~
	! Common migration target		! Common migration target
	\|-		\|-
	! colspan="5" \| All-in-one environments		! colspan="4" \| All-in-one environments
	\|-		\|-
	\| [https://www.cantab.net/users/john.wiseman/Documents/BPQ32.html LinBPQ / BPQ32]		\| [https://www.cantab.net/users/john.wiseman/Documents/BPQ32.html LinBPQ / BPQ32]
	\| ~~It’s its own packet~~ stack and ~~node/BBS environment~~; provides KISS, AXIP/UDP, AGWPE interfaces		\| Implements full stack and applications; provides KISS, AXIP/UDP, AGWPE interfaces
	\| Yes		\| Yes
	\| ~~Reconfigure~~		\| Point applications at its KISS or AGWPE endpoint, or use its built-in applications
	~~\| Configure~~ its KISS endpoint or ~~AXIP/UDP interface and point your~~ applications ~~at it. Or just use it for everything if it already covers your use case.~~
	\|-		\|-
	\| [https://www.langelaar.net/projects/jnos2/ JNOS 2]		\| [https://www.langelaar.net/projects/jnos2/ JNOS 2]
	\| ~~It is its own networking environment~~; ~~typically external TNC or~~ KISS ~~oriented~~		\| Implements full stack and applications; provides KISS and AGWPE interfaces
	\| Yes		\| Yes
	\| ~~Reconfigure~~		\| Point applications at its KISS or AGWPE endpoint, or use its built-in applications
	~~\| Configure~~ its KISS endpoint ~~and point your~~ applications ~~at it. Or point it at another TNC over AGWPE. Or just use it for everything if it already covers your use case.~~
	\|-		\|-
	! colspan="5" \| Software TNCs and soundmodems		! colspan="4" \| Software TNCs and soundmodems
	\|-		\|-
	\| [https://github.com/wb2osz/direwolf Dire Wolf]		\| [https://github.com/wb2osz/direwolf Dire Wolf]
	\| ~~User-space AX.25;~~ KISS over TCP/serial; AGWPE over TCP		\| KISS over TCP/serial; AGWPE over TCP
	\| Yes		\| Yes
	\| ~~Reconfigure~~		\| Point your applications at its KISS or AGWPE endpoint
	~~\| Set up Dire Wolf’s~~ KISS or AGWPE ~~interface and point your applications at it~~
	\|-		\|-
	\| [https://www.cantab.net/users/john.wiseman/Documents/QtSoundModem.html QtSoundModem]		\| [https://www.cantab.net/users/john.wiseman/Documents/QtSoundModem.html QtSoundModem]
	\| User-space modem/TNC; KISS and AGWPE host-side interfaces		\| User-space modem/TNC; KISS and AGWPE host-side interfaces
	\| Yes		\| Yes
	~~\| Reconfigure~~
	\| Point your applications at its KISS endpoint		\| Point your applications at its KISS endpoint
	\|-		\|-
Line 122:		Line 117:
	\| User-space modem/TNC; KISS and AGWPE host-side interfaces		\| User-space modem/TNC; KISS and AGWPE host-side interfaces
	\| Yes		\| Yes
	~~\| Reconfigure~~
	\| Point your applications at its KISS or AGWPE endpoint		\| Point your applications at its KISS or AGWPE endpoint
	\|-		\|-
	! colspan="5" \| Endpoint applications and clients		! colspan="4" \| Endpoint applications and clients
	\|-		\|-
	\| [https://github.com/la5nta/pat Pat]		\| [https://github.com/la5nta/pat Pat]
	\| AX.25 support with pluggable engines; AGWPE support; can use Dire Wolf directly over TCP		\| AX.25 support with pluggable engines; AGWPE support; can use Dire Wolf directly over TCP
	\| Yes		\| Yes
	~~\| Reconfigure~~		\| AGWPE
	\| AGWPE ~~endpoint~~
	\|-		\|-
	\| [https://github.com/Xastir/Xastir Xastir]		\| [https://github.com/Xastir/Xastir Xastir]
	\| Serial KISS, AGWPE, and optional Linux kernel AX.25 network ports		\| Serial KISS, AGWPE, and optional Linux kernel AX.25 network ports
	\| Depends		\| Depends
	~~\| Reconfigure~~		\| KISS or AGWPE
	\| KISS or AGWPE ~~endpoint~~
	\|-		\|-
	\| [https://thelifeofkenneth.com/aprx/ aprx]		\| [https://thelifeofkenneth.com/aprx/ aprx]
	\| Serial KISS or kernel AX.25 interface		\| Serial KISS or kernel AX.25 interface
	\| Depends		\| Depends
	~~\| Reconfigure~~		\| KISS
	\| KISS ~~endpoint~~
	\|-		\|-
	\| [https://sourceforge.net/projects/yetanotheraprsc/ YAAC]		\| [https://sourceforge.net/projects/yetanotheraprsc/ YAAC]
	\| User-space APRS client using external TNCs / serial interfaces		\| User-space APRS client using external TNCs / serial interfaces
	\| Yes		\| Yes
	~~\| Reconfigure~~		\| KISS
	\| KISS ~~endpoint~~
	\|-		\|-
	\| [https://github.com/n2ygk/aprsdigi/ aprsdigi]		\| [https://github.com/n2ygk/aprsdigi/ aprsdigi]
	\| APRS digipeater software; commonly used with KISS TNCs		\| APRS digipeater software; commonly used with KISS TNCs
	\| Yes		\| Yes
	~~\| Reconfigure~~		\| KISS
	\| KISS ~~endpoint~~
	\|-		\|-
	! colspan="5" \| Legacy patterns and kernel-bound tools		! colspan="4" \| Legacy patterns and kernel-bound tools
	\|-		\|-
	\| [https://www.ka9q.net/papers/kiss.html KISS-oriented legacy applications generally]		\| [https://www.ka9q.net/papers/kiss.html KISS-oriented legacy applications generally]
	\| Usually external TNC, pseudo-tty KISS, or TCP KISS		\| Usually external TNC, pseudo-tty KISS, or TCP KISS
	\| Depends		\| Depends
	~~\| Reconfigure or Replace~~		\| KISS
	\| KISS ~~endpoint~~
	\|-		\|-
	\| [https://packages.debian.org/sid/ax25-tools ax25-tools]		\| [https://packages.debian.org/sid/ax25-tools ax25-tools]
	\| Tools for configuring Linux AX.25 / NET/ROM / ROSE ports		\| Tools for configuring Linux AX.25 / NET/ROM / ROSE ports
	\| No		\| No
	~~\| Freeze (or Revive)~~
	\| None directly; replace the workflow with user-space TNC tooling or keep only in a legacy environment		\| None directly; replace the workflow with user-space TNC tooling or keep only in a legacy environment
	\|-		\|-
Line 174:		Line 161:
	\| User applications for AX.25 / NET/ROM / ROSE over the Linux stack, including <code>ax25d</code>		\| User applications for AX.25 / NET/ROM / ROSE over the Linux stack, including <code>ax25d</code>
	\| Mostly no		\| Mostly no
	\| ~~Freeze (or Revive)~~		\| Switch to something like LinBPQ, JNOS, Pat, or an APRS-specific tool
	~~\| Depends on the specific app; often~~ LinBPQ, JNOS, Pat, or an APRS-specific tool
	\|-		\|-
	\| [https://www.systutorials.com/docs/linux/man/8-net2kiss/ net2kiss]		\| [https://www.systutorials.com/docs/linux/man/8-net2kiss/ net2kiss]
	\| Converts a kernel AX.25 network interface into a pseudo-tty KISS stream		\| Converts a kernel AX.25 network interface into a pseudo-tty KISS stream
	\| No		\| No
	~~\| Replace~~
	\| No direct equivalent; consider refactoring your stack		\| No direct equivalent; consider refactoring your stack
	\|}		\|}

KI5QKX: mw push

2026-04-30T23:02:31Z

mw push

@@ Line 84: / Line 84: @@
 The “Common migration target” column is therefore mostly about host-side interfaces, not about naming one preferred tool. A KISS or AGWPE endpoint might come from Dire Wolf, QtSoundModem, SoundModem, a hardware TNC, or another program that exposes the same kind of interface.
-{| class="wikitable sortable"
+{| class="wikitable"
 ! Software
 ! Current interface
@@ Line 90: / Line 90: @@
 ! Next step to consider
 ! Common migration target
 |-
 | [https://github.com/wb2osz/direwolf Dire Wolf]
@@ Line 96: / Line 112: @@
 | Reconfigure
 | Set up Dire Wolf’s KISS or AGWPE interface and point your applications at it
 |-
 | [https://github.com/la5nta/pat Pat]
@@ Line 102: / Line 132: @@
 | Reconfigure
 | AGWPE endpoint
 |-
 | [https://github.com/Xastir/Xastir Xastir]
@@ Line 127: / Line 151: @@
 | KISS endpoint
 |-
-| [https://www.cantab.net/users/john.wiseman/Documents/QtSoundModem.html QtSoundModem]
+| [https://github.com/n2ygk/aprsdigi/ aprsdigi]
-| User-space modem/TNC; KISS and AGWPE host-side interfaces
+| APRS digipeater software; commonly used with KISS TNCs
 | Yes
 | Reconfigure
-| Point your applications at its KISS endpoint
+| KISS endpoint
 |-
-| [http://uz7.ho.ua/packetradio.htm SoundModem]
+! colspan="5" | Legacy patterns and kernel-bound tools
 |-
 | [https://www.ka9q.net/papers/kiss.html KISS-oriented legacy applications generally]
@@ Line 143: / Line 163: @@
 | Depends
 | Reconfigure or Replace
 | KISS endpoint
 |-

KI5QKX: mw push

2026-04-30T22:56:18Z

mw push

← Older revision		Revision as of 22:56, 30 April 2026
Line 62:		Line 62:
	=== Reconfigure ===		=== Reconfigure ===

	If you’re using software released relatively recently, you may be able to reconfigure it. For example, an APRS application that can use AGWPE or KISS over TCP may only need to be pointed at Dire Wolf or a hardware TNC via a different protocol.		If you’re using software released relatively recently, you may be able to reconfigure it. For example, an APRS application that can use AGWPE or KISS over TCP or serial may only need to be pointed at Dire Wolf or a hardware TNC via a different protocol.

	=== Replace ===		=== Replace ===

KI5QKX: mw push

2026-04-30T22:50:43Z

mw push

← Older revision		Revision as of 22:50, 30 April 2026
Line 255:		Line 255:
	== External resources ==		== External resources ==

	* [https://lore.kernel.org/netdev/20260421021824.1293976-1-kuba@kernel.org/#r Jakub Kicinski’s April 20, 2026 patch proposing removal of the in-tree amateur-radio networking subsystem]		* [https://lore.kernel.org/netdev/20260421021824.1293976-1-kuba@kernel.org/ Jakub Kicinski’s April 20, 2026 patch proposing removal of the in-tree amateur-radio networking subsystem]
	* [https://lore.kernel.org/netdev/20260424232427.792249-1-stephen@networkplumber.org/ Stephen Hemminger’s April 24, 2026 iproute2 cleanup patch noting that AX.25, ROSE, and NET/ROM have been removed upstream]		* [https://lore.kernel.org/netdev/20260424232427.792249-1-stephen@networkplumber.org/ Stephen Hemminger’s April 24, 2026 iproute2 cleanup patch noting that AX.25, ROSE, and NET/ROM have been removed upstream]
	* [https://lwn.net/Articles/1068928/ LWN coverage from April 22, 2026 summarizing the broader kernel code-removal effort]		* [https://lwn.net/Articles/1068928/ LWN coverage from April 22, 2026 summarizing the broader kernel code-removal effort]
	* [https://lore.kernel.org/netdev/CAEoi9W6ZRw6aEh62Xbgkg-TW8URHbVp6dHTT9krFiTkotjTuTA@mail.gmail.com/#t Dan Cross on the likely user-space direction, including TUN/TAP for IP over AX.25]		* [https://lore.kernel.org/netdev/CAEoi9W6ZRw6aEh62Xbgkg-TW8URHbVp6dHTT9krFiTkotjTuTA@mail.gmail.com/ Dan Cross on the likely user-space direction, including TUN/TAP for IP over AX.25]
	* [https://github.com/linux-netdev/mod-orphan linux-netdev/mod-orphan], the out-of-tree repository where the removed code is being staged		* [https://github.com/linux-netdev/mod-orphan linux-netdev/mod-orphan], the out-of-tree repository where the removed code is being staged
	* [https://github.com/wb2osz/direwolf Dire Wolf], a widely used user-space software TNC for AX.25 packet radio		* [https://github.com/wb2osz/direwolf Dire Wolf], a widely used user-space software TNC for AX.25 packet radio

KI5QKX: mw push

2026-04-30T22:49:09Z

mw push

← Older revision		Revision as of 22:49, 30 April 2026
Line 184:		Line 184:
	== Developing new user-space AX.25 tools ==		== Developing new user-space AX.25 tools ==

	~~One strong theme in this transition is that many~~ of the building blocks ~~people need~~ already exist in open source. Before starting a brand-new user-space AX.25 implementation, it is worth looking first at projects that already do some or all of the following:		Many of the building blocks already exist in open source. Before starting a brand-new user-space AX.25 implementation, it is worth looking first at projects that already do some or all of the following:

	* Modem/TNC functions		* Modem/TNC functions
Line 255:		Line 255:
	== External resources ==		== External resources ==

	* [https://~~www~~.~~spinics~~.~~net/lists~~/netdev/~~msg1179014~~.~~html~~ Jakub Kicinski’s April 20, 2026 patch proposing removal of the in-tree amateur-radio networking subsystem]		* [https://lore.kernel.org/netdev/20260421021824.1293976-1-kuba@kernel.org/#r Jakub Kicinski’s April 20, 2026 patch proposing removal of the in-tree amateur-radio networking subsystem]
	* [https://~~www~~.~~spinics~~.~~net/lists~~/netdev/~~msg1180117~~.~~html~~ Stephen Hemminger’s April 24, 2026 iproute2 cleanup patch noting that AX.25, ROSE, and NET/ROM have been removed upstream]		* [https://lore.kernel.org/netdev/20260424232427.792249-1-stephen@networkplumber.org/ Stephen Hemminger’s April 24, 2026 iproute2 cleanup patch noting that AX.25, ROSE, and NET/ROM have been removed upstream]
	* [https://lwn.net/Articles/1068928/ LWN coverage from April 22, 2026 summarizing the broader kernel code-removal effort]		* [https://lwn.net/Articles/1068928/ LWN coverage from April 22, 2026 summarizing the broader kernel code-removal effort]
	* [https://~~www~~.~~spinics~~.~~net/lists~~/netdev/~~msg1179252~~.~~html~~ Dan Cross on the likely user-space direction, including TUN/TAP for IP over AX.25]		* [https://lore.kernel.org/netdev/CAEoi9W6ZRw6aEh62Xbgkg-TW8URHbVp6dHTT9krFiTkotjTuTA@mail.gmail.com/#t Dan Cross on the likely user-space direction, including TUN/TAP for IP over AX.25]
	* [https://github.com/linux-netdev/mod-orphan linux-netdev/mod-orphan], the out-of-tree repository where the removed code is being staged		* [https://github.com/linux-netdev/mod-orphan linux-netdev/mod-orphan], the out-of-tree repository where the removed code is being staged
	* [https://github.com/wb2osz/direwolf Dire Wolf], a widely used user-space software TNC for AX.25 packet radio		* [https://github.com/wb2osz/direwolf Dire Wolf], a widely used user-space software TNC for AX.25 packet radio

KI5QKX: mw push

2026-04-30T22:35:00Z

mw push

← Older revision		Revision as of 22:35, 30 April 2026
Line 182:		Line 182:
	* '''No''' or '''Mostly no''' means the software category is tightly coupled to the old Linux stack and will not work with future kernels.		* '''No''' or '''Mostly no''' means the software category is tightly coupled to the old Linux stack and will not work with future kernels.

	== ~~Existing~~ user-space ~~projects worth studying first~~ ==		== Developing new user-space AX.25 tools ==

	One strong theme in this transition is that many of the building blocks people need already exist in open source. Before starting a brand-new user-space AX.25 implementation, it is worth looking first at projects that already do some or all of the following:		One strong theme in this transition is that many of the building blocks people need already exist in open source. Before starting a brand-new user-space AX.25 implementation, it is worth looking first at projects that already do some or all of the following:
Line 236:		Line 236:
	\| [https://www.langelaar.net/projects/jnos2/ project page]		\| [https://www.langelaar.net/projects/jnos2/ project page]
	\| Packet-radio networking environment and applications		\| Packet-radio networking environment and applications
	\| ~~Worth inspecting~~ for ~~people whose main interest is preserving~~ classic packet ~~workflows~~		\| Implements almost everything needed for a classic packet-radio setup in user space, and can be used as a reference for how to structure a complete user-space stack
	\|}		\|}

KI5QKX: mw push

2026-04-30T22:32:05Z

mw push

← Older revision		Revision as of 22:32, 30 April 2026
Line 30:		Line 30:
	* You already use a user-space TNC like Dire Wolf (without <code>kissattach</code>)		* You already use a user-space TNC like Dire Wolf (without <code>kissattach</code>)
	* The app you use has its own AX.25 built in (common with APRS software)		* The app you use has its own AX.25 built in (common with APRS software)
	* ~~You're~~ using applications that can talk to KISS or AGWPE directly, to either a software or hardware TNC		* You’re using applications that can talk to KISS or AGWPE directly, to either a software or hardware TNC

	== Kernel vs. user space ==		== Kernel vs. user space ==
Line 48:		Line 48:
	If you are learning, you face the challenge that much of the documentation currently available still refers to the old kernel-based model. This means a lot of the first search results you see may be outdated or not directly applicable to your situation. That documentation might still be useful for understanding the basics of AX.25, but it is unlikely to be a good guide for how to set up a new station today.		If you are learning, you face the challenge that much of the documentation currently available still refers to the old kernel-based model. This means a lot of the first search results you see may be outdated or not directly applicable to your situation. That documentation might still be useful for understanding the basics of AX.25, but it is unlikely to be a good guide for how to set up a new station today.

	== If ~~you're~~ more established ==		== If you’re more established ==

	If you are already running packet radio on Linux, the first question is what you want continued operation of your station to look like.		If you are already running packet radio on Linux, the first question is what you want continued operation of your station to look like.
Line 56:		Line 56:
	=== Freeze (keep it running as is) ===		=== Freeze (keep it running as is) ===

	If ~~you're~~ using software that depends on kernel AX.25, future kernel updates will break it. If you want to keep that software working, the simplest path may be to stay on the version of Linux you have now.		If you’re using software that depends on kernel AX.25, future kernel updates will break it. If you want to keep that software working, the simplest path may be to stay on the version of Linux you have now.

	You can keep using that system for as long as you like, but you will find ample advice to consider the security implications. Older kernels do not receive fixes for newly discovered vulnerabilities, and the longer a system stays pinned to an old kernel, the more exposed it can become. If you choose this path, it is worth taking extra precautions to secure the system.		You can keep using that system for as long as you like, but you will find ample advice to consider the security implications. Older kernels do not receive fixes for newly discovered vulnerabilities, and the longer a system stays pinned to an old kernel, the more exposed it can become. If you choose this path, it is worth taking extra precautions to secure the system.
Line 62:		Line 62:
	=== Reconfigure ===		=== Reconfigure ===

	If ~~you're~~ using software released relatively recently, you may be able to reconfigure it. For example, an APRS application that can use AGWPE or KISS over TCP may only need to be pointed at Dire Wolf or a hardware TNC via a different protocol.		If you’re using software released relatively recently, you may be able to reconfigure it. For example, an APRS application that can use AGWPE or KISS over TCP may only need to be pointed at Dire Wolf or a hardware TNC via a different protocol.

	=== Replace ===		=== Replace ===
Line 70:		Line 70:
	=== Revive ===		=== Revive ===

	If you have the technical interest and motivation, ~~there's~~ nothing to stop you reviving the kernel code in the out-of-tree repository.		If you have the technical interest and motivation, there’s nothing to stop you reviving the kernel code in the out-of-tree repository.

	The long absence of maintainers for the code that was just removed might be an indication of the challenges of this path.		The long absence of maintainers for the code that was just removed might be an indication of the challenges of this path.
Line 95:		Line 95:
	\| Yes		\| Yes
	\| Reconfigure		\| Reconfigure
	\| Set up Dire ~~Wolf's~~ KISS or AGWPE interface and point your applications at it		\| Set up Dire Wolf’s KISS or AGWPE interface and point your applications at it
	\|-		\|-
	\| [https://github.com/la5nta/pat Pat]		\| [https://github.com/la5nta/pat Pat]
Line 128:		Line 128:
	\|-		\|-
	\| [https://www.cantab.net/users/john.wiseman/Documents/QtSoundModem.html QtSoundModem]		\| [https://www.cantab.net/users/john.wiseman/Documents/QtSoundModem.html QtSoundModem]
	\| User-space modem/TNC; KISS and AGWPE~~-style~~ host-side interfaces		\| User-space modem/TNC; KISS and AGWPE host-side interfaces
	\| Yes		\| Yes
	\| Reconfigure		\| Reconfigure
Line 134:		Line 134:
	\|-		\|-
	\| [http://uz7.ho.ua/packetradio.htm SoundModem]		\| [http://uz7.ho.ua/packetradio.htm SoundModem]
	\| User-space modem/TNC; KISS and AGWPE~~-style~~ host-side interfaces		\| User-space modem/TNC; KISS and AGWPE host-side interfaces
	\| Yes		\| Yes
	\| Reconfigure		\| Reconfigure
Line 220:		Line 220:
	\| QtSoundModem		\| QtSoundModem
	\| [https://www.cantab.net/users/john.wiseman/Documents/QtSoundModem.html project page]		\| [https://www.cantab.net/users/john.wiseman/Documents/QtSoundModem.html project page]
	\| User-space modem/TNC with KISS and AGWPE~~-style~~ interfaces		\| User-space modem/TNC with KISS and AGWPE interfaces
	\| Another active example of the “software TNC in user space” approach		\| Another active example of the “software TNC in user space” approach
	\|-		\|-