From owner-freebsd-net@freebsd.org Tue Sep 22 15:33:55 2020 Return-Path: Delivered-To: freebsd-net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 936423EC71B for ; Tue, 22 Sep 2020 15:33:55 +0000 (UTC) (envelope-from Michael.Tuexen@lurchi.franken.de) Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "Sectigo RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Bwlhf2zw4z49hc for ; Tue, 22 Sep 2020 15:33:54 +0000 (UTC) (envelope-from Michael.Tuexen@lurchi.franken.de) Received: from [IPv6:2a02:8109:1140:c3d:bdd6:362b:23a8:349b] (unknown [IPv6:2a02:8109:1140:c3d:bdd6:362b:23a8:349b]) (Authenticated sender: lurchi) by mail-n.franken.de (Postfix) with ESMTPSA id 3EDD27777F4A5; Tue, 22 Sep 2020 17:33:51 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\)) Subject: Re: IP reassembly From: Michael Tuexen In-Reply-To: <88c72056-42a7-f104-ab08-7532fc5f649f@grosbein.net> Date: Tue, 22 Sep 2020 17:33:50 +0200 Cc: "freebsd-net@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <88c72056-42a7-f104-ab08-7532fc5f649f@grosbein.net> To: Eugene Grosbein X-Mailer: Apple Mail (2.3608.120.23.2.1) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-Rspamd-Queue-Id: 4Bwlhf2zw4z49hc X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of Michael.Tuexen@lurchi.franken.de has no SPF policy when checking 193.175.24.27) smtp.mailfrom=Michael.Tuexen@lurchi.franken.de X-Spamd-Result: default: False [-0.47 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[franken.de]; ARC_NA(0.00)[]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-0.89)[-0.894]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.02)[-0.021]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-0.86)[-0.857]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:680, ipnet:193.174.0.0/15, country:DE]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-net]; RCVD_IN_DNSWL_LOW(-0.10)[193.175.24.27:from] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2020 15:33:55 -0000 > On 22. Sep 2020, at 14:40, Eugene Grosbein 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"