All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Yasuyuki KOZAKAI <yasuyuki.kozakai@toshiba.co.jp>
Cc: netfilter-devel@lists.netfilter.org, kadlec@blackhole.kfki.hu
Subject: Re: nf_nat tree updated
Date: Fri, 24 Nov 2006 15:31:32 +0100	[thread overview]
Message-ID: <45670244.5070905@trash.net> (raw)
In-Reply-To: <200611241427.kAOERapt022342@toshiba.co.jp>

Yasuyuki KOZAKAI wrote:
> From: Patrick McHardy <kaber@trash.net>
> Date: Fri, 24 Nov 2006 09:16:09 +0100
> 
>>This is a first attempt - its quite ugly because of all the
>>new exports it needs. But even worse - what should we do about
>>proc entries added by modules, like the SCTP protocol module?
>>Should we just put this in nf_conntrack_standalone or in case
>>of SCTP in the module itself?
> 
> 
> I like later one from the point of view of modularity. BTW, in the first
> place, why sysctl entries for tcp/udp/icmp are registered by
> nf_conntrack_standalone, not each module ?


Good question - I guess its a relict from ip_chains compatibility
times, like the entire _core/_standalone split.

I'll take another stab at this :)

      parent reply	other threads:[~2006-11-24 14:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-23 15:55 nf_nat tree updated Patrick McHardy
2006-11-23 16:24 ` Yasuyuki KOZAKAI
2006-11-23 17:16   ` [PATCH 0/2] fixes helper assingments (Was: Re: nf_nat tree updated) Yasuyuki KOZAKAI
2006-11-23 23:54 ` nf_nat tree updated Jozsef Kadlecsik
2006-11-24  6:24   ` Patrick McHardy
2006-11-24  8:16     ` Patrick McHardy
2006-11-24 14:27       ` Yasuyuki KOZAKAI
     [not found]       ` <200611241427.kAOERapt022342@toshiba.co.jp>
2006-11-24 14:31         ` Patrick McHardy [this message]

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=45670244.5070905@trash.net \
    --to=kaber@trash.net \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=yasuyuki.kozakai@toshiba.co.jp \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.