fujiapple852 / trippy Goto Github PK

When a hop has multiple associated ip address, show only the top N most frequent.

A caching DNS & reverse-DNS resolver which does not block the application during lookup.

Assumption is that the Tui is registering and handling SIGINT

Use https://docs.rs/nix/latest/nix/ifaddrs/fn.getifaddrs.html

See net_find_interface_address_from_name in net.c

Support tracing to multiple targets in a single Trippy instance (ICMP only, Tui only).

Status

• Add tabs to the Tui
• Run multiple backends (one per thread, each with own sockets)
• Enforce only a single target for non-tui modes
• Enforce ICMP protocol only
• Support for ICMP

Follow up

system-wise unique identifier for each trace (see #123)
Multi-trace for UDP (see #121)
Multi-trace for TCP (see #122)

When a round is complete and published it should include an indicator of why the round is complete (i.e. we found the target or we timed out)

Enable support for Trippy on Windows.

See for background.

The full set of ICMP sockets to support:

The non-system DNS resolver includes a period (.) suffix on resolved hostnames whereas the system DNS resolver does not.

Which shells? Can be automated with clap.

Add a raw streaming mode, similar to the existing stream mode but showing the raw output of each Probe, not waiting until a round is complete to publish. Unclear why this is useful however.

Trippy needs a logo, help needed!

A regression from #104

For UDP tracing there is not trace_identifier and so we need a way to distinguish between separate traces.

Currently, the frequency% barchart shows the first N round-trip-time (depending on screen width) and so can exclude the largest frequencies if they happen to be higher than can be displayed. It would be better to centre around the highest frequency

Currently the sample count, which is used to display the sample history and frequency histogram, is hardcoded. This chane is to expose the max sample count as a configuration option.

See discussion in crossterm-rs/crossterm#660

Support for tracing with the IPv6 protocol.

Tracking issue for ICMP Extensions.

Add support for generic Ipv4 & Ipv6 ICMP extensions, with specific parsing for:

• #751
• #753
• Add support for Interface Information ICMP Extension Object
• Add support for Interface Identification ICMP Extension Object
• Add support for Extended Information ICMP Extension Object
• Add additional tests for non-compliant ICMP Extension Object cases
• #752
• #807
• #806
• #804
• Add support for IPv6 Extensions in splitter

The Tracer uses a circular buffer to track the state of all Probe in-flight. To access a Probe in this buffer, the index is calculated as sequence number of the probe modulo the buffer size.

Whilst this works, it has the draw back that the probes for a given round may wrap around the buffer and therefore must be processed with an Iterator rather than a slice.

This changes the logic to index into the buffer using sequence - round_sequence (i.e. the sequence number - the initial sequence number of the round).

Therefore the buffer access will always start from 0 in every round and will never wrap around as the buffer size is the same as the maximum ttl allowed.

Trippy current calculates the StDev column as:

pub fn stddev_ms(&self) -> f64 {
    if self.total_recv > 1 {
        (self.m2 / (self.total_recv - 1) as f64).sqrt()
    } else {
        0_f64
    }
}

Where, for each successful Probe (for a given hop ttl), the total_recv, mean and m2 values are updated as follows:

let dur = probe.duration();
let dur_ms = dur.as_secs_f64() * 1000_f64;
hop.total_recv += 1;
hop.mean += (dur_ms - hop.mean) / hop.total_recv as f64;
hop.m2 += (dur_ms - hop.mean) * (dur_ms - hop.mean);

We would like to add support for a Jitter columns similar to those provided by mtr (see https://networkengineering.stackexchange.com/questions/5288/what-is-interarrival-jitter-in-mtr)

Support tracing by sending UDP packets instead of ICMP EchoRequest packets.

When sending TCP packets the checksum is not being set which results in the packets being dropped by routers.

Trippy currently uses pnet layer4 and to set the checksum we need to know both the destination and source IP address. We need to obtain the source IP address using the technique described in datalink::interfaces, but as the documentation notes:

is not guaranteed to work on each system

Later, Trippy will move to use layer3 or layer2 channels (#46) and the source interface can be chosen explicitly (#42).

Note that for UDP we deliberately do not set the checksum as, in some configurations, the checksum is used as to track the sequence number (MTR behaviour).

When the round ends due to timeout on max_round_duration without finding the target, only the Probe which responded are published and so the statistics for all other Probe in the round are not updated. Notably, this includes the sent count and so this leads to a "tearing" effect whereby the sent count is not consistent for all hops in the trace.

Currently, AS lookup is only supported when using the trust_dns_resolver.

See #34 for the current implementation.

The Tracer is generic over the Network trait to abstract it from the underlying pnet implementation. We can use mockall to test the Tracer with a dummy Network implementation.

Support the ability to lookup AS information.

dig 1.2.3.4.origin.asn.cymru.com TXT +short

Currently, when asked to trace to an unknown host, trippy produces an unhelpful error on startup.

System DNS resolver:

Error: failed to lookup address information: nodename nor servname provided, or not known

Other DNS resolvers:

Error: no record found for name: dffghfghf. type: AAAA class: IN

Currently Trippy can retrieve more information about the AS than it displays. In particular, the AS name is not shown.

Add a new Tui feature where we show a multiline display per hop showing the various data about the hop (ip, hostname, ASN, AS Name and other associated fields) for the currently selected hop.

Moreover, Trippy can limit the number of hosts shown per hop, as the display can become unwieldily when there are many hosts to display per hop. This provide an alternative display mode where only one host is shown per hop, but users can navigate between hosts for a hop using new key bindings.

Switch to use socket2 for TCP and UDP:

• For TCP (see #134)
• For UDP (see #155)

Then allow for fixing either the source OR the destination port for both TCP and UDP tracing,

We do not currently allow fixing both source and destination ports, which is possible if we use use IP header checksum to hold the sequence.

aka ToS

Currently, for TCP probing, the source port is fixed and the target ports rotations (to track the sequence). The default for TCP should be the reverse.

Depends on #43

Switch to use TransportChannelType::Layer3 to allow adjusting various IPv4 header parameters.

Support tracing by sending TCP packets instead of ICMP EchoRequest packets.

Generate deb packages on release using cargo-deb or similar

Support for POSIX & Linux capacities to allow running without super-user privileges

TCP options being set by mtr, as sen by Wireshark:

    Options: (24 bytes), Maximum segment size, No-Operation (NOP), Window scale, No-Operation (NOP), No-Operation (NOP), Timestamps, SACK permitted, End of Option List (EOL)
        TCP Option - Maximum segment size: 1460 bytes
        TCP Option - No-Operation (NOP)
        TCP Option - Window scale: 6 (multiply by 64)
        TCP Option - No-Operation (NOP)
        TCP Option - No-Operation (NOP)
        TCP Option - Timestamps: TSval 2619510293, TSecr 0
        TCP Option - SACK permitted
        TCP Option - End of Option List (EOL)