Lines Matching refs:packet
44 Address Translation. It can also be used to enhance packet
360 information together with the packet is the enqueued via NFNETLINK.
445 "nfmark" value in the packet.
447 the netfilter mark (nfmark) field associated with the packet.
462 ctmark), similarly to the packet mark (nfmark). Using this
500 a packet that lacks a checksum. This is particularly useful,
512 the priority of a packet. Some qdiscs can use this value for
565 or the Priority field of an IPv6 packet, prior to routing.
604 This option adds the `IDLETIMER' target. Each matching packet
640 any iptables table which records the packet header to the syslog.
714 tristate '"TEE" - packet cloning to alternate destination'
719 This option adds a "TEE" target with which a packet can be cloned and
813 BPF matching applies a linux socket filter to each packet and
826 true when the packet must be handled by this cluster node. Thus,
904 currently handling the packet.
939 based on the Type Of Service fields of the IPv4 packet (which share
993 header of the packet.
1011 This option allows you to match against IPVS properties of a packet.
1019 This option allows you to match the length of a packet against a
1039 Ethernet address of the packet.
1111 Physdev packet matching matches against the physical bridge ports
1112 the IP packet arrived on or will leave by.
1117 tristate '"pkttype" packet type match support'
1120 Packet type matching allows you to match a packet by
1248 is a powerful tool for packet classification.
1279 MSS value of TCP SYN packets, which control the maximum packet size
1289 the packet arrival time (at the machine which netfilter is running)
1302 u32 allows you to extract quantities of up to 4 bytes from a packet,
1306 headers with lengths stored in the packet, as in IP or TCP header