Hi all the list. Seen what is blocking !
Again eth0 stopped after few hours running. But, this time, I have a little "investigate" around this big problem of reliability. See ip route before accident : 212.180.0.144 dev ppp0 proto kernel scope link src 212.180.113.45 212.180.0.144 dev ipsec0 proto kernel scope link src 212.180.113.45 44.151.177.64/27 dev wlan0 proto kernel scope link src 44.151.177.94 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.254 192.168.77.0/24 via 212.180.0.144 dev ipsec0 44.0.0.0/8 via 212.180.0.144 dev ipsec0 default via 212.180.0.144 dev ppp0 See ip route after accident : 212.180.0.144 dev ipsec0 proto kernel scope link src 212.180.113.45 212.180.0.144 dev ppp0 proto kernel scope link src 212.180.113.45 44.151.177.64/27 dev wlan0 proto kernel scope link src 44.151.177.94 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.254 192.168.77.0/24 via 212.180.0.144 dev ipsec0 44.0.0.0/8 via 212.180.0.144 dev ipsec0 default via 212.180.0.144 dev ipsec0 As you can read, default route has switched from ppp0 to ipsec0 ! I don't know why, but this could be why only few Bering users have this problem. May be Ipsec users only have it... What is happening with this defaul route ? I am not able to resolve this alone. Probably some Bering developers can help us ? To be continued ;-) Best Regards, Francois BERGERET, France. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
