New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 636402 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Dec 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Chrome OS Firewall Configuration Needed For Every Boot for ADB Access

Reported by mmur...@commonsware.com, Aug 10 2016

Issue description

Version: 53.0.2785.47 dev (64-bit)
Platform: 8530.43.0 (Official Build) dev-channel cyan

Steps to reproduce:
(1) Follow the instructions on http://www.chromium.org/chromium-os/android-apps listed as "Configure Firewall" in "Setup ADB"

(2) Confirm that you have adb access

(3) Power down the Chromebook and power it back on

(4) Attempt to acquire adb access again using adb connect

Expected result: adb access


Actual result: no adb access until you follow all the "Configure Firewall" steps again

Thanks!

 
Cc: arthurhsu@chromium.org
Owner: yusukes@chromium.org
Status: Assigned (was: Untriaged)
hmm, the documentation clearly says it should only need to be done once :)

Arthur (doc author) is out for a bit, Yusuke do you have any ideas why this does not persist reboots? Is the documentation wrong or did the behavior change?
Status: Started (was: Assigned)
Checked https://chromium.googlesource.com/chromiumos/platform2/+/master/debugd/src/helpers/dev_features_ssh.cc. I think the documentation is wrong. The main thing the command does is to start sshd with 'initctl start openssh-server', and it has to be done on every boot.

Who should I ask to fix the doc? I don't seem to have a write permission for the page.

https://developer.android.com/topic/arc/index.html has the same issue.

Yusuke, I'll connect you with the right person offline. 
This is tracked at b/30905055 internally.


Status: Fixed (was: Started)
https://developer.android.com/topic/arc/index.html looks good (finally........)
Closing.

Comment 7 by dchan@google.com, Mar 4 2017

Labels: VerifyIn-58
Status: Verified (was: Fixed)

Sign in to add a comment