Hello, On Thu, 17 Jan 2013 19:18:55 +0200 Lauri Tirkkonen <[email protected]> wrote:
> ifupdown runs dhclient with the '-1' option, presumably to block > during startup scripts. Not exactly. It was done to make the ifup process more consistent: if we get an address, we're up, if we don't — we know something's wrong. > In the event that configuration is > successful, dhclient will daemonize and exit successfully, and > ifupdown marks the interface configured. However, dhclient will exit > if at any point in the future renewing the lease fails, and an > administrator will have to manually ifup the affected interface > (actually ifdown first, since ifupdown will still think the interface > is up). I believe this is a regression since squeeze, and it looks > like #694541 is caused by the same change. I believe this may be a bug in dhclient. At least -1 in my understanding was supposed to affect initial handshake only. I'd recommend to use ifplugd together with ifupdown in such a setup, which ensures interfaces are re-configured properly when the link goes down and up. > As noted in #694541, the change was apparently made to fix #420784, > but this is a rather nasty side effect. Yes, and I don't currently know how to fix this properly until some core parts of ifupdown are rewritten, which is not going to happen before the release. In the version which is soon to be uploaded if approved by the release team, I've added tryonce option to switch -1 off if needed. For consistency, however, I guess there may be a hook script for dhclient which calls ifdown when it fails to renew the address and stops. -- WBR, Andrew
signature.asc
Description: PGP signature
