Date: Tue, 22 Sep 2020 17:33:50 +0200 From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de> To: Eugene Grosbein <eugen@grosbein.net> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: IP reassembly Message-ID: <CF9FAFF4-1E26-4632-810E-4A04D987ED92@lurchi.franken.de> In-Reply-To: <88c72056-42a7-f104-ab08-7532fc5f649f@grosbein.net> References: <88c72056-42a7-f104-ab08-7532fc5f649f@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 22. Sep 2020, at 14:40, Eugene Grosbein <eugen@grosbein.net> wrote: >=20 > Hi! >=20 > Is our IP reassembly facility supposed to handle incoming out-of-order = fragments? > For example, IPIP packet created with gif(4) interface is fragmented = with two parts, > and parts are delivered out of order, last fragment comes first. I would expect it to work without any assumptions on the sequence of = arrival of the fragments. Best regards Michael >=20 > In fact, I see this results in broken reassembly. > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CF9FAFF4-1E26-4632-810E-4A04D987ED92>