Hi, Harald.
Thank you for your concern, and I understand what you say.
> To summarize, I see the following options:
>
> 1) submit ip6_conntrack to the 2.6.x kernel
> We would then need somebody committe to maintaining it, assuring
> it keeps in sync with the work done on ip_conntrack. I do not want
> to put the burden of ip_conntrack / ip6_conntrack synchronization on
> everybody who submits patches/bugfixes/...
>
> 2) keep ip6_conntrack in patch-o-matic and start work on a l3
> independent conntrack system.
> This would give more users to the code, since most advanced
> netfilter users are using patch-o-matic anyway.
>
I interested on a L3 independent connection tracking.
Could you show me about concrete loadmap and the scheme of nf_conntrack ?
----------------------------------------
Yasuyuki KOZAKAI
Communication Platform Laboratory,
Corporate Research & Development Center,
Toshiba Corporation
yasuyuki.kozakai@xxxxxxxxxxxxx
----------------------------------------
|