On Thursday 21 February 2002 08:53, Simon Bolduc wrote: > There actually is no error - not in daemon.log or anything else for > that matter. There was a line in the exit-hooks to restart seawall, > after the reload all section, but that was removed thinking it may be > the issue. He's getting the same IP - so forwarding shouldn't need > to restarted anyway.
OK, there have been a couple of posts indicating something similar in the last week. I ran into it while writing the scripts for udhcp. If this persists, why don't you try replacing it with the udhcp package (server and client) and see if this clears the problem up. If it does clear up the problem, post back .... I have a good idea what is happening (exactly) if this is the case and can submit a patch for dhclient. The udhcp testing package(s) can be found at: For general LEAF/LRP versions use: http://leaf.sourceforge.net/devel/guitarlynn/images/udhcp.lrp For Dachstein/Eigerstein/other Mountain versions use: http://leaf.sourceforge.net/devel/guitarlynn/images/udhcp.lrp.dachstein Thx, -- ~Lynn Avants aka Guitarlynn guitarlynn at users.sourceforge.net http://leaf.sourceforge.net If linux isn't the answer, you've probably got the wrong question! _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
