From: Christoph Anton Mitterer <christoph.anton.mitterer@physik.uni-muenchen.de>
To: netfilter <netfilter@vger.kernel.org>
Subject: dropping UNTRACKED packets, breaks IPv6 - why?
Date: Fri, 26 Jul 2013 03:59:22 +0200 [thread overview]
Message-ID: <1374803962.5489.12.camel@fermat.scientia.net> (raw)
Hi.
I usually have some default rules in place on all nodes which look about
like this:
---------------------
-A INPUT --in-interface lo -j ACCEPT
-A OUTPUT --out-interface lo -j ACCEPT
-A INPUT -m state --state UNTRACKED -j DROP
-A FORWARD -m state --state UNTRACKED -j DROP
-A OUTPUT -m state --state UNTRACKED -j DROP
-A INPUT -m state --state INVALID -j DROP
-A FORWARD -m state --state INVALID -j DROP
-A OUTPUT -m state --state INVALID -j DROP
#handle IPsec only sources/destinations
#snip/snap
#allow incoming packets for all established and all related connections
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
#allow incoming ICMP packets
-A INPUT --protocol icmpv6 -j ACCEPT
---------------------
And the same for IPv4.
The idea with dropping the UNTRACKED/INVALID was that such packages are
probably not good fellows and should stay out...
Okay... now with IPv4 everything works as expected...
But with v6 nothing works at all and I get Destination unreachables
(even on pings)... I can't even reach the gateway.
When I disable dropping the untracked packets... it starts working,...
even when afterwards I enable it again.
Seems that there is some connection between the host an the gateway
shown then by conntrack.
Now... question is why?
Cheers,
Chris.
next reply other threads:[~2013-07-26 1:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 1:59 Christoph Anton Mitterer [this message]
2013-07-26 7:07 ` dropping UNTRACKED packets, breaks IPv6 - why? Arturo Borrero Gonzalez
2013-07-26 20:20 ` Christoph Anton Mitterer
2013-07-27 19:49 ` Pascal Hambourg
2013-07-27 20:53 ` Christoph Anton Mitterer
2013-07-28 7:51 ` 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=1374803962.5489.12.camel@fermat.scientia.net \
--to=christoph.anton.mitterer@physik.uni-muenchen.de \
--cc=netfilter@vger.kernel.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