Messages in this thread | | | From | Stefan Monnier <> | Subject | Killing a network connection | Date | Mon, 15 Oct 2007 14:40:59 -0400 |
| |
[ 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
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |