Hi Paul, Apologies for lagging to catch up with this. On Wed, Mar 22, 2023 at 09:35:32AM +0200, Paul Blakey wrote: > Currently, offloaded conntrack entries (flows) can only be deleted > after they are removed from offload, which is either by timeout, > tcp state change or tc ct rule deletion. This can cause issues for > users wishing to manually delete or flush existing entries. > > Support deletion of offloaded conntrack entries. > > Example usage: > # Delete all offloaded (and non offloaded) conntrack entries > # whose source address is 1.2.3.4 > $ conntrack -D -s 1.2.3.4 > # Delete all entries > $ conntrack -F This fine with me. I think probably it much be documented somewhere that in case of hardware offload, deletion is asynchronous.
