From owner-svn-src-all@freebsd.org Fri May 11 03:19:25 2018 Return-Path: Delivered-To: svn-src-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9314CFB2199; Fri, 11 May 2018 03:19:25 +0000 (UTC) (envelope-from freebsd@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E975077F22; Fri, 11 May 2018 03:19:24 +0000 (UTC) (envelope-from freebsd@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w4B3JGLd073463; Thu, 10 May 2018 20:19:16 -0700 (PDT) (envelope-from freebsd@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w4B3JGBv073462; Thu, 10 May 2018 20:19:16 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <201805110319.w4B3JGBv073462@pdx.rh.CN85.dnsmgr.net> Subject: Re: svn commit: r333476 - head/sys/net In-Reply-To: <86h8nfvtbk.fsf@next.des.no> To: =?UTF-8?Q?Dag-Erling_Sm=C3=B8rgrav?= Date: Thu, 10 May 2018 20:19:16 -0700 (PDT) CC: rgrimes@freebsd.org, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Reply-To: rgrimes@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 May 2018 03:19:25 -0000 [ Charset UTF-8 unsupported, converting... ] > "Rodney W. Grimes" writes: > > I do no need or want these routes created by this mechanism on my > > FreeBSD based routers, they only ever existed originally to use the > > MTU of the lo0 interface for things that wrongly open an IP address of > > an interface rather than 127.0.0.1. > > I'm not sure I understand enough of this to make an informed decision. > Are you saying they serve no practical purpose ever on current systems? > > These are the entries that route all traffic to any of our own addresses > over lo0, right? Like the bottom four here? Correct. > des@hive ~% netstat -4rn | grep -w lo0 > 127.0.0.1 link#2 UH lo0 > 192.168.144.15 link#1 UHS lo0 > 192.168.144.16 link#1 UHS lo0 > 192.168.144.19 link#1 UHS lo0 > 192.168.144.30 link#1 UHS lo0 > > I'm going to try a kernel with that code #ifdefed out... We did this back in the day so if you make a connection to your own IP (your 4 addresses above) then you use the MTU of lo0, which is usually 16k, instead of the MTU of the interface, which is usually 1500, or back in the day of SLIP was often 296. Eugene Grosbein says there is some use case for it where he has lots of tunX devices, but I just can not seem to understand why or what it is that he is doing that requires these routes. IIRC Linux has never had these routes. If you go back in the history of svn and read whey this was originally added it was to compensate for the fact that you lost the /etc/rc installed route if you did an if down/up, which is actually expected behavior, you loose ALL routes associtated with the IP of an interface if you down it. The CURRENT code makes it possible for you to ping the IP of a DOWNED interface due to this now silly lo0 route, just more demonstration of how wrong this idea is. This was caused by the addition of pinning these routes so that they stay in effect even when you down the interface. -- Rod Grimes rgrimes@freebsd.org