It happened to me again this weekend. This time on the new PC. Just as in Francois' case the default route changed. In my case it went from eth0 (connected to a cable modem) to ipsec0. There has to be some explanation for this behavior, and a way to keep it from happening.
Best Regards, Roger McClurg Reply-To: <[EMAIL PROTECTED]> From: "Francois BERGERET" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Subject: RE: [leaf-user] Bering lost it's NICs Date: Sat, 13 Sep 2003 21:38:26 +0200 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. ------------------------------------------------------- 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
