From: Alexis <alexis@attla.net.ar>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: Ping and traceroute denied?
Date: Wed, 18 Feb 2004 07:52:34 -0300 [thread overview]
Message-ID: <151921888.20040218075234@attla.net.ar> (raw)
In-Reply-To: <40332D1F.5010806@epost.de>
if you have policies for INPUT, OUTPUT and FORWARD to ACCEPT, those
rules are not needed.
Also, if the traffic is generated in the same firewall FORWARD chain
will not match. Its no needed
Before you add those rules, the pings and traces was working?
Hello Nicole,
Wednesday, February 18, 2004, 6:15:11 AM, you wrote:
NH> Hi,
NH> I added this rules (with fwbuilder):
NH> $IPTABLES -A FORWARD -p icmp -m state --state NEW -j ACCEPT
NH> $IPTABLES -A OUTPUT -p icmp -m state --state NEW -j ACCEPT
NH> $IPTABLES -A INPUT -p icmp -m state --state NEW -j ACCEPT
NH> Why was ping from an interface of my firewall-host denied?
NH> Traceroute too.
NH> What rule shall I add?
NH> Thanks!
NH> Nicole
--
Best regards,
Alexis mailto:alexis@attla.net.ar
prev parent reply other threads:[~2004-02-18 10:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 9:15 Ping and traceroute denied? Nicole Haehnel
2004-02-18 9:30 ` Ray Leach
2004-02-18 10:43 ` Nicole Haehnel
2004-02-18 10:52 ` Alexis [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=151921888.20040218075234@attla.net.ar \
--to=alexis@attla.net.ar \
--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.