netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ulrich Weber <ulrich.weber@googlemail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Ulrich Weber <ulrich.weber@googlemail.com>,
	Leo Baltus <Leo.Baltus@omroep.nl>,
	netfilter-devel@vger.kernel.org
Subject: Re: ip6tables breaks dnssec?
Date: Wed, 27 Apr 2011 13:43:22 +0200	[thread overview]
Message-ID: <4DB8015A.8050909@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1104271321060.10844@obet.zrqbmnf.qr>

On 04/27/2011 01:22 PM, Jan Engelhardt wrote:
> On Wednesday 2011-04-27 12:43, Ulrich Weber wrote:
> 
>> Each fragmented IPv6 packets will traverse netfilter separately,
>> in contrast to IPv4, where its only one refragmented packet.
> 
> Not really. All fragments enter nf_hook_slow, be it IPv4 or IPv6.
> It's just that nf_defrag - which is a netfilter module - collects and 
> suppresses fragments before spitting out the unfragmented one.

nf_ct_frag6_output() sends each fragment itself through netfilter.

Personally I don't like this and would rather see, that IPv6 behaves the
same way as IPv4, sending the unfragmented packet through netfilter...


Cheers
 Ulrich

  parent reply	other threads:[~2011-04-27 11:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27  8:57 ip6tables breaks dnssec? Leo Baltus
2011-04-27 10:08 ` Jan Engelhardt
2011-04-27 10:43   ` Ulrich Weber
2011-04-27 10:56     ` Leo Baltus
2011-04-27 11:22     ` Jan Engelhardt
2011-04-27 11:41       ` Leo Baltus
2011-05-06 14:05         ` Leo Baltus
2011-04-27 11:43       ` Ulrich Weber [this message]
2011-04-27 12:54       ` Stephen Clark
2011-04-27 13:01         ` Jan Engelhardt

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=4DB8015A.8050909@gmail.com \
    --to=ulrich.weber@googlemail.com \
    --cc=Leo.Baltus@omroep.nl \
    --cc=jengelh@medozas.de \
    --cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).