Tcpkill - Revision history

Unknown user: /* Examples */

2022-03-05T20:06:47Z

Examples

← Older revision		Revision as of 20:06, 5 March 2022
Line 42:		Line 42:
	<pre>		<pre>
	tcpkill −9 port 6346		tcpkill −9 port 6346
			</pre>

			To block all traffic going to/from 192.168.0.101 except traffic coming from 192.168.0.202:

			<pre>
			tcpkill ip host 192.168.0.101 and not 192.168.0.202
	</pre>		</pre>

Unknown user: /* How to use it? */

2022-03-05T19:57:24Z

How to use it?

@@ Line 13: / Line 13: @@
 To run tcpkill, you need a network card that can be operated in promiscuous mode (i.e., not Mac or Windows).
-You provide two arguments:
+You provide three arguments:
 * the network interface to listen on
 * the degree of brute force to use in killing a connection (1-9, default is 3). use higher numbers for faster connections, to inject more forged RST packets and get the timing right
 =Links=

Unknown user at 19:44, 5 March 2022

2022-03-05T19:44:02Z

← Older revision		Revision as of 19:44, 5 March 2022
Line 7:		Line 7:
	tcpkill will kill TCP connections by spoofing the TCP hangup request, which interferes with the connection.		tcpkill will kill TCP connections by spoofing the TCP hangup request, which interferes with the connection.

	To a victim, the end result is an infuriating mix of a network connection that ~~seems to work~~, but that cannot ~~sustain~~ any TCP connections.		To a victim, the end result is an infuriating mix of a network connection that appears connected and working when diagnosed, but that cannot keep any TCP connections alive.

	==How to use it?==		==How to use it?==
Line 13:		Line 13:
	To run tcpkill, you need a network card that can be operated in promiscuous mode (i.e., not Mac or Windows).		To run tcpkill, you need a network card that can be operated in promiscuous mode (i.e., not Mac or Windows).

			You provide two arguments:
			* the network interface to listen on
			* the degree of brute force to use in killing a connection (1-9, default is 3). use higher numbers for faster connections, to inject more forged RST packets and get the timing right

Unknown user at 19:25, 5 March 2022

2022-03-05T19:25:55Z

← Older revision		Revision as of 19:25, 5 March 2022
Line 3:		Line 3:
	==What is it?==		==What is it?==

	tcpkill is a command line utility installed as part of the [[Dsniff]] suite. ~~It kills~~ TCP connections by spoofing the TCP hangup request, which interferes with the connection.		tcpkill is a command line utility installed as part of the [[Dsniff]] suite.

			tcpkill will kill TCP connections by spoofing the TCP hangup request, which interferes with the connection.

	To a victim, the end result is an infuriating mix of a network connection that seems to work, but that cannot sustain any TCP connections.		To a victim, the end result is an infuriating mix of a network connection that seems to work, but that cannot sustain any TCP connections.

			==How to use it?==

			To run tcpkill, you need a network card that can be operated in promiscuous mode (i.e., not Mac or Windows).


Line 15:		Line 21:
	==Code==		==Code==

	C version: https://github.com/chartbeat/tcpkill		Official version: https://monkey.org/~dugsong/dsniff/

			Patched C version: https://github.com/chartbeat/tcpkill

	Python version: https://github.com/Kkevsterrr/tcpkiller		Python version: https://github.com/Kkevsterrr/tcpkiller
	* ethernet only, no 802.11 headers		* ethernet only, no 802.11 headers

Unknown user: Created page with "=Overview= ==What is it?== tcpkill is a command line utility installed as part of the Dsniff suite. It kills TCP connections by spoofing the TCP hangup request, which in..."

2022-03-05T19:21:32Z

Created page with "=Overview= ==What is it?== tcpkill is a command line utility installed as part of the Dsniff suite. It kills TCP connections by spoofing the TCP hangup request, which in..."

New page

=Overview=

==What is it?==

tcpkill is a command line utility installed as part of the [[Dsniff]] suite. It kills TCP connections by spoofing the TCP hangup request, which interferes with the connection.

To a victim, the end result is an infuriating mix of a network connection that seems to work, but that cannot sustain any TCP connections.

=Links=

==Code==

C version: https://github.com/chartbeat/tcpkill

Python version: https://github.com/Kkevsterrr/tcpkiller
* ethernet only, no 802.11 headers