From: Florian Boelstler <euphoria@web.de>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: traceroute
Date: Wed, 30 Jun 2004 23:47:24 +0200 [thread overview]
Message-ID: <40E334EC.1080606@web.de> (raw)
In-Reply-To: <200406301429.14248.Antony@Soft-Solutions.co.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I have a similar problem.
My traceroute says:
traceroute to www.google.akadns.net (66.102.11.99), 30 hops max, 38 byte
packets
traceroute: sendto: Operation not permitted
1 traceroute: wrote www.google.akadns.net 38 chars, ret=-1
[ ... ]
My setup is rather simple. I have "black-boxed" router connected to the
internet, that is able to forward traceroutes. My client is equipped
with netfilter.
When I disable my local netfilter on the client, traceroute works fine.
I use
$IPTABLES -A OUTPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
$IPTABLES -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
at the beginning of my firewall script.
Nevertheless traceroute does not work.
Do I miss something?
Thanks.
Cheers,
Florian
Antony Stone wrote:
> On Wednesday 30 June 2004 2:05 pm, Peter Marshall wrote:
>
>
>>Hi. I was wondering what I would need for rules to have traceroute work
>>through my firewall. (I have a box behind the firewall trying to get out
>>using traceroute).
>>
>>I have an allow established connections on my forwared chain, and I am
>>allowing anything from the source IP of the box in question to leave
... It
>>appears that the problem is on the packets comming back in .. but I am not
>>sure what I have to do to fix it ....
>
>
> Allow RELATED packets as well as ESTABLISHED.
>
> Regards,
>
> Antony.
>
...............................
Someone on the net said:
Frank, have you been sniffing medical samples again? - Hawkeye
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFA4zTswT2gPfZm6tURAoOnAKCtHbVHsvg7nrTBCviE4DVydenpQgCfeVuS
jdBS08sKpALhTTMJ+gGYcsc=
=g53n
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-06-30 21:47 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 ` Florian Boelstler [this message]
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 ` traceroute Florian Boelstler
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=40E334EC.1080606@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 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.