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

README 2.0 KB
History Raw

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748 
  1. $Id: README 1544 2006-07-29 06:21:36Z aturner $
    2. 

  2. [Please note that licensing, compiling, usage and other documentation can be 
    3. 

  3. found in the docs subdirectory.]
    4. 

  4. 

  5. If you have a question or think you are experiancing a bug, it is important
    6. 

  6. that you provide enough information for us to help you.  Failure to provide
    7. 

  7. enough information will likely cause your email to be ignored or get an
    8. 

  8. annoyed reply from the author.
    9. 

  9. 

  10. If your problem has to do with COMPILING tcpreplay:
    11. 

  11. - Version of tcpreplay you are trying to compile
    12. 

  12. - Platform (Red Hat Linux 9 on x86, Solaris 7 on SPARC, OS X on PPC, etc)
    13. 

  13. - ./configure arguments
    14. 

  14. - Contents of config.log
    15. 

  15. - Output from 'make'
    16. 

  16. - Any additional information you think that would be useful.
    17. 

  17. 

  18. If your problem has to do with RUNNING tcpreplay or one of the sub-tools:
    19. 

  19. - Version information (output of -V)
    20. 

  20. - Command line used (options and arguments)
    21. 

  21. - Platform (Red Hat Linux 9 on Intel, Solaris 7 on SPARC, etc)
    22. 

  22. - Make & model of the network card(s) and driver(s) version
    23. 

  23. - Error message (if available) and/or description of problem
    24. 

  24. - If possible, attach the pcap file used (compressed with bzip2 or gzip
    25. 

  25.     preferred)
    26. 

  26. - The core dump or backtrace if available
    27. 

  27. - Detailed description of your problem or what you are trying to accomplish
    28. 

  28. 

  29. Note: The author of tcpreplay primarily uses OS X; hence, if you're reporting
    30. 

  30. an issue on another platform, it is important that you give very detailed
    31. 

  31. information as I may not be able to reproduce your issue.
    32. 

  32. 

  33. You are also strongly encouraged to read the extensive documentation (man
    34. 

  34. pages, FAQ, documents in /docs and email list archives) BEFORE posting to the
    35. 

  35. tcpreplay-users email list:
    36. 

  36. 

  37. http://lists.sourceforge.net/lists/listinfo/tcpreplay-users
    38. 

  38. 

  39. Lastly, please don't email the author directly with your questions.  Doing so
    40. 

  40. prevents others from potentially helping you and your question/answer from
    41. 

  41. showing up in the list archives.
    42. 

  42. 

  43. Thanks,
    44. 

  44. Aaron (tcpreplay author)
    45. 

  45. 

  46. PS:
    47. 

  47. This product includes software developed by the University of
    48. 

  48. California, Berkeley and its contributors.
    49.