Date: Fri, 15 Jul 2005 21:11:23 +0200 From: Roman Neuhauser <neuhauser@sigpipe.cz> To: Craig Boston <craig@xfoil.gank.org>, Brooks Davis <brooks@one-eyed-alien.net>, Robert Watson <rwatson@freebsd.org>, freebsd-current@freebsd.org Subject: Re: Problems with OpenBSD dhclient Message-ID: <20050715191122.GA1194@isis.sigpipe.cz> In-Reply-To: <20050714191832.GA7462@nowhere> References: <20050714182136.071B35D07@ptavv.es.net> <20050714192403.H35071@fledge.watson.org> <20050714185851.GE19351@odin.ac.hmc.edu> <20050714191832.GA7462@nowhere>
next in thread | previous in thread | raw e-mail | index | archive | help
# 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050715191122.GA1194>