Skip to content

LAN-only-over-USB changes go over the pod's USB link; LAN address shown as used - #85

Merged
wardviaene merged 1 commit into
mainfrom
lan-writes-via-usb
Nov 21, 2026
Merged

wardviaene merged 1 commit into
mainfrom
lan-writes-via-usb

Conversation

@wardviaene

Copy link
Copy Markdown
Member

Found testing v0.10.2 against firmware 4.0.1 with LAN pairing on.

  • lan-pairing, lan-tls changes (https-only, scpi, regenerate, set-cert) and cloud ca/cloud proxy changes given a LAN address go over the pod's own USB link when its USB-C cable is in this computer, reusing lan-clients add over a LAN address pairs through the pod's USB link #84's helpers. An unpaired computer reads them over the link too.
  • BP0081 from a pod plugged into this computer: the hint says to pair now with benchpod lan-clients add --connection <host> instead of to plug it in.
  • Messages show the address actually used (192.168.1.164:8443, over TLS in status) or the host alone, not the plaintext 8080: status, setup, discover, and every command's pod label.

Tests: fake pods from #84 (LAN + USB link), no hardware.

🤖 Generated with Claude Code

…wn as used

lan-pairing, lan-tls changes (https-only, scpi, regenerate, set-cert) and
cloud ca/proxy changes given a LAN address now go over the pod's own USB link
when its USB-C cable is in this computer, as lan-clients does since #84 (same
helpers: readLanPodState, reachUSBLink). A computer that is not paired reads
lan-pairing, lan-tls and cloud ca/proxy over the link too.

A BP0081 refusal from a pod plugged into this computer now says to pair it
now with `benchpod lan-clients add`, instead of to plug it in.

Messages name a LAN pod by the address the connection used (host:8443 over
TLS), or by the host alone before one: status, setup, discover and every
command's label no longer show the plaintext 8080.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@wardviaene
wardviaene merged commit daedf7b into main Nov 21, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant