Well, it's hard to know, since your description doesn't describe your topology,
configuration, etc. That said, I guess I would start with tcpdump or flow
counts to see where packets appear to be getting dropped and why.
--Justin
> On May 25, 2017, at 6:03 PM, Gale Price
Where would you suggest I start looking?
Sent from my iPhone
> On May 25, 2017, at 8:39 PM, Justin Pettit wrote:
>
>
>> On May 25, 2017, at 11:11 AM, Gale Price wrote:
>>
>> I am using ovs on a Fedora 20 KVM Host with 6 defined vlans
>>
>> I am having a
> On May 25, 2017, at 11:11 AM, Gale Price wrote:
>
> I am using ovs on a Fedora 20 KVM Host with 6 defined vlans
>
> I am having a problem where when I stop any VM I lose connectivity to all
> other VM’s for about 6-7 Pings.
> Then everything starts working again.
>
>
> On May 25, 2017, at 2:08 PM, Пономарёв Вадим wrote:
>
> Hi all.
>
> I am setting up a network node for the OpenStack cluster (mitaka) in the
> classic scenario with OpenvSwitch
>
On Thu, May 25, 2017 at 10:26:29AM -0700, Justin Pettit wrote:
>
> > On May 25, 2017, at 2:10 AM, Avi Cohen (A) wrote:
> >
> > Hi All,
> > I need to capture all received SYN packets from all interfaces and to
> > mirror/output to a specific interface in addition to the
Hi Aaron
Thanks
I see there are 2 approaches as mentioned by you
1. Regarding the first I assume u mean creating another netns and creating
peers between ethwan1 and veth1
Say we have another netns lying outside ovs whose one interface (say veth1
lying inside netns test) is linked to ovs
Hi All,
I need to capture all received SYN packets from all interfaces and to
mirror/output to a specific interface in addition to the operational interface
that these packets should be forwarded.
Can I do it with a single dpctl add-flow cli command ? and not modify the
'operational' flows
I found this article very relevant to this issue:
http://porto.polito.it/2616822/1/2015_Chain_performance.pdf
especially it says that for the vhost-net interface used for standard OVS:
"the transmission of a batch of packets
from a VM causes a VM exit; this means that the CPU stops to