Searched refs:egress (Results 1 – 13 of 13) sorted by relevance
71 int ok = 0, iok = 0, mirror = 0, redir = 0, ingress = 0, egress = 0; in parse_direction() local80 } else if (!egress && matches(*argv, "egress") == 0) { in parse_direction()81 egress = 1; in parse_direction()91 if (egress) { in parse_direction()122 p.eaction = egress ? TCA_EGRESS_MIRROR : in parse_direction()132 p.eaction = egress ? TCA_EGRESS_REDIR : in parse_direction()
14 DIRECTION := <ingress | egress>33 Loops are not hard to create in the egress qdiscs.71 match u32 0 0 flowid 1:2 action mirred egress mirror dev eth183 match u32 0 0 flowid 1:2 action mirred egress redirect dev eth095 match u32 0 0 flowid 1:2 action mirred egress mirror dev eth0110 action mirred egress mirror dev eth0124 action mirred egress mirror dev eth1151 action mirred egress mirror dev dummy0
38 This stuff works on both ingress and egress qdiscs.79 *egress is mapped to post-routing hook133 or more interesting things on the egress.
25 Rules can be installed on both ingress and egress - this shows ingress
62 action mirred egress redirect dev ifb0
21 Return Code: Replying router is an egress for the FEC at stack depth 0 (3)48 Return Code: Replying router is an egress for the FEC at stack depth 0 (3)68 Return Code: Replying router is an egress for the FEC at stack depth 0 (3)88 Return Code: Replying router is an egress for the FEC at stack depth 0 (3)108 Return Code: Replying router is an egress for the FEC at stack depth 0 (3)
18 Return Code: Replying router is an egress for the FEC at stack depth 0 (3)39 Return Code: Replying router is an egress for the FEC at stack depth 0 (3)60 Return Code: Replying router is an egress for the FEC at stack depth 0 (3)81 Return Code: Replying router is an egress for the FEC at stack depth 0 (3)102 Return Code: Replying router is an egress for the FEC at stack depth 0 (3)
23 Return Code: Replying router is an egress for the FEC at stack depth 0 (3)52 Return Code: Replying router is an egress for the FEC at stack depth 0 (3)74 Return Code: Replying router is an egress for the FEC at stack depth 0 (3)96 Return Code: Replying router is an egress for the FEC at stack depth 0 (3)118 Return Code: Replying router is an egress for the FEC at stack depth 0 (3)
22 Return Code: Replying router is an egress for the FEC at stack depth 0 (3)47 Return Code: Replying router is an egress for the FEC at stack depth 0 (3)72 Return Code: Replying router is an egress for the FEC at stack depth 0 (3)97 Return Code: Replying router is an egress for the FEC at stack depth 0 (3)122 Return Code: Replying router is an egress for the FEC at stack depth 0 (3)
91 goto egress; in ss_listen()123 egress: in ss_listen()
4 - bpf_shared.c -> Ingress/egress map sharing example
508 _tc_one_of_list_from $from 'ingress egress'729 _tc_one_of_list 'root ingress egress parent'734 _tc_one_of_list 'root ingress egress parent'
1311 Barred over us, prohibit all egress.