Searched refs:ingress (Results 1 – 19 of 19) sorted by relevance
71 int ok = 0, iok = 0, mirror = 0, redir = 0, ingress = 0, egress = 0; in parse_direction() local82 if (ingress) { in parse_direction()89 } else if (!ingress && matches(*argv, "ingress") == 0) { in parse_direction()90 ingress = 1; in parse_direction()
25 Rules can be installed on both ingress and egress - this shows ingress28 tc qdisc add dev eth0 ingress
14 DIRECTION := <ingress | egress>69 tc qdisc add dev eth0 ingress79 # redirect all packets arriving on ingress of lo to eth081 tc qdisc add dev lo ingress103 #allow 1 out 10 packets on ingress of lo to randomly make it to the
18 which implies "if a packet is seen on the ingress of the lo device with38 This stuff works on both ingress and egress qdiscs.78 *ingress is mapped to pre-routing hook137 # Add an ingress qdisc on eth0138 tc qdisc add dev eth0 ingress
55 $TC qdisc add dev eth0 ingress108 qdisc ingress ffff: dev eth0 ----------------
39 ip netns exec ns1 tc filter add dev veth1 ingress bpf da obj test_xdp_meta.o sec t40 ip netns exec ns2 tc filter add dev veth2 ingress bpf da obj test_xdp_meta.o sec t
8 ts_tc "pedit" "Add ingress qdisc" qdisc add dev $DEV ingress13 qdisc del dev $DEV ingress15 qdisc add dev $DEV ingress
61 based on the tags from the ingress.77 *classify on ingress:
31 $TC qdisc add dev $INDEV handle ffff: ingress
40 $TC qdisc add dev $INDEV handle ffff: ingress
44 $TC qdisc add dev $INDEV handle ffff: ingress
29 $TC qdisc add dev $INDEV handle ffff: ingress
43 $TC qdisc add dev $INDEV handle ffff: ingress
46 $TC qdisc add dev $INDEV handle ffff: ingress
25 $TC qdisc add dev $INDEV handle ffff: ingress
32 ffff:fff1 ingress
508 _tc_one_of_list_from $from 'ingress egress'659 _tc_one_of_list 'root ingress parent clsact'664 _tc_one_of_list 'ingress clsact'729 _tc_one_of_list 'root ingress egress parent'734 _tc_one_of_list 'root ingress egress parent'
71 $TC qdisc add dev $DEV1 ingress
1397 - `TC_H_INGRESS`: same as `TC_H_ROOT` but on the ingress side of the