Sonar Scanning Wrong IP's

I'm using Sonar for network discovery, have input all the ip ranges or subnets for the areas of our network I want to scan, and I'm seeing during the scan it's scanning IP's I've not setup for that scan. At first I thought maybe it's doing this for whatever reason but the scan has been running much longer than I imagine it should. Any ideas as to why it's scanning IP's I never setup for the scan? (10.x.x.x , privates IP's, I haven't setup to scan any of these, refer below)

Find more posts tagged with

help!!!

sonar_discovery

subnets

discovering

perform

scanning

ip address

sonar

Accepted answers

rharland2012

Okay, I have your answer. On the 'Discovery Settings' step of sonar discovery, do you see the hop count slider? You've got it set to 1, I'll bet.

Set it to 0.

If this works and you found it helpful/correct, please mark as such.

Thanks.

All comments

rharland2012

Any chance you entered a seed router as part of this discovery?

FormerMember

I never thought about that.... One of the IP's could have this indeed, I'm just plugging in ranges to discover everything on certain subnets. Any way to bypass this other than leave the IP out for the seed router? Or anything else that might be causing this I can check as well?

rharland2012

Unless you specified a seed router (see attached image), it shouldn't auto-populate. Can you show the ranges (with identifying octets scrubbed out, of course)? I don't see a logical way that non-specified subnets/ranges would include things you didn't define.

FormerMember

This scan I used IP ranges, not Subnets, so plugged roughly 30 IP ranges into this portion, most of them are a /25 mask, some a /24 so there's not a real great deal of IP's in those ranges. Is there any difference using ranges compared to subnets? I've just started using this tool so I've been using both options to test.