Lines Matching +full:multi +full:- +full:touch
7 code execution etc) please send an e-mail to security@tcpdump.org, do not use
10 To report a non-security problem (failure to compile, incorrect output in the
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 2) [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
57 5) Do a `touch .devel` in your working directory.
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
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
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.
109 (If the rebase fails and you cannot resolve, issue `git rebase --abort`
114 11) [Initiate and send](https://help.github.com/articles/using-pull-requests/)
125 $ ./configure --enable-instrument-functions
126 $ make -s clean all
141 - unset or set to an empty string, print nothing, like with no
143 - set to "all" or "a", print all the functions names
144 - set to "global" or "g", print only the global functions names
158 The library libbfd is used, therefore the binutils-dev package is required.
166 random position, for example by capturing with `-s size` option.
183 would have to be bounds-checked using the `ND_TCHECK_*()` macros:
197 * Assign: `ndo->ndo_protocol = "protocol";`
204 sudo ./tcpdump -s snaplen [-v][v][...] -i lo # in a terminal
205 sudo tcpreplay -i lo sample.pcap # in another terminal
223 signed value is fetched. For multi-byte values, `BE` indicates that
224 a big-endian value ("network byte order") is fetched, and `LE`
225 indicates that a little-endian value is fetched. *n* is the length,
226 in bytes, of the multi-byte integral value to be fetched.
231 * tcpdump runs on both big-endian and little-endian systems, so
232 fetches of multi-byte integral values must be done in a fashion
234 tcpdump. The `GET_BE_*()` macros will fetch a big-endian value and
235 return a host-byte-order value on both big-endian and little-endian
236 machines, and the `GET_LE_*()` macros will fetch a little-endian
237 value and return a host-byte-order value on both big-endian and
238 little-endian machines.
241 multi-byte values, and packet values are not guaranteed to be
258 both big-endian and little-endian machines and will fetch values even
286 returns a string that is either a host name, if the `-n` flag wasn't
288 standard XXX.XXX.XXX.XXX-style representation of the address.
291 returns a string that is either a host name, if the `-n` flag wasn't
293 standard XXXX::XXXX-style representation of the address.
295 `GET_MAC48_STRING()` fetches a 48-bit MAC address (Ethernet, 802.11,
297 name, if the `-n` flag wasn't specified and a host name could be
299 XX:XX:XX:XX:XX:XX-style representation of the address.
301 `GET_EUI64_STRING()` fetches a 64-bit EUI pointed to by *p* and
302 returns a string that is the standard XX:XX:XX:XX:XX:XX:XX:XX-style
305 `GET_EUI64LE_STRING()` fetches a 64-bit EUI, in reverse byte order,
307 XX:XX:XX:XX:XX:XX:XX:XX-style representation of the address.
313 * `LINKADDR_MAC48` - if the length is 6, the string has the same
318 * `LINKADDR_FRELAY` - the string is "DLCI XXX", where XXX is the
322 * `LINKADDR_EUI64`, `LINKADDR_ATM`, `LINKADDR_OTHER` -
331 Those types all are aligned only on a 1-byte boundary, so a
351 The `nd_*` types for link-layer addresses are:
353 * `nd_mac48`, for MAC-48 (Ethernet, 802.11, etc.) addresses;
354 * `nd_eui64`, for EUI-64 values.
357 *N*-byte sequence should be declared as `nd_byte[N]`.
384 11) Avoid non-ASCII characters in code and commit messages.