VETHER(4)

📦
version 11.0 · 2 versions
, in nixpkgs unstable

🦋 VETHER(4) — virtual Ethernet interface 🦋

okay bestie, welcome to vether(4) from the Kernel Interfaces Manual — the virtual Ethernet interface, and she is lowkey iconic. ✨

💖 NAME 💖

vether — virtual Ethernet interface. That's the whole vibe, no cap. 💅

✨ SYNOPSIS ✨

pseudo-device vether

🌸 DESCRIPTION 🌸

So vether literally simulates a normal Ethernet interface by encapsulating standard network frames with an Ethernet header, specifically for use as a member in a bridge(4). It's giving fake-NIC-with-a-purpose, and we're obsessed. 🫶

To use vether, the administrator needs to configure an address onto the interface so that packets can be routed to it. An Ethernet header will be prepended, and if the vether interface is a member of a bridge(4), the frame will show up there. Periodt. 😭

The vether link state can be controlled using ifconfig(8):

media auto  link state “up”
media none  link state “down”

🦋 SEE ALSO 🦋

🎀 HISTORY 🎀

The vether interface first appeared in OpenBSD 4.7 and NetBSD 10. History! 🌈

👑 AUTHORS 👑

Shoutout to Theo de Raadt <deraadt@openbsd.org> — yes, that's the author, bestie. 👑

💀 BUGS 💀

Like tap(4), the Ethernet address chosen will be partially random, and may occasionally collide with another address. So yeah, she's a little random and might bump into someone else's address — not ideal, but that's the tea. 😭

💖 packaged by Debian, dated September 26, 2017, and filed under VETHER(4) — bye bestie! 💖

📦 where this page comes from