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

Issue 825641 link

Starred by 12 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature

Blocking:
issue 825671



Sign in to add a comment

Revisit "Prefer this network" UI

Project Member Reported by cernekee@chromium.org, Mar 25 2018

Issue description

Past discussions:  bug 452985 ,  bug 439173 ,  bug 446621 

shill has two per-service prioritization properties: Priority and PriorityWithinTechnology.  Currently it sets Priority to 1 if "Prefer this network" is checked, and 0 otherwise[0].  This means that if a user checks "Prefer this network" for (say) his home wifi, the home wifi service will have a higher sort order than ethernet and VPNs.  This often comes as a surprise to the user.

Chrome does not currently translate or use the PriorityWithinTechnology property.

Based on reading old bugs, I think this is the behavior we want:

 - Checking "Prefer this network" on a wifi service will set PriorityWithinTechnology=10, to rank this wifi SSID above other known wifi SSIDs.  It should not cause the wifi service to be preferred above ethernet or VPN services.

 - Checking "Always prefer cellular" on a cellular service will set Priority=10, to rank this cell service above all wifi and ethernet services.

 - VPN services should have Priority=50, because we always want them on the top of the stack.  If a VPN gets pushed down into second place, it won't encrypt any traffic.

 - Existing configurations should be upgraded in-place to reflect the new behavior.

(Exact priority numbers subject to change.)

WDYT?


[0] https://cs.chromium.org/chromium/src/chrome/browser/resources/settings/internet_page/internet_detail_page.js?rcl=474b839d898bfe57343d755b0e3af8fd5b246f36&l=278

 
#CBC-RS/TC-watchlist
Issue 825158 has been merged into this issue.
Blocking: 825671
Cc: steve...@chromium.org zalcorn@chromium.org
Owner: ----
Untriaged issues shouldn't be owned. I would like to have this discussion however. We need someone to drive it though.

tbuckley@, zalcorn@, who has bandwidth to get up to speed on some of these trickier network UI issues, now that we have some more bandwidth and flexibility in the UI?

Owner: dwmclary@chromium.org
I'll take it.  tbuckley@, zalcorn@ I'll be reaching out to you to get the right UI pieces in place.
Labels: Hotlist-ConOps-CrOS
(Bulk Edit) Adding the new conops Chrome OS hotlist to all open issues with the "#CBC-RS/TC-watchlist" tag, our former tracking tag.
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
This bug has affected me for months, with my VPNs being ignored.  So glad I finally found the cause.  See some of my other notes in this case: https://bugs.chromium.org/p/chromium/issues/detail?id=866179  comments 15 and 16.
Cc: -cernekee@chromium.org -dwmclary@chromium.org iferouz@chromium.org
Owner: ----
Status: Available (was: Assigned)
Labels: Enterprise-Triaged

Sign in to add a comment