Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp3994396ybl; Mon, 26 Aug 2019 03:55:50 -0700 (PDT) X-Google-Smtp-Source: APXvYqxJuWe+0eY7EBJ3fq9nbepQd+1Cbi8hsXf3SoeMhlu3kHYr84Qjibvd5ScBoWePN7/i9ryM X-Received: by 2002:a17:902:b413:: with SMTP id x19mr18735323plr.121.1566816950106; Mon, 26 Aug 2019 03:55:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566816950; cv=none; d=google.com; s=arc-20160816; b=Npv1z+h8t8F0ab73cfpp0bYvLqr2ay0cMxsOwC0W74lxLm8GFFvr+HHEmlanyPUUM0 vNaHvzoX//Cmi6LdpdzR8aBQAmMXrBCCgY8VQKgOxaPZHYklF3Wj+CaX/bn8gvfMZ2kQ cFnz0SrUrAP7mhzhQDTAuiVsDANkL6Raps9qO8Uggsd8LsMjGL5i4ggoACpm81DBvMdd Do8kdo4DXFP3dTzccq1l1KPiHIkV9bShLsuB3AlXM3HVX8Gi1yIjOXHiEjuhYrfU+cJY FVJb1mU3yeh+BZSqU5BblAhMBLeCD6Bb3jE2/Zb5PpZZNjFUBqDzN4IKRYGAQI4Qj2nw TE0w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=ww9vwKNvxJDsYIK0QN99CcmT8UepRfj8PTDMl97+Oak=; b=M5Ph1TZQC7FubbwJ+991nCV1v48IihOg3KYHGe3Xxh74GunCaHZMYW9wbTHIqtz59I ZZFhOrnzZ7jexxkD22Bq+V/Dxo5wlNlz32hmPB0b7tzaP4KyOCuHfxbv+QwIH+NzK21u /Zw6mNUIP9cSSOZ58k5022H/Cq1bBiyR+q+6Hvq8MIncqWhpBz5t+VpqJ3zqS3W875Bl oayfwkfPcKZX9+cuOqX/2oOaPLGjAm2gWU7bR/36bczezdiFkB0tUiWteyqi3ttZyx41 wLF+bpi1JyOwmACzVEMgUWqFy9hNYtqBYaPBghBkcKm+lhbNvdeTWUdgZcqFV8PKjznb Qo4Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m7si9138733pls.110.2019.08.26.03.55.34; Mon, 26 Aug 2019 03:55:50 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730306AbfHZIJZ (ORCPT + 99 others); Mon, 26 Aug 2019 04:09:25 -0400 Received: from a3.inai.de ([88.198.85.195]:35764 "EHLO a3.inai.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728168AbfHZIJZ (ORCPT ); Mon, 26 Aug 2019 04:09:25 -0400 X-Greylist: delayed 590 seconds by postgrey-1.27 at vger.kernel.org; Mon, 26 Aug 2019 04:09:24 EDT Received: by a3.inai.de (Postfix, from userid 25121) id 80EC73BB696A; Mon, 26 Aug 2019 09:59:33 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by a3.inai.de (Postfix) with ESMTP id 7FE983BB6EEC; Mon, 26 Aug 2019 09:59:33 +0200 (CEST) Date: Mon, 26 Aug 2019 09:59:33 +0200 (CEST) From: Jan Engelhardt To: Florian Westphal cc: Rundong Ge , davem@davemloft.net, kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org, netdev@vger.kernel.org, pablo@netfilter.org, kadlec@netfilter.org, roopa@cumulusnetworks.com, netfilter-devel@vger.kernel.org, coreteam@netfilter.org, bridge@lists.linux-foundation.org, nikolay@cumulusnetworks.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH] bridge:fragmented packets dropped by bridge In-Reply-To: <20190730123542.zrsrfvcy7t2n3d4g@breakpoint.cc> Message-ID: References: <20190730122534.30687-1-rdong.ge@gmail.com> <20190730123542.zrsrfvcy7t2n3d4g@breakpoint.cc> User-Agent: Alpine 2.21 (LSU 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday 2019-07-30 14:35, Florian Westphal wrote: >Rundong Ge wrote: >> Given following setup: >> -modprobe br_netfilter >> -echo '1' > /proc/sys/net/bridge/bridge-nf-call-iptables >> -brctl addbr br0 >> -brctl addif br0 enp2s0 >> -brctl addif br0 enp3s0 >> -brctl addif br0 enp6s0 >> -ifconfig enp2s0 mtu 1300 >> -ifconfig enp3s0 mtu 1500 >> -ifconfig enp6s0 mtu 1500 >> -ifconfig br0 up >> >> multi-port >> mtu1500 - mtu1500|bridge|1500 - mtu1500 >> A | B >> mtu1300 > >How can a bridge forward a frame from A/B to mtu1300? There might be a misunderstanding here judging from the shortness of this thread. I understood it such that the bridge ports (eth0,eth1) have MTU 1500, yet br0 (in essence the third bridge port if you so wish) itself has MTU 1300. Therefore, frame forwarding from eth0 to eth1 should succeed, since the 1300-byte MTU is only relevant if the bridge decides the packet needs to be locally delivered.