Date: Tue, 12 Dec 2017 10:02:20 -0800 (PST) From: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> To: Eugene Grosbein <eugen@grosbein.net> Cc: Jan Bramkamp <crest@rlwinm.de>, freebsd-net@freebsd.org Subject: Re: Changes to route(8) or routing between r325235 and r326782? Message-ID: <201712121802.vBCI2KTc087491@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <5A2FF94F.4080404@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[ 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201712121802.vBCI2KTc087491>