diff options
| author | Andrey Konovalov <andreyknvl@gmail.com> | 2017-10-30 13:05:13 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-10-30 13:05:13 +0100 |
| commit | a9b8c06deee63ab39aa7c634f10e56c94cd2af16 (patch) | |
| tree | 0fc641301775092eed858c755ab5132ba0528c80 /docs/linux/external_fuzzing_network.md | |
| parent | 80c748800e07c28955c3cf696e7eda464a3f0634 (diff) | |
Update external_fuzzing_network.md
Diffstat (limited to 'docs/linux/external_fuzzing_network.md')
| -rw-r--r-- | docs/linux/external_fuzzing_network.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/linux/external_fuzzing_network.md b/docs/linux/external_fuzzing_network.md index f5c844767..72c576b13 100644 --- a/docs/linux/external_fuzzing_network.md +++ b/docs/linux/external_fuzzing_network.md @@ -13,7 +13,7 @@ The template descriptions can be found in [sys/linux/vnet.txt](/sys/linux/vnet.t At this moment there are 2 fake syscalls: `syz_emit_ethernet` and `syz_extract_tcp_res`. The first one externally sends a packet through the virtual interface. The second one tries to externally receive a packet back and parse TCP sequence numbers from it for use in subseqent packets. -There many protocols or protocol extensions that are not described yet, so the additions are welcome! +There are many protocols or protocol extensions that are not described yet, so the additions are welcome! Since fuzzing may be done in mutiple executor proccesses within the same VM instance, we need a way to isolate the virtual network for different executors. Right now this is done by creating one virtual interface per executor and assigning different MAC, IPv4 and IPv6 addresses to each of these interfaces. |