Dear Leaf Users and developpers, Always searching how to resolve this problem... We are several to have it and not read any solution to correct it. For now, I can say that when this problem occures, the "manual" solution, excepting a complete reboot of my Soekris/Bering card, is to delete the default route, which have switched curiously from ppp0 to ipsec0, and to add a new default route assigning ppp0 again ! And Bering works again, always alive !
So, how can I do that automaticaly ? May be this occures with a little drop of my IPS link ? If yes, just to survey the up/down of ppp0 and del/add default route systematicaly when ppp0 is up again could resolve this ? But, to do that correctly, how to assign the IP address of mu ISP gateway which is not always the same at each PPPoE connection ? I have tempt an idiot command with %defaultroute, but, this variable seems to be not authorized at this place... What could be the correct solution ? Any idea guys ? Best Regards, Francois BERGERET, France. > -----Message d'origine----- > De : [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] la part de Francois > BERGERET > Envoy� : dimanche 7 septembre 2003 18:14 > � : [EMAIL PROTECTED] > Objet : RE: [leaf-user] Bering lost it's NICs > > > 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 > ------------------------------------------------------- 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
