Task #3366

Make use of vde_switch to unit-test transport behaviors

Added by Alex Afanasyev over 4 years ago. Updated over 1 year ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


vde_switch (part of VDE,; vde2 package on Ubuntu, vde package in Homebrew) emulates switch/hub, with ability to create TAP interfaces.

For example,

vde_switch -t testTap1 -t testTap2

will create testTap1 and testTap2 interfaces that can be later properly configured. The configuration could be tricky, as it is platform-specific.


Updated by Junxiao Shi over 4 years ago

  • Start date deleted (12/21/2015)

The use of TUN/TAP in unit testing is expressly rejected in #3306 note-10.


Updated by Alex Afanasyev over 4 years ago

  • Tracker changed from Task to Feature

I forgot about #3306. But we still may keep this issue alive, if we will have serious test issues with multicast udp/ethernet. I understand that this is not a trivial task, but may be beneficial.

If not unit tests, TAP interfaces can be embedded in integrated tests. Specifically, the VLAN issue (#3348) can be tested with vde_switch.


Updated by Davide Pesavento over 4 years ago

  • Subject changed from Make use of `vde_switch` to unit-test transport behaviors to Make use of vde_switch to unit-test transport behaviors

Considering we wouldn't use the "distributed" part of VDE, what are the advantages compared to other solutions such as a virtual bridge + a number of veth or tap devices?


Updated by Davide Pesavento over 1 year ago

  • Tags set to UnitTests
  • Tracker changed from Feature to Task
  • Category changed from Integration Tests to Faces
  • Priority changed from Normal to Low

Also available in: Atom PDF