What do the following commands yield ?
sudo ovs-vsctl -- get bridge datapath_type
sudo ovs-vsctl --no-wait get Open_vSwitch . other_config
>
> *From: * on behalf of Han Zhou <
> zhou...@gmail.com>
> *Date: *Thursday, May 2, 2019 at 7:12 PM
> *To: *"Zhang, Jing C. (Nokia - CA/Ottawa)"
> *Cc:
I'm seeing an identical issue to the one posted here a few months ago:
https://mail.openvswitch.org/pipermail/ovs-discuss/2018-October/047558.html
- I'll include the bug report template at the end.
The issue is an ovs-vswitchd thread consuming 100% CPU in a very lightly
used Openstack Rocky cloud
On Thu, May 2, 2019 at 6:04 PM Zhang, Jing C. (Nokia - CA/Ottawa) <
jing.c.zh...@nokia.com> wrote:
>
> We (our VNFs) continue to observe the same empty payload TCP (ACK) packet
drop with native firewall (see original post below) after upgrading to
Centos 7.6. This packet drop results in unacceptabl
We (our VNFs) continue to observe the same empty payload TCP (ACK) packet drop
with native firewall (see original post below) after upgrading to Centos 7.6.
This packet drop results in unacceptable TCP performance, by that native
firewall still can not be enabled in product.
https://mail.openvs
> On May 2, 2019, at 1:05 PM, Daniel H wrote:
>
> In the manual of ovs-dpctl it says:
>
> [...]
> "missed" displays the number of packets not matching any existing flow and
> require user space processing.
> "lost" displays number of packets destined for user space process but
> subsequentl
In the manual of ovs-dpctl it says:
[...]
"missed" displays the number of packets not matching any existing flow and require user space processing.
"lost" displays number of packets destined for user space process but subsequently dropped before reaching userspace.
[...]
I have the foll
OK.
The problem here is conceptual. br0 is just a port on your virtual
switch. It isn't along the path of your packet. It's like
disconnecting the Ethernet cable from the management port of a physical
switch: it doesn't disable traffic from flowing through the other ports.
On Thu, May 02, 2019
I am pinging from another server connected to the same switch. I can ping
from inside of an LXC container > br0 > eth0 > physical switch > eth0 (on
the other server) > br0 (on the other server) > an LXC container (on the
other server). I have done this from both servers and it goes through no
matte
Please stop dropping the mailing list. I don't help off-list.
On Thu, May 02, 2019 at 03:15:19PM -0500, Christopher Seeley wrote:
> That is the problem. It's not the wrong traffic, just getting traffic when
> the bridge is supposed to be down. Does an Open-vSwitch ever come down? The
> interface
On Thu, May 02, 2019 at 04:44:42PM -0300, Flavio Leitner via discuss wrote:
> On Tue, Apr 30, 2019 at 04:50:48PM -0700, Ben Pfaff wrote:
> > On Fri, Apr 26, 2019 at 11:52:22AM -0500, William Konitzer wrote:
> > > I'm reading
> > > (http://www.openvswitch.org/support/dist-docs/ovs-vswitchd.8.txt
> >
On Tue, Apr 30, 2019 at 04:50:48PM -0700, Ben Pfaff wrote:
> On Fri, Apr 26, 2019 at 11:52:22AM -0500, William Konitzer wrote:
> > I'm reading
> > (http://www.openvswitch.org/support/dist-docs/ovs-vswitchd.8.txt
> > section LIMITS) and it says "Performance will degrade beyond 1,024
> > ports per br
How is the ICMP traffic entering the system?
On Thu, May 02, 2019 at 09:13:42AM -0500, Christopher Seeley wrote:
> That would make sense, but the problem isn't different vlans coming
> through. When the bridge is down traffic is still flowing through it. The
> ovsdb is not updating the change in l
On Mon, Apr 29, 2019, 9:36 PM Aaron Conole wrote:
> Jaime Caamaño Ruiz writes:
>
> >> As a "security concern" you mean something among the lines where one
> >> of ovs-* processes running under openvswitch user would go ahead and
> >> create a file with its owner that later one of ovn processes w
13 matches
Mail list logo
