Lines Matching +full:protocol +full:- +full:tests

7 code execution etc) please send an e-mail to [email protected], do not use
10 To report a non-security problem (failure to compile, incorrect output in the
11 protocol printout, missing support for a particular protocol etc) please check
15 libpcap. If it does (and it is not a security-related problem, otherwise see
17 [bug tracker](https://github.com/the-tcpdump-group/tcpdump/issues)
21 * tcpdump and libpcap version (`tcpdump --version`)
23   (`uname -a`, compiler name and version, CPU type etc.)
33 [subscribe to the mailing list](https://www.tcpdump.org/#mailing-lists)
42 1) [Fork](https://help.github.com/articles/fork-a-repo/) the Tcpdump
43    [repository](https://github.com/the-tcpdump-group/tcpdump).
53    git remote add upstream https://github.com/the-tcpdump-group/tcpdump
59    * add (via `configure`, in `Makefile`) some warnings options (`-Wall`,
60      `-Wmissing-prototypes`, `-Wstrict-prototypes`, ...) to the compiler if it
66    ./configure && make -s && make check
69 6) Add/update tests
70    The `tests` directory contains regression tests of the dissection of captured
72    `-w sample.pcap`.  Additional options, such as `-n`, are used to create relevant
73    and reproducible output; `-#` is used to indicate which particular packets
74    have output that differs.  The tests are run with the `TZ` environment
76    tests are being run, is used when "local time" values are printed.  The
83    Configuration is set in `tests/TESTLIST`.
86    test-name   sample.pcap   sample.out   tcpdump-options
91    (cd tests && TZ=GMT0 ../tcpdump -# -n -r sample.pcap tcpdump-options > sample.out)
94    Or, for convenience, use `./update-test.sh test-name`
97    (none, `-v`, `-vv`, `-vvv`, etc.) depending on the code.
102    all tests pass.
109    (If the rebase fails and you cannot resolve, issue `git rebase --abort`
114 10) [Initiate and send](https://help.github.com/articles/using-pull-requests/)
116     This will trigger the upstream repository CI tests.
128    random position, for example by capturing with `-s size` option.
129    If your code reads and decodes every byte of the protocol packet, then to
139    would have to be bounds-checked using the `ND_TCHECK_*()` macros:
146    * Assign: `ndo->ndo_protocol = "protocol";`
153    sudo ./tcpdump -s snaplen [-v][v][...] -i lo # in a terminal
154    sudo tcpreplay -i lo sample.pcap             # in another terminal
174    If the commit concerns a protocol, the summary line must start with
175    "protocol: ".
182 *  Avoid non-ASCII characters in code and commit messages.