Unsupported
Traces routes through raw sockets, which Android does not let apps open.
Network configuration and firewalls
| Platform | Standard | VM |
|---|---|---|
| Android, ARM64 | Unsupported | Untested |
| GooglebookOS, ARM64 | Unsupported | Untested |
| GooglebookOS, x86-64 | Unsupported | Untested |
| ChromeOS, ARM64 | Unsupported | Untested |
| ChromeOS, x86-64 | Unsupported | Untested |
Commands in the package
tcptraceroute.mt
About tcptraceroute
From Debian's package description
The more traditional traceroute(8) sends out either UDP or ICMP ECHO packets with a TTL of one, and increments the TTL until the destination has been reached. By printing the gateways that generate ICMP time exceeded messages along the way, it is able to determine the path packets are taking to reach the destination.
The problem is that with the widespread use of firewalls on the modern Internet, many of the packets that traceroute(8) sends out end up being filtered, making it impossible to completely trace the path to the destination. However, in many cases, these firewalls will permit inbound TCP packets to specific ports that hosts sitting behind the firewall are listening for connections on. By sending out TCP SYN packets instead of UDP or ICMP ECHO packets, tcptraceroute is able to bypass the most common firewall filters.
From Debian's description of the tcptraceroute package, under that package's license.
Dependencies
Depends on
libc6libnet1libpcap0.8t64
Sources and licenses
- Name: the Debian package name.
- Summary: Debian's short description of the tcptraceroute package, under that package's license.
- Description: Debian's description of the tcptraceroute package, under that package's license.
- Versions and sizes: Debian's archive for ARM64, as on packages.debian.org.
- Popularity: Debian Popularity Contest counts.
More in About the catalog.