Re: [ovs-dev] [PATCH ovn v7 2/2] northd: Make the use of common zone in NAT configurable

On Thu, Apr 6, 2023 at 5:31 PM Ilya Maximets wrote: > On 4/6/23 16:53, Ales Musil wrote: > > > > > > On Thu, Apr 6, 2023 at 4:48 PM Ilya Maximets > wrote: > > > > On 4/6/23 16:37, Ales Musil wrote: > > > There are essentially three problems with the current >

Re: [ovs-dev] [PATCH ovn v7 2/2] northd: Make the use of common zone in NAT configurable

On 4/6/23 16:53, Ales Musil wrote: > > > On Thu, Apr 6, 2023 at 4:48 PM Ilya Maximets > wrote: > > On 4/6/23 16:37, Ales Musil wrote: > > There are essentially three problems with the current > > combination of DGP + SNAT + LB: > > > > 1) The

Re: [ovs-dev] [PATCH ovn v7 2/2] northd: Make the use of common zone in NAT configurable

On Thu, Apr 6, 2023 at 4:48 PM Ilya Maximets wrote: > On 4/6/23 16:37, Ales Musil wrote: > > There are essentially three problems with the current > > combination of DGP + SNAT + LB: > > > > 1) The first packet is being SNATed in common zone due > > to a problem with pinctrl not preserving

Re: [ovs-dev] [PATCH ovn v7 2/2] northd: Make the use of common zone in NAT configurable

On 4/6/23 16:37, Ales Musil wrote: > There are essentially three problems with the current > combination of DGP + SNAT + LB: > > 1) The first packet is being SNATed in common zone due > to a problem with pinctrl not preserving ct_mark/ct_label. > The commit would create a SNAT entry within the

[ovs-dev] [PATCH ovn v7 2/2] northd: Make the use of common zone in NAT configurable

There are essentially three problems with the current combination of DGP + SNAT + LB: 1) The first packet is being SNATed in common zone due to a problem with pinctrl not preserving ct_mark/ct_label. The commit would create a SNAT entry within the same with DNAT entry. 2) The unSNAT for reply