Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Athan <netfilter@miggy.org>
To: Sapient2003 <sapient@qwest.net>
Cc: netfilter@lists.netfilter.org
Subject: Re: UDP and ICMP traceroute
Date: Thu, 13 Mar 2003 00:16:36 +0000	[thread overview]
Message-ID: <20030313001636.GN1025@miggy.org> (raw)
In-Reply-To: <3E6FB954.8080708@qwest.net>

[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]

On Wed, Mar 12, 2003 at 05:48:52PM -0500, Sapient2003 wrote:
> I am trying to have iptables pick out traceroute packets. Windows uses 
> ICMP for it's traceroute, so I use this:
> 
> iptables -t filter -A INPUT -p icmp -s 0/0 -d 10.0.0.1 --icmp-type 
> time-exceeded -j QUEUE
> 
> Linux, however, uses both ICMP and UDP... How can I tell iptables to 
> look for UDP traceroute packets?

  You can't, without hacking the traceroute client to only use a very
specific range of ports.  We did this at one place I used to work when
we had a non-stateful firewall.

  I guess the other possibility is to hack the traceroute client to put
an actual, unique (enough), payload in the outgoing UDP packet, and then
have an ipt kernel module looking for that.

  If you must tie down outgoing UDP such that you can't just use the
statefulness of iptables/netfilter then I'd suggest trying to find a
linux traceroute that does things the same way as the Windows one.

-Ath
-- 
- Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/
                  Finger athan(at)fysh.org for PGP key
	   "And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence." Paula Cole - ME

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]

      reply	other threads:[~2003-03-13  0:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12 22:48 UDP and ICMP traceroute Sapient2003
2003-03-13  0:16 ` Athan [this message]

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=20030313001636.GN1025@miggy.org \
    --to=netfilter@miggy.org \
    --cc=netfilter@lists.netfilter.org \
    --cc=sapient@qwest.net \
    /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