ar: publish which visors can actually be reached, per transport type - #5270
Merged
Merged
Conversation
A binding says a visor listens for a type, not that anyone gets through. The AR now keeps a reach record per peer and publishes it as a small feed (dmsg port 76, reach/<h>): - stcpr/squicr/swtr: the AR probes each bound address itself (TCP connect; one unknown-version QUIC packet, answered by a version negotiation), so no peer has to succeed first. - sudph: whether the visor holds its UDP control connection at the AR, which the simultaneous open needs. - the visor's own "reach" leaf in its AR-bind feed: STUN NAT class, types it serves, when it last accepted an inbound transport of each. Autoconnect picks peers from it: known failures are skipped, confirmed peers go first, untested ones get three dials per phase per cycle. sudph and webrtc pairs are filtered by NAT class. Replaces the HTTP sudph list and the TPD stats/webrtc-visors leaf.
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.
A binding at the AR says a visor listens for a type, not that anyone can get through. Autoconnect now picks peers from a per-type reach record the AR publishes (new feed, dmsg port 76):
Known failures are skipped, confirmed peers are dialed first, untested ones get three dials per phase per cycle. Replaces the AR HTTP sudph list and the TPD
stats/webrtc-visorsleaf.