History log of /systemd/src/udev/net/link-config-gperf.gperf
Revision Date Author Comments Expand
5256e00e8b9015dd1a976d647fc71dc7efbd8cf8 10-Feb-2015 Tom Gundersen <teg@jklm.no>

net: support globbing and disjunction in Match logic Match{Name,OrginalName,Type,Driver,Path} can now take a space-separated glob of matches.

7eb08da4b388b920c8a894b1500c9cc7dc1f31ef 04-Dec-2014 Tom Gundersen <teg@jklm.no>

udev: net_setup - allow matching on OriginalName= This has been requested repeatedly, so let's give it a go. We explicitly do not allow matching on names that have already been changed (from a previous udev run, or otherwise), and matching on unpredictable names (ethX) is discouraged (but not currently disallowed). We also currently allow: [Match] Name=veth0 [Link] Name=my-name0 SomeOtherSetting=true Which means that the link file will be applied the first time it is invoked, but not on subsequent invocations, which may be surprising.

c6f7c917a1b494d4455800823472227463f87438 21-Mar-2014 Tom Gundersen <teg@jklm.no>

libsystemd-network: move network-utils from src/shared This does not belong in shared as it is mostly a detail of our networking subsystem. Moreover, now we can use libudev here, which will simplify things.

5556b5fe41173107a67dbe875fbd916a46e52a02 23-Feb-2014 Lennart Poettering <lennart@poettering.net>

core: clean up some confusing regarding SI decimal and IEC binary suffixes for sizes According to Wikipedia it is customary to specify hardware metrics and transfer speeds to the basis 1000 (SI decimal), while software metrics and physical volatile memory (RAM) sizes to the basis 1024 (IEC binary). So far we specified everything in IEC, let's fix that and be more true to what's otherwise customary. Since we don't want to parse "Mi" instead of "M" we document each time what the context used is.

733f7a2c69c794a81978a08a79916c224ba355a6 22-Feb-2014 Tom Gundersen <teg@jklm.no>

udev: net - allow MTU and Speed to be specified with units This also changes the names to MTUBytes and BitsPerSecond, respectively. Notice that the speed was mistakenly documented to be in bytes before this change.

edbb03e95a3c31bf719d5c6c46eec14d0bcb9c8f 21-Feb-2014 Tom Gundersen <teg@jklm.no>

.network/.netdev/.link: allow to match on architecture

2cc412b59353576cece2d5b30c6a39c70552f0a0 20-Feb-2014 Tom Gundersen <teg@jklm.no>

network/link: Match - filter on kernel cmdline, host and virt

d2df0d0ed3a88e491405b403e6022e6619750130 25-Nov-2013 Tom Gundersen <teg@jklm.no>

udev: net_setup_link - don't use Description as Alias Use Description only internally, and allow Alias to be set as a separate option. For instance SNMP uses ifalias for a specific purpose, so let's not write to it by default.

be32eb9b7fbcb22e4b648086d644135e38279633 04-Nov-2013 Tom Gundersen <teg@jklm.no>

net-config: start split out matching and parsing logic Move this to src/share/net-util.c, so it can be used elsewhere.

5fde13d748749f0e06e2e6cdd15f0980a79ea82c 29-Oct-2013 Tom Gundersen <teg@jklm.no>

udev: link-config - add proper parsing

16b9b87aeee9353b5b8dae6089a69752422a5b09 28-Oct-2013 Tom Gundersen <teg@jklm.no>

udev: link-config - add mac address policy This introduces a new key MACAddressPolicy. The possible policies are 'persistent' and 'random'. 'persistent' will do nothing if the current address is the hardware address, but if the hardware does not have an address (or another address is set for whatever reason), we will generate an address which will be random, but persistent between boots (based on machineid and persistent netif name). 'random' will do nothing if the kernel already set a random address, otherwise it will generate a random one and use that instead. This patch sets MACAddressPolicy=persistent in the default .link file.

daeb71a36a98834664e4d95773a3629b746f4db8 28-Oct-2013 Tom Gundersen <teg@jklm.no>

udev: link-config - move naming policy from udev rules This introduces a new key NamePolicy, which takes an ordered list of naming policies. The first successful one is applide. If all fail the value of Name (if any) is used. The possible policies are 'onboard', 'slot', 'path' and 'mac'. This patch introduces a default link file, which replaces the equivalent udev rule.

43b3a5ef61859f06cdbaf26765cab8e1adac4296 27-Oct-2013 Tom Gundersen <teg@jklm.no>

udev: link-config: add rtnl support This adds support for setting the mac address, name and mtu. Example: [Link] MTU=1450 MACAddress=98:76:54:32:10:ab Name=wireless0

a501033335ed402c8f7e86fe41a15531ba69abd7 26-Oct-2013 Tom Gundersen <teg@jklm.no>

udev: link-config: add ethtool support This adds support for setting the link speed, duplex and WakeOnLan settings. Example: [Link] SpeedMBytes=100 Duplex=half WakeOnLan=magic

af6f0d422c521374ee6a2dd92df5935a5a476ae5 26-Oct-2013 Tom Gundersen <teg@jklm.no>

udev: add network link configuration tool This tool applies hardware specific settings to network devices before they are announced via libudev. Settings that will probably eventually be supported are MTU, Speed, DuplexMode, WakeOnLan, MACAddress, MACAddressPolicy (e.g., 'hardware', 'synthetic' or 'random'), Name and NamePolicy (replacing our current interface naming logic). This patch only introduces support for Description, as a proof of concept. Some of these settings may later be overriden by a network management daemon/script. However, these tools should always listen and wait on libudev before touching a device (listening on netlink is not enough). This is no different from how things used to be, as we always supported changing the network interface name from udev rules, which does not work if someone has already started using it. The tool is configured by .link files in /etc/net/links/ (with the usual overriding logic in /run and /lib). The first (in lexicographical order) matching .link file is applied to a given device, and all others are ignored. The .link files contain a [Match] section with (currently) the keys MACAddress, Driver, Type (see DEVTYPE in udevadm info) and Path (this matches on the stable device path as exposed as ID_PATH, and not the unstable DEVPATH). A .link file matches a given device if all of the specified keys do. Currently the keys are treated as plain strings, but some limited globbing may later be added to the keys where it makes sense. Example: /etc/net/links/50-wireless.link [Match] MACAddress=98:f2:e4:42:c6:92 Path=pci-0000:02:00.0-bcma-0 Type=wlan [Link] Description=The wireless link