From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010702

Description of problem:
"ifdown ifcfg-eth0" will issue this command:
pump -r -i eth0

This causes the client to release its IP address, which Windows does not do.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.  Do a controlled shutdown of an ethernet interface that uses pump for DHCP


Actual Results:  pump gave a DHCPRELEASE message to the dhcp server,
freeing up the IP address.

Expected Results:  Windows does not issue a DHCPRELEASE upon controlled
shutdown.  Issuing a DHCPRELEASE is not a requirement nor a suggestion in
RFC2131.

Additional info:

This isn't a bug exactly - RFC2131 allows for DHCPRELEASE on controlled
shutdown; however, it doesn't recommend it either (unless the computer is
being permanently moved to another network).

Perhaps there should be an option in
/etc/sysconfig/network-scripts/ifcfg-eth* that allows for explicit Windows
compatability with DHCP.  


(...even more info...)

This is a minor problem on our (mostly Windows) network.  The administrator
won't give out static IP addresses, but does give a DHCP lease time of 8
days.  Some of the researchers have access to computers elswhere, but the
admins of those computers will only allow access from specific IP addresses
for security reasons.  

So the researchers have, at least, an unchanging IP address as long as they
don't turn off their computer for more than 8 days.  Unfortunately,
ifdown/pump issues a DHCP release, causing them to lose their IP address
almost every time they turn off their computer.