Michael C. Toren on Wed, 21 Nov 2001 23:44:58 -0500

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

[tcptra-dev] tcptraceroute-1.3beta2

tcptraceroute-1.3beta2 is now available on the beta website,
<http://michael.toren.net/code/tcptraceroute/beta.html>.  1.3beta2
includes some major internal structural changes.  From the changelog:

 *      probe() and capture() now use a new proberecord structure which
 *      contains information about each probe in a modularized way.
 *      Added a new command line argument, --track-port, which causes
 *      each probe to have a unique source port so that something other
 *      than the IP ID can be used to track it.  Hopefully this will
 *      make things work on Solaris, which modifies the IP ID of packets
 *      written to a raw socket.  Also added a corresponding --track-id
 *      argument to specify the old behavior of tracking IP ID's, which
 *      is still the default.  If a source port is specified with -p,
 *      --track-id is implied.
 *      probe() now calls allocateid() to generate an IP ID, which
 *      caches the last ALLOCATEID_CACHE_SIZE allocations to prevent
 *      against duplicates.

I'm hoping to release beta2 as version 1.3 in near future, perhaps in
a week or two if no one finds any bugs, and then begin work on 1.4.

For 1.4, there are a few features I'm looking forward to implementing
using the proberecord framework setup in 1.3.  One idea, suggested by
Darxus <darxus@chaosreigns.com>, is to allow a comma separated list of
destination ports on the command line, send a probe to each to see which
responds, and then trace using that port.  Another idea along the same
lines is a shotgun traceroute, where probes for each hop are sent out
in a single burst, and replies are then displayed as they come in.

As always, your feedback is very much appreciated.



tcptraceroute-dev mailing list