Make use of vde_switch to unit-test transport behaviors
vde_switch (part of VDE, http://vde.sourceforge.net/; vde2 package on Ubuntu, vde package in Homebrew) emulates switch/hub, with ability to create TAP interfaces.
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 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
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?