Paul, On Thu, 2003-01-30 at 16:59, Paul Evans wrote: > Yes, the usual learning cycle of break/repair, break/repair cycle takes a > looong time. I sure spent my time in the trenches. > Thanks very much. I suppose it's back to my old script then. I was stuck with > a 'file exists error', because of the existing default route. Of course, if I > were to delete it, I'd suddenly not be 'there' anymore to apply the script. > Maybe I can do both via cron instead. In that case you will want to use two different scripts. The existing one and the new one. Have cron simply restart the network every so often probably like you are. Also in part of your script is sounds like you need to flush out everything the default network script adds that you do not want. > Thanks yet again, I skipped Julian's page, because I thought it was just for > the patch. I will go and read it. When I finally get my head around this > part, I will probably have to consider recompiling the kernel and applying > the patch (I think we're talking about the one to eliminate the route > caching). Yes, I tried to play with the cache settings directly, but no combo made things work like the patches. You must also adhere to the nano-how-to rules on routes and such. > I'm familiar with bash functions and I will follow your advice, for me I am > still trying to untangle all the nested calling of the many and varied > scripts that come into play when bringing up all the interfaces. Which do you > recommend my redoing exactly. I mean the existing one for network, ifxxup, > adsl-start are all doing fine the way they are (except for the bit where I > don't know how to prevent a default route being set by adsl-start that is). I > had hoped I could end up with a single script from, say rc.local or > something. Not to be huh? ( I still haven't read the nano you ref'ed > earlier). You can still use your existing network script, just make another one that removes the default ADSL route and anything else that is getting in your way, and then run your commands to get things working your way. Once you are done with your script put it in /etc/rc.d/init.d and add a symbolic link in the proper run level(s) with the necessary startup number. Probably just after the standard network script is run. If you want a single one, add everything you need to your new script and use instead of the default. Although depending on the type of ADSL, PPOE type, you may want to keep and use the default startup script. There is nothing wrong with two, but it is Linux so do what you like and put things were you want them. Make sure to read the nano-how-to or at least make sure all your rules are exactly the same within reason. I tried some deviations, but all failed. Obviously you do need to use the exact IP's as in the example, but use the same rules, and commands using your IP info. > > The way it works for me, and to my knowledge the only way it works is by > > masquerading. That's where the patches make things work. > Ok good. That part realy confused me after all the reading I've done on stef's > site etc. That part still some what confuses me. What is clear is I had a goal and was able to reach it. Masquerading was not a requirement for me, but I did not mind doing it as well. I simply ended up with two rounds of NAT/PAT or two back to back firewalls on either link. More on my config can be found in the archives, but feel free to contact me directly for any questions and specific configuration examples. -- Sincerely, William L. Thomson Jr. Support Group Obsidian-Studios Inc. 439 Amber Way Petaluma, Ca. 94952 Phone 707.766.9509 Fax 707.766.8989 http://www.obsidian-studios.com
