Subject: Re: DHCP client, integration with ifconfig, etc.
To: None <tech-net@NetBSD.ORG>
From: Guenther Grau <email@example.com>
Date: 02/12/1997 18:00:25
[Matt Thomas' comments about how to handle ip-number
change in applications deleted]
> Another is the return of a new errno, EADDREXPIRED, on bound sockets to an
> expired address.
This looks reasonable to me, although it would be nicer if
applications wouldn't even notice that the IP-address has changed,
but I guess this is not really that easy to handle:-/ What is an
application excpected to do, when it get's such a message, in
whatever way? Should it shutdown all the connections it maintains
and reestablish them if/when a new IP-address is available? Is
there still time for the application to shutdown, because it will
get this message when the IP-address has already expired? How do
other OS' and the applications thereon handle this?