Thread (47 messages) 47 messages, 5 authors, 2014-06-27

Re: [PATCH net-next v2] net: filter: add insn for loading internal transport header offset

From: David Miller <davem@davemloft.net>
Date: 2014-05-05 19:12:05

From: Chema Gonzalez <redacted>
Date: Mon, 5 May 2014 11:42:00 -0700
On Fri, May 2, 2014 at 7:52 PM, David Miller [off-list ref] wrote:
quoted
We can probably add an extension to AF_PACKET which provides the flow
key at the end of the tpacket3_hdr if a certain socket option is set.

That would provide the transport header as well as a side effect, and
be much more powerful and efficient than this particular BPF
instruction.
I'm not sure whether I follow this. The goal is to be able to access
the inner-most headers inside BPF, not in userland by calling
getsockopt().
You're missing my entire point.

You can use AF_PACKET mmap() rings and in those ring entries all of the
flow dissection information can be put in the ring entry headers before
the packet contents.  Ports, header offsets, everything.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help