New issue
Advanced search Search tips

Issue 903444 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocked on:
issue 848063



Sign in to add a comment

Crostini seems to block port 8888

Project Member Reported by jonyepsilon@google.com, Nov 8

Issue description

Chrome version: 70.0.3538.76 (Official Build) (64-bit)
OS: Chrome

Repro steps:
1. Reboot chromebook
2. Start "Terminal"
3. Initiate an ssh connection to a remote machine (from crosh, not from within crostini VM) that tunnels port 8888 (-L 8888:localhost:8888).

Expected: the SSH connection should connect.
Actual: the SSH connection stalls. Connecting with -v shows that it is stalled trying to establish the port tunnel.

This is potentially troublesome because Colab kernels default to port 8888.
 
Blockedon: 848063
Components: OS>Systems>Containers
Owner: smbar...@chromium.org
Status: Assigned (was: Untriaged)
This is probably an artifact of the SSH port forwarding done by Crostini.

We're looking at a solution that wouldn't steal these ports from Chrome OS: issue 848063.
@smbarber that makes sense, if there isn't a quick fix for this feel free to WontFix since we should focus on Issue 848063
Would a possible quick "fix" be to move any ports used by Crositini's internals away from the 8000/8080/8888 range that is very widely used by (and thus forwarded for) other things? Doesn't fix the problem, but might result in fewer surprises for the typical user.

Sign in to add a comment