lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 4 Jan 2012 21:56:05 +0100
From:	Hans Schillstrom <hans@...illstrom.com>
To:	Jozsef Kadlecsik <kadlec@...ckhole.kfki.hu>
Cc:	Pablo Neira Ayuso <pablo@...filter.org>,
	Hans Schillstrom <hans.schillstrom@...csson.com>,
	Jan Engelhardt <jengelh@...ozas.de>,
	Patrick McHardy <kaber@...sh.net>,
	"netfilter-devel@...r.kernel.org" <netfilter-devel@...r.kernel.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH 1/1] netfilter: Add possibility to turn off netfilters defrag per netns


On Wednesday, January 04, 2012 19:05:10 Jozsef Kadlecsik wrote:
> On Wed, 4 Jan 2012, Pablo Neira Ayuso wrote:
> 
> > On Wed, Jan 04, 2012 at 12:48:35PM +0100, Hans Schillstrom wrote:
> > > I like that idea, an "early" table at prio -500 with PREROUTING.
> > > There is also a need for a new flag "--allfrags"
> > > i.e. all fragments needs to be sorted out and sent to same dest for defrag.
> > > 
> > > ex.
> > > iptables -t early -A PREROUTING -i eth0 --allfrags -j NOTRACK
> > 
> > New tables add too much overhead. We have discussed this before with
> > Patrick.
> > 
> > Since this still remains specific to your needs, I think you can
> > remove nf_conntrack module in your setup.
> > 
> > I don't come with one sane setup that may want selectively defragment
> > some traffic yes and other not.
> > 
> > Am I missing anything else?
> 
> I agree. If you don't want defragmentation at all, then make sure you 
> don't load the nf_conntrack module directly/indirectly. Conntrack doesn't 
> work without defragmentation anyway.

We are using LXC and it's only in the container that holds the external 
interface that can't have defragmentation.
The problem is if it's loaded you have it in all namespaces :-(

> 
> The only thing what such a really-early table could buy at the moment is 
> to specify which flows not to defragment at layer 3 level.
> 
> If we had dynamic hooks registration and hook priorities at table level, 
> that'd come handy now.

I do agree.

> 

Regards
Hans
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