Package: dhcp3-client Version: 3.0.1-2 Followup-For: Bug #295064 Got bitten by this as well.
There are two problems here. * One is that ifupdown has hardcoded options, that it passes to the dhcp clients. It uses the '-e' option when starting dhclient2, which is exactly the contrary of the needed behaveour in the problemspace at hand here and it stops dhclient3 with -r which will release the current IP address at reboot, which is also the wrong behaveour here. So, rock or a hard place? Ummh.. the design of ifupdown wrt using immutable hardcoded options is not sound. * The second is the here discussed behaveour of dhcp3-client with respect to '-r'. The report is 1.5 year old by now and the problem is real. Would it be possible to move on with this problem and apply the patch? Should the original reporters try to push the patch upstream? What's the course of action? Current behaveour is suboptimal, some action would be nice here. *t -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-386 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages dhcp3-client depends on: ii debconf 1.4.30.13 Debian configuration management sy ii debianutils 2.8.4 Miscellaneous utilities specific t ii dhcp3-common 3.0.1-2 Common files used by all the dhcp3 ii libc6 2.3.2.ds1-22sarge3 GNU C Library: Shared libraries an -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
