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
Decided to also try out the WiFi scanning option and to my suprise I was caught with an informal error when trying to start data on the interface. The following error occurred
I figured this was just me being weird, so I decided to pop open airmon ( as instructed ) [typically I use other tools but it was just to recreate the error] and I started one of my interfaces. I then configured the script properly and got an issue still saying that I was trying to use wlan0 when the configuration file and other options all stated using the interface wlp6s0mon.
Further Fixing
I highly suggest that you do end up changing the hardcoded value that is used in the code file shown below.
When it comes to port scanning on networks, IoT devices will typically use ports like 5555 or 8888 or even other weird and wacky ports like 1532. It's highly suggested that you also allow users to customize the port range start and end. Instead of hardcoding values as executed in
scan_start = 1
scan_end = 1025
Sub Note: Port Scanning Suggestions
When you start scanning or ask for input, the suggestion or example is 192.168.1.1/24. This is a network range and as attempted in the script is not supported by the scanner itself. Currently, I run a network that uses Class A private IP addresses, so the range 10.0.0.1/24 would be my equivalent of 192.168.1.1/24. Generally speaking, this range does not work or is not supported! Definitely suggest changing recommendations!
The text was updated successfully, but these errors were encountered:
Decided to also try out the WiFi scanning option and to my suprise I was caught with an informal error when trying to start data on the interface. The following error occurred
Recreation
I figured this was just me being weird, so I decided to pop open airmon ( as instructed ) [typically I use other tools but it was just to recreate the error] and I started one of my interfaces. I then configured the script properly and got an issue still saying that I was trying to use
wlan0
when the configuration file and other options all stated using the interfacewlp6s0mon
.Further Fixing
I highly suggest that you do end up changing the hardcoded value that is used in the code file shown below.
scanner.py
Suggested Fix
When it comes to port scanning on networks, IoT devices will typically use ports like 5555 or 8888 or even other weird and wacky ports like 1532. It's highly suggested that you also allow users to customize the port range start and end. Instead of hardcoding values as executed in
Sub Note: Port Scanning Suggestions
When you start scanning or ask for input, the suggestion or example is
192.168.1.1/24
. This is a network range and as attempted in the script is not supported by the scanner itself. Currently, I run a network that uses Class A private IP addresses, so the range10.0.0.1/24
would be my equivalent of192.168.1.1/24
. Generally speaking, this range does not work or is not supported! Definitely suggest changing recommendations!The text was updated successfully, but these errors were encountered: