LIBVDEPLUG_BONDING(1)

💖 LIBVDEPLUG_BONDING 💖

okay bestie, welcome to the libvdeplug_bonding page — it's from the General Commands Manual section, so you already know it's giving real-deal system documentation energy ✨

🌸 NAME 🌸

libvdeplug_bonding — the multiplexing vdeplug module, aka: bonding links 🫶

🎀 SYNOPSIS 🎀

libvdeplug_bonding.so

🦋 DESCRIPTION 🦋

So this is a libvdeplug multiplex module and what it does is implement the bonding of multiple links. That's the whole vibe.

The common usage — like, the reason people reach for it — is to support multiple links between virtual machines or switches. This module transmits packets on all the available links in a round-robin manner. And if those links use several paths and channels, it's possible to reach a higher bandwidth. no cap, that's the payoff 🔥

This module of libvdeplug4 can be used in any program supporting vde, like vde_plug, kvm, qemu, user-mode-linux and virtualbox. iconic lineup honestly 👑

The vde_plug_url syntax of this module is the following:

bonding://[path]
bonding://[path][[OPTION][/OPTION][/OPTION]...]

And if path is omitted, the path of the bonding is /tmp/vdenode_$USERNAME — for example /tmp/vdenode_john if the username is john. cute, it names itself after you 🥺

---

✨ OPTIONS ✨

• mode=MODE — defines the permissions for the bonding node (peep chmod for the deets). MODE is an octal number. The standard permission mask is 0600, which means only processes owned by the same user can join the network. locked down, as it should be 💅
• dirmode=DIRMODE — defines the permissions for the bonding node control directory (again, see chmod). DIRMODE is an octal number. If you omit it, it gets computed from mode. she's self-sufficient like that 🎀
• grp=GROUP — defines the group ownership of the bonding node. it's giving "we share this" 🫶

---

🌈 EXAMPLES 🌈

bonding:///tmp/bonding

Other virtual machines, namespaces or vde_plug can join this bondinglink using vde:///tmp/hub or simply /tmp/hub 🌸

Given two virtual machines using bonding:///tmp/vm1 and bonding:///tmp/vm2 respectively, it is possible to connect them using vde_plug /tmp/vm1 /tmp/vm2. And if the second virtual machine is running on a remote hosts — like, ip1.vm2.domain.org and ip2.vm2.domain.org are two ip addresses permitting to reach that remote host using different paths — then the commands

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

create two channels between the two virtual machines. And packets are sent in turns on one or the other link. two paths, one bond, main character energy fr fr 💅

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

It is the same bondinglink, but everybody is allowed to connect their processes. (yes bestie, that's the permissive one — know what you're doing 🙈)

---

💀 NOTICE 💀

Virtual Distributed Ethernet is not related in any way with www.vde.com — that's the "Verband der Elektrotechnik, Elektronik und Informationstechnik", i.e. the German "Association for Electrical, Electronic & Information Technologies". same letters, completely different people, don't get it twisted 💀

---

👑 SEE ALSO 👑

• vde_plug(1),

---

Virtual Distributed Ethernet • April 30, 2017 — mwah, that's the page, go bond some links bestie, ily 🫶💖✨