Sorry, I've had some intermittent hardware failure and was otherwise busy. I've switched to Hardy now, and there the system behaves as the user expects. I believe this comes from the switch to dhcdbd, i.e. DBus is driving DHCP and immediately started/stopped each time a particular interfaces goes up or down. In previous distributions, dhclient lived completely on its own, sleeping for long time before bothering to check whether something had changed in between.
Thus on one hand, you can treat the problem as fixed. On the other hand, Dapper is still a supported platform, where the problem exists. But I don't know what the Ubuntu development guidelines say about fixing problems in an old distribution. For Dapper: >Does it work if roaming is turned on? I'm not aware of any roaming with Dapper. >Does this seem to affect a particular network card? No, because the new hardware behaves the same when booting Dapper. >What is the DHCP server? I found no mention of it in /var/log/ or the lease file. How to tell? -- DHCP recognizes LAN only minutes after plugging cable https://bugs.launchpad.net/bugs/59926 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
