From owner-freebsd-current@FreeBSD.ORG Fri Jul 15 19:11:26 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2283516A41C; Fri, 15 Jul 2005 19:11:26 +0000 (GMT) (envelope-from neuhauser@sigpipe.cz) Received: from isis.sigpipe.cz (fw.sigpipe.cz [62.245.70.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id A77B243D45; Fri, 15 Jul 2005 19:11:24 +0000 (GMT) (envelope-from neuhauser@sigpipe.cz) Received: by isis.sigpipe.cz (Postfix, from userid 1001) id 133C51F87BF4; Fri, 15 Jul 2005 21:11:23 +0200 (CEST) Date: Fri, 15 Jul 2005 21:11:23 +0200 From: Roman Neuhauser To: Craig Boston , Brooks Davis , Robert Watson , freebsd-current@freebsd.org Message-ID: <20050715191122.GA1194@isis.sigpipe.cz> Mail-Followup-To: Craig Boston , Brooks Davis , Robert Watson , freebsd-current@freebsd.org References: <20050714182136.071B35D07@ptavv.es.net> <20050714192403.H35071@fledge.watson.org> <20050714185851.GE19351@odin.ac.hmc.edu> <20050714191832.GA7462@nowhere> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050714191832.GA7462@nowhere> User-Agent: Mutt/1.5.9i X-Mailman-Approved-At: Sat, 16 Jul 2005 14:47:34 +0000 Cc: Subject: Re: Problems with OpenBSD dhclient X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2005 19:11:26 -0000 # craig@xfoil.gank.org / 2005-07-14 14:18:32 -0500: > On Thu, Jul 14, 2005 at 11:58:51AM -0700, Brooks Davis wrote: > > I'm seeing this as well. I think we're going to need to handle wireless > > and wired interfaces differently since their links work differently. > > If anything, please PLEEEEEASE make it possible to disable this behavior > for ALL interface types. > > There's nothing more annoying (to me) than unplugging a Windows 2000 > machine for half a second to reroute or swap a network cable, then > finding that all the open connections were terminated because it briefly > lost its IP address. The suggestion above got me quite agitated as this behavior of windows is one of the things I abhor in the software, because it (the behavior) cuts down usability of the software. Pull the wrong cable from a switch after you've downloaded most of an iso image, and you'll see how useful this behavior is. The situation gets even worse in wireless networks where you can occasionaly have link down without doing anything to the equipment. All in all, doing too much when the link goes down would be a big mistake. -- How many Vietnam vets does it take to screw in a light bulb? You don't know, man. You don't KNOW. Cause you weren't THERE. http://bash.org/?255991