Lines Matching refs:packets
10 This allows you to classify packets from ingress using the Netfilter
18 This allows you to classify packets before transmission using the
60 for queueing packets via NFNETLINK.
68 for logging packets via NFNETLINK.
88 Connection tracking keeps a record of what packets have passed
120 of packets, but this mark value is kept in the conntrack session
121 instead of the individual packets.
130 packets using the CONNSECMARK target and copied back from
131 connections to packets with the same target, with the packets
535 packets matching some criteria.
635 of a packets security association.
651 This option allows matching packets from an specific OS.
779 Netfilter mark matching allows you to match packets based on the
821 audit records for packets dropped/accepted.
833 Some old DHCP clients drop packets because they are not aware
837 when such packets are sent via a virtual network device.
868 The CONNSECMARK target copies security markings from packets
870 to packets (if the packets are not already marked). This would
915 since you can easily create immortal packets that loop
950 response to particular packets passing through your machine.
1051 mapped onto the incoming interface's address, causing the packets to
1110 The TRACE target allows you to mark packets so that the kernel
1111 will log every rule which match the packets as those traverse
1123 packets, for use with security subsystems.
1133 MSS value of TCP SYN packets, to control the maximum size for that
1138 block ICMP Fragmentation Needed packets. The symptoms of this
1141 packets:
1160 TCP options from TCP packets.
1192 generated packets based on which net_cls control group processes
1204 all nodes see all packets and this match decides which node handles
1205 what packets. The work-load sharing algorithm is based on source
1227 number of bytes and/or packets for each direction within a connection.
1281 CPU matching allows you to match packets based on the CPU
1316 It will also add a "tos" match, which allows you to match packets
1336 inside ESP header of IPSec packets.
1360 Helper matching allows you to match packets in dynamic connections
1369 HL matching allows you to match packets based on the hoplimit
1378 inside IPComp header of IPSec packets.
1435 MAC matching allows you to match packets based on the source
1453 Multiport matching allows you to match TCP or UDP packets based on
1476 analyzing incoming TCP SYN packets.
1487 Socket owner matching allows you to match locally-generated packets
1496 Policy matching allows you to match packets based on the
1592 packets for which a TCP or UDP socket lookup finds a valid socket.
1603 Connection state matching allows you to match packets based on their
1604 relationship to a tracked connection (ie. previous packets). This
1614 on packets periodically or randomly with a given percentage.
1627 pattern matchings in packets.
1636 MSS value of TCP SYN packets, which control the maximum packet size
1647 on) or departure time/date (for locally generated packets).