Tunnel to the rack through Nexus - #66
Draft
plotnick wants to merge 3 commits into
Draft
Conversation
Given --nexus, the client carries its connections over authenticated websockets to Nexus's support-shell endpoint, which pipes them to a sush proxy. The platform TLS and signed requests inside cross Nexus untouched, so the tech port and the tunnel carry identical traffic. Co-Authored-By: Claude Mythos 5 <noreply@anthropic.com>
Like curl --resolve: --nexus-resolve supplies the socket address while the URL's host still names the server for TLS, standing in for rack DNS that is not yet populated. Co-Authored-By: Claude Mythos 5 <noreply@anthropic.com>
Creation already shows the session; the start's echo of the same line was noise. The explicit three-step start still announces. Co-Authored-By: Claude Mythos 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.
Given
--nexus, the client carries its connections over authenticated WebSockets to Nexus's support-shell endpoint, which pipes them to a sush proxy. The platform TLS and signed requests inside cross Nexus untouched, so the tech port and the tunnel carry identical traffic.Requires oxidecomputer/omicron#11199.