From: Olaf Kirch <okir@suse.de>
To: netdev@vger.kernel.org
Subject: Releasing new traceroute
Date: Mon, 1 Sep 2008 13:53:53 +0200 [thread overview]
Message-ID: <200809011353.53449.okir@suse.de> (raw)
Hi all,
a new version of my traceroute implementation is available from
ftp://ftp.lst.de/pub/people/okir/traceroute. I rewrote part
of the protocol handling to make it more flexible, and added
traceroute over TCP support. This uses the old-fashioned
listen-for-icmp-errors-on-raw-socket approach because we don't
have MSG_ERRQUEUE support in TCP, so it requires root privs.
Please give it a try and let me know whether you're seeing any
problems with it. One thing that's still missing is that over
IPv6, traceroute supports only UDP tracing, no ICMP or TCP.
That's mostly because I need to write the packet parsing code
that unwraps the IPv6 packet contained in the ICMP error
messages.
Cheers,
Olaf
--
And mention in the Fitz incident that DCOP is no ego shooter!
--micha istinie, 2001
reply other threads:[~2008-09-01 11:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200809011353.53449.okir@suse.de \
--to=okir@suse.de \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).