Ping class acts differently on Linux vs Windows

[rjrizzuto]

When I set a TTL of 1 (to implement traceroute functionality), I get TimedOut with an address of 0.0.0.0 on Linux. On Windows, I get the expected TtlExpired with the IP address of my router.

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[rjrizzuto]

Using Wireshark I can confirm that the ping request is properly formatted, and an immediate Time-to-live exceeded message is returned by my router. However, my application returned a timeout status 5 seconds after the initial request. It seems like the Ping class is not processing the message from the router.

[CarnaViire]

cc @dotnet/ncl

[wfurt]

looks like dup of #73232

[rjrizzuto]

I am not sure. That ticket is talking about containers. My issue is on Linux mint 21.3,. Net 8 with sudo for raw socket access.

[wfurt]

do you have any simple repro you can share @rjrizzuto? That would simplify the investigation.

[wfurt]

(and what .NET version do you use)

[rjrizzuto]

dotnet --version reports 8.0.103

This is the simple test code I wrote:

using System.Net.NetworkInformation;

var X = new Ping();
var options = new PingOptions(1, true);
byte[] buffer = new byte[0];
var reply = X.Send("8.8.8.8",5000,buffer,options);
Console.WriteLine(reply.Address.ToString());
Console.WriteLine(reply.Status.ToString());

Here's what I see on my Linux system:

ay@Green-lantern:~/Dotnet Projects/Test/Test/bin/Release/net8.0/linux-x64$ sudo ./Test
[sudo] password for ray:
0.0.0.0
TimedOut

[kasperk81]

copy paste error after "Here's what I see on my Linux system:"?

[rjrizzuto]

My bad. It's fixed now.

[rjrizzuto]

On Windows 11, the same code outputs this:

192.168.86.1
TtlExpired

That is the expected behavior.

[wfurt]

fixed by #99875