> The mark is already a bitfield, you may dividide it into separate > marks with the exception of routes which do not yet support a > mask.
Just checked, now that we have --and-mask and --or-mask, this is much better than before. The bitmask is OK when up to 32 marks are needed (like, for classification). But a common setup is NAT+QoS that first hides the src IP and then has to do QoS and mark is the only usable carrier of this information. So the mark value needs to carry both classification info and IP address info and here things become very limited. Though using say 8 bits for host should be usually enough... Maybe just add original src and/ord DST for carrying this information through SNAT/DNAT? Or is it too much bloat for carrying around? -- Meelis Roos ([EMAIL PROTECTED]) - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
