Peter Tribble wrote:
> I logged a bug in b.o.o - 6691647 is the ID - which has been marked
> incomplete.
>
> (Heaven knows how someone external is meant to supply
> additional information though.)
>
> But anyway, the symptom I'm seeing is that on a Sun Blade 1500
> that gets its adress using dhcp from a home router, the IP address
> often comes up as 0.0.0.0 after a suspend/resume cycle.
>
> Needless to say, this is pretty useless. It's true with both
> network/physical:default and network/physical:nwam. A couple
> of manual workarounds are to pull the network cable, or to manually
> restart nwam. I've got a cron job running every minute to kick nwam
> if it detects the address being four zeros, which at least means the
> machine can recover itself.
>
> (To be clear, this isn't an nwam problem - it looks like the underlying
> dhcp.)
>
>
I put the following comments in the bug:
I wonder, has the lease expired while the host was suspended? Maybe
an attempt to renew a lease is not possible because the address has
been given out elsewhere while the system was suspended?
It strikes me that dhcp is probably one of those few bits of
software that needs to "know" about a S/R cycle. In this case, I
think setting up a signal handler for SIGTHAW could enable it to
know when it has been resumed, and logic added to reacquire an
address (perhaps not just asking for a renewal, but for a whole new
address if necessary).
The other possible thing to look at, I suppose, is the MAC address
-- ensure that the MAC address on resume is the same as it was on
suspend. If that is not correct, it is indicative of a driver bug.
Its probably just a matter of teaching dhcp about resume.
-- Garrett
_______________________________________________
networking-discuss mailing list
[email protected]
