containers reach network-online only with a dhcp lease, and bao users wait for it
This commit is contained in:
parent
04f8683f99
commit
81a57a9f81
1 changed files with 77 additions and 3 deletions
|
|
@ -25,7 +25,14 @@
|
|||
config = {
|
||||
networking.useDHCP = true;
|
||||
networking.resolvconf.enable = false;
|
||||
networking.dhcpcd.extraConfig = "nohook resolv.conf";
|
||||
# `noipv4ll` and `wait = "ipv4"`: dhcpcd counts an IPv4LL address as an
|
||||
# address, so by default `network-online.target` is reached on 169.254.x
|
||||
# before the lease arrives. With both set it waits for the lease.
|
||||
networking.dhcpcd.extraConfig = ''
|
||||
nohook resolv.conf
|
||||
noipv4ll
|
||||
'';
|
||||
networking.dhcpcd.wait = "ipv4";
|
||||
|
||||
# A unicast DHCP renewal reply otherwise reaches dhcpcd only by
|
||||
# matching the firewall's ESTABLISHED,RELATED conntrack rule against
|
||||
|
|
|
|||
Loading…
Reference in a new issue