From owner-freebsd-net@freebsd.org  Tue Dec 12 18:02:22 2017
Return-Path: <owner-freebsd-net@freebsd.org>
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 B5FB9EA0A49
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Tue, 12 Dec 2017 18:02:22 +0000 (UTC)
 (envelope-from freebsd-rwg@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 7D2C568848
 for <freebsd-net@freebsd.org>; Tue, 12 Dec 2017 18:02:22 +0000 (UTC)
 (envelope-from freebsd-rwg@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 vBCI2KFm087492;
 Tue, 12 Dec 2017 10:02:20 -0800 (PST)
 (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net)
Received: (from freebsd-rwg@localhost)
 by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id vBCI2KTc087491;
 Tue, 12 Dec 2017 10:02:20 -0800 (PST) (envelope-from freebsd-rwg)
From: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net>
Message-Id: <201712121802.vBCI2KTc087491@pdx.rh.CN85.dnsmgr.net>
Subject: Re: Changes to route(8) or routing between r325235 and r326782?
In-Reply-To: <5A2FF94F.4080404@grosbein.net>
To: Eugene Grosbein <eugen@grosbein.net>
Date: Tue, 12 Dec 2017 10:02:20 -0800 (PST)
CC: Jan Bramkamp <crest@rlwinm.de>, freebsd-net@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: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Dec 2017 18:02:22 -0000

[ Charset windows-1252 unsupported, converting... ]
> 12.12.2017 22:15, Rodney W. Grimes wrote:
> 
> > The FreeBSD kernel now has a BIGGER bug, it now totally ignores the
> > user's specified routing policy and makes routing policy decissions
> > of its own, thinking that it knows what is best for the user.
> > 
> > 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.  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? 

If you say it is cause of its harder to filter, then
you are breaking everyone else cause you dont want to
do something right yourself.


-- 
Rod Grimes                                                 rgrimes@freebsd.org