> On Mon, Jun 22, 2020 at 5:02 AM Lorenzo Bianconi wrote:
> >
> > > On Fri, Jun 19, 2020 at 4:48 AM Lorenzo Bianconi
> > > wrote:
> > > >
> > > > ovs connection tracking module performs de-fragmentation on incoming
> > > > fragmented traffic. Take info account if traffic has been de-fragmented
>
On Mon, Jun 22, 2020 at 5:02 AM Lorenzo Bianconi wrote:
>
> > On Fri, Jun 19, 2020 at 4:48 AM Lorenzo Bianconi wrote:
> > >
> > > ovs connection tracking module performs de-fragmentation on incoming
> > > fragmented traffic. Take info account if traffic has been de-fragmented
> > > in execute_che
> On Fri, Jun 19, 2020 at 4:48 AM Lorenzo Bianconi wrote:
> >
> > ovs connection tracking module performs de-fragmentation on incoming
> > fragmented traffic. Take info account if traffic has been de-fragmented
> > in execute_check_pkt_len action otherwise we will perform the wrong
> > nested acti
On Fri, Jun 19, 2020 at 4:48 AM Lorenzo Bianconi wrote:
>
> ovs connection tracking module performs de-fragmentation on incoming
> fragmented traffic. Take info account if traffic has been de-fragmented
> in execute_check_pkt_len action otherwise we will perform the wrong
> nested action consideri
ovs connection tracking module performs de-fragmentation on incoming
fragmented traffic. Take info account if traffic has been de-fragmented
in execute_check_pkt_len action otherwise we will perform the wrong
nested action considering the original packet size. This issue typically
occurs if ovs-vsw
