Subject: Re: kern/35196: sockets should die if addresses vanish
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: Perry E. Metzger <perry@piermont.com>
List: netbsd-bugs
Date: 12/07/2006 21:40:11
The following reply was made to PR kern/35196; it has been noted by GNATS.

From: "Perry E. Metzger" <perry@piermont.com>
To: Manuel Bouyer <bouyer@antioche.eu.org>
Cc: gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org,
	gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: kern/35196: sockets should die if addresses vanish
Date: Thu, 07 Dec 2006 16:40:24 -0500

 Manuel Bouyer <bouyer@antioche.eu.org> writes:
 >>  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.
 
 That is one problem. The bigger problem is processes that don't know
 that they should be doing something to re-open a socket because their
 original connection is no longer actually real.
 
 Perry