Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 4 additions & 6 deletions doc/rtd/topics/network-config-format-v2.rst
Original file line number Diff line number Diff line change
Expand Up @@ -50,9 +50,8 @@ currently being defined.
There are two physically/structurally different classes of device definitions,
and the ID field has a different interpretation for each:

Physical devices

: (Examples: ethernet, wifi) These can dynamically come and go between
Physical devices (Examples: ethernet, wifi):
These can dynamically come and go between
reboots and even during runtime (hotplugging). In the generic case, they
can be selected by ``match:`` rules on desired properties, such as
name/name pattern, MAC address, driver, or device paths. In general these
Expand All @@ -69,9 +68,8 @@ Physical devices
which is only being used for references from definitions of compound
devices in the config.

Virtual devices

: (Examples: veth, bridge, bond) These are fully under the control of the
Virtual devices (Examples: veth, bridge, bond):
These are fully under the control of the
config file(s) and the network stack. I. e. these devices are being created
instead of matched. Thus ``match:`` and ``set-name:`` are not applicable for
these, and the ID field is the name of the created virtual device.
Expand Down