> My workaround was to add the command "seawall restart" after > "reload_all" (see below). [Note: you will see in this code some logic > I added to tell my dynamic dns service that my IP has changed. This > code also logs when that logic executes. Actually, my IP has changed > once in the last two years, I have the poor man's static IP! :-)] > > My question is NOT what is the bug in the ip changing logic below, I > can probably figure that out (though if someone sees it instantly > there is no harm in writing me). This code is supposed to have a bug > fix I saw in the list from Charles. Maybe I dropped it or did it > wrong. I will upgrade the the Latest Dachstein and see if this IP > change detection has changed > > Here are the questions: > > 1. Are there any other places in Dachstein that update the network, > and need to be followed by "seawall restart"?
Other than on initial startup (which apparently works OK already), the only other thing that comes to mind is if someone's manually bringing network services up/down (ie using "svi network reload" or similar)...presumably anyone doing so would also remember to manually restart seawall... > 2. Is there a better fix for this problem? (This fix works, my humble > web site has been visible continuously since I edited dhclient-exit- > hooks.) Unfortuantely my fix entangles seawall.lrp and dhclient.lrp. The dhclient enter and exit hooks scripts are the cleanest location for this sort of code, AFAIK. Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
