pkg.soopen package index

brew / Rang 802

vde mit Homebrew, apt installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für vde in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install vde

local Homebrew formula metadata

Linux

Debian aptverifiziert · 92%
sudo apt install vde-switch

Debian stable package indexes · vde-switch · Quelle: deb.debian.org

Überblick

Paketzusammenfassung

Ethernet compliant virtual network

Befehle und Aliase

  • dpipe
  • unixcmd
  • vde_autolink
  • vde_over_ns
  • vde_pcapplug
  • vde_plug
  • vde_plug2tap
  • vde_router
  • vde_switch
  • vdecmd
  • vdeterm
  • wirefilter

Verlauf

Projektgeschichte und Nutzung

VDE, Virtual Distributed Ethernet, is a suite for building Ethernet-like virtual networks out of software switches, plugs, cables, tunnels, and TAP connections. It belongs to the VirtualSquare research-and-tooling tradition around virtual machines, emulators, and distributed network labs.

The package is old-school virtualization infrastructure: it predates today's container-networking defaults and gives users explicit virtual switches and virtual cables that can connect QEMU, User Mode Linux, Bochs, MPS machines, real Linux hosts, and remote switches.

Projektgeschichte

The vde-2 README credits Renzo Davoli for VDEv2 work from 2003 through 2006 and notes that it was based long ago on uml-router work by Yon Uriarte and Jeff Dike from 2002. A 2005 TridentCom paper by Davoli describes VDE as an Ethernet-compliant, distributed, software virtual network intended to connect emulators, virtual machines, real operating systems, and other tools.

The historical hosting path also shows its age. SourceForge records VDE as a Virtual Distributed Ethernet project and states that the project moved to GitHub at virtualsquare/vde-2, with new issues and patches directed there. The current GitHub repository was created on 2016-02-22, preserving the vde-2 codebase under the VirtualSquare organization.

Adoptionsgeschichte

VDE's adoption was strongest in virtualization and network-emulation niches. The manpage documents end nodes including real Linux boxes through TUN/TAP, Bochs, QEMU, and MPS virtual machines; Oracle's VirtualBox manual describes VDE networking as an optional source-code feature and credits Renzo Davoli at the University of Bologna.

The 2005 paper framed VDE as a general virtual networking layer rather than a single-emulator feature. That distinction is the adoption hook: users could build virtual Ethernet topologies across different hosts and virtualization systems instead of accepting the networking model bundled with one emulator.

Wie es verwendet wird

A typical VDE setup runs vde_switch, connects local or remote endpoints with vde_plug/vde cables, and optionally attaches a host TAP interface. The vde_switch manpage describes management through console or a Unix-socket terminal, support for VLAN-like behavior, Fast Spanning Tree work, and daemon mode.

VDE is used for heterogeneous VM labs, tunnels, mobility experiments, and overlay networks where Ethernet frames should move through a user-controlled virtual topology. The README emphasizes that units connected to VDE see each other as if they were on a real Ethernet.

Warum Paket-Nerds sich dafür interessieren

VDE is significant because it exposes virtual networking as composable Unix tools rather than a hidden hypervisor setting. For package users building labs, that means repeatable topologies made of processes and sockets: switches, plugs, TAPs, packet captures, and filters.

It is also a good example of research software that became distribution software. The same package can be read as a 2000s virtualization artifact, a QEMU-era networking tool, and a still-useful way to build small Layer 2 experiments without deploying a larger SDN stack.

Zeitleiste

  • 2002: The vde-2 README credits earlier uml-router work by Yon Uriarte and Jeff Dike.
  • 2003-2006: The vde-2 README credits Renzo Davoli's VDEv2 work across these years.
  • 2005: Davoli's Virtual Distributed Ethernet paper described VDE as Ethernet-compliant, distributed, and useful for virtual machines and real systems.
  • 2016-02-22: The virtualsquare/vde-2 GitHub repository was created.
  • 2022-05-02: GitHub release v2.3.3 was published.

Related projects

  • VDE is related to QEMU, User Mode Linux, Bochs, MPS, VirtualBox VDE networking, TUN/TAP tooling, and later virtual-switch systems such as Open vSwitch. In the VirtualSquare family, vdeplug4 is a later related project that rethinks VDE plug connections.

Sicherheitslage

Risikostufe: blue

broad file, network, media, or database tool signal.

Risikoklassifikator

blue Risiko · mittel Konfidenz · tool

Warum

  • broad file, network, media, or database tool signal

Signale

  • text:network

Installationsverhalten

  • Es wurden keine Homebrew-Bottle-Metadaten erfasst.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
dpipeExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
unixcmdExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vde_autolinkExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vde_over_nsExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vde_pcapplugExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vde_plugExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vde_plug2tapExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vde_routerExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vde_switchExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vdecmdExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vdetermExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
wirefilterExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-08-03
Manager-Version2.3.3
Manager aktualisiert
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:vde
Version2.3.3
PaketmanagerHomebrew
Homepagehttps://github.com/virtualsquare/vde-2
Repositoryhttps://github.com/virtualsquare/vde-2
Bottlenicht erfasst
Dienstkeiner deklariert

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Debian apt92%

vde-switch 2.3.2+r586-11

Virtual Distributed Ethernet.

http://vde.sourceforge.net

sudo apt install vde-switch
  • Section: net
  • Architecture: amd64
  • Source Package: vde2
  • 2 Abhängigkeiten
  • installed executable or alias match
  • Abgeglichen nach: Vde Switch
Debian stable package indexes · deb.debian.org · Debian stable package indexes: vde-switch from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz
Ubuntu apt92%

vde-switch 2.3.2+r586-10

Virtual Distributed Ethernet.

http://vde.sourceforge.net

sudo apt install vde-switch
  • Section: universe/net
  • Architecture: amd64
  • Source Package: vde2
  • 2 Abhängigkeiten
  • installed executable or alias match
  • Abgeglichen nach: Vde Switch
Ubuntu 24.04 LTS package indexes · archive.ubuntu.com · Ubuntu 24.04 LTS package indexes: vde-switch from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • pkg.so package database
  • pkgdb category and tag curation