All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Taylor, Grant" <gtaylor@riverviewtech.net>
To: netfilter@lists.netfilter.org
Subject: Re: Prevent traceroutes
Date: Fri, 20 May 2005 01:39:52 -0500	[thread overview]
Message-ID: <428D8638.4040301@riverviewtech.net> (raw)
In-Reply-To: <20050519233347.GA9462@bender.817west.com>

> looking at that response--there's a situation screaming for a custom
> chain:
> 
>   iptables -N DROP_TRACE
>   iptables -A DROP_TRACE -p udp --dport 33434:33523 -j DROP
>   iptables -A DROP_TRACE -p icmp --icmp-type 8 -m ttl --ttl-lt 5 -j DROP
> 
>   iptables -A INPUT -j DROP_TRACE
>   iptables -A FORWARD -j DROP_TRACE

I don't think that I could agree more about the need for a new chain.  I think I'd be tempted to do my match a bit differently though.

iptables -t filter -A DROP_TRACE -o eth0 -p udp -m recent --name Drop_Traceroute --update --seconds 200 --rdest -j DROP
iptables -t filter -A DROP_TRACE -o eth0 -p udp -m recent --name Drop_Traceroute --set --rdest -m ttl --ttl-eq 1 -j DROP
iptables -t filter -A DROP_TRACE -o eth0 -p icmp -m recent --name Drop_Traceroute --update --seconds 200 --rdest -j DROP
iptables -t filter -A DROP_TRACE -o eth0 -p icmp -m recent --name Drop_Traceroute --set --rdest -m ttl --ttl-eq 1 -j DROP

This should match any traffic (UDP or ICMP) that is leaving your network with a TTL of 1 which *should* be first packet in a traceroute that your firewall / router would see.  Seeing as how this should match any traceroute traffic you should be able to change the DROP target to be any thing else that you would want to redirect the traffic out some other interface be it via the ROUTE target or the MARK target in conjunction with ip routes.

The only thing that I have not figured out as of yet how to do is DROP the first packet that the firewall sees as every attempt that I made, even a DROP policy on the FORWARD and OUTPUT chain, did not block the first "TTL Time Exceeded" response.



Grant. . . .


  reply	other threads:[~2005-05-20  6:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19 22:07 Prevent traceroutes Kenneth Kalmer
2005-05-19 23:23 ` Jason Opperisano
2005-05-19 23:33   ` Jason Opperisano
2005-05-20  6:39     ` Taylor, Grant [this message]
2005-05-20  7:44       ` Taylor, Grant
2005-05-20 15:20         ` Jason Opperisano
2005-05-20 15:34           ` Taylor, Grant
2005-05-20 18:44           ` Charlie Brady
2005-05-20 19:03             ` Taylor, Grant
2005-05-20 19:37               ` Jason Opperisano
2005-05-23  7:01                 ` Jozsef Kadlecsik
2005-05-20  8:01       ` Kenneth Kalmer
2005-05-20  1:12 ` Sertys
2005-05-20 19:17 ` Sebastian Siewior

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=428D8638.4040301@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.