C01-AX: Yes
Rationale
A NET/ROM node hosting the destination can retain its callsign/SSID when its previous crosslink attachment is replaced by a reachable configured neighbor. NODES advertisements and route aging update routes keyed by that same destination callsign. Linux NET/ROM looks up the destination node separately from the selected next-hop neighbor and AX.25 interface, so routing can deliver to the replacement attachment without changing the address used by the sender.
Assessment method
Primary documentation and pinned source review; no runtime experiment
Source context
Meshtastic directed/flooded forwarding and NET/ROM destination/neighbor route separation
Outstanding qualification
The witness is the same NET/ROM node and local endpoint, not an AX.25-only terminal changing gateways. It uses the selected Linux NET/ROM and netromd composition with administrator-configured ports, permitted neighbors, announcements and appropriate route quality/aging. Old routes must expire, fail over or be updated and a viable path must converge within hop limits. A fresh transport circuit is allowed; no uninterrupted circuit or bounded recovery-time guarantee. Callsigns are not cryptographically authenticated and no public-radio licensing permission is inferred. No IP tunnel or additional mobility protocol. No runtime experiment.
Public sources
- https://raw.githubusercontent.com/torvalds/linux/v6.12/net/netrom/nr_route.c
- https://manpages.debian.org/testing/ax25-tools/netromd.8.en.html
- https://deb.debian.org/debian/pool/main/a/ax25-tools/ax25-tools_0.0.10-rc5+git20230513+d3e6d4f.orig.tar.gz
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round531.html
- round531-sources.json