On 9/11/20 9:42 AM, Laura García Liébana wrote:
On Tue, Sep 8, 2020 at 2:55 PM Daniel Borkmann <daniel@xxxxxxxxxxxxx> wrote:
On 9/5/20 7:24 AM, Lukas Wunner wrote:
On Fri, Sep 04, 2020 at 11:14:37PM +0200, Daniel Borkmann wrote:
On 9/4/20 6:21 PM, Lukas Wunner wrote:
[...]
The tc queueing layer which is below is not the tc egress hook; the
latter is for filtering/mangling/forwarding or helping the lower tc
queueing layer to classify.
People want to apply netfilter rules on egress, so either we need an
egress hook in the xmit path or we'd have to teach tc to filter and
mangle based on netfilter rules. The former seemed more straight-forward
to me but I'm happy to pursue other directions.
I would strongly prefer something where nf integrates into existing tc hook,
not only due to the hook reuse which would be better, but also to allow for a
more flexible interaction between tc/BPF use cases and nf, to name one
That sounds good but I'm afraid that it would take too much back and
forth discussions. We'll really appreciate it if this small patch can
be unblocked and then rethink the refactoring of ingress/egress hooks
that you commented in another thread.
I'm not sure whether your comment was serious or not, but nope, this needs
to be addressed as mentioned as otherwise this use case would regress. It
is one thing for you wanting to remove tc / BPF from your application stack
as you call it, but not at the cost of breaking others.
Thank you,
Daniel
