surge-ping

A Ping (ICMP) detection tool, you can personalize the Ping parameters. Since version 0.4.0, a new Client data structure has been added. This structure wraps the socket implementation and can be passed between any task cheaply. If you have multiple addresses to detect, you can easily complete it by creating only one system socket(Thanks @wladwm).

Crates.io MIT licensed API docs

rust ping libray based on tokio + socket2 + pnet_packet.

Example

simple usage:

```rust use surge_ping::IcmpPacket;

[tokio::main]

async fn main() { match surgeping::ping("127.0.0.1".parse().unwrap()).await { Ok((IcmpPacket::V4(packet), duration)) => { println!( "{} bytes from {}: icmpseq={} ttl={:?} time={:.2?}", packet.getsize(), packet.getsource(), packet.getsequence(), packet.getttl(), duration ); } Ok(_) => unreachable!(), Err(e) => println!("{:?}", e), }; } ```

multi address usage: multi_ping.rs

Ping(ICMP)

There are three example programs that you can run on your own.

```shell $ git clone https://github.com/kolapapa/surge-ping.git $ cd surge-ping

$ cargo build --example simple sudo ./target/debug/examples/simple -h 8.8.8.8 -s 56 V4(Icmpv4Packet { source: 8.8.8.8, destination: 10.1.40.79, ttl: 53, icmptype: IcmpType(0), icmpcode: IcmpCode(0), size: 64, real_dest: 8.8.8.8, identifier: 111, sequence: 0 }) 112.36ms

$ cargo build --example cmd sudo ./target/debug/examples/cmd -h google.com -c 5
PING google.com (172.217.24.238): 56 data bytes 64 bytes from 172.217.24.238: icmpseq=0 ttl=115 time=109.902 ms 64 bytes from 172.217.24.238: icmpseq=1 ttl=115 time=73.684 ms 64 bytes from 172.217.24.238: icmpseq=2 ttl=115 time=65.865 ms 64 bytes from 172.217.24.238: icmpseq=3 ttl=115 time=66.328 ms 64 bytes from 172.217.24.238: icmp_seq=4 ttl=115 time=68.707 ms

--- google.com ping statistics --- 5 packets transmitted, 5 packets received, 0.00% packet loss round-trip min/avg/max/stddev = 65.865/76.897/109.902/16.734 ms ```

Notice

If you are time sensitive, please do not use asynchronous ping program, because if there are a large number of asynchronous events waiting to wake up, it will cause inaccurate calculation time. You can directly use the ping command of the operating system.

License

This project is licensed under the [MIT license].