Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 170 users
Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: 2017-01-10
OS: Chrome
Pri: 2
Type: Feature

Blocking:
issue 676195
issue 220820

Restricted
  • Only users with EditIssue permission may comment.



Sign in to add a comment
Add UI for setting hostname that Chrome OS will request via DHCP
Reported by deepakg@chromium.org, Dec 4 2011 Back to list
Chrome OS Version  :  1011.137
Chrome Version     :  15.0.874.121 (Official Build 109964)
Type of computer   :  x86-device
Network info       :  Wifi

Please specify Area - Network

What new or enhanced feature are you proposing?
Allow user to name the computer. 

What goal would this enhancement help you achieve?
Makes it easier to recognize and connect to a machine over a network.

 
Chrome OS doesn't have any network services listening for incoming connections, so I don't know what the use case here is.
Comment 2 by derat@chromium.org, Dec 4 2011
Status: WontFix
Yeah, this doesn't make sense to me either.
Since its a personal device it would be a good personalization if one can name their device. I was checking all the devices connected to a particular router the other day and had to run through each and every chrome devices mac address to find which one is connected, whereas all the windows and mac machines had their names listed.
Comment 5 by derat@chromium.org, Dec 5 2011
Labels: -Area-DesktopUI Area-Network
Status: Unconfirmed
I think you're asking for dynamic DNS support.  Assigning a hostname to a device that doesn't permit incoming connections still doesn't seem useful to me.
Comment 6 by pstew@chromium.org, Dec 8 2011
Labels: -Pri-2 Pri-3
Status: Available
It's not an ask for dynamic DNS support so much as it is asking for the user to be able to set a unique hostname in their DHCP request.  The DHCP server could choose to set up a DNS entry as a result, or note in some interface the mapping of IP addresses to these names it was given.  I consider this even lower priority than a 2, but would be easy enough to do in shill by (a) creating a Manager DBus interface for setting the device host name, (b) sending this host name in DHCP requests.
Comment 7 by derat@chromium.org, Dec 8 2011
Cc: kanliu@chromium.org
Thanks for the clarification.  Since we'd need to add UI for this too, adding Kan to see whether he thinks it's worthwhile.
Comment 8 by kanliu@chromium.org, Dec 13 2011
Cc: alcor@google.com kuscher@chromium.org glen@chromium.org
Labels: Mstone-X
agree this is pretty low priority and usefulness right now. punting to mx
This would be very useful in environments where there are multiple ChromeOS devices on the network. Any user who sets firewall rules by hostname (or uses hostname to configure MAC filtering) will benefit from having human-comprehensible names.

(I'm not sure if I'm supposed to be writing here since my email address is not from chromium.org... if not, sorry.)


Comment 10 by pstew@chromium.org, Jan 18 2012
Labels: -Area-Network Area-DesktopUI
shill now has a "Hostname" parameter in the Manager, which when set will be passed to DHCP requests.  When shill is the default connection mananger, and the UI plumbs this parameter, this functionality will be available.
Project Member Comment 11 by bugdroid1@chromium.org, Jan 18 2012
Commit: d32f484b91ab583ccc9a14b2a6b5182fda6958f0
 Email: pstew@chromium.org

shill: Pass a parameter to dhcp client to request a hostname

This will enable dynamic DNS, or at the very least allow DHCP
requests to be identified and distinguished at the server side.

BUG=chromium-os:23741
TEST=New unit tests monitor hostname arg passed to dhcpcd,
and to assure values are being loaded/saved.  Also double
checked on real system by doing a dbus-send to set manager.HostName
and checked that the name was persisted, and that the next
DHCP server we connected to stored this hostname.
CQ-DEPEND=Ic807a2235e0cdcb32a08f9c2c760a86c3579431c

Change-Id: Ic127b65d8563b15e55549a0f029385d0632eaf6c
Reviewed-on: https://gerrit.chromium.org/gerrit/14045
Reviewed-by: Paul Stewart <pstew@chromium.org>
Tested-by: Paul Stewart <pstew@chromium.org>
Commit-Ready: Paul Stewart <pstew@chromium.org>

