ICMP Destination Unreachable identified as Timeout

[Petermarcu]

@gserfont commented on Fri Aug 10 2018

Issue Title

ICMP Destination Unreachable identified as Timeout

General

Using .Net Core 2.1.301 on OSX 10.13.6

SendPingAsync seems to incorrectly report the reason for Ping failure.

            var reply = await ping.SendPingAsync(Theip, timeout);
            if (reply.Status == System.Net.NetworkInformation.IPStatus.Success)
            {
                Console.WriteLine("Success:" + Theip);
            }
            if (reply.Status == System.Net.NetworkInformation.IPStatus.DestinationHostUnreachable)
            {
                Console.WriteLine("Destination host unreachable:" + Theip);
            }
            if (reply.Status == System.Net.NetworkInformation.IPStatus.DestinationUnreachable)
            {
                Console.WriteLine("Destination unreachable:" + Theip);
            }
            if (reply.Status == System.Net.NetworkInformation.IPStatus.TimedOut) //Everything hits here .. 
            {
                Console.WriteLine("Destination timedout:" + Theip);
            }

[wfurt]

I could not reproduce it @gserfont

I wraped your code to simple console app and it works as expected for me.
macik2:poll furt$ dotnet run 10.10.80.10
Destination timedout:10.10.80.10

I would recommend to do packet capture for ICMP traffic.

Also note, that on Unix (including OSX/MacOS) the implementation changes depending on user privilege. If possible .net uses RAW sockets and falls back to executing system 'ping' utility if needed.

Please provide more info.

[karelz]

Not actionable, closing. If you have more information available in future, we can reopen. Thanks!