From owner-freebsd-bugs@freebsd.org Thu Jun 29 10:21:32 2017 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C51E0D9921F for ; Thu, 29 Jun 2017 10:21:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3BBBD7ECD3 for ; Thu, 29 Jun 2017 10:21:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v5TALU9i001869 for ; Thu, 29 Jun 2017 10:21:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 220351] Path MTU discovery works only after resetting an internal interface MTU (mpd5, ng_nat, ipfw) Date: Thu, 29 Jun 2017 10:21:30 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: la5lbtyi@aon.at X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jun 2017 10:21:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220351 Bug ID: 220351 Summary: Path MTU discovery works only after resetting an internal interface MTU (mpd5, ng_nat, ipfw) Product: Base System Version: 11.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: la5lbtyi@aon.at Scenario: =3D=3D=3D=3D=3D=3D=3D=3D=3D I am using the following setup to connect a home network to the ISP: - mpd5 with "set iface enable nat" (so that mpd5 uses ng_nat) - ipfw - RFC1918 internal address range - FreeBSD 11.0 as border router running mpd5 and ipfw - FreeBSD 11.0 internal machine. - The internal network is wired Ethernet (100baseTX for the border router, 1000baseT for the internal machine), MTU 1500. Due to this setup, ipfw sees only the NATted addresses and is not concerned with NATting itself. Ipfw is configured to allow icmptypes 0,3,4,11,12 in and 3,8,11,12 out. Recently, the provider changed from PPPoA to PPPoE. This means that now the= MTU on the link to the provider is 1492 instead of 1500. In mpd5, I now have 's= et link mtu 1492; set link mru 1492'. Before that change, the problem described below in this PR did not occur. Scenario 1 (good): =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Running svn, git, and rsync from the border router to machines on the Inter= net works. Scenario 2 (problem): =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Running svn, git, and rsync from the internal machine to machines on the Internet nearly never works (maybe one out of 20). However, if I manually set the internal machine's Ethernet I/F MTU to 1492 = and immediately thereafter reset it to 1500 all subsequent connections work flawlessly (ifconfig mtu 1492; ifconfig mtu 1500). Expected result: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Svn, git, and rsync connections from the internal machine to machines on the Internet should work right after boot. -- Martin --=20 You are receiving this mail because: You are the assignee for the bug.=