From owner-freebsd-net@freebsd.org Tue Dec 12 18:11:00 2017 Return-Path: Delivered-To: freebsd-net@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 408CFEA128B for ; Tue, 12 Dec 2017 18:11:00 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C498D691F9 for ; Tue, 12 Dec 2017 18:10:59 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id vBCIAslZ018081 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 12 Dec 2017 19:10:55 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: freebsd-rwg@pdx.rh.CN85.dnsmgr.net Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTP id vBCIAoJO075281; Wed, 13 Dec 2017 01:10:50 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Changes to route(8) or routing between r325235 and r326782? To: "Rodney W. Grimes" References: <201712121802.vBCI2KTc087491@pdx.rh.CN85.dnsmgr.net> Cc: Jan Bramkamp , freebsd-net@freebsd.org From: Eugene Grosbein Message-ID: <5A301BAA.8010509@grosbein.net> Date: Wed, 13 Dec 2017 01:10:50 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <201712121802.vBCI2KTc087491@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE, T_DATE_IN_FUTURE_96_Q autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 0.0 T_DATE_IN_FUTURE_96_Q Date: is 4 days to 4 months after Received: * date * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-Spam-Level: ** X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 12 Dec 2017 18:11:00 -0000 On 13.12.2017 01:02, Rodney W. Grimes wrote: >>> The whole maintain_loopback_route should be KILLED from the kernel, >>> it is simply the wrong thing to be doing. >> >> Only if you can supply alternative way to assign highest priority >> (administrative distance = 0) for "directly connected" routes. >> And ability to override dynamically received prefixes with direct >> interface address assignment. > > This is all done by correctly configured routing daemon > running in userland over the route socket. Do we have such daemon maintaining directly connected routed in the base system? > Only being doing that for 25+ years that way, why suddenly does the > kernel need to over ride what has already been done and working? I cannot speak for 25+ years but I can for 17+ while there was NO way in FreeBSD to assign an address like 192.168.0.1/24 to an interface when such prefix already was installed to the kernel by routing daemon. Pinning loopback prefixes solved this problem at last.