Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

first subnet #3

Closed
juvilius opened this issue Dec 29, 2021 · 3 comments
Closed

first subnet #3

juvilius opened this issue Dec 29, 2021 · 3 comments

Comments

@juvilius
Copy link

why is it not permitted to configure "0" as the first subnet to scan?

@git-elliot
Copy link
Collaborator

If you know little bit of networking then 0 in the last octet is used for network ID and this IP can not be a host IP.

@juvilius
Copy link
Author

i know very little indeed. what i meant by first subnet was the third number or like you say octet.
long story short, i wasn't able to scan for this IP in my routers network: 192.168.0.100

@git-elliot
Copy link
Collaborator

git-elliot commented Jan 16, 2022

First three octets are auto fetched from the routers wifi and the last octet is what you can change as per your need. Valid range for last octet which you can change in settings also first subnet and last subnet is 1 to 254. 0 is reserved for network ID and 255 is reserved for broadcast address.
I guess you have to change last subnet to value above 100 in order to scan the IP 192.168.0.100

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants