F28-AX: No
Rationale
The selected application uses Linux 6.12 NET/ROM circuits. Its connect operation selects the destination callsign; NET/ROM forwarding chooses a neighbor from routing state. AX.25 digipeater sequences can be attached to configured neighbor routes, but this does not give the NET/ROM endpoint an interface to select downstream intermediaries for its communication.
Assessment method
Primary specification and pinned code review; no runtime experiment
Source context
Linux v6.12 NET/ROM connection and route configuration
Outstanding qualification
This verdict does not deny AX.25 source routing through digipeaters. It distinguishes the selected NET/ROM socket service from raw AX.25 operation and administrative route provisioning. Linux exposes the route modification path under CAP_NET_ADMIN; nr_route_frame uses the selected neighbor and its configured digipeater path. A separate raw AX.25 endpoint or application-controlled route mechanism would require an explicit composition change. No runtime path test was performed.
Public sources
- https://raw.githubusercontent.com/torvalds/linux/v6.12/net/netrom/af_netrom.c
- https://raw.githubusercontent.com/torvalds/linux/v6.12/net/netrom/nr_route.c
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round517.html
- round517-sources.json