pub struct DhcpOverrides {
pub use_dns: Option<bool>,
pub use_ntp: Option<bool>,
pub send_hostname: Option<bool>,
pub use_hostname: Option<bool>,
pub use_mtu: Option<bool>,
pub hostname: Option<String>,
pub use_routes: Option<bool>,
pub route_metric: Option<u16>,
pub use_domains: Option<String>,
}Expand description
Several DHCP behavior overrides are available. Most currently only have any effect when using the networkd backend, with the exception of use-routes and route-metric.
Overrides only have an effect if the corresponding dhcp4 or dhcp6 is set to true.
If both dhcp4 and dhcp6 are true, the networkd backend requires that dhcp4-overrides and dhcp6-overrides contain the same keys and values. If the values do not match, an error will be shown and the network configuration will not be applied.
When using the NetworkManager backend, different values may be specified for dhcp4-overrides and dhcp6-overrides, and will be applied to the DHCP client processes as specified in the netplan YAML.
Fields§
§use_dns: Option<bool>Default: true. When true, the DNS servers received from the DHCP server will be used and take precedence over any statically configured ones. Currently only has an effect on the networkd backend.
use_ntp: Option<bool>Default: true. When true, the NTP servers received from the DHCP server will be used by systemd-timesyncd and take precedence over any statically configured ones. Currently only has an effect on the networkd backend.
send_hostname: Option<bool>Default: true. When true, the machine’s hostname will be sent to the DHCP server. Currently only has an effect on the networkd backend.
use_hostname: Option<bool>Default: true. When true, the hostname received from the DHCP server will be set as the transient hostname of the system. Currently only has an effect on the networkd backend.
use_mtu: Option<bool>Default: true. When true, the MTU received from the DHCP server will be set as the MTU of the network interface. When false, the MTU advertised by the DHCP server will be ignored. Currently only has an effect on the networkd backend.
hostname: Option<String>Use this value for the hostname which is sent to the DHCP server, instead of machine’s hostname. Currently only has an effect on the networkd backend.
use_routes: Option<bool>Default: true. When true, the routes received from the DHCP server will be installed in the routing table normally. When set to false, routes from the DHCP server will be ignored: in this case, the user is responsible for adding static routes if necessary for correct network operation. This allows users to avoid installing a default gateway for interfaces configured via DHCP. Available for both the networkd and NetworkManager backends.
route_metric: Option<u16>Use this value for default metric for automatically-added routes. Use this to prioritize routes for devices by setting a lower metric on a preferred interface. Available for both the networkd and NetworkManager backends.
use_domains: Option<String>Takes a boolean, or the special value “route”. When true, the domain name received from the DHCP server will be used as DNS search domain over this link, similar to the effect of the Domains= setting. If set to “route”, the domain name received from the DHCP server will be used for routing DNS queries only, but not for searching, similar to the effect of the Domains= setting when the argument is prefixed with “~”.
Trait Implementations§
Source§impl Clone for DhcpOverrides
impl Clone for DhcpOverrides
Source§fn clone(&self) -> DhcpOverrides
fn clone(&self) -> DhcpOverrides
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more