git Service of IN-Ulm e.V. Explore Help
Sign In
cbiedl
/
tcpreplay
1
0
Fork 0
Files
Tree: bd9528e255
Branches Tags
tcpreplay
/
tcpreplay.8

tcpreplay.8 2.1 KB
History Raw

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091 
  1. .\" yo there.
    2. 

  2. .TH TCPREPLAY 8  "12 April 1999"
    3. 

  3. .SH NAME
    4. 

  4. tcpreplay \- replay traffic from a saved tcpdump file
    5. 

  5. .SH SYNOPSIS
    6. 

  6. .na
    7. 

  7. .B tcpreplay
    8. 

  8. [
    9. 

  9. .B \-i
    10. 

  10. .I intf
    11. 

  11. ] [
    12. 

  12. .B \-l
    13. 

  13. .I loop count
    14. 

  14. ] [
    15. 

  15. .B \-r
    16. 

  16. .I rate
    17. 

  17. |
    18. 

  18. .B \-m
    19. 

  19. .I multiplier
    20. 

  20. ]
    21. 

  21. .I file ...
    22. 

  22. .br
    23. 

  23. .ad
    24. 

  24. .SH DESCRIPTION
    25. 

  25. .LP
    26. 

  26. .I Tcpreplay
    27. 

  27. is a program for replaying network traffic saved in packet-trace files
    28. 

  28. generated using 
    29. 

  29. \fItcpdump(8)\fP's
    30. 

  30. .B \-w
    31. 

  31. flag.
    32. 

  32. .LP
    33. 

  33. The basic operation of
    34. 

  34. .I tcpreplay
    35. 

  35. is to resend all packets from its input file(s) at the speed at which
    36. 

  36. they were recorded, at some specified data \fIrate\fP, or as fast as the hardware is 
    37. 

  37. capable of.  If no
    38. 

  38. \fIrate\fP or
    39. 

  39. \fImultiplier\fP are given, 
    40. 

  40. .I tcpreplay 
    41. 

  41. will replay packets as fast as the hardware will allow.
    42. 

  42. If no
    43. 

  43. \fIfile\fP is given,
    44. 

  44. .I tcpreplay
    45. 

  45. will accept packet data from \fIstdin\fP.
    46. 

  46. .SH OPTIONS
    47. 

  47. .LP
    48. 

  48. .TP
    49. 

  49. .B \-i
    50. 

  50. Specify the interface to send packets out on.
    51. 

  51. .TP
    52. 

  52. .B \-r
    53. 

  53. Resend the packets at the \fIrate\fR specified (in Mbps).
    54. 

  54. .TP
    55. 

  55. .B \-m
    56. 

  56. Resend the packets at a \fImultiple\fR of the speed at which they were
    57. 

  57. recorded.
    58. 

  58. .TP
    59. 

  59. .B \-l
    60. 

  60. Resend the pcap file(s) \fIloop count\fR times.
    61. 

  61. .SH "SEE ALSO"
    62. 

  62. tcpdump(8)
    63. 

  63. .SH AUTHOR
    64. 

  64. Matt Undy, Anzen Computing.
    65. 

  65. .LP
    66. 

  66. The current version is available via HTTP:
    67. 

  67. .LP
    68. 

  68. .RS
    69. 

  69. .I http://www.anzen.com/research/nidsbench/
    70. 

  70. .RE
    71. 

  71. .SH BUGS
    72. 

  72. .I tcpreplay
    73. 

  73. can only send packets as fast as your machine's interface,
    74. 

  74. processor, and disk will allow.
    75. 

  75. .LP
    76. 

  76. ``\fIN\fR write attempts failed from full buffers and were repeated''
    77. 

  77. does not indicate that these packets were not sent, but that the send
    78. 

  78. was retried \fIN\fR times until it succeeded.
    79. 

  79. .LP
    80. 

  80. Looping captured traffic may simulate odd conditions on a network.
    81. 

  81. For example, opening the same TCP connection multiple times may 
    82. 

  82. exhaust resources on machines tracking the connection. The 
    83. 

  83. .B \-l
    84. 

  84. flag is provided to allow faster sending on machines with greater I/O
    85. 

  85. constraints.
    86. 

  86. .LP
    87. 

  87. On BSD-based systems, kernel modifications are required to preserve
    88. 

  88. outgoing link layer source addresses. Refer to the \fIlibnet(3)\fP
    89. 

  89. documentation for more information on how to do this.
    90. 

  90. .LP
    91. 

  91. Please send bug reports to nidsbench@anzen.com.
    92.