X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd-networkd.service.xml;h=9c7ca83438d83c7ab197e38fb65ec0c74f320699;hb=6bebb0add4d7c32c503e688105c1607e5e20f979;hp=908354c5875463c4fe39712ff1c30e4ffc99b6b1;hpb=e0e009c067aa7237f9683c46e5845bbb11ec67c2;p=elogind.git diff --git a/man/systemd-networkd.service.xml b/man/systemd-networkd.service.xml index 908354c58..9c7ca8343 100644 --- a/man/systemd-networkd.service.xml +++ b/man/systemd-networkd.service.xml @@ -61,11 +61,16 @@ network devices as they appear, as well as creating virtual network devices. + To configure low-level link settings independently of + networks, see + udev7 + . + Network configurations applied before networkd is started - are not removed, and configuration applied by networkd are not - removed when networkd exits. This ensures restarting networkd - does not cut the network connection, and, in particular, that - it is safe to transition between the initrd and the real root, + are not removed, and static configuration applied by networkd + are not removed when networkd exits. This ensures restarting + networkd does not cut the network connection, and, in particular, + that it is safe to transition between the initrd and the real root, and back. @@ -87,11 +92,11 @@ disables the configuration file entirely. Virtual Network Devices - Netdev files must have the extension .netdev; - other extensions are ignored. Virtual network devices are created as soon - as networkd is started. + Virtual Network Device files must have the extension + .netdev; other extensions are ignored. Virtual + network devices are created as soon as networkd is started. - The [Bridge] section accepts the following + The [NetDev] section accepts the following keys: @@ -102,7 +107,29 @@ bridge. This option is compulsory. + + Kind + + The netdev kind. Currently, bridge, + bond and vlan + are supported. This option is compulsory. + + + + The [VLAN] section only applies for netdevs of kind vlan, + and accepts the following key: + + + + Id + + The VLAN ID to use. An integer in the range 0–4094. + This option is compulsory. + + + + Networks @@ -168,11 +195,17 @@ presentation purposes. + + DHCP + + A boolean. When true, enables basic DHCPv4 support. + + Address A static IPv4 or IPv6 address and its prefix length, - separated by a '/' character. The format of the address must + separated by a / character. The format of the address must be as described in inet_pton3 . This is a short-hand for an [Address] section only containing an Address key (see below). @@ -186,10 +219,31 @@ . This is a short-hand for a [Route] section only containing a Gateway key. + + DNS + + A DNS server address, which must be in the format described in + inet_pton3 + . + + Bridge - The name of the bridge to add the configured link to. + The name of the bridge to add the link to. + + + + Bond + + The name of the bond to add the link to. + + + + VLAN + + The name of a VLAN to create on the link. This option + may be specified more than once. @@ -200,7 +254,16 @@ Address - As in the [Network] section. + As in the [Network] section. This key is mandatory. + + + + Broadcast + + The broadcast address, which must be in the format described in + inet_pton3 + . This key only applies to IPv4 addresses. If it is not given, it is + derived from the Address key. @@ -217,7 +280,7 @@ Gateway - As in the [Network] section. + As in the [Network] section. This key is mandatory. @@ -227,7 +290,42 @@ prefixlength, if ommitted a full-length host route is assumed. + + + The [DHCPv4] section accepts the following keys: + + + + UseDNS + + When true (the default), the DNS servers received from the DHCP server will + be used and take precedence over any statically configured ones. + + + + UseMTU + + When true, the interface maximum transmission unit from the DHCP server will + be used on the current link. Defaults to false. + + + + UseHostname + + When true (the default), the hostname received from the DHCP server + will be used as the transient hostname. + + + + CriticalConnection + + When true, the connection will never be torn down even if the DHCP lease + expires. This is contrary to the DHCP specification, but may be the best choice + if, say, the root filesystem relies on this connection. Defaults to false. + + +