mtr.moe Open in urlscan Pro
2a03:90c0:e1:2801::254  Public Scan

Form analysis
0 forms found in the DOM

Text Content

Skip to the content.


NEXTTRACE


AN OPEN SOURCE VISUAL ROUTE TRACKING CLI TOOL

View on GitHub


NEXTTRACE

An open source visual routing tool that pursues light weight, developed using
Golang.


HOW TO USE

Document Language: English 简体中文


AUTOMATED INSTALLATION

# Linux one-click install script
bash <(curl -Ls https://raw.githubusercontent.com/sjlleo/nexttrace/main/nt_install.sh)

# macOS brew install command
brew tap xgadget-lab/nexttrace && brew install nexttrace

# GHProxy Mirror (For China Mainland User)
bash -c "$(curl -Ls https://ghproxy.com/https://raw.githubusercontent.com/sjlleo/nexttrace/main/nt_install.sh)"


Windows users please go to Release Page directly and download exe file.

 * Release provides compiled executables for many systems and architectures, if
   not, you can compile it yourself.
 * Some of the necessary dependencies of this project are not fully implemented
   in Golang on Windows, so currently NextTrace is experimental on Windows
   platform.


GET STARTED

NextTrace uses the ICMP protocol to perform TraceRoute requests by default,
which supports both IPv4 and IPv6

# IPv4 ICMP Trace
nexttrace 1.0.0.1
# URL
nexttrace http://example.com:8080/index.html?q=1

# Form printing (output all hops at one time, wait 20-40 seconds)
nexttrace --table 1.0.0.1

# IPv6 ICMP Trace
nexttrace 2606:4700:4700::1111

# Disable Path Visualization With the -M parameter
nexttrace koreacentral.blob.core.windows.net
# MapTrace URL: https://api.leo.moe/tracemap/html/c14e439e-3250-5310-8965-42a1e3545266.html


PS: The routing visualization drawing module was written by @tsosunchia, and the
specific code can be viewed at tsosunchia/traceMap.

Note that in LeoMoeAPI 2.0, due to the addition of geographical location data,
we have deprecated the online query part of the OpenStreetMap API in the
traceMap plugin and are using location information from our own database.

The routing visualization function requires the geographical coordinates of each
Hop, but third-party APIs generally do not provide this information, so this
function is currently only supported when used with LeoMoeAPI.

NextTrace now supports quick testing, and friends who have a one-time backhaul
routing test requirement can use it

# IPv4 ICMP Fast Test (Beijing + Shanghai + Guangzhou + Hangzhou) in China Telecom / Unicom / Mobile / Education Network
nexttrace --fast-trace

# You can also use TCP SYN for testing
nexttrace --fast-trace --tcp


NextTrace already supports route tracing for specified Network Devices

# Use eth0 network interface
nexttrace --dev eth0 2606:4700:4700::1111

# Use eth0 network interface's IP
# When using the network interface's IP for route tracing, note that the IP type to be traced should be the same as network interface's IP type (e.g. both IPv4)
nexttrace --source 204.98.134.56 9.9.9.9


NextTrace can also use TCP and UDP protocols to perform Traceroute requests, but
UDP protocols only supports IPv4 now

# TCP SYN Trace
nexttrace --tcp www.bing.com

# You can specify the port by yourself [here is 443], the default port is 80
nexttrace --tcp --port 443 2001:4860:4860::8888

# UDP Trace
nexttrace --udp 1.0.0.1

nexttrace --udp --port 53 1.0.0.1


NextTrace also supports some advanced functions, such as ttl control, concurrent
probe packet count control, mode switching, etc.

# Send 2 probe packets per hop
nexttrace --queries 2 www.hkix.net

# No concurrent probe packets, only one probe packet is sent at a time
nexttrace --parallel-requests 1 www.hkix.net

# Start Trace with TTL of 5, end at TTL of 10
nexttrace --first 5 --max-hops 10 www.decix.net

# Turn off the IP reverse parsing function
nexttrace --no-rdns www.bbix.net

# Feature: print Route-Path diagram
# Route-Path diagram example:
# AS6453 Tata Communication「Singapore『Singapore』」
#  ╭╯
#  ╰AS9299 Philippine Long Distance Telephone Co.「Philippines『Metro Manila』」
#  ╭╯
#  ╰AS36776 Five9 Inc.「Philippines『Metro Manila』」
#  ╭╯
#  ╰AS37963 Aliyun「ALIDNS.COM『ALIDNS.COM』」
nexttrace --route-path www.time.com.my


NextTrace supports users to select their own IP API (currently supports:
LeoMoeAPI, IP.SB, IPInfo, IPInsight, IPAPI.com)

# You can specify the IP database by yourself [IP.SB here], if not specified, LeoMoeAPI will be used
nexttrace --data-provider IP.SB
## Note that the ipinfo API needs users to purchase services from ipinfo. If necessary, you can clone this project, add the token provided by ipinfo and compile it yourself
## Fill the token to: ipgeo/tokens.go
## Please be aware: Due to the serious abuse of IP.SB, you will often be not able to query IP data from this source
## IPAPI.com has a stricter restiction on API calls, if you can't query IP data from this source, please try again in a few minutes.


NextTrace supports mixed parameters and shortened parameters

Example:
nexttrace --data-provider IPAPI.com --max-hops 20 --tcp --port 443 --queries 5 --no-rdns 1.1.1.1
nexttrace -tcp --queries 2 --parallel-requests 1 --table --route-path 2001:4860:4860::8888

Equivalent to:
nexttrace -d IPAPI.com -m 20 -T -p 443 -q 5 -n 1.1.1.1
nexttrace -T -q 2 --parallel-requests 1 -t -R 2001:4860:4860::8888



IP DATABASE

WE USE BGP.TOOLS AS A DATA PROVIDER FOR ROUTING TABLES.

NextTrace BackEnd is now open-source.

https://github.com/sjlleo/nexttrace-backend

All NextTrace IP geolocation API DEMO can refer to here


FOR FULL USAGE LIST, PLEASE REFER TO THE USAGE MENU

usage: nexttrace [-h|--help] [-T|--tcp] [-U|--udp] [-F|--fast-trace] [-p|--port
                 <integer>] [-q|--queries <integer>] [--parallel-requests
                 <integer>] [-m|--max-hops <integer>] [-d|--data-provider
                 (IP.SB|IPInfo|IPInsight|IPAPI.com)] [-n|--no-rdns]
                 [-a|--always-rdns] [-P|--route-path] [-r|--report]
                 [-o|--output] [-t|--table] [-c|--classic] [-f|--first
                 <integer>] [-M|--map] [-v|--version] [-s|--source "<value>"]
                 [-D|--dev "<value>"] [-R|--route] [-z|--send-time <integer>]
                 [-i|--ttl-time <integer>] [-g|--language (en|cn)] [IP Address
                 or Domain]

                 An open source visual route tracking CLI tool

Arguments:

  -h  --help                         Print help information
  -T  --tcp                          Use TCP SYN for tracerouting (default port
                                     is 80)
  -U  --udp                          Use UDP SYN for tracerouting (default port
                                     is 53)
  -F  --fast-trace                   One-Key Fast Trace to China ISPs
  -p  --port                         Set the destination port to use. It is
                                     either initial udp port value for
                                     "default"method (incremented by each
                                     probe, default is 33434), or initial seq
                                     for "icmp" (incremented as well, default
                                     from 1), or some constantdestination port
                                     for other methods (with default of 80 for
                                     "tcp", 53 for "udp", etc.)
  -q  --queries                      Set the number of probes per each hop.
                                     Default: 3
      --parallel-requests            Set ParallelRequests number. It should be
                                     1 when there is a multi-routing. Default:
                                     18
  -m  --max-hops                     Set the max number of hops (max TTL to be
                                     reached). Default: 30
  -d  --data-provider                Choose IP Geograph Data Provider
                                     [LeoMoeAPI,IP.SB, IPInfo, IPInsight,
                                     IPAPI.com]. Default: LeoMoeAPI
  -n  --no-rdns                      Do not resolve IP addresses to their
                                     domain names
  -a  --always-rdns                  Always resolve IP addresses to their
                                     domain names
  -P  --route-path                   Print traceroute hop path by ASN and
                                     location
  -r  --report                       output using report mode
  -o  --output                       Write trace result to file
                                     (RealTimePrinter ONLY)
  -t  --table                        Output trace results as table
  -c  --classic                      Classic Output trace results like
                                     BestTrace
  -f  --first                        Start from the first_ttl hop (instead from
                                     1). Default: 1
  -M  --map                          Disable Print Trace Map Function
  -v  --version                      Print version info and exit
  -s  --source                       Use source src_addr for outgoing packets
  -D  --dev                          Use the following Network Devices as the
                                     source address in outgoing packets
  -R  --route                        Show Routing Table [Provided By BGP.Tools]
  -z  --send-time                    Set the time interval for sending every
                                     packet. Useful when some routers use
                                     rate-limit for ICMP messages. Default: 100
  -i  --ttl-time                     Set the time interval for sending packets
                                     groups by TTL. Useful when some routers
                                     use rate-limit for ICMP messages. Default:
                                     500
  -g  --language                     Choose the language for displaying [en,
                                     cn]. Default: cn



PROJECT SCREENSHOT






NEXTTRACE ENHANCED

NextTrace Enhanced is an enhanced version for enthusiasts, Enhanced provides
trace route calls in the form of Web API and a simple Looking Glass webpage with
built-in visualization.

Please Notice that NextTrace Enhanced is currently not supported in English.

https://github.com/OwO-Network/nexttrace-enhanced


LEOMOEAPI CREDIT

NextTrace focuses on Golang Traceroute implementations, and its LeoMoeAPI
geolocation information is not supported by raw data, so a commercial version is
not possible.

The LeoMoeAPI data is subject to copyright restrictions from multiple data
sources, and is only used for the purpose of displaying the geolocation of route
tracing.

 1. We would like to credit samleong123 for providing nodes in Malaysia, TOHUNET
    Looking Glass for global nodes, and Ping.sx from Misaka, where more than 80%
    of reliable calibration data comes from ping/mtr reports.

 2. At the same time, we would like to credit isyekong for their contribution on
    rDNS-based calibration ideas and data. LeoMoeAPI is accelerating the
    development of rDNS resolution function, and has already achieved automated
    geolocation resolution for some backbone networks, but there are some
    misjudgments. We hope that NextTrace will become a One-Man ISP-friendly
    traceroute tool in the future, and we are working on improving the
    calibration of these ASN micro-backbones as much as possible.

 3. In terms of development, I would like to credit missuo and zhshch for their
    help with Go cross-compilation, design concepts and TCP/UDP Traceroute
    refactoring, and tsosunchia for their support on TraceMap.

 4. I would also like to credit FFEE_CO, TheresaQWQ, stydxm and others for their
    help. leoMoeAPI has received a lot of support since its first release, so I
    would like to credit them all!

We hope you can give us as much feedback as possible on IP geolocation errors
(see issue) so that it can be calibrated in the first place and others can
benefit from it.


JETBRAIN SUPPORT

THIS PROJECT USES JETBRAIN OPEN-SOURCE PROJECT LICENSE. WE PROUDLY DEVELOP BY
GOLAND.




CREDITS

BGP.TOOLS provided some data support for this project and we would like to
express our sincere gratitude.

Vincent Young (i@yyt.moe)

Sam Sam (samsam123@samsam123.name.my)

tsosunchia

waiting4new

FFEE_CO


OTHERS

Although other third-party APIs are integrated in this project, please refer to
the official website of the third-party APIs for specific TOS and AUP. If you
encounter IP data errors, please contact them directly to correct them.


STAR HISTORY



nexttrace is maintained by sjlleo. This page was generated by GitHub Pages.