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

Issue 711504 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

192.168.254.0/24 is unusable on chromebooks with arc++

Project Member Reported by roy...@google.com, Apr 13 2017

Issue description

It looks like arc++ devices creates a bridge network using a specific /24. We have one enterprise customer reporting that this broke their internal network because they had resources on the same subnet.

Can we consider checking for IP collisions and picking a different network address for the bridge network ?
 
Cc: marchuk@google.com

Comment 2 by roy...@google.com, Apr 13 2017

[ Clarification: this didn't break the network, just broke the device which was trying to reach that network ]
Status: Assigned (was: Untriaged)

Comment 4 by roy...@google.com, Apr 14 2017

Cc: atwilson@chromium.org naveenv@chromium.org
Labels: -Pri-2 M-58 Pri-1
Owner: bhthompson@chromium.org
Customer said the issue started in 55.

Owner: abhishekbh@chromium.org
This is a dupe of an internal issue we have been looking at for a long time now.

https://b.corp.google.com/issues/31285667
Project Member

Comment 6 by sheriffbot@chromium.org, Apr 17 2017

Labels: Hotlist-Recharge-BouncingOwner
Owner: ----
Status: Untriaged (was: Assigned)
The assigned owner "abhishekbh@chromium.org" is not able to receive e-mails, please re-triage.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 7 by sheriffbot@chromium.org, Jul 20 2017

Labels: Hotlist-Google

Comment 8 by roy...@google.com, Jul 30 2017

Status: WontFix (was: Untriaged)
b/31285667 is fixed in 59/60. Please reopen if this is still causing issue.

Sign in to add a comment