This RFE is submitted to track the requirement to test the reachability
of a host (or more likely an InetAddress). This RFE stems from the
feedback to 4093850 "ICMP protocol support a.k.a. PING applets" where
it clear that many developers have a basic requirement to test if a
host was reachable (something akin to the ping utility).
In its simplest form it we could test if a host is reachable
within a specified timeout. Another variant could be to test if
a host is reachable from a specified java.net.NetworkInterface.
Implementation-wise there needs to be flexibility to choose how
reachability is determined. If we can create an ICMP socket then
we can send/receive an echo request/reply ala classic ping.
Alternatively if we can't create an ICMP socket then a UDP or TCP
approach might be used (for example we could send a UDP packet to
the echo port and handle timeout/port unreachable).
Send UDP packet to echo port. Wait for reply with timeout. If a
reply is received or java.net.PortUnreachableException is thrown
then you know that the host is reachable.
Name: jc17350 Date: 02/19/2002
This feature has been added for Tiger release
A note to developers on the JDC :-
4093850 "ICMP protocol support a.k.a. PING applets" was a long
standing RFE seeking ICMP/raw sockets support. It attracted approximately
250 votes on the JDC. It became clear from the feedback to the RFE
that there were broadly two requirements :-
- Advanced & Raw Socket support - needed by those developing network
tools (such as ping & traceroute), and networking daemons (such as
- "ping" support where an application needs to determine if a
host is reachable or not.
Accordingly we have split 4093850 into 2 RFEs :-
4727550 is tracking the requirement for complete raw socket support
4639861 is tracking the requirement to test reachability of a host.
4093850 was closed as a duplicate of 4639861 and hence the JDC votes
& customer records were automatically transfered to 4639861.
BugTraq+ Release Management Values
COMMIT TO FIX: