This is the mail archive of the
mailing list for the Cygwin project.
- From: Nicholas Wourms <nwourms at yahoo dot com>
- To: Randall R Schulz <rrschulz at cris dot com>, cygwin at cygwin dot com
- Date: Mon, 9 Sep 2002 15:52:35 -0700 (PDT)
- Subject: RE: Traceroute?
--- Randall R Schulz <email@example.com> wrote:
> Cygwin is not a world apart. You can invoke Windows tracert (and
> all other
> Windows executables) directly from Cygwin.
> For commonly used commands that reside in a directory I don't
> want in my PATH, I just define aliases or shell functions in my
Well I think the real issue is some missing functionality in the
tcp/ip interface within Cygwin. Alas, the icmp headers seem to be
missing as well as ip_var.h/tcp_var.h/udp_var.h. Too bad I don't
know enough about lowlevel windows tcp/ip, otherwise I'd jump on
trying to fix the holes in the current tcp/ip stack.
I think, many times, people get caught up in the argument that well
windows already has so-and-so tool. Well that's nice, but sometimes
the windows version of the tool sucks. In this case I'm inclined to
say windows traceroute is barely acceptable. I much prefer the
version that comes with bsd/*nix (ee.lbl.gov). Here's how they
Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout]
-d Do not resolve addresses to hostnames.
-h maximum_hops Maximum number of hops to search for target.
-j host-list Loose source route along host-list.
-w timeout Wait timeout milliseconds for each reply.
traceroute [ -dFInrvx ] [ -f first_ttl ] [ -g gateway ]
[ -i iface ] [ -m max_ttl ] [ -p port ]
[ -q nqueries ] [ -s src_addr ] [ -t tos ]
[ -w waittime ] [ -z pausemsecs ]
host [ packetlen ]
Obviously the *nix version provides for a finer granularity of
control whereas the windows version is rather spartan.
Oh well, since I can't submit a patch I guess I should shutup now...
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html