On Wed, Oct 18, 2017 at 09:17:53AM +0200, Jannis Ohms wrote:
> Hi
>
>
> I used the following command to create 4 queues
>
> ovs-vsctl -- set port s7-eth2 qos=@newqos -- --id=@newqos create qos
> type=linux-htb other-config:max-rate=1000 queues:1=@newQ queues:2=@newQ2
> queues:3=@newQ3 --
On Tue, Oct 24, 2017 at 02:27:59PM -0700, Ben Pfaff wrote:
> On Tue, Oct 24, 2017 at 11:07:58PM +0200, Daniel Alvarez Sanchez wrote:
> > Hi guys,
> >
> > Great job Numan!
> > As we discussed over IRC, the patch below may make more sense.
> > It essentially sets the dl_type so that when packet
On Tue, Oct 24, 2017 at 11:07:58PM +0200, Daniel Alvarez Sanchez wrote:
> Hi guys,
>
> Great job Numan!
> As we discussed over IRC, the patch below may make more sense.
> It essentially sets the dl_type so that when packet comes from the
> controller, it matches
> a valid type and
Hi guys,
Great job Numan!
As we discussed over IRC, the patch below may make more sense.
It essentially sets the dl_type so that when packet comes from the
controller, it matches
a valid type and OVS_KEY_ATTR_CT_ORIG_TUPLE_IPV4 is not added.
Maybe what Numan proposed and this patch could be a
On Tue, Oct 24, 2017 at 09:04:22PM +0530, Numan Siddique wrote:
> We did some more investigation. This issue is seen only when OVN native
> dhcp is used and with kernel datapath which doesn't support
> OVS_KEY_ATTR_CT_ORIG_TUPLE_IPV4. The reason for this failure is because
> ovs-vswitchd
We did some more investigation. This issue is seen only when OVN native
dhcp is used and with kernel datapath which doesn't support
OVS_KEY_ATTR_CT_ORIG_TUPLE_IPV4. The reason for this failure is because
ovs-vswitchd includes the attribute OVS_KEY_ATTR_CT_ORIG_TUPLE_IPV4 when it
sends the packet
Hi,
I am using ovs(2.8.1)+dpdk(17.05.2), and notice that there are lots of ovs log
as below:
2017-10-23T21:55:13.382Z|00241|netdev_linux|INFO|ioctl(SIOCGIFINDEX) on
vxlan_sys_4789 device failed: No such device
2017-10-23T21:55:13.384Z|00242|netdev_linux|INFO|ioctl(SIOCGIFINDEX) on
