Repository navigation
LAN pairing: client key, setup pairs over USB, lan-clients - #83
Merged
Merged
Conversation
…lients - tcpclient: one TLS client identity per user (client.key/client.crt next to known_pods.json, made on first use; BENCHPOD_CLIENT_KEY_PEM or BENCHPOD_CLIENT_CERT/_KEY for CI), presented on every 8443 connection. - setup: pairs this computer in step 1 over the USB console (works with the USB network off) and pins the pod's LAN certificate from USB; a pod only on the network is paired through embeddedci.com when it is on your account, else setup says to plug in USB-C once. - lan-clients [add [--new-key --name] | remove | clear], lan-pairing. - discover: "paired" / "this computer is not paired". - BP0081 lan_not_paired is Locked; catalogs synced from the firmware. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
setup filtered the USB pods by device path only, so usb:<name> with two pods plugged in stopped with "found 2 BenchPods". The probe now keeps each pod's identity short id and setup matches it (benchpod-<id> too); an unknown name lists the pods it found. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
wardviaene
force-pushed
the
lan-pairing
branch
from
November 20, 2026 22:00
e2735ea to
7f9d5f6
Compare
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.
For firmware 4.0.1 LAN pairing (embeddedci-com/benchpod-firmware#209).
client.key/client.crtnext toknown_pods.json, made on first use, shared with the SDK.BENCHPOD_CLIENT_KEY_PEMorBENCHPOD_CLIENT_CERT/_KEYfor CI. Presented on every 8443 connection.setuppairs this computer in step 1 over the USB console (works with the USB network off) and pins the pod's LAN certificate from USB. A pod only on the network is paired through embeddedci.com when it is on your account; otherwise setup says to plug in USB-C once.lan-clients [add [--new-key --name] | remove | clear],lan-pairing [on|off].discovershows paired / not paired.lan_not_pairedis a Locked refusal. Catalog and feature map synced.setup --connection usb:<name>now picks that pod when several are on USB (it filtered by device path only).Tested on benchpod-30a9f1 with the dev firmware: setup from a fresh config pairs in step 1 and then works over LAN TLS; lan-clients over the console, the USB link and the cloud; a change from the LAN is refused (BP0041). The usb: fix checked with two pods on USB.
go test ./...passes.🤖 Generated with Claude Code