Linux workstation

Upstream software project

2ping

Bi-directional ping utility

Project identity

Project
2ping
Publisher
Not authoritatively mapped
Native package records
8
Operating systems
debian-12, debian-13, fedora-43, fedora-44, opensuse-leap-15-6, opensuse-leap-16-0, opensuse-tumbleweed
License expression
MPL-2.0
Quality score
100/100
Homepage
Visit upstream site
Source repository
Not reported

Upstream description

This description is kept separate from distribution package descriptions.

2ping is a bi-directional ping utility. It uses 3-way pings (akin to TCP SYN, SYN/ACK, ACK) and after-the-fact state comparison between a 2ping listener and a 2ping client to determine which direction packet loss occurs.

Packages by operating system

Every link opens the native package record, where versions, dependencies, files, checksums, repositories, and maintainers remain distribution-specific.

  1. 2ping

    Debian 12 (Bookworm) / net

    4.5-1.1

    Ping utility to determine directional packet loss

    allbookworm
  2. 2ping

    Debian 13 (Trixie) / net

    4.5-1.2

    Ping utility to determine directional packet loss

    alltrixie
  3. 2ping

    Fedora 43 / Unspecified / source 2ping

    4.5.1-22.fc43

    Bi-directional ping utility

    noarch43
  4. 2ping

    Fedora 44 / Unspecified / source 2ping

    4.5.1-24.fc44

    Bi-directional ping utility

    noarch44
  5. 2ping

    openSUSE Leap 15.6 / Unspecified / source 2ping

    4.5.1-bp156.4.3

    Bi-directional ping utility

    noarchleap-15.6
  6. 2ping

    openSUSE Leap 16.0 / Unspecified / source 2ping

    4.5.1-bp160.1.11

    Bi-directional ping utility

    noarchleap-16.0
  7. 2ping

    openSUSE Tumbleweed / Unspecified / source 2ping

    4.6.1-1.2

    Bi-directional ping utility

    noarchtumbleweed
  8. 2ping-bash-completion

    openSUSE Tumbleweed / System/Shells / source 2ping

    4.6.1-1.2

    Bash completion for 2ping

    noarchtumbleweed

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.