The following reply was made to PR kern/35196; it has been noted by GNATS.

From: Manuel Bouyer <bouyer@antioche.eu.org>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org,
	netbsd-bugs@NetBSD.org, perry@piermont.com
Subject: Re: kern/35196: sockets should die if addresses vanish
Date: Thu, 7 Dec 2006 22:36:32 +0100

 On Thu, Dec 07, 2006 at 02:30:08PM +0000, Perry E. Metzger wrote:
 >  > And not necessarily unstable;  not so long ago most ADSL ISPs in France
 >  > used to disconnect people after 24h.  It was a pain for Windows users,
 >  > that OS being one that does what Perry wants.
 >  
 >  Well, as I said, we could always make the behavior sysctl'able so you
 >  could pick based on your usage pattern.
 >  
 >  For my usage, I'm constantly opening up my laptop and acquiring a new
 >  address when I arrive somewhere. Generally, I then have all these
 >  connections that were active when I was at my last location some hours
 >  earlier that are now dead, and yet which now are around and sending
 >  out packets that can never be replied to.
 >  
 >  In addition to the possibility of a sysctl for the behavior, here is
 >  another idea: perhaps if you no longer have the origination address
 >  bound to any interface, you drop the packets you would otherwise send
 >  out from earlier connections rather than sending them out on an actual
 >  network. Then, if you get the address back, you can stop dropping
 >  them. This surely will cause no one any inconvenience, since those
 >  packets could never be replied to. It will not, however, be an optimal
 >  solution from my point of view...
 
 If your problem is that the system sends packets that could be seen as
 spoofed, then yes it's an acceptable solution.
 
 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 26 ans d'experience feront toujours la difference
 --