receive all multicast packets. Can be toggled through sysfs.
auto media select active. Can be toggled through sysfs.
broadcast address valid. Volatile.
turn on debugging. Can be toggled through sysfs.
driver signals dormant. Volatile.
dialup device with changing addresses. Can be toggled through sysfs.
echo sent packets. Volatile.
is a loopback net. Volatile.
driver signals L1 up. Volatile.
master of a load balancer. Volatile.
Supports multicast. Can be toggled through sysfs.
no ARP protocol. Can be toggled through sysfs. Volatile.
avoid use of trailers. Can be toggled through sysfs. Volatile.
interface is has p-p link. Volatile.
can set media type. Can be toggled through sysfs.
receive all packets. Can be toggled through sysfs.
interface RFC2863 OPER_UP. Volatile.
slave of a load balancer. Volatile.
interface is up. Can be toggled through sysfs.
Generated using TypeDoc
These are the &struct net_device flags, they can be set by drivers, the kernel and some can be triggered by userspace. Userspace can query and set these flags using userspace utilities but there is also a sysfs entry available for all dev flags which can be queried and set. These flags are shared for all types of net_devices. The sysfs entries are available via /sys/class/net//flags. Flags which can be toggled through sysfs
are annotated below, note that only a few flags can be toggled and some
other flags are always preserved from the original net_device flags
even if you try to set them via sysfs. Flags which are always preserved
are kept under the flag grouping @IFF_VOLATILE. Flags which are volatile
are annotated below as such.
You should have a pretty good reason to be extending these flags.