docs: BPQ APPLICATION line needs the DAPPS callsign in APPLCALL - #147
Merged
Conversation
The docs rewrite in d174cbe dropped the APPLCALL field from the documented APPLICATION line (APPLICATION 1,DAPPS,,,,, 0). Verified in a two-node linbpq lab: with that shape, BPQ ignores inbound L2 connects to the AGW-registered DAPPS callsign entirely (callers see RETRYOUT) - the runtime 'X' registration tells BPQ which AGW client gets the session, but only the APPLCALL declaration makes BPQ accept the connect at all. Restoring the full form fixes node-to-node probes both ways. Also documents two failure signatures hit while reproducing a field report (Kevin M0AHN): UA-then-silence when a neighbour row points at the remote NODECALL instead of its DAPPS callsign, and the need for an AXIP/AXUDP MAP entry covering the remote DAPPS callsign. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The docs rewrite in d174cbe dropped the APPLCALL field from the documented BPQ APPLICATION line, leaving
APPLICATION 1,DAPPS,,,,, 0. That shape does not work: BPQ ignores inbound L2 connects to the AGW-registered DAPPS callsign entirely (remote callers see RETRYOUT). The runtime AGW 'X' registration only tells BPQ which AGW client gets the session; the APPLCALL declaration is what makes BPQ accept the connect at all. (XRouter has the opposite rule - X-frame alone works, APPL block must be absent - which is probably how the field got dropped.)Verified in a two-node linbpq lab replicating Kevin M0AHN's field report (two BPQ nodes over AXUDP, DAPPS on each via AGW):
APPLICATION 1,DAPPS,,,,, 0(current docs)*** DISCONNECTED RETRYOUTboth directionsAPPLICATION 1,DAPPS,,<dappscall>,DAPPS,0timeout: no data from peer within 180sChanges
getting-started.md,connect/bpq.md: restore the APPLCALL field in the documented line and explain the APPLCALL-vs-AGW-registration division of labour.connect/bpq.md: new AXIP/AXUDP section - MAP entries must cover the remote DAPPS callsign, not just the remote node call.troubleshooting.md: RETRYOUT cause list gains the missing-APPLCALL case; new bullet for the UA-then-silence signature (neighbour row pointing at a NODECALL).🤖 Generated with Claude Code