[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AE90C24D6B3A694183C094C60CF0A2F6026B7051@saturn3.aculab.com>
Date: Thu, 18 Oct 2012 10:00:44 +0100
From: "David Laight" <David.Laight@...LAB.COM>
To: "Mikael Abrahamsson" <swmike@....pp.se>,
"Chris Friesen" <chris.friesen@...band.com>
Cc: "netdev" <netdev@...r.kernel.org>,
"David Miller" <davem@...emloft.net>,
"Alexey Kuznetsov" <kuznet@....inr.ac.ru>,
"James Morris" <jmorris@...ei.org>,
"Patrick McHardy" <kaber@...sh.net>,
"Hideaki YOSHIFUJI" <yoshfuji@...ux-ipv6.org>
Subject: RE: Bug? TCP shutdown behaviour when deleting local IP addresses
> 2. When a network connection (physical interface) goes down, wait a few
> seconds, give up, reset all connectivity related to that connection,
> basically give up.
Doing that is almost pointless and gives people false expectations.
Consider the simple network host-hub-hub-host.
If you disconnect the link between the two hubs then
only timeouts can cause disconnects.
Such a remote fault is much more likely than the local one.
If the kernel takes down connections when a local interface
goes down (as windows does) then people doing testing
fail to test the correct scenario.
You also don't want a power glitch in the wiring cupboard
to disconnect all your connections.
In the past I've also moved IP addresses between physical
interfaces - modern HA systems might do the same.
David
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists