Totally bogus scan results from 3.9.2

[szamosj]

Describe the bug
A clear and concise description of what the bug is.

When I run Angry IP Scanner, it usually finds 30+ hosts on my /24 subnet, but most or occasionally all are bogus.
The subnet currently has 3 pingable IPs. When I run 2.2.1, that one returns the correct result.

To Reproduce
Steps to reproduce the behavior:

1. Enter IP range = 172.23.233.0 to 172.23.233.255
2. Click "Start"

Expected behavior
Finding only 3 hosts, not 30+

Screenshots
If applicable, add screenshots to help explain your problem.

Versions (please copy from the About dialog or complete manually):

• Version of Angry IP Scanner
  Version: 3.9.2
  Build date: 2025-08-18
• OS, version, CPU architecture: Windows 8.1, Intel Xeon 5504
• Java version, vendor (java -version) - or if Windows installer was used with bundled Java
  Java: BellSoft 17.0.16+12-LTS
  OS: Windows 8.1 6.3 (amd64)
  SWT: win32 4968

Logs:

• Please run Angry IP Scanner from Terminal and see if any relevant logs were written. Paste them here:
  • Windows: jre\bin\java -jar ipscan.exe (inside of installation directory, e.g. C:\Program Files\Angry IP Scanner)
  • Mac: Angry\ IP\ Scanner.app/Contents/MacOS/ipscan
  • Linux: ipscan or java -jar ipscan.jar

C:\Program Files\Angry IP Scanner>jre\bin\java -jar ipscan.exe
Oct 27, 2025 11:54:20 PM net.azib.ipscan.fetchers.HostnameFetcher
WARNING: Could not get InetAddressImpl
java.lang.reflect.InaccessibleObjectException: Unable to make field static final java.net.InetAddressImpl java.net.InetAddress.impl accessible: module java.base
does not "opens java.net" to unnamed module @5a1c0542
at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(Unknown Source)
at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(Unknown Source)
at java.base/java.lang.reflect.Field.checkCanSetAccessible(Unknown Source)
at java.base/java.lang.reflect.Field.setAccessible(Unknown Source)
at net.azib.ipscan.fetchers.HostnameFetcher.(HostnameFetcher.java:37)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Unknown Source)
at java.base/java.lang.reflect.Constructor.newInstance(Unknown Source)
at net.azib.ipscan.di.Injector.createInstance(Injector.java:41)
at net.azib.ipscan.di.Injector.require(Injector.java:24)
at java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Unknown Source)
at java.base/java.util.stream.ReferencePipeline$Head.forEach(Unknown Source)
at net.azib.ipscan.di.Injector.register(Injector.java:29)
at net.azib.ipscan.config.ComponentRegistry.register(ComponentRegistry.java:20)
at net.azib.ipscan.config.ComponentRegistry.init(ComponentRegistry.java:35)
at net.azib.ipscan.config.ComponentRegistry.init(ComponentRegistry.java:29)
at net.azib.ipscan.Main.main(Main.java:57)

Attached one 3.9.2 result log with bogus hosts and a 2.2.1 result log that is correct (for comparison)

scan22.txt

scan392.txt

[JonnyTech]

Are you set to view alive hosts only?

[szamosj]

No, but changing view had no effect on the results -- the IPs were bogus.  However, changing "Pinging method" did have some effect:1. Windows ICMP: all results bogus, did not find any of the 3 alive hosts2. UDP packet:  many bogus results, but it did find all 3 alive hosts3. TCP port probe: many bogus results, but it did find all 3 alive hosts4. Combined UDP + TCP: many bogus results, but it did find all 3 alive hosts 5. Java built-in: many bogus results, but it did find all 3 alive hosts 6. ARP: many bogus results, found 1 of the 3 alive hosts On Tuesday, October 28, 2025 at 01:33:12 AM PDT, JonnyTech ***@***.***> wrote: JonnyTech left a comment (angryip/ipscan#488) Are you set to view alive hosts only? image.png (view on web) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[JonnyTech]

When you say bogus, what is the colour of the circle at the start of the lines?

[szamosj]

Blue; and there are ping results from 0 ms to 2000 ms as shown below. On Tuesday, October 28, 2025 at 10:59:38 AM PDT, JonnyTech ***@***.***> wrote: JonnyTech left a comment (angryip/ipscan#488) When you say bogus, what is the colour of the circle at the start of the lines? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[JonnyTech]

as shown below

If you send an email then the images and attachments are stripped so we cannot see anything. Please post directly from the github webpage.