In message <b447a30d0511080849i2c904d6cm@mail.gmail.com>, chandru writes:
>On 08/11/05, Steven M. Bellovin <smb@cs.columbia.edu> wrote:
>> I think this is something I've run into when the lease changes.  Delete
>> your default route and manually recreate it.  (One hotel I visit
>> annually has a *really* stupid wireless system that triggers it.)
>>
>
>Woohoo! That worked! Thank you! But how exactly does it work? The
>route looked exactly the same before and after. I used the command
>"netstat -rnf inet" to examine it.
>

I haven't tracked it down, but I suspect it's the link in the data 
structure to the interface's address structure.

The question is what to do about it, and at what level -- is it the 
dhclient script that needs fixing?

		--Steven M. Bellovin, http://www.cs.columbia.edu/~smb