summaryrefslogtreecommitdiff
path: root/README.tcpreplay
diff options
context:
space:
mode:
authorlijia <[email protected]>2019-07-10 17:54:02 +0800
committerlijia <[email protected]>2019-07-10 17:54:02 +0800
commitf36a4fca258fc0a725352cfc744037634a08b076 (patch)
tree45865b5d9dee3037ee491b6aa5fa46febcf22dcf /README.tcpreplay
copy from intranet.
Diffstat (limited to 'README.tcpreplay')
-rw-r--r--README.tcpreplay48
1 files changed, 48 insertions, 0 deletions
diff --git a/README.tcpreplay b/README.tcpreplay
new file mode 100644
index 0000000..0313645
--- /dev/null
+++ b/README.tcpreplay
@@ -0,0 +1,48 @@
+$Id: README 1796 2007-04-11 04:55:14Z aturner $
+[Please note that licensing, compiling, usage and other documentation can be
+found in the docs subdirectory.]
+
+If you have a question or think you are experiancing a bug, it is important
+that you provide enough information for us to help you. Failure to provide
+enough information will likely cause your email to be ignored or get an
+annoyed reply from the author.
+
+If your problem has to do with COMPILING tcpreplay:
+- Version of tcpreplay you are trying to compile
+- Platform (Red Hat Linux 9 on x86, Solaris 7 on SPARC, OS X on PPC, etc)
+- ./configure arguments
+- Contents of config.log
+- Output from 'make'
+- Any additional information you think that would be useful.
+
+If your problem has to do with RUNNING tcpreplay or one of the sub-tools:
+- Version information (output of -V)
+- Command line used (options and arguments)
+- Platform (Red Hat Linux 9 on Intel, Solaris 7 on SPARC, etc)
+- Make & model of the network card(s) and driver(s) version
+- Error message (if available) and/or description of problem
+- If possible, attach the pcap file used (compressed with bzip2 or gzip
+ preferred)
+- The core dump or backtrace if available
+- Detailed description of your problem or what you are trying to accomplish
+
+Note: The author of tcpreplay primarily uses OS X; hence, if you're reporting
+an issue on another platform, it is important that you give very detailed
+information as I may not be able to reproduce your issue.
+
+You are also strongly encouraged to read the extensive documentation (man
+pages, FAQ, documents in /docs and email list archives) BEFORE posting to the
+tcpreplay-users email list:
+
+http://lists.sourceforge.net/lists/listinfo/tcpreplay-users
+
+Lastly, please don't email the author directly with your questions. Doing so
+prevents others from potentially helping you and your question/answer from
+showing up in the list archives.
+
+Thanks,
+Aaron (tcpreplay author)
+
+PS:
+This product includes software developed by the University of
+California, Berkeley, Lawrence Berkeley Laboratory and its contributors.