status: failed for IPv6 ping

[jason5ng32]

I tried to ping a v6 IP address on globalping, datas were returned correctly, but the status returned failed. Would you consider supporting Ping6 command or make Ping command work correctly for v6 address? Thanks.

[MartinKolarik]

It should already work correctly. If you see something that looks wrong, please provide more details.

[jason5ng32]

When I try to ping6 2606:4700:4700::1111, the responds are:

{
  "id": "lsT7xusW30mVrP5e",
  "type": "ping",
  "status": "finished",
  "createdAt": "2024-07-16T12:40:08.569Z",
  "updatedAt": "2024-07-16T12:40:12.004Z",
  "target": "2606:4700:4700::1111",
  "probesCount": 2,
  "locations": [
    {
      "country": "TW"
    },
    {
      "country": "US"
    }
  ],
  "measurementOptions": {
    "packets": 5,
    "ipVersion": 6
  },
  "results": [
    {
      "probe": {
        "continent": "AS",
        "region": "Eastern Asia",
        "country": "TW",
        "state": null,
        "city": "Taichung",
        "asn": 9678,
        "longitude": 120.68401,
        "latitude": 24.14687,
        "network": "Hosting Inside Ltd.",
        "tags": [
          "datacenter-network"
        ],
        "resolvers": [
          "103.98.74.88",
          "103.98.73.88"
        ]
      },
      "result": {
        "status": "failed",
        "rawOutput": "PING 2606:4700:4700::1111(2606:4700:4700::1111) 56 data bytes\n64 bytes from 2606:4700:4700::1111: icmp_seq=1 ttl=61 time=0.662 ms\n64 bytes from 2606:4700:4700::1111: icmp_seq=2 ttl=61 time=0.893 ms\n64 bytes from 2606:4700:4700::1111: icmp_seq=3 ttl=61 time=0.970 ms\n64 bytes from 2606:4700:4700::1111: icmp_seq=4 ttl=61 time=1.11 ms\n64 bytes from 2606:4700:4700::1111: icmp_seq=5 ttl=61 time=0.853 ms\n\n--- 2606:4700:4700::1111 ping statistics ---\n5 packets transmitted, 5 received, 0% packet loss, time 2025ms\nrtt min/avg/max/mdev = 0.662/0.897/1.110/0.146 ms",
        "resolvedAddress": null,
        "resolvedHostname": null,
        "timings": [],
        "stats": {
          "min": null,
          "max": null,
          "avg": null,
          "total": null,
          "loss": null,
          "rcv": null,
          "drop": null
        }
      }
    },
    {
      "probe": {
        "continent": "NA",
        "region": "Northern America",
        "country": "US",
        "state": "NJ",
        "city": "New York",
        "asn": 14061,
        "longitude": -74.1377,
        "latitude": 40.8344,
        "network": "DigitalOcean, LLC",
        "tags": [
          "datacenter-network"
        ],
        "resolvers": [
          "67.207.67.2",
          "67.207.67.3"
        ]
      },
      "result": {
        "status": "failed",
        "rawOutput": "PING 2606:4700:4700::1111(2606:4700:4700::1111) 56 data bytes\n64 bytes from 2606:4700:4700::1111: icmp_seq=1 ttl=57 time=2.05 ms\n64 bytes from 2606:4700:4700::1111: icmp_seq=2 ttl=57 time=1.67 ms\n64 bytes from 2606:4700:4700::1111: icmp_seq=3 ttl=57 time=2.15 ms\n64 bytes from 2606:4700:4700::1111: icmp_seq=4 ttl=57 time=1.86 ms\n64 bytes from 2606:4700:4700::1111: icmp_seq=5 ttl=57 time=1.51 ms\n\n--- 2606:4700:4700::1111 ping statistics ---\n5 packets transmitted, 5 received, 0% packet loss, time 2004ms\nrtt min/avg/max/mdev = 1.513/1.848/2.147/0.234 ms",
        "resolvedAddress": null,
        "resolvedHostname": null,
        "timings": [],
        "stats": {
          "min": null,
          "max": null,
          "avg": null,
          "total": null,
          "loss": null,
          "rcv": null,
          "drop": null
        }
      }
    }
  ]
}

The rawOutput are correctly returned, but the status, timing, and stats values in probes are not right or empty. For example, status should be finished rather than failed.

[MartinKolarik]

Thanks, it looks like a bug indeed; we'll check it.

[jason5ng32]

Great to know this issue has been fixed, is it possible to test on globalping website lately?

[MartinKolarik]

Not yet, we'll comment here when we make a release that includes the fix (should be this week). After that, the change will be live in 30 minutes.

[github-actions[bot]]

:tada: This issue has been resolved in version 0.32.3 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: