VDE_OVER_NS(1)

πŸ’… vde_over_ns β€” the group chat manual ✨

okay bestie, so this is vde_over_ns, straight out of the General Commands Manual section (section 1, we're fancy like that). Steganographic cable over the NS protocol for Virtual Distributed Ethernet. Yes. You read that right. Sit down, hydrate, let's go 🫢


✨ NAME ✨

vde_over_ns β€” a steganographic cable over NS protocol for Virtual Distributed Ethernet 🌈


πŸŽ€ SYNOPSIS πŸŽ€

vde_over_ns [-D] [-c server_address] [-s vde_plug] [-i ip.to.bi.nd]
domain.name

πŸ¦‹ DESCRIPTION πŸ¦‹

A vde_over_ns lets you connect two remote vde_switches through steganographic NS query/response datagrams. like, the packets are out here cosplaying as totally normal NS traffic. iconic behavior honestly. e.g.:

dpipe vde_plug /tmp/s1 = vde_over_ns tun.mydomain.vde

this one binds to udp port 53 and listens for incoming steganographic NS queries β€” that's server mode, babes. πŸ’– And every bit of traffic going to/from stdout/stdin gets redirected to the client via ns responses. the way it just... reroutes everything. obsessed.

it creates a wire between two vde_switches (with sockets /tmp/s1 and /tmp/s2 respectively). fair warning though: this cable looses 10% of the packets in each direction. 😭 ten percent!! gone!! every direction!! it's giving unreliable narrator but it's actually a cable.

The same vde_over_dns server can be created using:

vde_over_ns -s /tmp/s1 tun.mydomain.vde

The syntax is almost identical for the client mode, except that to have a vde_over_ns client connect to that server, the -c server option must be specified. no cap, that one flag is the whole difference 🫢


πŸ‘‘ OPTIONS πŸ‘‘

  • -s vdeplug β€” If specified, the vde_over_ns will connect to the local vde socket vdeplug instead pf stdin/stdout, using the libvdeplug library. (yes it says "pf", we don't fix the queen's typos, we respect her πŸ’…)
  • -D β€” Detach console and send the process to background. bye bestie, go live your life in the background ✨
  • -b ip.to.bind β€” The NS server will bind only to the specified ip, instead of any ip. Only valid in server mode (without -c) β€” so don't try it in client mode, it's not for you 🌸
  • -c server_addr β€” If specified, client mode is enabled. Vde_over_ns will try to send NS requests to server_addr. If not specified, server mode is enabled by default. main character energy: default is server πŸŽ€

πŸ’€ 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").

like. same letters. completely different people. do not @ them. πŸ™ˆ


🌈 SEE ALSO 🌈

vde_switch(1), vdeq(1). dpipe(1). unixterm(1).

go read those too, they're in the same friend group πŸ¦‹


πŸ’œ AUTHORS πŸ’œ

VDE_OVER_NS is a tool by Daniele Lacamera <root@danielinux.net>

VDE is a project by Renzo Davoli <renzo@cs.unibo.it>

based on nstx, a steganographic ns client/server software by:

  • Florian Heinz <sky@sysv.de>
  • Julien Oster <frodo@sysv.de>

⭐ shoutout to the whole squad for building a whole stealth network inside NS queries. legends only.

and that's the page bestie!! this whole thing lives under Virtual Distributed Ethernet, version dated May 2, 2007 β€” a vintage baddie fr fr. now go run it, slay, and remember: 10% packet loss is just the vibe βœ¨πŸ’…πŸŽ€