From: Andi Kleen <andi@firstfloor.org>
To: Bodo Eggert <7eggert@gmx.de>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Killing a network connection
Date: Tue, 16 Oct 2007 11:31:21 +0200 [thread overview]
Message-ID: <20071016093121.GA28393@one.firstfloor.org> (raw)
In-Reply-To: <E1IhZi3-0001Hd-Ug@be1.lrz>
On Tue, Oct 16, 2007 at 01:50:55AM +0200, Bodo Eggert wrote:
> Andi Kleen <andi@firstfloor.org> wrote:
> > Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
> >> The main use for me is to deal with dangling connections due to taking
> >> network interfaces up&down with different IP addresses (typically the wlan0
> >> interface where the IP is different because I've modes from an AP to
> >> another). Of course, maybe there's another way to solve this particular
> >> problem, in case I'd like to hear about it as well.
> >
> > Long ago I did a 2.4 patch that solved exactly this problem. It introduced
> > a new ifconfig flag "dynamic" and when a dynamic address went down
> > all TCP connections originating from it were killed. It's still available
> > in older SUSE releases. I might post a forward port later.
>
> There is a /proc/sys/net/ipv4/ip_dynaddr sysctl in 2.6.21.
That only handles SYN_SENT and does something different (it rewrites
the source address)
-Andi
next prev parent reply other threads:[~2007-10-16 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9eFcS-It-3@gated-at.bofh.it>
[not found] ` <9eGsi-2Sr-35@gated-at.bofh.it>
2007-10-15 23:50 ` Killing a network connection Bodo Eggert
2007-10-16 3:42 ` Stefan Monnier
2007-10-16 9:31 ` Andi Kleen [this message]
2007-10-15 18:40 Stefan Monnier
2007-10-15 22:12 ` Andi Kleen
2007-10-16 3:15 ` Stefan Monnier
2007-10-18 0:44 ` Bill Davidsen
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=20071016093121.GA28393@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=7eggert@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=monnier@iro.umontreal.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.