All hosts display as alive

[ghost]

Mac OS X 10.10.5 IP Scanner 3.2.1

When I scan with combined method, all IPs return as alive. No other scanners work. Happens on latest version as well.

How do I fix it?

Thanks!

[angryziber]

Please use the latest version 3.3.3 and try UDP and TCP pingers separately. Which one works?

Do you have an unusual network configuration, socks proxy or something simular?

On Sat, 29 Aug 2015, 16:09 jstipe notifications@github.com wrote:

Mac OS X 10.10.5 IP Scanner 3.2.1

When I scan with combined method, all IPs return as alive. No other scanners work. Happens on latest version as well.

How do I fix it?

Thanks!

— Reply to this email directly or view it on GitHub https://github.com/angryziber/ipscan/issues/43.

[ghost]

Running version 3.3.3:

Scanned 172.22.1.0/24, subnet I am in:

UDP returned no hosts

TCP returned 254 hosts

Probably have less than 20 hosts on the network.

No unusual network configuration. No proxies enabled.

Currently connected to home network behind Netgear N600 router. Same behavior on work network connected to Cisco access layer and backbone network devices through Cisco Wireless Access Point.

On Sat, Aug 29, 2015 at 11:58 AM, Anton Keks notifications@github.com wrote:

Please use the latest version 3.3.3 and try UDP and TCP pingers separately. Which one works?

Do you have an unusual network configuration, socks proxy or something simular?

On Sat, 29 Aug 2015, 16:09 jstipe notifications@github.com wrote:

Mac OS X 10.10.5 IP Scanner 3.2.1

When I scan with combined method, all IPs return as alive. No other scanners work. Happens on latest version as well.

How do I fix it?

Thanks!

— Reply to this email directly or view it on GitHub https://github.com/angryziber/ipscan/issues/43.

— Reply to this email directly or view it on GitHub https://github.com/angryziber/ipscan/issues/43#issuecomment-136004913.

[ghost]

I scanned at work this morning in case it might be something on my home network. See attached. 508 hosts returned as alive. There are probably less than a dozen on this network.

[ghost]

Do you have any suggestions? The tool is not very useful to me if it returns dead hosts as alive.

[ghost]

Downloaded version 3.4. Issue persists

[medved-nsk]

The only thing I can suppose there is a gateway/router which answer with non-used IPs. The first thing which worth to be checked are the MAC addresses of these IPs. I'm not familar with MacOS but since its bsd-kernel based then 'arp -na' should help.

[le-jawa]

I'm seeing the exact same issue with 3.4.1. On a Windows box on the same subnet, AngryIP works as expected. From a Mac (OS X 10.10.5), I see the following issues:

• Results are inconsistent. Sometimes, a few hosts will show up as dead (but not nearly all of them), but most of the time, all hosts show up as alive (blue dot, not green).
• The totals that get tallied at the end are not only off, but impossible (for example, 437/254 hosts alive). Again, this number varies with each scan.
• A straight UDP scan returns no hosts alive. TCP returns all hosts alive.
• Again, this works fine on the same subnets with the Windows version, so I don't see it being a router/switch issue.
• JRE on the Mac is version 1.8.91.

Thanks for looking at this, and let me know if you need additional info.

[tuksaur]

seeing same behavior. no amount of reinstall resolves. TCP all hosts alive all the time; UDP no hosts alive. Only 20 actual hosts on network.

Is there a configuration file that can be altered to correct this behavior?

Angry IP v3.4.2; build date August 4, 2016. Running Mac OSX 10.11.6.

[angryziber]

No idea yet of what might be the cause, but have any of you tried using TCP/UDP/Combined pingers on Windows on the same subnet? Windows version uses a different pinging method by default provided by the OS. Also, if you can, please provide a dump of packets during the scan using either Wireshark or tcpdump

On Thu, 18 Aug 2016, 18:45 tuksaur, notifications@github.com wrote:

seeing same behavior. no amount of reinstall resolves. TCP all hosts alive all the time; UDP no hosts alive. Only 20 actual hosts on network.

Is there a configuration file that can be altered to correct this behavior?

Angry IP v3.4.2; build date August 4, 2016. Running Mac OSX 10.11.6.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/angryziber/ipscan/issues/43#issuecomment-240765892, or mute the thread https://github.com/notifications/unsubscribe-auth/AA11YKCF39ubiNeteS9fB0yQw96nm1Cgks5qhH4pgaJpZM4F0f8E .

[tuksaur]

my windows 7 vm scans just fine. expected results. but i dont want to have to run my vm every time i need to do a network scan. OS X used to work just fine.

dump file attached from OS X scan (all hosts alive).

DumpFile01.pcap.zip

[angryziber]

Thanks for the quick dump, I will analyze it. Which Pinger did you use, the default Combined one? Also, what happens if you use the same Pinger in Windows?

On Thu, Aug 18, 2016 at 7:08 PM tuksaur notifications@github.com wrote:

