Lines Matching full:which

154 present which allow defining rules on a higher level and therefore free the
168 Typically filter delegation is done by means of a hash table, which leads to the
170 can select a hash table and provide a key selector from which a hash is to be
171 computed and used as key to lookup the table's bucket which contains filters for
180 parameter and ideally a handle by which the table can be identified. If the
181 latter is not given, the kernel chooses one on it's own, which has to be
184 Creating filters which link to the created table in
188 parameter and defining the packet data which the kernel will use to calculate
197 parameter, which gives sample data to hash and thereby define the table bucket
208 Options and selectors require values to be specified in a specific format, which
262 Alternatively one may specify a single, 32bit long hex number which contains
268 Set an offset which defines where matches of subsequent filters are applied to.
296 which consists of either 16bit
310 which serves the same purpose.
315 to specify which bucket to add this filter to. This allows one to avoid having
406 assumes a suitable layer four protocol is present (which has Source and
429 IPv6 only. Match the header's Traffic Class field, which has the same purpose
435 only 20bytes long, which are the least significant ones here. The remaining
495 which affects in which order multiple filters attached to the same
524 filter, which contains a hash table of size 1 (as the
528 The third line then shows the actual filter which was added above: it sits in
539 which is 192, 168 and 8.
568 The next step is to create a filter which links to the created hash table:
582 determine which table and bucket to redirect to. In this case the hash key
583 should be constructed out of the second byte at offset 12, which corresponds to
604 selects an amount of data which could exceed the
614 and IPv6 supports extension headers which affect upper layer header offset. To
619 matches which use
622 way to achieve that is by doing it in a separate filter which then links to the
623 filter which wants to use it. Here is an example of doing so:
645 to reference to it. The second call then adds the actual filter, which pushes
658 the hash table from first call is referenced which holds the filter from second