Public bug reported:
with the backport of the latest netplan to xenial you can now use the
wlan and ethernet interfaces in subiquity on a pi3 (before the
bind/unbind cycle broke wlan and you were forced to use ethernet in the
first boot setup (and re-configure for wlan later)).
now, when doing the first-boot configuration for wlan only and not
touching the ethernet defaults in console-conf at all (and not having
any cable connected) i end up with:
ogra@pi3:~$ sudo cat /etc/netplan/00-snapd-config.yaml
# This is the network config written by 'console_conf'
network:
ethernets:
eth0:
addresses: []
dhcp4: true
version: 2
wifis:
wlan0:
access-points:
XXXXXXXXXXX: {password: XXXXXXXXXX}
addresses: []
dhcp4: true
this setup (with no cable connected) causes a 2min timeout of the
systemd-networkd-wait-online.service during boot... this service blindly
waits for all configured interfaces by default ...
to avoid this you actually have to explicitly disable the dhcp settings
of the ethernet device in console-conf, not touching eth0 and only
setting up wlan0 will leave the ethernet device configured for dhcp,
even though there was never any cable connected...
subiquity should check the link state before bringing up the network
configuration UI and not default to configure eth0 for dhcp if there is
no cable connected ... or alternatively simply not default to having
dhcp enabled on interfaces the user never touched during system
configuration.
** Affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707888
Title:
ethernet defaults for unconnected device are wrong
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1707888/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
