On Wed, Mar 10, 2010 at 09:46:49AM -0800, Qing Li wrote: > > > > 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. > > The change itself is not a huge change but if you disagree, then > please be specific.
I'm not disagreeing. I'm saying you and others that have worked in the routing code are the best judge. > The current mechanism and code is broken according to the original > design intention. But able to ping 127.0.0.1. :-) > When you say > "... made the kernel toxic" and "...I don't want to assume ...", well, > again, be specific instead about what you mean and give me details. A stock kernel cannot ping 127.0.0.1. It is claimed there is no route to 127.0.0.1. David Wolfskill has the same problem, as have others in the freebsd-current@ mailing list. I don't know about others, but not being able to connect to 127.0.0.1 totally breaks my installation. -- -- David (obr...@freebsd.org) _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"