Virtual and software-defined networking devices (TUN/TAP, veth, virtio-net, Xen netfront, macvlan/ipvlan)
A collection of virtual network interfaces that underpin modern Linux containers, virtual machines, and user-space networking. It includes TUN/TAP (used by VPNs), veth pairs (the backbone of Docker and Kubernetes networking), virtio-net (the standard fast NIC for KVM/QEMU guests), Xen netfront for paravirtualized Xen guests, and stacking interfaces like macvlan, ipvlan, and dummy.
recommendation
It should stay because this is core plumbing for nearly every cloud, container, and virtualization stack running Linux today. Upstream activity is brisk into 2026, with ongoing patches to tun.c and virtio_net.c, and the components are explicitly recommended device models in current QEMU and kernel documentation. There is no realistic deprecation path for software networking that the rest of the ecosystem depends on.
repository signals
sources
- lore.kernel.org
Recent netdev patch traffic still touches drivers/net/tun.c in 2026, indicating active upstream maintenance rather than obsolescence.
- lore.kernel.org
Recent netdev patch traffic still touches drivers/net/virtio_net.c in 2026, including fixes/features for virtio-net.
- docs.kernel.org
TUN/TAP is a kernel driver for user-space packet I/O, showing this directory contains current software-defined networking infrastructure, not only legacy hardware support.
- qemu.org
QEMU documents VirtIO devices as recommended device models for virtual machines, supporting ongoing new deployments of virtio-net-backed guests.
- qemu.org
QEMU documents current virtio-net failover usage with the guest net_failover kernel module, showing active VM/virtualization deployment relevance for drivers/net components.
codex reasoning notes (technical)
`drivers/net` is a live umbrella driver directory, not a single obsolete chipset. Local shell inspection showed active configs such as TUN, VETH, VIRTIO_NET, XEN_NETDEV_FRONTEND, DUMMY, MACVLAN, and IPVLAN under this path. Lore evidence was gathered with `lore_activity` on `drivers/net/tun.c` and `drivers/net/virtio_net.c`, which returned 2026 traffic and lore URLs. Deployment evidence was gathered via `web.search_query`, which returned current kernel TUN/TAP docs and QEMU VirtIO/virtio-net failover docs. `lore_subsystem_churn` on `path:drivers/net/` returned no aggregate hits, likely because top-level directory matching is sparse in lore; that does not outweigh the direct per-file activity. Because this directory serves heavily used VM/container/user-space networking functions and still sees upstream fixes, the correct outcome is keep, not deprecate/remove.