> > This error was caused by my commit r204902 from yesterday. > > Please try patch at > > http://people.freebsd.org/~qingli/route.h.diff > The route.h.diff patch warrants some explanation. What I did here is basically excluding "if_link_state" checks against loopback interfaces and point-to-point interfaces. The loopback interface does not modify this variable and conceptually it is always up. The bug was due to the check was also performed on the loopback interface, and broke all self destined traffic (127.0.0.1 and all local IPs). The route.h.diff fixes this bug. The story for the point-to-point interfaces is slightly different. For example, if_tun interface updates the if_link_state but I am not sure about the other ppp pseudo interface. By excluding the PPP interfaces from the link state check, the behavior may be when ECMP is enabled and a PPP link is actually down, traffic would go into blackhole, but that's exactly the current behavior. So with r204902 and ECMP enabled, you can failover and load-balance across physical interfaces and those dependent interface types such as if_vlan and if_lagg, but not PPP link types (for now, which I will fix in time). Your comments are welcome. -- Qing > > > > -----Original Message----- > > From: owner-freebsd-current_at_freebsd.org [mailto:owner-freebsd- > > current_at_freebsd.org] On Behalf Of Li, Qing > > Sent: Tuesday, March 09, 2010 11:05 AM > > To: Renato Botelho; FreeBSD Current > > Subject: RE: Error 127.0.0.1: no route to host > > > > Thanks for the report, I am looking at it and will get back to you. > > > > -- Qing > > > > > > > -----Original Message----- > > > From: owner-freebsd-current_at_freebsd.org [mailto:owner-freebsd- > > > current_at_freebsd.org] On Behalf Of Renato Botelho > > > Sent: Tuesday, March 09, 2010 10:47 AM > > > To: FreeBSD Current > > > Subject: Error 127.0.0.1: no route to host > > > > > > I updated my 9.0-current amd64 today on rev. 204915 and start > > > to get errors like this > > > > > > 127.0.0.1: no route to host > > > > > > I boot using kernel.old and everything back to normal. I don't know > > > exactly revision of my kernel.old because last change made on > > > sys/conf/newvers.sh simply removed this information from my > > > uname, see: > > > > > > FreeBSD botelhor.bplab.local 9.0-CURRENT FreeBSD 9.0-CURRENT #1: > Mon > > > Mar 8 15:52:59 BRT 2010 > > > root_at_botelhor.bplab.local:/usr/obj/usr/src/sys/GARGA amd64 > > > > > > I just know it was built yesterday about 18:00 UTC > > > > > > Is there any other way to get this information? > > > > > > Let me know if you need more information about my environment. > > > > > > Regards > > > -- > > > Renato Botelho > > > _______________________________________________ > > > freebsd-current_at_freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > To unsubscribe, send any mail to "freebsd-current- > > > unsubscribe_at_freebsd.org" > > _______________________________________________ > > freebsd-current_at_freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current- > > unsubscribe_at_freebsd.org" > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current- > unsubscribe_at_freebsd.org"Received on Wed Mar 10 2010 - 18:17:03 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:01 UTC