On 18/04/14 02:42, Jarno Rajahalme wrote:
On Apr 17, 2014, at 11:26 AM, Zoltan Kiss wrote:
On 16/04/14 18:00, Justin Pettit wrote:
On April 16, 2014 at 9:00:15 AM, Zoltan Kiss (zoltan.k...@citrix.com) wrote:
My actual problem is that an important rule gets deleted:
cookie=0x0, duration=15
On Apr 17, 2014, at 11:26 AM, Zoltan Kiss wrote:
> On 16/04/14 18:00, Justin Pettit wrote:
>> On April 16, 2014 at 9:00:15 AM, Zoltan Kiss (zoltan.k...@citrix.com) wrote:
>>
>>> My actual problem is that an important rule gets deleted:
>>>
>>> cookie=0x0, duration=1581.083s, table=0, n_packets
On 16/04/14 18:00, Justin Pettit wrote:
On April 16, 2014 at 9:00:15 AM, Zoltan Kiss (zoltan.k...@citrix.com) wrote:
My actual problem is that an important rule gets deleted:
cookie=0x0, duration=1581.083s, table=0, n_packets=52804,
n_bytes=88968151, idle_age=0, priority=0,in_port=ANY actions=
On April 16, 2014 at 9:00:15 AM, Zoltan Kiss (zoltan.k...@citrix.com) wrote:
> To elaborate a bit more: now I figured out that normally the controller
> should take care of removing OpenFlow rules when the port is deleted. I
> thought ovs-vswitchd checks the tables for any reference to the deleted
To elaborate a bit more: now I figured out that normally the controller
should take care of removing OpenFlow rules when the port is deleted. I
thought ovs-vswitchd checks the tables for any reference to the deleted
port, but it seems it doesn't.
My actual problem is that an important rule gets
Hi,
I came accross a problem recently, where the destroying of a VM's port
(with ovs-vsctl del-port) seems to blow away other OpenFlow rules from
the userspace. It seems to me logical for ovs-vswitchd to delete the
associated OpenFlow rules when the port is deleted, but I couldn't find
in the
