HI Erich, The idea about cron use is from our friend Jacques. I think that it is a good idea ;-) Cron is abble to launch any script at preset time interval (this is that I have understood) and I like this idea that something is always surveying what is happening with default route status.
I have seen the pointed message from FreeSWan's users list which I am a subscriber too. I don't like fixed values as IP address and Gateway... I have a french provider which often changes his gateways : he have 4 or 5 different gateways offered at each connection. It seems to be a strange thing but existing ! I prefear to check what is connected at the other side (ISP) because it is more universal for other friends configuration and I switch from time to time from another ISP's to do demonstrations to my HAM radio friends and other wireless communities, during hexibitions or other events. I have rewrited again end definitively the script, to avoid to repeat the instructions twice, if IP changes or gateway cheanges. Only one procedure loop is called now, minus lines. If any guy want it, I can post the final file. But, may be the better way is to do as this FreeSWan user, to modify the ip-up.local file to render it more universal without fixed IP and Gateway values ? Sure, this will avoid many cron.log lines input (one by minute) ;-) The main target is to resolve our default route lost, and, in the two cases, it is ok... What is the better way ? I don't know. Who can explain me what case is good or better ? I want to lurn Linux scripting art ! Best Regards, Francois BERGERET, France. > -----Message d'origine----- > De : Erich Titl [mailto:[EMAIL PROTECTED] > Envoyé : lundi 29 septembre 2003 00:55 > Ŕ : [EMAIL PROTECTED]; [EMAIL PROTECTED] > Objet : RE: [leaf-user] Modefied script RESOLVED : Bering lost it's NICs > > > Francois > > Interesting, only I am puzzled by the fact that you have to run this from > cron. > I am currently listening on the freeswan list and found something which > might interest you: > > <[EMAIL PROTECTED]> > ...... > I've never had this difficulty. I've lost 'net connectivity over my pppoe > connection thanks to a common difficulty: when pppoe disconnects/reconnects, > the ppp0 interface goes away and comes back. As a result, the virtual device > (ipsec0) becomes disconnected and needs to be re-attached. Plus, I've seen > issues with the default gateway route going away. > > Sounds complex, but the fix is simple. Here's a link to my copy of > /etc/ppp/ip-up.local. Note that you may need to alter the interface names > (ppp0/ipsec0) and the IP address of your default gateway, if this turns out > to be useful to you. > > http://raven.crowgirl.com/ip-up.local > ...... > </[EMAIL PROTECTED]> > > Erich > > At 16:17 28.09.2003, Francois BERGERET wrote: > >Hi all the list. > > > >I have added IPSec restart in the script, because it seems not to work > >well without it at each time. > >Sorry ! > >Now, it seems to be ok. > > THINK > Püntenstrasse 39 > 8143 Stallikon > mailto:[EMAIL PROTECTED] > PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16 > > ------------------------------------------------------- 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
