Ability to assign static ip's to chrome devices from the admin console
Reported by
dwar...@natickps.org,
Sep 5 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36 Platform: Google_Rikku.6301.110.4 Steps to reproduce the problem: 1. Login to the G Suite Admin Console. 2. Go to Device Management > Chrome devices > <Device> 3. There is no way to assign a static ip to the device. What is the expected behavior? What went wrong? I would like the ability to assign a static ip to a device added to the G Suite admin console. Did this work before? N/A Chrome version: 62.0.3198.0 Channel: stable OS Version: 62.0.3198.0 Flash Version: Shockwave Flash 26.0 r0
,
Sep 12 2017
,
Mar 21 2018
For those requesting this feature: It would be great if you could add details on why static IP-MAC mapping by DHCP (which I assume is adopted by many enterprise/education environments) is not a feasible solution. This information helps us understand the importance of this feature.
,
Mar 21 2018
This feature is similar to my bug report (https://bugs.chromium.org/p/chromium/issues/detail?id=820213) and I was directed to this Issue by Google Support. I don't necessarily need the feature at the admin console but it would be nice. To answer your question about static mapping by DHCP reservation, our issue with this is that the application server we are using the Chromeboxes for is the DHCP server and Default Gateway. It is an all-in-one portable server. However, there are no configurable settings in it. We set the static IPs primarily to specify a different default gateway so that the systems can reach the Internet. Our issue is that ChromeOS updates lose the static IP and revert back to DHCP.
,
Aug 23
,
Sep 18
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by emaxx@chromium.org
, Sep 11 2017Owner: dskaram@chromium.org
Status: Assigned (was: Unconfirmed)