Hello, everyone. I am using OVS+DPDK to test the throughput of two docker containers. I set up my platform as described in the following question in StackOverflow (url: https://stackoverflow.com/questions/56539216/docker-container-connected-by-ovsdpdk-ping-work-but-iperf-not ).
There are two containers (box1, box2) and one OVS bridge (ovs-br1), which connects box1-eth1 and box2-eth1. I can ping from box1-eth1 to box2-eth2 using bridge ovs-br1. However, iperf does not work. I have checked the packets sent by box1-eth1 has reached box2-eth1, and the iperf server in box2 has no reaction. The detailed description in another question in StackOverflow (url: https://stackoverflow.com/questions/56555930/interface-received-packets-iperf-application-does-not-get-packets-and-does-no ) Briefly, I find that the datapath_type may be the problem. *The original setting is:* sudo ovs-vsctl add-br ovs-br1 -- set bridge ovs-br1 datapath_type=netdev The log of OVS is: 2019-06-13T03:38:33.303Z|00068|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports recirculation 2019-06-13T03:38:33.303Z|00069|ofproto_dpif|INFO|netdev@ovs-netdev: MPLS label stack length probed as 3 2019-06-13T03:38:33.303Z|00070|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports truncate action 2019-06-13T03:38:33.303Z|00071|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports unique flow ids 2019-06-13T03:38:33.303Z|00072|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports ct_state 2019-06-13T03:38:33.303Z|00073|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports ct_zone 2019-06-13T03:38:33.303Z|00074|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports ct_mark 2019-06-13T03:38:33.303Z|00075|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports ct_label 2019-06-13T03:38:33.303Z|00076|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath does not support ct_state_nat 2019-06-13T03:38:33.304Z|00077|bridge|INFO|bridge ovs-br1: added interface ovs-br1 on port 65534 2019-06-13T03:38:33.304Z|00078|bridge|INFO|bridge ovs-br1: using datapath ID 00005203106b4948 2019-06-13T03:38:33.304Z|00079|connmgr|INFO|ovs-br1: added service controller "punix:/usr/local/var/run/openvswitch/ovs-br1.mgmt" 2019-06-13T03:38:41.003Z|00080|bridge|INFO|bridge ovs-br1: added interface 1dd6d0d9888a4_l on port 1 2019-06-13T03:38:41.003Z|00081|netdev_linux|WARN|error receiving Ethernet packet on 1dd6d0d9888a4_l: Network is down 2019-06-13T03:38:41.003Z|00082|dpif_netdev|ERR|error receiving data from 1dd6d0d9888a4_l: Network is down 2019-06-13T03:38:41.241Z|00083|bridge|INFO|bridge ovs-br1: added interface 959a4d31f93c4_l on port 2 2019-06-13T03:38:41.241Z|00084|netdev_linux|WARN|error receiving Ethernet packet on 959a4d31f93c4_l: Network is down 2019-06-13T03:38:41.241Z|00085|dpif_netdev|ERR|error receiving data from 959a4d31f93c4_l: Network is down I was wondering why datapath_type=netdev does not work for iperf. Thank you for your time. Best wishes. Rui Xia *The new setting is:* sudo ovs-vsctl add-br ovs-br1 This time, iperf server works well, and the log of OVS is: 2019-06-13T03:08:02.488Z|00007|ofproto_dpif|INFO|system@ovs-system: Datapath does not support recirculation 2019-06-13T03:08:02.488Z|00008|ofproto_dpif|INFO|system@ovs-system: MPLS label stack length probed as 0 2019-06-13T03:08:02.488Z|00009|ofproto_dpif|INFO|system@ovs-system: datapath does not support masked set action feature. 2019-06-13T03:08:02.488Z|00010|ofproto_dpif|INFO|system@ovs-system: Datapath does not support truncate action 2019-06-13T03:08:02.488Z|00011|ofproto_dpif|INFO|system@ovs-system: Datapath does not support unique flow ids 2019-06-13T03:08:02.488Z|00012|ofproto_dpif|INFO|system@ovs-system: Datapath does not support ct_state 2019-06-13T03:08:02.488Z|00013|ofproto_dpif|INFO|system@ovs-system: Datapath does not support ct_zone 2019-06-13T03:08:02.488Z|00014|ofproto_dpif|INFO|system@ovs-system: Datapath does not support ct_mark 2019-06-13T03:08:02.488Z|00015|ofproto_dpif|INFO|system@ovs-system: Datapath does not support ct_label 2019-06-13T03:08:02.488Z|00016|ofproto_dpif|INFO|system@ovs-system: Datapath does not support ct_state_nat 2019-06-13T03:08:02.491Z|00001|ofproto_dpif_upcall(handler1)|INFO|received packet on unassociated datapath port 0 2019-06-13T03:08:02.493Z|00017|bridge|INFO|bridge ovs-br1: added interface ovs-br1 on port 65534 2019-06-13T03:08:02.493Z|00018|bridge|INFO|bridge ovs-br1: using datapath ID 0000bef6ed276749 2019-06-13T03:08:02.493Z|00019|connmgr|INFO|ovs-br1: added service controller "punix:/usr/local/var/run/openvswitch/ovs-br1.mgmt" 2019-06-13T03:08:05.501Z|00020|memory|INFO|8564 kB peak resident set size after 10.1 seconds 2019-06-13T03:08:05.501Z|00021|memory|INFO|handlers:8 ports:1 revalidators:4 rules:5 2019-06-13T03:09:47.238Z|00022|bridge|INFO|bridge ovs-br1: added interface ed03f2fd53694_l on port 1 2019-06-13T03:10:37.665Z|00023|bridge|INFO|bridge ovs-br1: added interface 26d01f8770224_l on port 2 2019-06-13T03:18:47.974Z|00024|bridge|WARN|could not open network device 26d01f8770224_l (No such device) 2019-06-13T03:18:57.645Z|00025|bridge|WARN|could not open network device 26d01f8770224_l (No such device) 2019-06-13T03:18:57.645Z|00026|ofproto|WARN|ovs-br1: cannot get STP status on nonexistent port 1 2019-06-13T03:18:57.645Z|00027|ofproto|WARN|ovs-br1: cannot get RSTP status on nonexistent port 1 2019-06-13T03:18:57.647Z|00028|bridge|WARN|could not open network device 26d01f8770224_l (No such device) 2019-06-13T03:18:57.648Z|00029|bridge|WARN|could not open network device ed03f2fd53694_l (No such device)
_______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
