Lines Matching full:which

158 present which allow defining rules on a higher level and therefore free the
172 Typically filter delegation is done by means of a hash table, which leads to the
174 can select a hash table and provide a key selector from which a hash is to be
175 computed and used as key to lookup the table's bucket which contains filters for
184 parameter and ideally a handle by which the table can be identified. If the
185 latter is not given, the kernel chooses one on it's own, which has to be
188 Creating filters which link to the created table in
192 parameter and defining the packet data which the kernel will use to calculate
201 parameter, which gives sample data to hash and thereby define the table bucket
212 Options and selectors require values to be specified in a specific format, which
266 Alternatively one may specify a single, 32bit long hex number which contains
272 Set an offset which defines where matches of subsequent filters are applied to.
300 which consists of either 16bit
314 which serves the same purpose.
319 to specify which bucket to add this filter to. This allows one to avoid having
418 assumes a suitable layer four protocol is present (which has Source and
441 IPv6 only. Match the header's Traffic Class field, which has the same purpose
447 only 20bytes long, which are the least significant ones here. The remaining
507 which affects in which order multiple filters attached to the same
536 filter, which contains a hash table of size 1 (as the
540 The third line then shows the actual filter which was added above: it sits in
551 which is 192, 168 and 8.
580 The next step is to create a filter which links to the created hash table:
594 determine which table and bucket to redirect to. In this case the hash key
595 should be constructed out of the second byte at offset 12, which corresponds to
616 selects an amount of data which could exceed the
626 and IPv6 supports extension headers which affect upper layer header offset. To
631 matches which use
634 way to achieve that is by doing it in a separate filter which then links to the
635 filter which wants to use it. Here is an example of doing so:
657 to reference to it. The second call then adds the actual filter, which pushes
670 the hash table from first call is referenced which holds the filter from second