On Thu, Sep 22, 2016 at 10:28:51PM +0800, Liping Zhang wrote: > From: Liping Zhang <liping.zhang@xxxxxxxxxxxxxx> > > Currently, if the user want to match ct l3proto, we must specify the > direction, for example: > # nft add rule filter input ct original l3proto ipv4 > ^^^^^^^^ > Otherwise, error message will be reported: > # nft add rule filter input ct l3proto ipv4 > nft add rule filter input ct l3proto ipv4 > <cmdline>:1:1-38: Error: Could not process rule: Invalid argument > add rule filter input ct l3proto ipv4 > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > Actually, there's no need to require NFTA_CT_DIRECTION attr, because > ct l3proto and protocol are unrelated to direction. > > And for compatibility, even if the user specify the NFTA_CT_DIRECTION > attr, do not report error, just skip it. Applied, thanks. -- 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
