ovs tap "internal" vs tuntap tap

Question

I'm building an SDN testbed consists of an OpenvSwitch switch installed on Linux Ubuntu 18.04 and 5 VMs (Linux Ubuntu 16.04 server) running on VirtualBox. The OVS is managed by OpenDaylight Boron.

• When I use ip tuntap add mode tap tapN to create taps to link the VMs to OVS, everything works just fine and I can ping between VMs "within the same subnet". however when I try: ovs-ofctl -O OpenFlow13 dump-ports br0, statistics such as (rx pkts and tx pkts) show only Zeros on all ports except the LOCAL port.

• But when I use ovs-vsctl add-port br0 vnet0 -- set Interface tapN type=internal to create the taps, I can see statistics on all ports even if only one device pings another one. My questions:

  1. Why (dump-ports) doesn't show statistics in the first case?

  2. Is it Ok to continue use (ovs internal taps) in my testbed as described in the second case?

---

Here is the complete OVS configuration case 1:

ovs-vsctl add-br br0

ip tuntap add mode tap vnet0
ip tuntap add mode tap vnet1
ip tuntap add mode tap vnet2
ip tuntap add mode tap vnet3
ip tuntap add mode tap vnet4
ip tuntap add mode tap vnet5

ip link set vnet0 up 
ip link set vnet1 up
ip link set vnet2 up
ip link set vnet3 up 
ip link set vnet4 up
ip link set vnet5 up 


ovs-vsctl add-port br0 vnet0
ovs-vsctl add-port br0 vnet1
ovs-vsctl add-port br0 vnet2
ovs-vsctl add-port br0 vnet3
ovs-vsctl add-port br0 vnet4
ovs-vsctl add-port br0 vnet5

ifconfig br0 up
ovs-vsctl set bridge br0 protocols=OpenFlow13

ovs-vsctl set-controller br0 tcp:10.10.80.50:6633