Re: [PATCH] bridge: make bridge-nf-call-*tables default configurable
From: Jan Engelhardt <hidden>
Date: 2009-06-30 20:16:34
Also in:
netfilter-devel
Possibly related (same subject, not in this thread)
- 2009-07-01 · Re: [PATCH] bridge: make bridge-nf-call-*tables default configurable · Mark Smith <hidden>
- 2009-07-01 · Re: [PATCH] bridge: make bridge-nf-call-*tables default configurable · Herbert Xu <herbert@gondor.apana.org.au>
- 2009-07-01 · Re: [PATCH] bridge: make bridge-nf-call-*tables default configurable · David Miller <davem@davemloft.net>
- 2009-07-01 · Re: [PATCH] bridge: make bridge-nf-call-*tables default configurable · Patrick McHardy <hidden>
- 2009-07-01 · Re: [PATCH] bridge: make bridge-nf-call-*tables default configurable · David Miller <davem@davemloft.net>
On Tuesday 2009-06-30 21:06, David Miller wrote:
Adding appropriate lists and persons to CC:quoted
On Tue, Jun 30, 2009 at 05:27:47PM +0100, Mark McLoughlin wrote:quoted
However, because nf_conntrack introduces an skb_orphan(), it is now recommended that bridge-nf-call-iptables be disabled completely so as to ensure features like TUNSETSNDBUF work as expected.Patrick, does conntrack ever make sense for bridging? Perhaps we should get rid of that completely?
It makes sense absolutely. Consider: * packet enters bridge * NF_HOOK(PF_INET6, NF_INET_PRE_ROUTING, ...) is called by nr_netfilter.c * (connection tracking entry is set up) * let bridging decision be "local delivery"