On Mon, Feb 21, 2022 at 01:34:58PM +0100, Eelco Chaudron wrote:
> On 21 Feb 2022, at 12:36, Ilya Maximets wrote:
...
> > And while we're here, I'm not sure why we need to check the +est+new
> > combination in that code either.
>
> Because according to the kernel these two flags are mutually exclusive, so
> you can not set a filter for both. A connection can be new and established at
> the same time, not sure why they choose to ignore the new state, guess the
> kernel module ignores this also.
And also for ovs, at least at openflow level. On ovs-fields.7 man page
it says:
There are additional constraints on these flags, listed in
decreasing order of precedence
below:
1. If trk is unset, no other flags are set.
2. If trk is set, one or more other flags may be set.
3. If inv is set, only the trk flag is also set.
4. new and est are mutually exclusive.
5. new and rpl are mutually exclusive.
6. rel may be set in conjunction with any other flags.
>
> Guess I could also do a similar fix, i.e. force the +trk flag when not set?
> What do you think!? I did not test this, so it might bring new side effects ;)
>
>
> > Best regards, Ilya Maximets.
>
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
