Introduce a post_defrag router ingress pipeline stage and move current defrag
code in post_defrag stage. This is a preliminary patch to just defrag IP
fragment traffic (without performing DNAT) before accessing L4 info (e.g.
L4 protocol port) since they are not available in all IP fragment.
Signed
Bleep bloop. Greetings Lorenzo Bianconi, I am a robot and I have tried out
your patch.
Thanks for your contribution.
I encountered some error that I wasn't expecting. See the details below.
checkpatch:
WARNING: Line is 101 characters long (recommended limit is 79)
#69 FILE: northd/northd.c:32
On Mon, Feb 27, 2023 at 02:52:53PM +0100, Lorenzo Bianconi wrote:
> Introduce a post_defrag router ingress pipeline stage and move current defrag
> code in post_defrag stage. This is a preliminary patch to just defrag IP
> fragment traffic (without performing DNAT) before accessing L4 info (e.g.
>
On Wed, Mar 8, 2023 at 6:45 AM Simon Horman wrote:
>
> On Mon, Feb 27, 2023 at 02:52:53PM +0100, Lorenzo Bianconi wrote:
> > Introduce a post_defrag router ingress pipeline stage and move current
> > defrag
> > code in post_defrag stage. This is a preliminary patch to just defrag IP
> > fragment
On Fri, Mar 17, 2023 at 5:35 PM Numan Siddique wrote:
>
> On Wed, Mar 8, 2023 at 6:45 AM Simon Horman wrote:
> >
> > On Mon, Feb 27, 2023 at 02:52:53PM +0100, Lorenzo Bianconi wrote:
> > > Introduce a post_defrag router ingress pipeline stage and move current
> > > defrag
> > > code in post_defr
