core-agent-linux/network/udev-qubes-network.rules

# old udev has ENV{ID_NET_DRIVER}
SUBSYSTEMS=="xen", KERNEL=="eth*", ACTION=="add", ENV{ID_NET_DRIVER}=="vif", RUN+="/usr/lib/qubes/setup-ip"
SUBSYSTEMS=="net", KERNEL=="eth*", ACTION=="remove", ENV{ID_NET_DRIVER}=="vif", RUN+="/usr/lib/qubes/setup-ip"
# new udev has DRIVERS
SUBSYSTEMS=="xen", KERNEL=="eth*", ACTION=="add", DRIVERS=="vif", RUN+="/usr/lib/qubes/setup-ip"
network: fix rules for network setup on new udev New udev have `DRIVERS` matcher, instead of `ENV{ID_NET_DRIVER}`. Add appropriate rule to the file. Without it, network was working incidentally, because there is a fallback in qubes-misc-post.service, but dynamic network change was broken. This applies at least to Debian stretch. Fixes QubesOS/qubes-issues#3192 2017-10-19 15:10:31 +02:00			`# old udev has ENV{ID_NET_DRIVER}`
network: run setup-ip only on xen frontend interfaces Fixes QubesOS/qubes-issues#1882 2016-03-29 12:30:26 +02:00			`SUBSYSTEMS=="xen", KERNEL=="eth*", ACTION=="add", ENV{ID_NET_DRIVER}=="vif", RUN+="/usr/lib/qubes/setup-ip"`
Refactor and handle new network qubesdb configuration 2019-06-18 16:07:36 +02:00			`SUBSYSTEMS=="net", KERNEL=="eth*", ACTION=="remove", ENV{ID_NET_DRIVER}=="vif", RUN+="/usr/lib/qubes/setup-ip"`
network: fix rules for network setup on new udev New udev have `DRIVERS` matcher, instead of `ENV{ID_NET_DRIVER}`. Add appropriate rule to the file. Without it, network was working incidentally, because there is a fallback in qubes-misc-post.service, but dynamic network change was broken. This applies at least to Debian stretch. Fixes QubesOS/qubes-issues#3192 2017-10-19 15:10:31 +02:00			`# new udev has DRIVERS`
			`SUBSYSTEMS=="xen", KERNEL=="eth*", ACTION=="add", DRIVERS=="vif", RUN+="/usr/lib/qubes/setup-ip"`