From: Eric Dumazet <eric.dumazet@gmail.com>
To: Chris Friesen <chris.friesen@genband.com>
Cc: netdev <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
James Morris <jmorris@namei.org>,
Patrick McHardy <kaber@trash.net>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>
Subject: Re: Bug? TCP shutdown behaviour when deleting local IP addresses
Date: Thu, 18 Oct 2012 09:29:42 +0200 [thread overview]
Message-ID: <1350545382.26103.1103.camel@edumazet-glaptop> (raw)
In-Reply-To: <507FAAE1.6000903@genband.com>
On Thu, 2012-10-18 at 01:08 -0600, Chris Friesen wrote:
>
> While I agree generally, it's a bit unfortunate that we can't (as a
> quality of implementation thing) give an earlier notice of failure since
> the kernel knows about both ends of the connection even though the IP
> address is gone. On the other hand, I imagine that would mean
> special-casing things and presumably that would open a whole can of worms.
Really what is the difference between a cable cut and what you are
doing ?
Some frames are lost (Dropped), and sender doesnt 'know' that is
definitive or temporary failure.
If you want faster response, you need to send RST messages, not dropping
frames.
So change your strategy, and add an iptables rule for example ?
next prev parent reply other threads:[~2012-10-18 7:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 23:01 Bug? TCP shutdown behaviour when deleting local IP addresses Chris Friesen
2012-10-17 23:27 ` David Miller
2012-10-18 6:33 ` Chris Friesen
2012-10-18 6:05 ` Eric Dumazet
2012-10-18 7:08 ` Chris Friesen
2012-10-18 7:29 ` Eric Dumazet [this message]
2012-10-19 15:12 ` Chris Friesen
2012-10-19 20:43 ` Andi Kleen
2012-10-18 8:05 ` Mikael Abrahamsson
2012-10-18 9:00 ` David Laight
2012-10-18 10:00 ` Mikael Abrahamsson
2012-10-18 9:13 ` Eric Dumazet
2012-10-18 9:58 ` Mikael Abrahamsson
2012-10-18 10:01 ` Alexey Kuznetsov
2012-10-18 10:10 ` Mikael Abrahamsson
2012-10-18 10:37 ` Benny Amorsen
2012-10-18 13:00 ` Mikael Abrahamsson
2012-10-18 13:09 ` Benny Amorsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1350545382.26103.1103.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=chris.friesen@genband.com \
--cc=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox