I just noticed that NAT "random-fully" option. Guys, can we *please* not use the names of defines for keywords if their name is obviously chosen to have a common prefix, not to be a user facing option? We don't aim to follow the iptables model of naming options after kernel internal names, we want something that is easy and descriptive for the user. To have random and random-fully is confusing enough, we don't need to make it worse by using backwards named options. "fully-random" would at least be a proper english term. I'll rename it, luckily we didn't have a release so far. Sorry for getting a bit upset about this, but messing this up means having compat crap and this one was really obviously a bad choice. -- 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
