shill: allow for device in developer mode to operate without a dhcp server-given IP |
||
Issue descriptionUse-case is to have a chromebook (or a barebones board version of it) to connect to a linux host, get a static IP and stay put there. That doesn't happen today because shill does both of the following: (a) keeps trying to get a DHCP server given IP (b) keeps trying portal checks and eventually disconnects when they fail like they are supposed to here. I am not sure what the right solution is, but one hacky way around it is to provide dbus commands that tell shill to disable both (a) and (b). These dbus commands should be prevented from being used in prod though - how do we do that?
,
Jan 15 2018
To disable portal checks I have used: dbus-send --system --dest=org.chromium.flimflam --print-reply / org.chromium.flimflam.Manager.SetProperty string:CheckPortalList string:"" i.e. "don't do portal checks for any technology (wifi, ethernet, etc.)" If you specify a static IP + DNS server in the UI, is shill happy with that?
,
Jan 15 2018
I see there is a /usr/local/lib/flimflam/test/set-address script, but that just overwrites the current IP. Maybe we could write a better version that sets the static IP configuration and CheckPortal properties on a given service (perhaps identified by its SSID). I don't see an easy way to tell shill not to send DHCP requests at all. Even the static IP configuration seems to happen through Device::AcquireIPConfigWithLeaseName(). Maybe when we refactor the static IP logic, we should add a property to disable this behavior.
,
Jan 15 2018
Prior context also in this bug: https://bugs.chromium.org/p/chromium/issues/detail?id=703906 "Shill is oblivious to static IP, starts DHCP anyways"
,
Jan 15
|
||
►
Sign in to add a comment |
||
Comment 1 by kirtika@google.com
, Jan 15 2018