Phil Sutter <phil@xxxxxx> wrote: > Existing code is a bit quirky: If no connlabel.conf was found, the local > function connlabel_value_parse() is called which tries to interpret > given label as a number. If the config exists though, > nfct_labelmap_get_bit() is called instead which doesn't care about > "undefined" connlabel names. So unless installed connlabel.conf contains > entries for all possible numeric labels, rules added by users may stop > working if a connlabel.conf is created. Fix this by falling back to > connlabel_value_parse() function also if connlabel_open() returned 0 but > nfct_labelmap_get_bit() returned an error. Acked-by: Florian Westphal <fw@xxxxxxxxx>