In the good old times of Kernel Extensions, it was possible to set a cookie when using a socket filter and it was possible to attach a tag to a mbuf.
I've noticed the identifier property for a flow but it does not look like it can provide exactly the same kind of services.
In addition to this, I've not found till now some clear explanations about the lifecycle of a flow (e.g. does a data filter provider receive the handleInboundDataCompleteForFlow: message if a flow is denied by another provider, do you get a new flow if some packet is reinjected, etc.).
Considering that cookies and tags could be used to avoid filtering packets that have already been processed, it's a bit mysterious so far how you can do the same thing with a Network Extension.
Questions
Side note:
Why does typing "NetworkExtension" in the Search Forums search field return no posts with the NetworkExtension tag (at least in the first result pages)?
I've noticed the identifier property for a flow but it does not look like it can provide exactly the same kind of services.
In addition to this, I've not found till now some clear explanations about the lifecycle of a flow (e.g. does a data filter provider receive the handleInboundDataCompleteForFlow: message if a flow is denied by another provider, do you get a new flow if some packet is reinjected, etc.).
Considering that cookies and tags could be used to avoid filtering packets that have already been processed, it's a bit mysterious so far how you can do the same thing with a Network Extension.
Questions
What is the equivalent of the cookie parameter of kpi socket filter callbacks?
What is the equivalent of the mbuf tag?
Side note:
Why does typing "NetworkExtension" in the Search Forums search field return no posts with the NetworkExtension tag (at least in the first result pages)?