From: Chris Verges <cverges@sentient-energy.com>
To: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
Cc: David Miller <davem@davemloft.net>,
jmorris@namei.org, yoshfuji@linux-ipv6.org, kaber@trash.net,
netdev@vger.kernel.org
Subject: Re: Established sockets remain open after iface down or address lost
Date: Tue, 1 Oct 2013 10:07:40 -0700 [thread overview]
Message-ID: <20131001170740.GA9331@cverges-dev-lnx.sentient-energy.com> (raw)
In-Reply-To: <CAMrnHh6Lr9q27yiSmJ-EbJMTeUVyf9650vK+6QmbfTVfz_omxg@mail.gmail.com>
On Tue, Oct 01, 2013 at 08:33:04PM +0400, Alexey Kuznetsov wrote:
> > P.S. I apologize in advance if I missed this answer in the netdev
> > archives.
>
> FYI googling f.e. "netdev tcp remove local address" instantly finds
> all that you want to know. Namrly, subj: Re: "TCP shutdown behaviour
> when deleting local IP addresses"
Oustanding. Thank you! I really appreciate the pointer to bring me up
to speed on the history. It sounds like Mikael and I share a similar
desire and rationale for why such a thing would be useful.
Your comment regarding the tcp hash table scanning is what I was
planning to code up, though it sounds like some amount of effort was
made in this attempt and abandoned. Would you happen to know where any
out-of-kernel code related to this might be parked if one wanted to
continue this effort?
I do agree with Mikael that offloading this from the kernel to some kind
of connection manager would be ideal. I'll ponder this some more....
Again, many thanks for the help.
Chris
next prev parent reply other threads:[~2013-10-01 17:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 6:04 Established sockets remain open after iface down or address lost Chris Verges
2013-09-26 13:49 ` Eric Dumazet
2013-10-01 13:27 ` Chris Verges
2013-10-01 15:44 ` Rick Jones
2013-10-01 16:08 ` Chris Verges
2013-10-01 17:06 ` Rick Jones
2013-10-01 16:33 ` Alexey Kuznetsov
2013-10-01 17:07 ` Chris Verges [this message]
2013-10-01 19:00 ` Alexey Kuznetsov
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=20131001170740.GA9331@cverges-dev-lnx.sentient-energy.com \
--to=cverges@sentient-energy.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;
as well as URLs for NNTP newsgroup(s).