Hi Dumitru, Numan,
I’ve sent a corresponding patch to openvswitch with my findings.
It’d be great if you can take a look on it.
Thanks.
https://patchwork.ozlabs.org/project/openvswitch/patch/20211126205942.9354-1-odiv...@gmail.com/
Regards,
Vladislav Odintsov
> On 21 Sep 2021, at 14:43,
On 9/21/21 1:33 PM, Vladislav Odintsov wrote:
> Hi Dumitru,
Hi Vladislav,
>
> are you talking about any specific _mising_ patch?
No, sorry for the confusion. I just meant there's a bug in the OOT
module that was probably already fixed in the in-tree one so, likely,
one would have to figure
Hi Dumitru,
are you talking about any specific _mising_ patch?
Regards,
Vladislav Odintsov
> On 16 Sep 2021, at 19:09, Dumitru Ceara wrote:
>
> On 9/16/21 4:18 PM, Vladislav Odintsov wrote:
>> Sorry, by OOT I meant non-inbox kmod.
>> I’ve tried to use inbox kernel module (from kernel package)
On 9/16/21 4:18 PM, Vladislav Odintsov wrote:
> Sorry, by OOT I meant non-inbox kmod.
> I’ve tried to use inbox kernel module (from kernel package) and problem
> resolved.
>
> Regards,
> Vladislav Odintsov
>
>> On 16 Sep 2021, at 17:17, Vladislav Odintsov wrote:
>>
>> Hi Dumitru,
>>
>> I’ve
Sorry, by OOT I meant non-inbox kmod.
I’ve tried to use inbox kernel module (from kernel package) and problem
resolved.
Regards,
Vladislav Odintsov
> On 16 Sep 2021, at 17:17, Vladislav Odintsov wrote:
>
> Hi Dumitru,
>
> I’ve tried to exclude OOT OVS kernel module.
> With OVN 20.06.3 + OVS
Hi Dumitru,
I’ve tried to exclude OOT OVS kernel module.
With OVN 20.06.3 + OVS 2.13.4 the problem solved.
Could you please try with OOT kmod? For me it looks like a bug in OOT OVS
kernel module code.
Thanks.
Regards,
Vladislav Odintsov
> On 16 Sep 2021, at 11:02, Dumitru Ceara wrote:
>
>
On 9/16/21 2:50 AM, Vladislav Odintsov wrote:
> Hi Dumitru,
>
> thanks for your reply.
>
> Regards,
> Vladislav Odintsov
>
>> On 15 Sep 2021, at 11:24, Dumitru Ceara wrote:
>>
>> Hi Vladislav,
>>
>> On 9/13/21 6:14 PM, Vladislav Odintsov wrote:
>>> Hi Numan,
>>>
>>> I’ve checked with OVS
Hi Dumitru,
thanks for your reply.
Regards,
Vladislav Odintsov
> On 15 Sep 2021, at 11:24, Dumitru Ceara wrote:
>
> Hi Vladislav,
>
> On 9/13/21 6:14 PM, Vladislav Odintsov wrote:
>> Hi Numan,
>>
>> I’ve checked with OVS 2.16.0 and OVN master. The problem persists.
>> Symptoms are the same.
Hi Vladislav,
On 9/13/21 6:14 PM, Vladislav Odintsov wrote:
> Hi Numan,
>
> I’ve checked with OVS 2.16.0 and OVN master. The problem persists.
> Symptoms are the same.
>
> # grep ct_zero_snat /var/log/openvswitch/ovs-vswitchd.log
>
Hi Numan,
I’ve checked with OVS 2.16.0 and OVN master. The problem persists.
Symptoms are the same.
# grep ct_zero_snat /var/log/openvswitch/ovs-vswitchd.log
2021-09-13T16:10:01.792Z|00019|ofproto_dpif|INFO|system@ovs-system: Datapath
supports ct_zero_snat
Regards,
Vladislav Odintsov
> On 13
On Mon, Sep 13, 2021 at 8:10 AM Vladislav Odintsov wrote:
>
> Hi,
>
> we’ve encountered a next problem with stateful ACLs.
>
> Suppose, we have one logical switch (ls1) and attached to it a VIF type
> logical ports (lsp1, lsp2).
> Each logical port has a linux VM besides it.
>
> Logical ports
There’s a typo in my previous mail. Please, see inline fix.
Regards,
Vladislav Odintsov
> On 13 Sep 2021, at 15:09, Vladislav Odintsov wrote:
>
> Hi,
>
> we’ve encountered a next problem with stateful ACLs.
>
> Suppose, we have one logical switch (ls1) and attached to it a VIF type
>
Hi,
we’ve encountered a next problem with stateful ACLs.
Suppose, we have one logical switch (ls1) and attached to it a VIF type logical
ports (lsp1, lsp2).
Each logical port has a linux VM besides it.
Logical ports reside in port group (pg1) and two ACLs are created within this
PG:
to-lport
13 matches
Mail list logo
