On Wed, Feb 15, 2017 at 12:16 PM, Mike Pontillo <<email address hidden>
> wrote:
> By the way, to add to (2) above, in order to create a link-down DHCP
> interface which does not block the boot process if DHCP fails, you also
> need another workaround involving a post-up/pre-down script to launch
> the DHCP client and release the address, respectively.
>
That doesn't seem right; either you want/need the interface to dhcp
(mode=auto)
and then of course you block the boot waiting on DHCP and mark that it
failed
Or it's manual, in which case it;s not blocking boot as it won't be
required "up"
to continue.
On Wed, Feb 15, 2017 at 12:16 PM, Mike Pontillo <<email address hidden>
> wrote:
> By the way, to add to (2) above, in order to create a link-down DHCP
> interface which does not block the boot process if DHCP fails, you also
> need another workaround involving a post-up/pre-down script to launch
> the DHCP client and release the address, respectively.
>
That doesn't seem right; either you want/need the interface to dhcp
(mode=auto)
and then of course you block the boot waiting on DHCP and mark that it
failed
Or it's manual, in which case it;s not blocking boot as it won't be
required "up"
to continue.
> /bugs.launchpad .net/bugs/ 1664844 /bugs.launchpad .net/netplan/ +bug/1664844/ +subscriptions
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> No distinction between link-up and link-down interfaces
>
> To manage notifications about this bug go to:
> https:/
>