2015-04-29 09:41:42 +02:00
|
|
|
[Match]
|
2023-07-04 10:24:29 +02:00
|
|
|
#Name=*
|
|
|
|
|
# Can be {colon,hyphen,dot}-delimited hexadecimal or IPv{4,6} address
|
|
|
|
|
#MACAddress=
|
|
|
|
|
Type=ether
|
2015-04-29 09:41:42 +02:00
|
|
|
|
2023-03-31 12:33:27 +02:00
|
|
|
[Link]
|
|
|
|
|
# My devices generally also have WiFi so lack of ethernet is not a reason
|
|
|
|
|
# to wait for systemd-networkd-wait-online.service
|
2024-04-12 08:52:32 +02:00
|
|
|
RequiredForOnline=false
|
2023-08-23 13:40:18 +02:00
|
|
|
# Takes "ipv4", "ipv6", "both", or "any" (default).
|
|
|
|
|
RequiredFamilyForOnline=both
|
2024-04-12 08:52:32 +02:00
|
|
|
# Always set administrative state to up. Implies RequiredForOnline=true
|
2023-03-31 12:33:27 +02:00
|
|
|
#ActivationPolicy=always-up
|
2024-04-12 08:52:32 +02:00
|
|
|
# Required for mDNS
|
|
|
|
|
Multicast=true
|
2023-03-31 12:33:27 +02:00
|
|
|
|
2015-04-29 09:41:42 +02:00
|
|
|
[Network]
|
2024-04-12 08:52:32 +02:00
|
|
|
#DHCP=true
|
2023-03-07 13:46:28 +01:00
|
|
|
# /24, /16, /8 are the the class C, B, A networks
|
|
|
|
|
Address=192.168.0.2/24
|
|
|
|
|
Gateway=192.168.0.1
|
2023-06-25 13:13:00 +02:00
|
|
|
IPv6PrivacyExtensions=true
|
|
|
|
|
IPv6LinkLocalAddressGenerationMode=stable-privacy
|
2023-03-07 13:46:28 +01:00
|
|
|
# DNS has no effect unless systemd-resolved is used. Why would it be used?
|
2015-04-29 09:41:42 +02:00
|
|
|
# systemctl enable systemd-resolved && systemctl start systemd-resolved
|
|
|
|
|
# ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf
|
2023-03-07 13:46:28 +01:00
|
|
|
#DNS=127.0.0.1
|
|
|
|
|
#DNS=::1
|
|
|
|
|
#DNS=8.8.4.4
|
|
|
|
|
# Enable systemd-timesyncd with `timedatectl set-ntp true`, may be specified
|
|
|
|
|
# multiple times, but you are using Chrony instead, right?
|
|
|
|
|
#NTP=fi.pool.ntp.org
|
|
|
|
|
#NTP=time.cloudflare.com
|
2024-04-12 08:52:32 +02:00
|
|
|
# Enable mDNS/.local for systemd-resolved
|
|
|
|
|
MulticastDNS=true
|
|
|
|
|
# Windows
|
|
|
|
|
LLMNR=true
|
