From owner-freebsd-net@freebsd.org Tue Dec 12 20:24:44 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 B75FEE8388E for ; Tue, 12 Dec 2017 20:24:44 +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 8E2CF71082 for ; Tue, 12 Dec 2017 20:24:44 +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 vBCKOh71088254; Tue, 12 Dec 2017 12:24:43 -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 vBCKOh18088253; Tue, 12 Dec 2017 12:24:43 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201712122024.vBCKOh18088253@pdx.rh.CN85.dnsmgr.net> Subject: Re: Changes to route(8) or routing between r325235 and r326782? In-Reply-To: <5A303832.6030909@grosbein.net> To: Eugene Grosbein Date: Tue, 12 Dec 2017 12:24:43 -0800 (PST) CC: sthaug@nethelp.no, freebsd-net@freebsd.org, crest@rlwinm.de 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Dec 2017 20:24:44 -0000 > On 13.12.2017 03:00, Rodney W. Grimes wrote: > > >> If I want something more complicated (typically BGP) I'll install > >> quagga. > > > > One of the problems now is that these programs are fighting with > > the kernel over these routes and just fill your logs with lots > > of useless messages and you can not reliably predict the loop > > back routes even if you ARE running a routing protocol daemon. > > quagga does not do that. It plays nice with our kernel. I believe quagga silently ignores that it doesnt own the route it tried to install and bangs on the route socket, but maybe that got fixed. > > > I also find it hillarious that the code emits a bogous console > > message when I down an interface that it could not delete the > > loopback route > > This is already fixed. In what commit? -- Rod Grimes rgrimes@freebsd.org