dhcp3-client doesn't renew leases after suspend

[Keenan Tims]

Binary package hint: dhcp3-client

After a suspend/resume, network interfaces are not reconfigured. After long suspend periods, machines will come up using addresses they may not have a lease for, and dhclient doesn't make a fresh request immediately. NetworkManager seems to have an appropriate script in place already, however users using the traditional interfaces configuration file will stomp on the network management.

I have modified a pm-utils sleep.d script submitted to Fedora ( here: https://bugzilla.redhat.com/show_bug.cgi?id=479639 ) so that it can work with Debian-style configuration files. It is probably not robust, but seems to work fine with my configuration.

[Stéphane Graber (stgraber)]

The idea sounds good, the script should probably be using ifquery instead and work with dhclient -4 and dhclient -6.

Triaging the bug as wishlist as I'm unlikely to find time to work on that just now (proposed file isn't ready for inclusion as-is).

[Brian J. Murrell (brian-interlinx)]

This is not wishlist. This is a bug.

It is absolutely invalid and wrong to just get onto a network and use an address that was not either given to you manually by the network administrator or obtained through some autoconfiguration tool such as DHCP. Therefore, using an IP address after it's lease has expired is simply wrong, and very well likely a network policy violation. In a corporate environment this BUG could be exposing network users to the risk of being sanctioned by their IT and security departments for violating policies.