Repository navigation
lan-clients add over a LAN address pairs through the pod's USB link - #84
Merged
Merged
Conversation
An unpaired computer still gets status over the LAN, and status carries the pod's own USB network address (usb.ip). lan-clients (add, remove, clear, and a list an unpaired computer may not read) and setup now pair through that address when it answers from here, so the right pod is paired even with several on USB. The pod on the USB link must present the LAN certificate pinned for the LAN address. Without the link, the error says to plug the pod in over USB-C or use --connection embeddedci:<pod> (BP0081); a paired computer is told it is paired. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 21, 2026
Merged
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
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.
Found testing BenchPod Desktop 0.2.2's "Pair this computer" with two pods on USB: the app was on the LAN (192.168.1.164) and ran
--connection usb lan-clients add, which asked which pod.lan-clientswith a LAN connection (IP, pod name or.localname) readsstatusthere. Whenusb.linkis true andusb.ipanswers from this computer, changes (and a list an unpaired computer may not read) go over that USB link. The pod there must present the LAN certificate pinned for the LAN address, else it refuses. After pairing, the LAN certificate is pinned from the USB link when there was no pin.addfrom a computer that is paired already, without the link: "This computer (name) is already paired with the pod at X."setupfor a pod found only on the network tries the USB link before embeddedci.com.benchpod-xxxxxxandbenchpod-xxxxxx.localalready resolve the same (mDNS, else USB); no change needed.Tests: fake LAN pod + fake USB-link pod (pairs over the link, no link, paired already, paired list stays on LAN, another pod's link refused, setup).
🤖 Generated with Claude Code