node2.html 13 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362
  1. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
  2. <!--Converted with LaTeX2HTML 2002-2-1 (1.70)
  3. original version by: Nikos Drakos, CBLU, University of Leeds
  4. * revised and updated by: Marcus Hennecke, Ross Moore, Herb Swan
  5. * with significant contributions from:
  6. Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
  7. <HTML>
  8. <HEAD>
  9. <TITLE>1 General Info</TITLE>
  10. <META NAME="description" CONTENT="1 General Info">
  11. <META NAME="keywords" CONTENT="FAQ">
  12. <META NAME="resource-type" CONTENT="document">
  13. <META NAME="distribution" CONTENT="global">
  14. <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
  15. <META NAME="Generator" CONTENT="LaTeX2HTML v2002-2-1">
  16. <META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
  17. <LINK REL="STYLESHEET" HREF="FAQ.css">
  18. <LINK REL="next" HREF="node3.html">
  19. <LINK REL="previous" HREF="node1.html">
  20. <LINK REL="up" HREF="FAQ.html">
  21. <LINK REL="next" HREF="node3.html">
  22. </HEAD>
  23. <BODY >
  24. <DIV CLASS="navigation"><!--Navigation Panel-->
  25. <A NAME="tex2html132"
  26. HREF="node3.html">
  27. <IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
  28. <A NAME="tex2html128"
  29. HREF="FAQ.html">
  30. <IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
  31. <A NAME="tex2html122"
  32. HREF="node1.html">
  33. <IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
  34. <A NAME="tex2html130"
  35. HREF="node1.html">
  36. <IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
  37. <BR>
  38. <B> Next:</B> <A NAME="tex2html133"
  39. HREF="node3.html">2 Bugs, Feature Requests,</A>
  40. <B> Up:</B> <A NAME="tex2html129"
  41. HREF="FAQ.html">Tcpreplay 3.x FAQ</A>
  42. <B> Previous:</B> <A NAME="tex2html123"
  43. HREF="node1.html">Contents</A>
  44. &nbsp; <B> <A NAME="tex2html131"
  45. HREF="node1.html">Contents</A></B>
  46. <BR>
  47. <BR></DIV>
  48. <!--End of Navigation Panel-->
  49. <!--Table of Child-Links-->
  50. <A NAME="CHILD_LINKS"><STRONG>Subsections</STRONG></A>
  51. <UL CLASS="ChildLinks">
  52. <LI><A NAME="tex2html134"
  53. HREF="node2.html#SECTION00021000000000000000"><SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">1</SPAN> What is this FAQ for?</A>
  54. <LI><A NAME="tex2html135"
  55. HREF="node2.html#SECTION00022000000000000000"><SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">2</SPAN> What tools come with tcpreplay?</A>
  56. <LI><A NAME="tex2html136"
  57. HREF="node2.html#SECTION00023000000000000000"><SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">3</SPAN> What tools no longer come with Tcpreplay?</A>
  58. <LI><A NAME="tex2html137"
  59. HREF="node2.html#SECTION00024000000000000000"><SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">4</SPAN> How can I get tcpreplay's source?</A>
  60. <LI><A NAME="tex2html138"
  61. HREF="node2.html#SECTION00025000000000000000"><SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">5</SPAN> What requirements does tcpreplay have?</A>
  62. <LI><A NAME="tex2html139"
  63. HREF="node2.html#SECTION00026000000000000000"><SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">6</SPAN> Are there binaries available?</A>
  64. <LI><A NAME="tex2html140"
  65. HREF="node2.html#SECTION00027000000000000000"><SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">7</SPAN> Is there a Microsoft Windows port?</A>
  66. <LI><A NAME="tex2html141"
  67. HREF="node2.html#SECTION00028000000000000000"><SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">8</SPAN> How is tcpreplay licensed?</A>
  68. <LI><A NAME="tex2html142"
  69. HREF="node2.html#SECTION00029000000000000000"><SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">9</SPAN> What is tcpreplay?</A>
  70. <LI><A NAME="tex2html143"
  71. HREF="node2.html#SECTION000210000000000000000"><SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">10</SPAN> What are some uses for tcpreplay?</A>
  72. <LI><A NAME="tex2html144"
  73. HREF="node2.html#SECTION000211000000000000000"><SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">11</SPAN> What are some uses for flowreplay?</A>
  74. <LI><A NAME="tex2html145"
  75. HREF="node2.html#SECTION000212000000000000000"><SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">12</SPAN> What is the history of tcpreplay?</A>
  76. </UL>
  77. <!--End of Table of Child-Links-->
  78. <HR>
  79. <H1><A NAME="SECTION00020000000000000000">
  80. <SPAN CLASS="arabic">1</SPAN> General Info</A>
  81. </H1>
  82. <P>
  83. <H2><A NAME="SECTION00021000000000000000">
  84. <SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">1</SPAN> What is this FAQ for?</A>
  85. </H2>
  86. <P>
  87. Tcpreplay is a suite of powerful tools, but with that power comes
  88. complexity. While I have done my best to write good man pages for
  89. tcpreplay and it's associated utilities, I understand that many people
  90. may want more information then I can provide in the man pages. Additionally,
  91. this FAQ attempts to cover material which I feel will be of use to
  92. people using tcpreplay, as well as common questions that occur on
  93. the Tcpreplay-Users &lt;tcpreplay-users@lists.sourceforge.net&gt; mailing
  94. list.
  95. <P>
  96. <H2><A NAME="SECTION00022000000000000000">
  97. <SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">2</SPAN> What tools come with tcpreplay?</A>
  98. </H2>
  99. <P>
  100. <UL>
  101. <LI>tcpreplay - replay ethernet packets stored in a pcap file as they
  102. were captured
  103. </LI>
  104. <LI>tcprewrite - edit packets stored in a pcap file
  105. </LI>
  106. <LI>tcpprep - a pcap pre-processor for tcpreplay
  107. </LI>
  108. <LI>flowreplay<A NAME="tex2html1"
  109. HREF="#foot136"><SUP><SPAN CLASS="arabic">1</SPAN></SUP></A> - connects to a server(s) and replays the client side of the connection
  110. stored in a pcap file
  111. </LI>
  112. </UL>
  113. <P>
  114. <H2><A NAME="SECTION00023000000000000000">
  115. <SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">3</SPAN> What tools no longer come with Tcpreplay?</A>
  116. </H2>
  117. <P>
  118. Recently, other people and projects have developed better versions
  119. of two applications that ship with tcpreplay 2.x:
  120. <P>
  121. <UL>
  122. <LI>pcapmerge - merges two or more pcap files into one. Ethereal now ships
  123. with a more powerful appliation called 'mergecap'.
  124. </LI>
  125. <LI>capinfo - displays basic information about a pcap file. Ethereal now
  126. ships with a more powerful application of the same name.
  127. </LI>
  128. </UL>
  129. <P>
  130. <H2><A NAME="SECTION00024000000000000000">
  131. <SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">4</SPAN> How can I get tcpreplay's source?</A>
  132. </H2>
  133. <P>
  134. The source code is available in tarball format on the tcpreplay homepage:
  135. http://tcpreplay.sourceforge.net/ I also encourage users familiar
  136. with Subversion to try checking out the latest code as it often has
  137. additional features and bugfixes not found in the tarballs.
  138. <P>
  139. svn checkout https://www.synfin.net:444/svn/tcpreplay/trunk tcpreplay
  140. <P>
  141. <H2><A NAME="SECTION00025000000000000000">
  142. <SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">5</SPAN> What requirements does tcpreplay have?</A>
  143. </H2>
  144. <P>
  145. <OL>
  146. <LI>You'll need recent versions of the libnet<A NAME="tex2html2"
  147. HREF="#foot36"><SUP><SPAN CLASS="arabic">2</SPAN></SUP></A> and libpcap<A NAME="tex2html3"
  148. HREF="#foot37"><SUP><SPAN CLASS="arabic">3</SPAN></SUP></A> libraries.
  149. </LI>
  150. <LI>To support the packet decoding feature you'll need tcpdump<A NAME="tex2html4"
  151. HREF="#foot38"><SUP><SPAN CLASS="arabic">4</SPAN></SUP></A> installed.
  152. </LI>
  153. <LI>You'll also need a compatible operating system. Basically, any UNIX-like
  154. or UNIX-based operating system should work. Linux, *BSD, Solaris,
  155. OS X and others should all work. If you find any compatibility issues
  156. with any UNIX-like/based OS, please let me know.
  157. </LI>
  158. </OL>
  159. <P>
  160. <H2><A NAME="SECTION00026000000000000000">
  161. <SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">6</SPAN> Are there binaries available?</A>
  162. </H2>
  163. <P>
  164. The tcpreplay project does not maintain binaries for any platforms.
  165. However some operating systems such as Debian GNU/Linux (apt-get)
  166. and OS X (fink) have packages available. Try searching on Google.
  167. <P>
  168. <H2><A NAME="SECTION00027000000000000000">
  169. <SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">7</SPAN> Is there a Microsoft Windows port?</A>
  170. </H2>
  171. <P>
  172. Not really. We had one user port the code over for an old version
  173. of tcpreplay to Windows. Now we're looking for someone to help merge
  174. and maintain the code in to the main development tree. If you're interested
  175. in helping with this please contact Aaron Turner or the tcpreplay-users
  176. list. Other then that, you can download the tcpreplay-win32.zip file
  177. from the website and give it a go. Please understand that the Win32
  178. port of tcpreplay comes with no support whatsoever, so if you run
  179. into a problem you're on your own.
  180. <P>
  181. <H2><A NAME="SECTION00028000000000000000">
  182. <SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">8</SPAN> How is tcpreplay licensed?</A>
  183. </H2>
  184. <P>
  185. Tcpreplay is licensed under a three clause BSD-style license. For
  186. details see the docs/LICENSE file included with the source code.
  187. <P>
  188. <H2><A NAME="SECTION00029000000000000000">
  189. <SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">9</SPAN> What is tcpreplay?</A>
  190. </H2>
  191. <P>
  192. In the simplest terms, tcpreplay is a tool to send network traffic
  193. stored in pcap format back onto the network; basically the exact opposite
  194. of tcpdump. Just to make things more confusing, tcpreplay is also
  195. a suite of tools: tcpreplay, tcpprep, tcprewrite and flowreplay.
  196. <P>
  197. <H2><A NAME="SECTION000210000000000000000">
  198. <SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">10</SPAN> What are some uses for tcpreplay?</A>
  199. </H2>
  200. <P>
  201. Originally, tcpreplay was written to test network intrusion detection
  202. systems (NIDS), however tcpreplay has been used to test firewalls,
  203. routers, and other network devices. With the addition of flowreplay,
  204. most<A NAME="tex2html5"
  205. HREF="#foot46"><SUP><SPAN CLASS="arabic">5</SPAN></SUP></A> any udp or tcp service on a server can be tested as well.
  206. <P>
  207. <H2><A NAME="SECTION000211000000000000000">
  208. <SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">11</SPAN> What are some uses for flowreplay?</A>
  209. </H2>
  210. <P>
  211. A lot of people wanted a tool like tcpreplay, but wanted to be able
  212. to replay traffic <SPAN CLASS="textit">to</SPAN> a server. Since tcpreplay was unable to
  213. do this, I developed flowreplay which replays the data portion of
  214. the flow, but recreates the connection to the specified server(s).
  215. This makes flowreplay an ideal tool to test host intrusion detection
  216. systems (HIDS) as well as captured exploits and security patches when
  217. the actual exploit code is not available. Please note that flowreplay
  218. is still alpha quality code which means it doesn't work very well
  219. (some would argue it doesn't work at all) and is currently missing
  220. some important features.
  221. <P>
  222. <H2><A NAME="SECTION000212000000000000000">
  223. <SPAN CLASS="arabic">1</SPAN>.<SPAN CLASS="arabic">12</SPAN> What is the history of tcpreplay?</A>
  224. </H2>
  225. <P>
  226. Tcpreplay has had quite a few authors over the past five or so years.
  227. One of the advantages of the BSD and GPL licenses is that if someone
  228. becomes unable or unwilling to continue development, anyone else can
  229. take over.
  230. <P>
  231. Originally, Matt Undy of Anzen Computing wrote tcpreplay. Matt released
  232. version 1.0.1 sometime in 1999. Sometime after that, Anzen Computing
  233. was (at least partially) purchased by NFR and development ceased.
  234. <P>
  235. Then in 2001, two people independently started work on tcpreplay:
  236. Matt Bing of NFR and Aaron Turner. After developing a series of patches
  237. (the -adt branch), Aaron attempted to send the patches in to be included
  238. in the main development tree.
  239. <P>
  240. After some discussion between Aaron and Matt Bing, they decided to
  241. continue development together. Since then, two major rewrites have
  242. occured, and more then thirty new features have been added, including
  243. the addition of a number of accessory tools.
  244. <P>
  245. Today, Aaron continues active development of the code.
  246. <P>
  247. <BR><HR><H4>Footnotes</H4>
  248. <DL>
  249. <DT><A NAME="foot136">... flowreplay</A><A
  250. HREF="node2.html#tex2html1"><SUP><SPAN CLASS="arabic">1</SPAN></SUP></A></DT>
  251. <DD>Flowreplay is still ``alpha'' quality and is not usable for most
  252. situations. Anyone interested in helping me develop flowreplay is
  253. encouraged to contact me.
  254. </DD>
  255. <DT><A NAME="foot36">... libnet</A><A
  256. HREF="node2.html#tex2html2"><SUP><SPAN CLASS="arabic">2</SPAN></SUP></A></DT>
  257. <DD>http://www.packetfactory.net/libnet/
  258. </DD>
  259. <DT><A NAME="foot37">... libpcap</A><A
  260. HREF="node2.html#tex2html3"><SUP><SPAN CLASS="arabic">3</SPAN></SUP></A></DT>
  261. <DD>http://www.tcpdump.org/
  262. </DD>
  263. <DT><A NAME="foot38">... tcpdump</A><A
  264. HREF="node2.html#tex2html4"><SUP><SPAN CLASS="arabic">4</SPAN></SUP></A></DT>
  265. <DD>http://www.tcpdump.org/
  266. </DD>
  267. <DT><A NAME="foot46">...
  268. most</A><A
  269. HREF="node2.html#tex2html5"><SUP><SPAN CLASS="arabic">5</SPAN></SUP></A></DT>
  270. <DD>Note the flowreplay does not support protocols such as ftp which use
  271. multiple connections.
  272. </DD>
  273. </DL>
  274. <DIV CLASS="navigation"><HR>
  275. <!--Navigation Panel-->
  276. <A NAME="tex2html132"
  277. HREF="node3.html">
  278. <IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
  279. <A NAME="tex2html128"
  280. HREF="FAQ.html">
  281. <IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
  282. <A NAME="tex2html122"
  283. HREF="node1.html">
  284. <IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
  285. <A NAME="tex2html130"
  286. HREF="node1.html">
  287. <IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
  288. <BR>
  289. <B> Next:</B> <A NAME="tex2html133"
  290. HREF="node3.html">2 Bugs, Feature Requests,</A>
  291. <B> Up:</B> <A NAME="tex2html129"
  292. HREF="FAQ.html">Tcpreplay 3.x FAQ</A>
  293. <B> Previous:</B> <A NAME="tex2html123"
  294. HREF="node1.html">Contents</A>
  295. &nbsp; <B> <A NAME="tex2html131"
  296. HREF="node1.html">Contents</A></B> </DIV>
  297. <!--End of Navigation Panel-->
  298. <ADDRESS>
  299. Aaron Turner
  300. 2005-08-07
  301. </ADDRESS>
  302. </BODY>
  303. </HTML>