my windows 7 vm scans just fine. expected results. but i dont want to have to run my vm every time i need to do a network scan. OS X used to work just fine.

dump file attached from OS X scan (all hosts alive).

DumpFile01.pcap.zip https://github.com/angryziber/ipscan/files/425365/DumpFile01.pcap.zip

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/angryziber/ipscan/issues/43#issuecomment-240773129, or mute the thread https://github.com/notifications/unsubscribe-auth/AA11YF1gsnOZ04GlOOFodo5nckS3Iqbcks5qhIOMgaJpZM4F0f8E .

[tuksaur]

ya no problem. thanks for putting a second set of eyes on it. I tried both TCP and TCP+UDP, same results in OSX. in Windows it gives expected/correct results. red icon for dead host, blue for alive (no greens; although only pinging for response and not for ports). OS X reports all 255 range as 'blue' or 'alive' for both Pinger types.

[angryziber]

The dump doesn't show anything unusual. Here is a debug build for OS X Please run it from Terminal, select TCP pinging method, scan, and paste the output that you get in the terminal.

[tuksaur]

here is a TXT of the debug. again, 254/254 ping/alive. angry_debug.txt

[angryziber]

Thanks, that means that sockets on your JVM behave erratically... Let's have another try (with some of the optimization options removed) ipscan-mac-3.4.x-debug.zip

[tuksaur]

sorry, what do you mean w/o the optimization options? or is that change built into the debug you sent?

[angryziber]

Yes, that's built-in. Please run the scan and attach the log

[tuksaur]

new scan results.

angry_debug.txt

[angryziber]

OK, that didn't help. Another try please: ipscan-mac-3.4.x-debug.zip

[tuksaur]

unfortunately same results as before.

angry_debug_v3.txt

[angryziber]

Thanks for trying, I am out of ideas for now. Do you use the official Java from Oracle?

[angryziber]

I have tried Angry IP Scanner 3.4.2 on two diffierent Macs with older and latest Java (1.8 b101) and scanning worked properly...

Please try installing the latest official JVM from Oracle: http://java.com

[tuksaur]

how can i completely uninstall/remove angry IP scanner from my OS X system and try a reinstall? i have java up to date.

On Aug 22, 2016, at 11:07 AM, Anton Keks notifications@github.com wrote:

I have tried Angry IP Scanner 3.4.2 on two diffierent Macs with older and latest Java (1.8 b101) and scanning worked properly...

Please try installing the latest official JVM from Oracle: http://java.com http://java.com/ — You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/angryziber/ipscan/issues/43#issuecomment-241443539, or mute the thread https://github.com/notifications/unsubscribe-auth/AQ-ysq4344iYaXD87hHlNLYgTtqeg0zJks5qibs9gaJpZM4F0f8E.

[le-jawa]

Angryziber,

Thanks for looking into this. I did a clean install of AngryIP 3.4.2 (I believe it was clean, anyway) and updated my JDK to 1.8.0.u101. Unfortunately, I'm still seeing the same problems; all hosts report alive, then the summary report shows an impossible number of live hosts (and it changes every scan). Also, I've also got OS X upgraded and updated all the way (10.11.6)

Could we be running a newer version of OS X than you?

[le-jawa]

tuksaur,

To answer your question to the best of my ability: Deleting the app itself should do it. I looked in ~/Library/Application Support and didn't see a directory for AngryIP, so I presume there are no other files for it beyond the app package.

I've been wrong before though... ;-)

[tuksaur]

np. thank you. i’ll use my windows VM until i get the change to clean wipe my Mac and try to reinstall. cheers,

On Aug 22, 2016, at 4:09 PM, le-jawa notifications@github.com wrote:

tuksaur,

To answer your question to the best of my ability: Deleting the app itself should do it. I looked in ~/Library/Application Support and didn't see a directory for AngryIP, so I presume there are no other files for it beyond the app package.

I've been wrong before though... ;-)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/angryziber/ipscan/issues/43#issuecomment-241533887, or mute the thread https://github.com/notifications/unsubscribe-auth/AQ-yssruaOctHHWXZ-s3QkFsm8MRqUQRks5qigHygaJpZM4F0f8E.

[Fractal7]

Currently using the latest version of Angry IP scanner on mac and I am as well now dealing with this issue.

[le-jawa]

I think I found the problem. Here's what I get when I run AngryIP from the command line as root:

SEVERE: Unable to create pinger: pinger.icmp
<full trace removed for brevity>
Caused by: java.lang.RuntimeException: Unable to extract native library: rocksaw
    at net.azib.ipscan.core.LibraryLoader.loadLibrary(LibraryLoader.java:48)
    at org.savarese.rocksaw.net.RawSocket.<clinit>(RawSocket.java:82)
    ... 19 more
Caused by: java.io.IOException: librocksaw.dylib not found in the jar file (classpath)
    at net.azib.ipscan.core.LibraryLoader.loadLibrary(LibraryLoader.java:34)
    ... 20 more

Full stack trace attached. AnryIP Stack Trace.txt