[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#610553: installation-reports: does not cleanly deconfigure network configured with DHCP



clone 610553
reassign 610553 finish-install
reassign -1 di-utils-reboot
thanks

On Wed, Jan 19, 2011 at 03:32:59PM -0500, Jeffrey Sheinberg wrote:
> Install of squeeze-rc1 (expert mode, non-graphical) from *.iso - works
> great except the network is not cleanly deconfigured for DHCP.
> 
> Solution - please send SIGUSR2 to the "udhcpc" process at end of
> installation (menu items: finish up the installation, or abort the
> installation).

That can probably be arranged.  It covers two separate packages, so I'm
going to clone out this report to get it fixed everywhere (finish-install
for regular completion, and di-utils-reboot for "Abort the installation").
di-utils-exit-installer ("Exit the installer") is only used in installer
demos, apparently, so that probably doesn't need to be changed.

(Note to implementors: example code for wiping out the DHCP client is in
netcfg/killall.sh; only minor adaptations should be required, although it
appears that different DHCP clients use different methods to signal release,
so that'll complicate matters)

However...

> This is because my ISP's DHCP server already has handed out a lease to
> my computer and this lease is still active.  
> 
> This active lease was obtained during the installation process, however,
> the installation process did not release the DCHP lease before it
> terminated the installation.
> 
> Why hasn't this problem been reported before?  Answer - most routers
> will just re-offer an active DHCP lease to the same MAC address that had
> originally obtained the lease.  However, my ISP's DHCP servers will only
> re-offer an active leave when the requested ip-address matches the
> ip-address that was provided with the original lease.

That must make life *really* entertaining for the ISP's support staff after
an area-wide power outage.  It also appears to be in contravention of a
quick skim of RFC2131, since there's no requirement for clients to send a
DHCPRELEASE.  Section 4.4.6 states, "Note that the correct operation of DHCP
does not depend on the transmission of DHCPRELEASE messages."  I wonder what
other brokenness your ISP is hiding...

- Matt



Reply to: