Regards and thanks for usage.
If you only know about how you can build ping or traceroute things, please visit the samples file, where you can find examples for those routines.
The following list shows some configurations with which the library was tested.
| System | Current state | Description | Tested with version | Comment |
|---|---|---|---|---|
| Microsoft Windows (x64) | working | 0.1.18 | Windows 10 / 11 | |
| Microsoft Windows (arm64) | working *1) | 0.1.19 | VM under MacOS / Traceroute doesn't work as expected; Ping works fine. Seems to be a problem with the Virtualization Engine? | |
| Microsoft Windows (x64) WSL | working | 0.1.19 | WSL 2 | |
| Microsoft Windows (arm64) WSL | not tested | |||
| Linux (x64) | working | ubuntu | 0.1.18 | |
| Linux (arm64) | working *1) | ubuntu | 0.1.19 | VM under MacOS / Traceroute doesn't work as expected Ping works fine. Seems to be a problem with the Virtualization Engine? |
| Linux (arm64) | working | ubuntu server | 0.1.19 | native on a raspberry pi |
| MacOSx (x64) | not tested | 0.1.18 | ||
| MacOSx (arm64) | working | 0.1.18 | fixed with 0.1.18 | |
| Docker (x64) | working | ubuntu image | 0.1.18 | |
| Docker (arm64) | not tested |
For testing purposes on arm64, i setup the following configuration:
- Host MacBook Pro 2021 on Arm Chip
- VM-Virtualisation Parallels Desktop 17
- Guest 1: Windows 11 Home for Arm64
- Newest Dontnet Core for Arm64
Running the app with traceroute, i get the following result:
Do a Traceroute to 1.1.1.1
------------------------------
hop: 1 :: MaxHops: 30 :: Tp: 3
TP: 0
1 : 1.1.1.1 : 8 ms : EchoReply
------------------------------The result is in any case the endpoint, not the intermediate "TimeExceeded" steps.
- Guest 2: Debian Linux 11 (Bullseye) for Arm64
- Newest Dontnet Core for Arm64
Running the app with traceroute, i get the following result:
Do a Traceroute to 1.1.1.1
------------------------------
hop: 1 :: MaxHops: 30 :: Tp: 3
TP: 0
1 : 1.1.1.1 : 7 ms : EchoReply
------------------------------The result is in any case the endpoint, not the intermediate "TimeExceeded" steps.
After i searching some things around, i did the following tests. I do a built in traceroute from the os.
Windows 11 on Arm64:
tracert 1.1.1.1
Routenverfolgung zu one.one.one.one [1.1.1.1]
über maximal 30 Hops:
1 8 ms 7 ms 6 ms one.one.one.one [1.1.1.1]
Ablaufverfolgung beendet.Debian 11 Bullseye on Arm64:
traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 bytes packets
1 * one.one.one.one (1.1.1.1) 8.753 ms *Same behavior with the os built in traceroute commands.
I will extend the traceroute on arm64 native on a raspberry pi soon to check it out under real circumstances.
I believe it is no a behavior with the OS (it would be very strange if windows and linux struggle with the same prob at the same time), i think it is a prob with the virtualization engine or the virtual network or what ever.
As expected, with an Raspberry Pi 4 / 4 GB RAM and the following configuration:
/home/ubuntu/dotnet/dotnet --info
.NET SDK (reflecting any global.json):
Version: 6.0.300
Commit: 8473146e7d
Runtime Environment:
OS Name: ubuntu
OS Version: 20.04
OS Platform: Linux
RID: ubuntu.20.04-arm64
Base Path: /home/ubuntu/dotnet/sdk/6.0.300/
Host (useful for support):
Version: 6.0.5
Commit: 70ae3df4a6
.NET SDKs installed:
6.0.300 [/home/ubuntu/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.5 [/home/ubuntu/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.5 [/home/ubuntu/dotnet/shared/Microsoft.NETCore.App]the Traceroute works like a charme as expected.
Do a Traceroute to 1.1.1.1
------------------------------
1 : 192.168.0.1 : 0 ms : TimeExceeded
2 : 195.14.226.125 : 5 ms : TimeExceeded
3 : 89.1.16.161 : 5 ms : TimeExceeded
4 : 89.1.86.45 : 5 ms : TimeExceeded
5 : 81.173.192.6 : 5 ms : TimeExceeded
6 : 194.146.118.139 : 6 ms : TimeExceeded
7 : 1.1.1.1 : 6 ms : EchoReply
------------------------------
Finished TracerouteThe behavior is like on virtual machines (especially Parallels Desktop 17?).
As native running app on Arm64 machines it works.
As easy as is, use nuget to include the lib (dll) to your project and use it.
Or you download the sources (clone the repo) and compile it for yourself.
I found, that the current implementation of ping (https://docs.microsoft.com/de-de/dotnet/api/system.net.networkinformation.ping?view=net-6.0) in dotnet core (current 6.0.1)
- is very buggy if you don´t use windows
- use the ping command from operating system
The buggy implementation prevent me to use this functionality inside a linux docker container.
A ping from macos or linux returned in every case a timeout, if the ttl is set to lower than the pinged host is away.
And for the other point, it feels for me very clumsy, when i know, that there is not a native implementation of things although there are all the stuff here to implement it correctly.
And it is a lot of fun to code with low level network sockets, i've learned al lot of things.
Some tips and tricks and how the things could work, i learned from here
http://www.java2s.com/Code/CSharp/Network/SimplePing.htm
Very usefull code example
I take the newest (from 1981) documentation from here about icmp
https://datatracker.ietf.org/doc/html/rfc792
and read / try to understand how it works.
For debugging purposes, i use wireshark, to see directly what goes to the network and what comes back.
As i say, very forensic and funny.
Beware!
As of operating systems restrictions (windows, linux and mac) you should run the app included this library with administrator privileges.
E.g. https://docs.microsoft.com/de-de/windows/win32/winsock/tcp-ip-raw-sockets-2?redirectedfrom=MSDN
Thats sad, but not my fault.
Anyway.
If you use the lib in your project, simply do things as this (c# syntax):
var response = await Icmp.Ping("1.1.1.1", 64, 3000, true, cts.Token);
OR
var response = await Icmp.Ping("one.one.one.one", 64, 3000, true, cts.Token);
OR
var response = await Icmp.Ping("2606:4700:4700::1111", 64, 3000, true, cts.Token);
OR (in case that you need it in synchronous manner)
var respnse = Icmp.PingSync("hostNameOrIp", ttl, timeout, dontFragment)
The method Ping(...) runs asynchron, so it´s in your app-code to await the things. Later i will implement a synchronous variant (internal async)
The method parameters are:
- ipOrHostName - string - as described, the ip or hostname of the host to ping
- ttl - int - it´s not a time but more a number of max hops to the host to ping. Its very usefull for traceroutes.
- receiveTimeout - int - timespan in ms when the packet is send and no pong returned back
- dontFragment (optional) - bool - if the frame too big, split it in multiple packets. Attention! This thing does not run with MacOS
- token - CancellationToken - The token, when the async process is cancelled (async can theoretically runs for ever and that ist not the goal). Attention! The token value should be higher than the receiveTimeout value because it cancel the async process before the receiveTimeout is reached!
The result is much more comprehensive than the std OS-Ping or the dotnet core ping, which use the std-OS-Ping. If you don´t believe this, rename your ping command and try to run the dotnet core ping. It says: No ping command found.
Please look at the SAMPLES.md document to checkout how the things work and how you could use the lib to build ping and traceroute methods.
As a result of a request, i implement a traceroute function in this library. See the samples.md for an example of usage.
Have a great day!