You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: examples/syn-flood/README.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,9 +14,15 @@ The example is located in the `examples/syn-flood` sub-directory. To run the app
14
14
/examples/syn-flood$ cargo run -- -f syn-flood.toml
15
15
```
16
16
17
+
To observe the `SYN` flood traffic, in the vagrant VM, run `tcpdump` to capture packets sent to the destination IP address and port,
18
+
19
+
```
20
+
$ sudo tcpdump -nn host 10.100.1.255 and port 80
21
+
```
22
+
17
23
## Explanation
18
24
19
-
The application schedules a periodic pipeline on port `eth1`'s assigned core `1`. The pipeline will repeat every 10 milliseconds. Instead of receiving packets from the port, the pipeline uses `batch::poll_fn` to generate a batch of new SYN packets each iteration and sends them through the port. Every packet is assigned a different spoofed source IP address.
25
+
The application schedules a periodic pipeline on port `eth1`'s assigned core `1`. The pipeline will repeat every 10 milliseconds. Instead of receiving packets from the port, the pipeline uses `batch::poll_fn` to generate a batch of new SYN packets each iteration and sends them to the interface `eth3` with assigned IP `10.100.1.255` on port`80`. Every packet is assigned a different spoofed source IP address.
20
26
21
27
On the main core `0`, a scheduled task prints out the port metrics once every second.
0 commit comments