[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20071016093121.GA28393@one.firstfloor.org>
Date: Tue, 16 Oct 2007 11:31:21 +0200
From: Andi Kleen <andi@...stfloor.org>
To: Bodo Eggert <7eggert@....de>
Cc: Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
Stefan Monnier <monnier@....umontreal.ca>
Subject: Re: Killing a network connection
On Tue, Oct 16, 2007 at 01:50:55AM +0200, Bodo Eggert wrote:
> Andi Kleen <andi@...stfloor.org> wrote:
> > Stefan Monnier <monnier@....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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists