This is more a "me too" than a solution, I'm afraid. On 10/31/05, Hannah Schroeter <[EMAIL PROTECTED]> wrote: > If I include an alias directive in /etc/dhclient.conf, dhclient exits > after having acquired a lease, the syslog messages are like this:
This is quite similar to something I also experienced [1,2] on a machine that gets a public IP from a DSL provider while still wanting to locally talk to the DSL modem. Unfortunately, I have no solution, but I can verify that the problem exists (an exiting dhclient) in 3.7, as well as it did in 3.6. [2] also includes my configuration on the machine in question. Unfortunately, I never got around to providing a more detailed report than that as I could happily leave the DSL modem on its own. I suspect running with a debugger may provide a few clues as well. Regards, Rogier References: 1. MARC 'dhclient and multiple networks (/24 alias) fails (bug?)' http://marc.theaimsgroup.com/?l=openbsd-misc&m=110088400431506&w=2 2. MARC 'dhclient suddenly exiting together with arpresolve: can't allocate llinfo' http://marc.theaimsgroup.com/?l=openbsd-misc&m=110061784801356&w=2 -- If you don't know where you're going, any road will get you there.
