Re: [PATCH] bridge: make bridge-nf-call-*tables default configurable
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: 2009-07-01 16:33:37
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 Wed, Jul 01, 2009 at 11:21:44AM +0200, Patrick McHardy wrote:
Agreed, at least as long as this is still the default behaviour. Mark, could you add this to your patch? br_nf_pre_routing_finish() looks like a good place to print a warning when skb->nfct != NULL.
Here's a suggestion: Can we add another field to the conntrack tuple? This would be used to ensure that every bridge's conntrack is distinct from each other, as well as that of the system IP stack. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} [off-list ref] Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt