From 34994e615adce0b07424a22131f6b687ef4de631 Mon Sep 17 00:00:00 2001 From: Brendan LE GLAUNEC Date: Thu, 12 Oct 2017 16:55:35 +0200 Subject: [PATCH] Fix in README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 424a681..38475de 100644 --- a/README.md +++ b/README.md @@ -95,7 +95,7 @@ The cameradar library also provides two functions that take file paths as inputs The **RTSP port used for most cameras is 554**, so you should probably specify 554 as one of the ports you scan. Not specifying any ports to the cameraccess application will scan the 554 and 8554 ports. -`docker run -t ullaakut/cameradar -p "18554,19000-19010" -t localhost` will scan the ports 18554, and the range of ports between 19000 and 19010 on localhost. +`docker run -t --net=host ullaakut/cameradar -p "18554,19000-19010" -t localhost` will scan the ports 18554, and the range of ports between 19000 and 19010 on localhost. You **can use your own files for the ids and routes dictionaries** used to attack the cameras, but the Cameradar repository already gives you a good base that works with most cameras, in the `/dictionaries` folder.