public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Killing a network connection
Date: Mon, 15 Oct 2007 23:15:32 -0400	[thread overview]
Message-ID: <jwvwstnsqds.fsf-monnier+inbox@gnu.org> (raw)
In-Reply-To: <p73przg10yp.fsf@bingen.suse.de> (Andi Kleen's message of "Tue\, 16 Oct 2007 00\:12\:46 +0200")

>> 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.

Actually, I'm pretty happy sometimes with the current behavior: if the
interface goes down and back up with the same AP within a short enough time,
it typically gets the same IP and the router's NAT table still has the TCP
connection live and things "just work".

So I'd want to kill the connections not when the interface goes down, but in
comes back up with a different IP.


        Stefan

  reply	other threads:[~2007-10-16  3:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-15 18:40 Killing a network connection Stefan Monnier
2007-10-15 22:12 ` Andi Kleen
2007-10-16  3:15   ` Stefan Monnier [this message]
2007-10-18  0:44 ` Bill Davidsen
     [not found] <9eFcS-It-3@gated-at.bofh.it>
     [not found] ` <9eGsi-2Sr-35@gated-at.bofh.it>
2007-10-15 23:50   ` Bodo Eggert
2007-10-16  3:42     ` Stefan Monnier
2007-10-16  9:31     ` Andi Kleen

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=jwvwstnsqds.fsf-monnier+inbox@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.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