Date: Wed, 10 Mar 2010 13:01:06 -0500 From: John Baldwin <jhb@freebsd.org> To: obrien@freebsd.org Cc: svn-src-head@freebsd.org, Qing Li <qingli@freebsd.org>, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r204902 - in head/sys: net netinet Message-ID: <201003101301.06583.jhb@freebsd.org> In-Reply-To: <20100310160858.GC58634@dragon.NUXI.org> References: <201003090111.o291Bj79062503@svn.freebsd.org> <201003101050.46696.jhb@freebsd.org> <20100310160858.GC58634@dragon.NUXI.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 10 March 2010 11:08:58 am David O'Brien wrote: > On Wed, Mar 10, 2010 at 10:50:46AM -0500, John Baldwin wrote: > > On Wednesday 10 March 2010 10:23:39 am David O'Brien wrote: > > > Hi Qing, > > > > > > This change doesn't seem to work in the common case, and has made the > > > kernel toxic - with folks unable to connect to 127.0.0.1. Please back > > > this out or adjust the change. > > > > Did you try the route.h patch he posted to current@? > > I looked at it, and at the diff of his original commit. The changes were > large enough that I don't want to assume his patch takes care of all the > issues given that patch hasn't been committed verbatim. > > We also have reports of the patch not working in freebsd-current@. The reports have all said that the patch fixes pinging 127.0.0.1. The one problem report is a different situation involving a VPN tunnel. Just patch your system with the route.h patch for now. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201003101301.06583.jhb>