From d302000382da4aa74df1e3fe8d04d4cb35d23417 Mon Sep 17 00:00:00 2001 From: GyulyVGC <100347457+GyulyVGC@users.noreply.github.com> Date: Wed, 17 Aug 2022 16:57:56 +0200 Subject: [PATCH] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index ed4835ee..2c601c11 100644 --- a/README.md +++ b/README.md @@ -66,7 +66,7 @@ Then there is a detail about the initial timestamp of the sniffing process, the Finally, it describes the status of the possible filters applicable by the user through the command line: minimum number of packets for an address:port pair to be printed in the report, IP address version, transport layer protocol and port minimum and maximum number. -Note that an application layer protocol filter is not provided since the user can use the lowest and highest port options to this purpose (e.g., to filter DNS traffic a user can specify ```packet_sniffer -l 53 -h 53```, to filter HTTPS traffic a user can specify ```packet_sniffer -l 443 -h 443``` and so on). +Note that an application layer protocol filter is not provided since the user can use the lowest and highest port options to this purpose (e.g., to filter DNS traffic a user can specify ```sniffnet -l 53 -h 53```, to filter HTTPS traffic a user can specify ```sniffnet -l 443 -h 443``` and so on). ### Report addresses list @@ -140,7 +140,7 @@ In this section are reported the errors that may occur while the application is     In this case the application will suggest using the ```-d``` option to print on the standard output a list of the available devices. -    ```packet_sniffer -d``` prints a list of all the available network adapters names and addresses, as in the example that follows. +    ```sniffnet -d``` prints a list of all the available network adapters names and addresses, as in the example that follows.     ![Screenshot](./img/device_list.png)