Le mercredi 25 mai 2011 Ã 15:09 +0200, Maciej Åenczykowski a Ãcrit : > Not that I've really been following the thread. > But I think that this sort of functionality should most likely be > developed as a virtual (tun/tap/veth/sit) style tunnel-like device. > > You would use ipv4/ipv6 routing in the normal kernel to direct traffic > out this virtual interface, and immediately ipv6/ipv4 traffic would > come back out of it. > > This should allow all the rest of the kernel (including connection > tracking) to function normally - although of course every connection > would be registered in an unrelated way twice (once as v4, once as > v6). > > I think this has nice 'black box' semantics. CERNET doc refers to : http://linux.ivi2.org/ With an implementation for linux-2.6.18 : http://linux.ivi2.org/impl/ This seems enough to me, and not intrusive. Pierre, you really should discuss why a netfilter module is needed at all. Maybe you have a pdf or some slides somewhere (no code, but formal discussion) ? -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
