... | @@ -19,18 +19,15 @@ Pcap logging will create several files using the following naming: `<sw_name>-<i |
... | @@ -19,18 +19,15 @@ Pcap logging will create several files using the following naming: `<sw_name>-<i |
|
|
|
|
|
If you enable pcap in the `p4app.json` configuration file, switches will be started with the `--pcap` option and use as output dir `./pcap`.
|
|
If you enable pcap in the `p4app.json` configuration file, switches will be started with the `--pcap` option and use as output dir `./pcap`.
|
|
|
|
|
|
### Wireshark/Tshark:
|
|
### *Wireshark*/*TShark*:
|
|
|
|
|
|
Another option is to observe the traffic as it flows. For that you can use tools like `tshark` and its GUI version `wireshark`. Wireshark
|
|
Another option is to observe the traffic as it flows. For that you can use tools like *TShark* and its GUI version *Wireshark*, which are already installed in the VM. To capture traffic with *TShark* run:
|
|
is already installed in the VM, you can find its executable in the desktop.
|
|
|
|
|
|
|
|
To capture traffic with tshark run:
|
|
|
|
|
|
|
|
```bash
|
|
```bash
|
|
sudo tshark -i <interface_name>
|
|
sudo tshark -i <interface_name>
|
|
```
|
|
```
|
|
|
|
|
|
### Tcpdump:
|
|
### *Tcpdump*:
|
|
|
|
|
|
Similarly, and if you prefer, you can use `tcpdump` (also already installed in the VM).
|
|
Similarly, and if you prefer, you can use `tcpdump` (also already installed in the VM).
|
|
|
|
|
... | | ... | |