: Reinject packet instead of calling netfilter directly on input
Get series with b4
b4 am 1196369374.4437.18.camel@localhostVersions newest first
- v1 Latest2 patches 7 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | : Reinject v4 packet on input instead of calling netfilternet/ | +14 | 0 replies | |
| 2/2 | : Reinject v6 packet on input instead of calling netfilternet/ | +14 | 4 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] [IPSEC]: Reinject packet instead of calling netfilter directly on input
Herbert,
This is a simplified version of one of your earlier patches that never made it in. I liked it so much that i reduced it to this and infact given the cycles today, tested it (with transport and tunnel mode only;->).
We re-inject a decrypted ipsec (other than tunnel mode) back and let it bubble up the network stack. This improves debugability (since sniffers like tcpdump can see the packet) and usability since ingress tc filters can act on it.
Ive broken it down into two: IPv4 and IPV6. If you want to go through the xfrm reinject() method, then I am gonna need more time to resubmit or you be my guest and go for it and i will test it.
cheers,
jamal