This require some traffic to be actually captured. Also note that the `command-argument` string is both passed to the command and written as file, hence some restrictions apply.
This require some traffic to be actually captured. Also note that the `command-argument` string is both passed to the command and written as file, hence some restrictions apply.
This saves the packet dump (count is 1) from the loopback interface to a file. To trigger the capture use something like:
```
nc -u localhost 1 <<<DATA
```
While `user` is the owner of the packet dump file, the invoking user must be able to capture traffic on the device.
tcpdump-ln-ilo-w/path/to/output-file-c1-Zuser
Evidence
Upstream reference
Environment
Local host
Compatibility
Linux reference. macOS compatibility has not been checked for this command and execution context.
This saves the packet dump (count is 1) from the loopback interface to a file. To trigger the capture use something like:
```
nc -u localhost 1 <<<DATA
```
While `user` is the owner of the packet dump file, the invoking user must be able to capture traffic on the device.
tcpdump-ln-ilo-w/path/to/output-file-c1-Zuser
Evidence
Upstream reference
Environment
Local host
Compatibility
Linux reference. macOS compatibility has not been checked for this command and execution context.
This saves the packet dump (count is 1) from the loopback interface to a file. To trigger the capture use something like:
```
nc -u localhost 1 <<<DATA
```
While `user` is the owner of the packet dump file, the invoking user must be able to capture traffic on the device.
tcpdump-ln-ilo-w/path/to/output-file-c1-Zuser
Evidence
Upstream reference
Environment
Local host
Compatibility
Linux reference. macOS compatibility has not been checked for this command and execution context.