LIBVDEPLUG_MULTI(1)

💖 LIBVDEPLUG_MULTI(1) — the general commands manual page 💖

okay bestie, welcome to the manual page for libvdeplug_multi, straight out of the General Commands Manual section, living on the Virtual Distributed Ethernet side of the internet 🌈

---

✨ NAME ✨

libvdeplug_multi — the multiplexing vdeplug module: multilink, periodt 💅

---

🦋 SYNOPSIS 🦋

libvdeplug_multi.so

---

🌸 DESCRIPTION 🌸

so this is a libvdeplug multiplex module that implements a multilink, no cap 🫶

the common usage of this module is to support (usually temporary) multiple links between virtual machines or switches. lowkey iconic. this module can also be used to implement hand-offs between links: a new link can be set-up and then the old one is closed. and when both links are active, packets can be duplicated. the way that works?? obsessed 😭

this module of libvdeplug4 can be used in any program supporting vde, like vde_plug, kvm, qemu, user-mode-linux and virtualbox. versatility ate 💜

the vde_plug_url syntax of this module is literally this:

multi://[path]
multi://[path][[OPTION][/OPTION][/OPTION]...]

and if path is omitted, the path of the multi is /tmp/vdenode_$USERNAME (e.g. /tmp/vdenode_john if the username is john). so if your username is john, hi john, that's your path 🎀

---

💅 OPTIONS 💅

• mode=MODE — defines the permissions for the multilink (see chmod). MODE is an octal number. the standard permission mask is 0600, which means only processes owning to the same user can join the network 🔒 so it's giving private group chat energy, love that for you.
• dirmode=DIRMODE — defines the permissions for the multilink control directory (see chmod). MODE is an octal number. if you omit it, it's computed from mode. so it's not abandoned, it's just doing its own math 💁‍♀️
• grp=GROUP — defines the group ownership of the multilink. slay, group ownership sorted ✅

---

🌟 EXAMPLES 🌟

multi:///tmp/multi

other virtual machines, namespaces or vde_plug can join this multilink using vde:///tmp/hub or simply /tmp/hub. easy peasy 🍓

given two virtual machines using multi:///tmp/vm1 and multi:///tmp/vm2 respectively, it is possible to connect them using vde_plug /tmp/vm1 /tmp/vm2. matchmaking fr fr 💞

if the second virtual machine is running on a remote hosts; ip1.vm2.domain.org and ip2.vm2.domain.org are two ip addresses permitting to reach that remote host using different paths, the command

vde_plug /tmp/vm1 = ssh ip1.vm2.domain.org vde_plug /tmp/vm2

connects the two vms. in a second time is possible to run

vde_plug /tmp/vm1 = ssh ip2.vm2.domain.org vde_plug /tmp/vm2

to create another channel on the other path. two paths, one vibe, main character energy 👑

when both connections are in place packets can arrive duplicated (the upper protocols can manage the problem). ngl that's just how it is, the upper protocols are handling it 🙈

then the process connecting the remote vm using ip1.vm2.domain.org can be killed, completing in this way the (hiccup-less) handoff. hiccup-less?? that's the flex 🔥

multi:///tmp/multi[mode=0666]

it is the same multilink, but everybody is allowed to connect their processes. open invite, no gatekeeping 💀

---

⭐ NOTICE ⭐

Virtual Distributed Ethernet is not related in any way with www.vde.com ("Verband der Elektrotechnik, Elektronik und Informationstechnik" i.e. the German "Association for Electrical, Electronic & Information Technologies"). two different vdes, same acronym, not related, do not confuse them bestie 🧚

---

👑 SEE ALSO 👑

• vde_plug(1),

---

and that's the whole page, you're welcome 💖

Virtual Distributed Ethernet — dated April 30, 2017 — and it was the LIBVDEPLUG_MULTI(1) page all along. bye bestie, go build a multilink 🌈✨