Date: Fri, 11 May 2018 04:07:11 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: "Rodney W. Grimes" <freebsd@pdx.rh.CN85.dnsmgr.net> Cc: rgrimes@freebsd.org, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r333476 - head/sys/net Message-ID: <86h8nfvtbk.fsf@next.des.no> In-Reply-To: <201805110127.w4B1RoUT073114@pdx.rh.CN85.dnsmgr.net> (Rodney W. Grimes's message of "Thu, 10 May 2018 18:27:50 -0700 (PDT)") References: <201805110127.w4B1RoUT073114@pdx.rh.CN85.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
"Rodney W. Grimes" <freebsd@pdx.rh.CN85.dnsmgr.net> 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? 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... DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86h8nfvtbk.fsf>