SubnetPing is a handy tool to get information about used IP-addresses in an IPv4 network.
All Reviews:
No user reviews
Release Date:
Feb 13, 2019

Sign in to add this item to your wishlist, follow it, or mark it as not interested

Curator Review

Recommended
By Cadeaux Gratuit February 19

“Facile, relativement complet est petit, il permet de rapidement scanner un range de IP pour obtenir la liste des appareils connectés. Informations technique de base, outils réseau de base.”

Buy SubnetPing

 

Recent updates View all (1)

February 14

Upcomming Updates

- IPv6 Neighbor Discovery will be in final state soon

- SNMP will be testet in different network envoriments to improve it

- Trace IPv4 Network Diagram will be improved this week
- redraw cycle, speed up
- detect dublicate routes
- hop hostname DNS resolution
- target hostname DNS resolution
- GUI responsiveness
- GUI layout changes
- IPv6
5 comments Read more

About This Software

SubnetPing is a small but useful tool to determine information about used IPv4-addresses in an IPv4 network.

Detect IP-Addresses (IPv4)
Scan an entire IPv4/24 (Class C) subnet by sending IMCP echo requests to all possible hosts in the selected subnet.
SubnetPing uses the default network interface the operating system and local routing table offers for this task.
It should be possible detect available hosts in remote subnets, behind routers, remote networks thru an VPN, or even public networks as long as the hosts respond to IMCP echo requests and the TTL is high enough so that the packet will no be dropped by any router in the path.

Determine Ping (time in ms)
The Ping time is determined by sending an IMCP echo request to the target IPv4 and waiting for the IMCP echo reply. The Ping time is the locally measured time from sending the IMCP echo request to the target until the IMCP echo reply received. The IMCP echo reply has to be received within a give time-frame (timeout), or the Ping attempted will be considered as a timeout and the IMCP echo reply will be dropped.

Determine Hops (number of routers in the path)
There is no 100% accurate way to get this information. SubnetPing uses an approximation technique to guess the hop count based on some assumptions. This is because the router has do decrease the TTL by at least one, and most of routers do exactly that. The reply packets might have another base TTL than your request packet had.
The base TTL has starts at 256,128,64 or 32. Therefore it should be correct if the packet has less than 32 hops in total and every router in the path decreased it by only one.

Measure Packetloss
Packetloss is calculated based on the attempts to ping an host with an IMCP echo request and the number of received echo reply responses within a given time-frame (timeout).

Resolve MAC-Addresses
Determine the MAC-Addresses by sending ARP requests to all available hosts.
This works only on the local subnet of the Computer your scanning from.
It is not possible to resolve the MAC-Address of any device behind a router using ARP requests.

Resolve Hostnames
Determine the Hostnames by using the operating system's default DNS server of the default network interface that is selected thru the routing table for accessing hosts in subnet be be scanned. This works only on the local subnet of the Computer your scanning from, due to the lack of revers lookup DNS entries in an public DNS Server.

Detect open Ports
Scan available Hosts for common open TCP ports.

*Early Access and BETA functionality.
This functionalities are classified as BETA status due to issues in certain network environments. Unfortunately, it can not be guaranteed that this functionality works as intended. It is possible that this functionality does not yield any results.

Detect SNMP devices (BETA)*
Determine the device description using SNMPv1 and SNMPv2 requests via UDP port 161.
There are still some problems detecting SNMP devices.
Some devices respond only to SNMPv1 community = “public“, OID = “1.3.6.1.2.1.1.1.0“
As others only respond to SNMPv2 community = “public“, OID = “1.3.6.1.2.1.1.1.0“
In some devices SNMP is just disabled by default and unfortunately there are still some devices that will not respond to SNMPv1 or SNMPv2 community = “public“ requests due to administration settings.
These devices will only respond to authenticated SNMPv3 requests.

Detect IPv6-Addresses (Ipv6) (Early Access)*
This is the same as Ipv4 detection but due to the gigantic address space of Ipv6 its not possible detect them using IMCP or to resolve the MAC address using ARP requests.
Fortunately it is possible to detect Ipv6 local link addresses and MAC-Addresses using the Neighbor Discovery Protocol (NDP).
This is an very early stage functionality and has some restrictions:
- Ping should work fine.
- Hops will always be “0” due to detection method restrictions.
- Packetloss should work fine.
- MAC-Addresses should work fine.
- Hostnames should work fine.
- Ports should work fine.

System Requirements

    Minimum:
    • OS: Windows 10
    • Processor: 2 GHz
    • Memory: 2 GB RAM
    • Storage: 50 MB available space
    Recommended:
    • OS: Windows 10
    • Processor: 2 GHz
    • Memory: 2 GB RAM
    • Storage: 50 MB available space

Customer reviews

Review Type


Purchase Type


Language


Date Range
To view reviews within a date range, please click and drag a selection on a graph above or click on a specific bar.

Show graph



Display As:
Review Beta NEW!
When enabled, will sort reviews by new Helpfulness score. Read more about it in the blog post.
Show graph
 
Hide graph
 
Filters
Review Helpfulness Beta Enabled
There are no more reviews that match the filters set above
Adjust the filters above to see other reviews
Loading reviews...