From: Florian Boelstler <euphoria@web.de>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: traceroute
Date: Thu, 01 Jul 2004 01:06:29 +0200 [thread overview]
Message-ID: <40E34775.5010802@web.de> (raw)
In-Reply-To: <200406302339.02075.Antony@Soft-Solutions.co.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Antony Stone wrote:
>>By looking at other posts in this thread I've learned that traceroutes
>>are done with echo-requests. Is this true for Linux 2.6.6 ?
>
>
> No, that's true for Windows systems. Unix machines (Linux included)
uses
> high-port numbered UDP packets.
>
> Therefore you need to allow UDP packets to leave your machine for you
to be
> able to run traceroute from it.
Hmm, this could end up in an unfeasible task, when I do not allow
unrestricted output.
I just found out that traceroute offers a -I switch, that uses ICMP echo
requests instead.
On the other hand one could use -p for a specific base port to get a
certain determinism.
Florian
...............................
Someone on the net said:
I am Clinton of Borg. Prepare to see me make a fool of myself.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFA40d1wT2gPfZm6tURAn4AAJ9OfnD/kMw7Ua1ss/7lRfQzIbo5SgCfezgN
Ch0ifus6ReGzusVIarwR+z8=
=bIgk
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-06-30 23:06 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 13:05 traceroute Peter Marshall
2004-06-30 13:29 ` traceroute Antony Stone
2004-06-30 21:47 ` traceroute Florian Boelstler
2004-06-30 21:52 ` traceroute Antony Stone
2004-06-30 22:36 ` traceroute Florian Boelstler
2004-06-30 22:39 ` traceroute Antony Stone
2004-06-30 23:06 ` Florian Boelstler [this message]
2004-07-01 9:21 ` traceroute Jozsef Kadlecsik
2004-07-01 9:30 ` traceroute Antony Stone
2004-07-01 10:27 ` traceroute Jozsef Kadlecsik
2004-07-01 12:15 ` traceroute Cedric Blancher
2004-07-01 0:16 ` traceroute Cedric Blancher
2004-06-30 14:04 ` traceroute Ruprecht Helms
-- strict thread matches above, loose matches on Subject: below --
2004-07-01 9:52 traceroute Piszcz, Justin Michael
2004-07-01 12:25 ` traceroute Cedric Blancher
2004-06-30 18:20 traceroute Piszcz, Justin Michael
2004-06-30 20:55 ` traceroute Cedric Blancher
2004-07-01 8:19 ` traceroute Jozsef Kadlecsik
2004-06-30 16:28 traceroute Piszcz, Justin Michael
2004-06-30 16:47 ` traceroute Antony Stone
2004-06-30 16:10 traceroute Piszcz, Justin Michael
2004-06-30 16:21 ` traceroute Antony Stone
2004-06-30 16:25 ` traceroute Peter Marshall
2004-06-30 17:00 ` traceroute Antony Stone
2004-06-30 15:21 traceroute Piszcz, Justin Michael
2004-06-30 18:17 ` traceroute Jozsef Kadlecsik
2004-06-30 20:51 ` traceroute Cedric Blancher
2004-06-30 15:10 traceroute Piszcz, Justin Michael
2004-06-30 15:19 ` traceroute Jozsef Kadlecsik
2004-06-30 15:33 ` traceroute Antony Stone
2004-06-30 14:52 traceroute Piszcz, Justin Michael
2004-06-30 14:36 traceroute Piszcz, Justin Michael
2004-06-30 14:34 traceroute Piszcz, Justin Michael
2004-06-30 14:50 ` traceroute Peter Marshall
2004-06-30 14:57 ` traceroute Antony Stone
2004-06-30 13:47 traceroute Piszcz, Justin Michael
2004-06-30 14:25 ` traceroute Peter Marshall
2004-06-30 13:33 traceroute Piszcz, Justin Michael
2004-06-13 13:55 traceroute Prash
2004-06-13 14:53 ` traceroute Cedric Blancher
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=40E34775.5010802@web.de \
--to=euphoria@web.de \
--cc=netfilter@lists.netfilter.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