Re: mark set datatype check too strict?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Florian,

On Wed, Jan 20, 2016 at 05:31:24PM +0100, Florian Westphal wrote:
> Hello Patrick
> 
> last your you added check to make this illegal:
> 
> nft add rule ip filter input ip daddr 192.168.7.1 meta mark set '(ip saddr & 0xff)'
> datatype mismatch: expected packet mark, expression has type IPv4 address
> 
> My question is -- why?
> The changelog for 068e138a8d9eb doesn't say :)
> Doesn't that take away a lot of flexibility?
> 
> For instance one could e.g. set conntrack zones based on the VLAN id:
> 
> bridge ... prerouting ct zone set vlan id
> (yes, I know that zone cannot be set at the moment).
> 
> 'nft add rule bridge filter prerouting meta mark set vlan id'
> should work, in my opinion.  Any ideas/comments?

Last time we talked about this, Patrick mentioned about adding
explicit casting. We definitely want this flexibility.
--
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



[Index of Archives]     [Netfitler Users]     [LARTC]     [Bugtraq]     [Yosemite Forum]

  Powered by Linux