On Wednesday 2008-04-09 18:35, Patrick McHardy wrote: > >> A few concerns. >> If so, how would you deal with the addition of a new, real, >> protocol? Suppose someone added support for the >> semifictional IPv5, say AF_INET5=42 or so. How would >> this affect the NFPROTO list? > > It wouldn't since those values simply have seperate > meanings. AF_INET5 might be 42, NFPROTO_INET5 could > be .. lets say 5. > Then the big question is: what do you store in ct->tuplehash[0].src.l3num, AF_INET5 or NFPROTO_IPV5? Probably NFPROTO_IPV5. Ok, then the only issue - if there is such - is when AF_ values from the networking code pass into netfilter territory, then you would need a translation function. -- 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
