Welcome, Guest
Username: Password: Remember me

TOPIC: How to use traceroute properly in EE environment

How to use traceroute properly in EE environment 19 Mar 2022 09:03 #1

  • VK6NX
  • VK6NX's Avatar
  • OFFLINE
  • Posts: 296
  • Thank you received: 139
Rationale: use TCP and UDP traceroute instead of ICMP traceroute.
Reasons:
ICMP is
  • often blocked by transit providers
  • low priority protocol (from public network perspective) and very much differs from transport protocols (TCP and UDP) used by Expert Electronic

How to.

Linux users: use native traceroute
To TCP traceroute towards EE remote auth server :
traceroute -T -O info -p 5450 cloud.eesdr.com
trace-lin.png


To UDP traceroute towards transceiver:
traceroute -U -O info -p 50001 [IP addr of Transceiver]

Mac users:
To TCP traceroute towards EE remote auth server use tcptraceroute (install: brew install tcptraceroute)
sudo tcptraceroute cloud.eesdr.com 5450
trace-mac.png


To UDP traceroute towards transceiver use mac native traceroute command(note: mac native tracerouter uses UDP by default however you can reassure it)
traceroute -p 50001 -P 17 [IP addr of Transceiver]

Windows users.
Windows does not have native TCP traceroute tool within standard Windows distribution.

At current stage (with Win 10 and 11) it is recommended to use nmap tool with Zenmap frontend (Zenmap is included into nmap installer)

And example command for TCP traceroute towards EE remote auth server:
nmap -T4 -A -Pn cloud.eesdr.com
nmap.jpg


And example command for TCP traceroute towards transceiver:
nmap -T4 -A -Pn [IP addr of Transceiver]

Note: nmap can also be used under mac and linux via respective distribution.
Important: Do not abuse nmap towards EE auth server unless you wish to be banned.
The administrator has disabled public write access.
The following user(s) said Thank You: Rome
Time to create page: 0.076 seconds