Thank you for reply.
Unfortunately that staff happens be in product environment with >
200Mb/s outgoing trafic from virtual machines (XCP 1.1 with upgrade to
ovs1.4.3), so tcpdump is kinda impossible.
Some data on configuration:
no flow controller, some rules (antispoofing) are applied during
Hmm. Yesterday I looked over all of the datapath commits since version
1.4.3 and didn't see any bugfixes, not applied to branch-1.4, that would
account for this particular message. That means that this may be a
problem that we aren't yet aware of.
Unfortunately, this particular class of issue is
That happens in freshly installed ovs 1.4.3 :
ovs-ofctl --version
ovs-ofctl (Open vSwitch) 1.4.3
Compiled Oct 11 2012 11:08:37
OpenFlow versions 0x1:0x1
On 22.10.2012 23:28, Ben Pfaff wrote:
On Sat, Oct 20, 2012 at 04:03:18AM +0400, George Shuklin wrote:
After upgrading from ovs 1.0 to 1.4 o
On Sat, Oct 20, 2012 at 04:03:18AM +0400, George Shuklin wrote:
> After upgrading from ovs 1.0 to 1.4 on XCP 1.1 I found following
> message in log appears every 10-20min:
>
> Oct 20 03:37:42|00245|ofproto_dpif|WARN|unexpected flow from
> datapath
> in_port(1),eth(src=88:e0:f3:23:42:c0,dst=92:cf:
Good day.
After upgrading from ovs 1.0 to 1.4 on XCP 1.1 I found following message
in log appears every 10-20min:
Oct 20 03:37:42|00245|ofproto_dpif|WARN|unexpected flow from datapath
in_port(1),eth(src=88:e0:f3:23:42:c0,dst=92:cf:e9:66:a1:46),eth_type(0x0800),ipv4(src=122.226.56.20,dst=188.1