M	cellular_unittest.cc
M	default_profile.cc
M	default_profile.h
M	default_profile_unittest.cc
M	device.cc
M	device_unittest.cc
M	dhcp_config.cc
M	dhcp_config.h
M	dhcp_config_unittest.cc
M	dhcp_provider.cc
M	dhcp_provider.h
M	dhcp_provider_unittest.cc
M	manager.cc
M	manager.h
M	mock_dhcp_config.cc
M	mock_dhcp_config.h
M	mock_dhcp_provider.h
M	wifi_unittest.cc
Project Member Comment 12 by bugdroid1@chromium.org, Jan 18 2012
Commit: 0fca587e4f3f3522093c913fd61ffc8b16a55fb8
 Email: pstew@chromium.org

shill: Add a "HostName" property

This manager property will store a user-defined hostname which will
be used to identify this host.  This hostname will be passed to
DHCP servers which can use this to label requests with this unique
user-specified token and optionally create DNS entries.

BUG=chromium-os:23741
TEST=None

Change-Id: Ic807a2235e0cdcb32a08f9c2c760a86c3579431c

M	dbus/service_constants.h
maybe it makes sense for us to set a default one like "Chromebook" etc. for now to help anyone in the situation where they have a bunch of devices on a network that doesn't report hostname so it's all "Unknown" but again low pri
Comment 14 Deleted
Machine names can also be useful for the open-tab sync feature of recent Chrome,
It shows the list of "other devices" names, in which all Chromebooks are shown as "Chromebook"s.

It'd be good if they are distinguishable, for users who have multiple Chromebooks :).
Comment 16 Deleted
Cc: trond@chromium.org sumit@chromium.org
 Issue 26641  has been merged into this issue.
Comment 18 Deleted
Shall we merge this into  issue chromium:122185 ?
I actually think this bug is probably separate. 122185 relates to the device's name as far as sync is concerned, while this is more of a local system-level capability. Obviously if we added this, sync should inherit the user-set device name, but I don't think it's a dupe.

Note we'll be tracking the ability to change a device's name as it appears in tab sync in chromium:124964
Comment 21 Deleted
Cc: apps-tses-bugs@chromium.org
Issue chromium-os:39533 has been merged into this issue.
Cc: keybuk@chromium.org
Labels: -Pri-3 Pri-2 Feature-Ash-Networking
Owner: kuscher@chromium.org
Status: Assigned
keybuk also just brought up a need for something like this to be used when pairing with bluetooth devices like phones.

Perhaps it's time that some priority be given to this so that we don't wind up with 3 or 4 different names for your chrome device -- one for your network hostname, one for your BT device name and one for your sync session.
Owner: ----
Status: Untriaged
Marking this so it comes up in our next triage
Comment 25 Deleted
Labels: -Cr-UI
Owner: xiaowenx@chromium.org
Status: Assigned
Xiaowen, I believe you are looking into networking stuff?
Comment 27 Deleted
Comment 28 by cubl...@gmail.com, Jun 19 2013
I also have a need for this feature. I am trying to replace PCs on a bank teller line with Chromeboxes that will use RDP to connect to a Windows Terminal Server to run our line of business teller app. The app users the hostname to associate a printer with a machine. If this feature were available, it would greatly ease our configuration issues as this association now has to be done using the IP address of the Chromebox: If I could set host names, I could let the Chromeboxes use DHCP normally and not have to worry about support calls should the address change.
Cc: xiaowenx@chromium.org
Owner: dobri@chromium.org
dobri@ is working on revamping the settings UI.  This would be a good feature to consider with that revamp.  Feel free to assign back to me if that's not part of your scope.
Comment 30 by Deleted ...@, Oct 9 2013
I need this feature as well. We are testing replacing PCs as well and need to RDP to a terminal server on another domain over untrusted networks. Part of the verification required for the RDP security is the client hostname. 
Owner: tbuck...@chromium.org
Tom owns settings UI now.
Summary: Add UI for setting hostname that Chrome OS will request via DHCP (was: UI for users to name their CrOS machine.)
I agree, you should be able to change the hostname not only for Chromebook, but Chromecast as well.

