Re: [ovs-discuss] [dpdk-users] OVS-DPDK - TAP0 - vdev (af_packet) device is linkdown

On Tue, 20 Jun 2017 09:40:47 + "Avi Cohen (A)" wrote: > Hello All, > > I did upgrade to dpdk-17.05 and ovs-2-7.1 and create a vdev - af_packet > device according the config script below > This tap device connects the ovs-dpdk to a name space > The problem is that

Re: [ovs-discuss] [ovs-dev] rpmbuild failure for ovs_dpdk

Correction: ovs-discuss@openvswitch.org On 6/20/17, 9:01 AM, "ovs-discuss-boun...@openvswitch.org on behalf of Darrell Ball" wrote: Again, send to disc...@openvswitch.org Do you see something like this ?

[ovs-discuss] Match only the upper 3 bits of dscp field

Hi I need to modify the tos field of ipv4 frames. The rule I currently have for this looks something like: ovs-ofctl add-flow br0-wlan0 "table=20 priority=100 dl_type=0x0800 nw_tos=32 actions=mod_nw_tos:224" I only want to match the upper most 3 bits of the DSCP field. This rule as it is has

Re: [ovs-discuss] OVS-DPDK - TAP0 - vdev (af_packet) device is linkdown

Update I see in log file the following error msgs .. libvirtd[1734]: Failed to open file '/sys/class/net/tap0/operstate': No such file or directory libvirtd[1734]: unable to read: /sys/class/net/tap0/operstate: No such file or directory kernel: [ 38.948590] IPv6: ADDRCONF(NETDEV_UP): tap0:

[ovs-discuss] OVS-DPDK - TAP0 - vdev (af_packet) device is linkdown

Hello All, I did upgrade to dpdk-17.05 and ovs-2-7.1 and create a vdev - af_packet device according the config script below This tap device connects the ovs-dpdk to a name space The problem is that this tap00 device is linkdown - (never reach RUNNING state ) - hence no pkt is received