public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: linux-kernel@vger.kernel.org
Subject: Killing a network connection
Date: Mon, 15 Oct 2007 14:40:59 -0400	[thread overview]
Message-ID: <jwvodf01b5i.fsf-monnier+gmane.linux.kernel@gnu.org> (raw)

[ I suppose this is not the best place to ask this, but
  comp.os.linux.networking couldn't come up with a good answer and I can't
  think of any intermediate step between these two groups ;-( ]

I'd like (as root, obviously) to kill some of the TCP connections visible
in netstat.  I've found `tcpkill' and `cutter' but `cutter' only kills TCP
connections that go *though* the machine (in my case, the machine is not
a router, so there aren't any such thu connections anyway) and `tcpkill'
can only kill the conection after seeing some activity (and it doesn't know
to exit when the connections are killed).  Also those 2 tools seem
just overkill.
I'd like simply to do (metaphorically)

  rm /tcpfs/<foo>

so it should not need to involve *any* use of the TCP protocol: just kill it
locally, warn the associated process(es), free the resources and let the
other end deal with it.

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.


        Stefan


             reply	other threads:[~2007-10-15 20:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-15 18:40 Stefan Monnier [this message]
2007-10-15 22:12 ` Killing a network connection Andi Kleen
2007-10-16  3:15   ` Stefan Monnier
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=jwvodf01b5i.fsf-monnier+gmane.linux.kernel@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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