I've been checking my router "attached devices" logs and my Chromebook appears as "></tr>" and my 2 Chromecast dongles vary, with "_Zzz_" and "s" or "t" or "`"

I hope my devices haven't been hacked. 
Now my Samsung Series 3, just switch back to "stable" from "dev"
Version 30.0.1599.116
Platform 4537.147.0 (Official Build) stable-channel daisy
Firmware Google_Snow.2695.117.0

Has this at the Device Name in the router log:

#	IP Address	Device Name	MAC Address
2	192.168.1.18	rip_direction" size="1"> <op�:5�)Oalue=1><%600%></option>	XX:XX:XX:XX:XX:XX  (masked Mac address)
Comment 35 by derat@chromium.org, Nov 12 2013
Labels: Restrict-AddIssueComment-EditIssue
Please star this issue (top-left corner of the page) if you want to follow its progress.
Cc: quiche@chromium.org pstew@chromium.org
 Issue 322968  has been merged into this issue.
Even creating an /etc/hostname file is not enough. There needs to be a script that executes at boot that reads that file and sets the hostname to that, this is what ubuntu does:
% cat ./init/hostname.conf
#
# This task is run on startup to set the system hostname from /etc/hostname,
# falling back to "localhost" if that file is not readable or is empty and
# no hostname has yet been set.

description     "set system hostname"

start on startup

task
exec hostname -b -F /etc/hostname

Cc: vapier@chromium.org
including an upstart job like that will be a waste of time on most (all?) systems, and /etc/hostname is in the rootfs, not stateful, so you can't change it (so it'd have to be a symlink like /etc/resolv.conf).

also, we have a few places that assume "localhost", so changing it to anything else will break.  off the top of my head, X currently requires it via the xauthority logic.

last time we did board bring ups (w/out X), we ran into some random system services failing until it was corrected to localhost in the kernel config.  i don't recall specific details though.

but what uname() returns on the local system is orthogonal to what things (like shill) report to the network.
Comment 39 Deleted
Adding to the MD-Settings hotlist so we can think about it during the redesign. If it makes sense, I'd like to merge this with the ability to set a human-readable name that can be used with Chrome Sync (related to #341356).
Labels: Hotlist-MD-Settings
Labels: M-47
Tom, what was the result from the MD-Settings discussions?
I count 4 use cases that want to "name" the device:
1) "normal" chromebook users (that monitor their routers)
2) network admins to setup firewall rules
3) chromebox for enterprise (bank teller replacement)
4) bluetooth pairing

And I'll add: 
5) Google OnHub: chromebooks are currently "unamed device" and other PCs/Macs advertise some "human readable" name.

Given both OnHub and ChromeBooks are Google products, seems we should do better. 

Until we add some UI to change the name, could the "default" name that is advertised be the primary "owner" of the machine?

e.g. "chromebook-grantgrundler" (@gmail.com) or "chromebook-grundler" (@google.com) depending on which email I use to initially sign in on.
Agree that this feature would be useful.

But regarding default name: I'm not sure that we actually have an "owner" concept in ChromeOS, since CrOS deliberately tries to treat all user accounts the same. Note that even if we knew which user was the owner, we might not know their email address until after they logged in. (I believe that falls out of our privacy/security design.)
Comment 45 by derat@chromium.org, Oct 16 2015
We shouldn't automatically publish the device owner's username.
yeah, 100% agree that we should not be broadcasting PII
Yeah, I thought the same thing after I posted it. /o\  It's ok for people to set that up but a terrible idea as the default.

But maybe the "hwid"?
See bios_info under chrome://system.

