From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] traceroute not working
Date: Fri, 22 Feb 2013 11:40:55 -0500 [thread overview]
Message-ID: <51279F97.5050002@gmail.com> (raw)
In-Reply-To: <5127941A.1070903@libertytrek.org>
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
On 02/22/2013 10:51 AM, Tanstaafl wrote:
> Hi all,
>
> Weird, I don't use it much, but needed to run a traceroute today, and it
> is failing with:
>
> # traceroute 192.168.1.4
> traceroute to 192.168.1.4 (192.168.1.4), 30 hops max, 60 byte packets
> send: Operation not permitted
>
> I know the problem is in my firewall, because when I stop it,
> traceroutes work as expected.
>
> I have allowed all ICMP in my firewall:
>
> Chain INPUT (policy DROP)
> target prot opt source destination
> <snip>
> ACCEPT icmp -- anywhere anywhere icmp any
> <snip>
>
> Chain FORWARD (policy DROP)
> target prot opt source destination
> ACCEPT icmp -- anywhere anywhere icmp any
>
> Chain OUTPUT (policy DROP)
> target prot opt source destination
> <snip>
> ACCEPT icmp -- anywhere anywhere icmp any
>
> Any ideas what I'm missing?
>
> I can send all of my firewall rules privately if someone thinks I may
> have something that is dropping these packets before my ALLOW rule kicks
> in, but I'm fairly sure I have them right...
>
> Thanks
>
Try moving your ACCEPT rules for icmp closer to (or all the way to) the top.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]
next prev parent reply other threads:[~2013-02-22 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 15:51 [gentoo-user] traceroute not working Tanstaafl
2013-02-22 16:28 ` Mick
2013-02-22 16:40 ` Michael Mol [this message]
2013-02-22 17:18 ` Mike Gilbert
2013-02-22 20:30 ` Tanstaafl
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=51279F97.5050002@gmail.com \
--to=mikemol@gmail.com \
--cc=gentoo-user@lists.gentoo.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