I don't think RFC2131 is anywhere near that specific. It says "reasonable period of time" corresponding to the local internetworking facilities, and suggests an algorithm which is then referenced as "if using timeout suggested in section 4.1" and other such phrases. The only hard limit is section 4.4.5, which is talking about reacquisition and so doesn't apply here.
15 seconds was always known to be a compromise, and of course you can always retry. However, I'll reluctantly bump it to 30. I don't want to push it higher than that in case there are people with analogous problems cancelling the timeout (or who just don't notice that you can cancel it and complain ...) compared with your problems retrying. Note that in our default configuration static network configuration is not offered until after DHCP fails or is cancelled. ** Changed in: netcfg (Ubuntu) Sourcepackagename: debian-installer => netcfg -- DHCP timeout with netinstall/alternative/d-i... https://bugs.launchpad.net/bugs/267656 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
