On 16 November 2017 at 09:26, Sébastien Bernard wrote:
> On 16/11/2017 13:08, Guru Shetty wrote:
>
>
>
> On 16 November 2017 at 01:56, Sébastien Bernard
> wrote:
>
>> Ok,
>>
>> I got to reproduce the error I had yesterday.
>>
>> Here's the path :
>>
>>
On 11/12/2017 1:21 PM, Fred Licht wrote:
Hi All,
I was curious if there was a way to have an OVS port reflect its up/down
status to force a different port’s status to match. I am hosting a firewall VM
on a system, and would want to have the LAN interface go down if the upstream
(real)
Yes
I have done some work here and it will likely be added for 2.9
From: on behalf of 王嵘
Date: Tuesday, November 21, 2017 at 4:10 AM
To: "ovs-discuss@openvswitch.org"
Subject: [ovs-discuss] Will fragment
On November 20, 2017 11:44:09 PM PST, Sara Gittlin
wrote:
>Thank you Ben
>Is this L2 flow is an entry in one of the kernel megaflow tables ?
>otherwise if it an entry in the kernel microflow table - then there
>should be multiple microflow tables, because L2 flow keys
Hi,
The current solution for running OVS with non-root user in Fedora makes it not
possible to support UIO drivers [1].
Setting the user to root:root via /etc/sysconfig/openvswitch should be a
solution, but it is also currently broken, since the systemd
ovs-vswitchd.service is forcing the
hi,
I am using ovs-dpdk now, and find that the fragment has not been processed
before the userspace connection track,
which is very necessary for me to use.
And I want to know, whether this function will be added?
Thanks very much.
WangRong
Best Regards.