From: "Michal Kubeček" <mkubecek@suse.cz>
To: netfilter@vger.kernel.org
Cc: Nick Edwards <nick.z.edwards@gmail.com>
Subject: Re: ipv6 rule icmp bug maybe
Date: Thu, 04 Apr 2013 07:50:09 +0200 [thread overview]
Message-ID: <5293489.MPThhE2Fke@alaris> (raw)
In-Reply-To: <CAMD-=VJU3PesmF7P4c0nQuk1Nw_XdoUf559h8tXfbEGXEv=2dQ@mail.gmail.com>
On Thursday 04 of April 2013 10:02EN, Nick Edwards wrote:
> with ipv4 we have been able to
> -P INPUT DROP
> loopback accepts etc...
>
> -A INPUT -s 192.168.1.0/24 -j ACCEPT
>
> hitting this, means allow all from 192.168.1.1/2/3/4.... etc - tcp.
> udp. icmp whatever..
>
> But with ip6tables this same approach does not seem to work, it
> permits tcp/udp, but it does not allow icmp, bug?
Hard to say unless you tell us what do your rules look like and what
packets are dropped (and you think they shouldn't be).
Michal Kubecek
next prev parent reply other threads:[~2013-04-04 5:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 0:02 ipv6 rule icmp bug maybe Nick Edwards
2013-04-04 5:50 ` Michal Kubeček [this message]
2013-04-04 7:13 ` Nick Edwards
2013-04-04 7:16 ` Nick Edwards
2013-04-07 9:15 ` Pascal Hambourg
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=5293489.MPThhE2Fke@alaris \
--to=mkubecek@suse.cz \
--cc=netfilter@vger.kernel.org \
--cc=nick.z.edwards@gmail.com \
/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