hwid identifies the production run for that set of machines. This is NOT a unique identifier for any machine.  I'll remind the machine is required to advertise it's MAC address to use DHCP which is a unique identifier.

Unique identifier != PII. :-)
How about defaulting to the HWID? That's better than "unnamed device".

i'm aware of the WiFi MAC.  doesn't mean it's a good idea ;).

including the board name should be fine, so something like "$DEVICETYPE-$CHROMEOS_RELEASE_BOARD" (fields taken from /etc/lsb-release), rather than the HWID which might have undesirable characters.
Cc: alexking@chromium.org
I don't think that the HWID is helpful to users who are not super familiar with ChromeOS hardware. It would be great if the name described the machine in terms that users can easily recognize like

OEM-DeviceType

Although, not sure if OEM is something we could populate
we do not (currently) include the OEM details.  it is something we could add, but if something like "chromebook-wolf" is good enough, then that's something we could easily pull off today.
chromebook-wolf would definitely be a big improvement :)
Might also be worth thinking about including some sort of (random) number at the end to cover the case of  multiple Chromebooks of the same model on a local network. 
Labels: Cr-Enterprise
Cc: krishna...@chromium.org
Comment 56 by pstew@chromium.org, Dec 16 2015
Cc: saswat@chromium.org dskaram@chromium.org
 Issue 570289  has been merged into this issue.
Labels: Hotlist-Enterprise Hotlist-Enterprise-Support
Labels: -M-47 M-54
Cc: -keybuk@chromium.org
Cc: aashutoshk@chromium.org tienchang@chromium.org
Cc: -saswat@chromium.org
NextAction: 2017-01-10
@tbuckley, could you please review this bug and update the owner and Milestone appropriately. 
Moving this to M57 for now.
Labels: -M-54 M-57
Labels: -M-57 M-58
If we implement this it will be part of MD Settings, and should be done after the initial release, so M-58 at best.

FWIW: Enterprise has meanwhile grown an "asset identifier", which could arguably make for a good hostname? It's an identifier that's available also via extension API as well as server APIs, so is very useful to match up a device with device records in other systems.
Comment 66 by derat@chromium.org, Dec 21 2016
Rereading the history here, the original request (and most of the discussion) has been about letting the user assign their own hostname. The asset ID you're referring to is the one described at https://support.google.com/chrome/a/answer/1698333?hl=en, right? It sounds from the docs like we already expose some UI to let the user set this during enrollment. Is the ID tied to enterprise, or would it be possible to make it available in non-enterprise environments?
Asset ID is currently tied to enterprise. It may be possible to make it work in non-enterprise environments too, but I doubt the UX would be ideal for that case (i.e. a chrome://settings text field seems more appropriate for consumer devices?).
Blocking: 676195
Components: UI>Settings
Labels: -Hotlist-MD-Settings Hotlist-MD-Settings-People
Making sure this shows up in the MD Settings bug list.
Labels: -M-58 M-59
Is this feature still targeting M-59?
Labels: -M-59
Status: Untriaged
I haven't heard anything about it lately, so given that we've branched already, I suspect it isn't.
Status: Assigned
Now that MD Settings has launched we'll look into this.
Thanks Tom. a couple of questions:

1. Will this value apply to all networks connecting on this device or only networks connecting through a user session? I ask because we have both user- and device-wide networks and whatever we build here should work for both.

2. When you add the wiring for the value, would appreciate if you can also add a policy so that admins can set this remotely. This has been an ask for some time from admins.

Labels: Proj-MaterialDesign-WebUI
Hi, We also have a customer requesting this feature. Customer wants to add Hostname/DNS name to Chromebooks. Details are below: 

Use case:
They need to identify Chromebooks by DNS name as this is used by their web filter to identify traffic. Currently Chromebook traffic is only logged against the user, not the device.

Motivation:
They need to know what exact device a user is using to browse the internet in order to pinpoint the user’s whereabouts for safeguarding/e-safety/child protection purposes.

Existing workarounds: There are no known workarounds.
Sign in to add a comment