| /linux-6.8/tools/testing/selftests/net/ |
| D | test_bridge_backup_port.sh | 267 log_test $? 0 "Forwarding out of swp1"
269 log_test $? 0 "No forwarding out of vx0"
277 log_test $? 0 "No forwarding out of swp1"
279 log_test $? 0 "No forwarding out of vx0"
282 busywait $BUSYWAIT_TIMEOUT bridge_link_check $sw1 swp1 forwarding
294 log_test $? 0 "Forwarding out of swp1"
296 log_test $? 0 "No forwarding out of vx0"
304 log_test $? 0 "No forwarding out of swp1"
306 log_test $? 0 "Forwarding out of vx0"
309 busywait $BUSYWAIT_TIMEOUT bridge_link_check $sw1 swp1 forwarding
[all …]
|
| D | ndisc_unsolicited_na_test.sh | 66 local forwarding=$3
82 # forwarding=0 case is to check that a non-router
86 ${ROUTER_CONF}.forwarding=${forwarding}
142 local forwarding=$3
148 [ ${forwarding} -eq 1 ]; then
177 "forwarding=$3")
183 # Args: drop_unsolicited_na accept_untracked_na forwarding
|
| D | amt.sh | 215 printf "TEST: %-60s [ OK ]\n" "IPv4 amt multicast forwarding"
218 printf "TEST: %-60s [FAIL]\n" "IPv4 amt multicast forwarding"
227 printf "TEST: %-60s [ OK ]\n" "IPv6 amt multicast forwarding"
230 printf "TEST: %-60s [FAIL]\n" "IPv6 amt multicast forwarding"
276 printf "TEST: %-60s [ OK ]\n" "IPv4 amt traffic forwarding torture"
278 printf "TEST: %-60s [ OK ]\n" "IPv6 amt traffic forwarding torture"
|
| D | udpgro_fwd.sh | 230 ip netns exec $NS_DST ethtool -K veth$DST rx-udp-gro-forwarding on
238 ip netns exec $NS_DST ethtool -K veth$DST rx-udp-gro-forwarding on
250 ip netns exec $NS_DST ethtool -K veth$DST rx-udp-gro-forwarding on
262 ip netns exec $NS_DST ethtool -K veth$DST rx-udp-gro-forwarding on
|
| /linux-6.8/tools/testing/selftests/net/forwarding/ |
| D | router_broadcast.sh | 188 log_test "h1 -> net2: reply from r1 (not forwarding)"
190 log_test "h1 -> net3: reply from r1 (not forwarding)"
194 log_test "h1 -> 255.255.255.255: reply from r1 (not forwarding)"
197 log_test "h2 -> net1: reply from r1 (not forwarding)"
199 log_test "h2 -> net3: reply from r1 (not forwarding)"
203 log_test "h2 -> 255.255.255.255: reply from r1 (not forwarding)"
209 log_test "h1 -> net2: reply from h2 (forwarding)"
211 log_test "h1 -> net3: reply from h3 (forwarding)"
215 log_test "h1 -> 255.255.255.255: reply from r1 (not forwarding)"
218 log_test "h2 -> net1: reply from h1 (forwarding)"
[all …]
|
| D | ip6_forward_instats_vrf.sh | 4 # Test ipv6 stats on the incoming if when forwarding with VRF
131 # Disable forwarding temporary while sending the packet
132 sysctl -qw net.ipv6.conf.all.forwarding=0
135 sysctl -qw net.ipv6.conf.all.forwarding=1
|
| /linux-6.8/Documentation/networking/ |
| D | nf_flowtable.rst | 15 Once the first packet of the flow successfully goes through the IP forwarding
22 classic IP forwarding path (the visible effect is that you do not see these
25 follows the classic IP forwarding path.
34 classic IP forwarding path unless the user explicitly instruct flows to use this
35 new alternative forwarding path via policy.
38 forwarding path including the Netfilter hooks and the flowtable fastpath bypass.
74 forwarding path. The TTL is decremented before calling neigh_xmit(). Fragmented
75 traffic is passed up to follow the classic IP forwarding path given that the
77 TCP RST and FIN packets are also passed up to the classic IP forwarding path to
79 the classic forwarding path to report packet-too-big ICMP errors to the sender.
[all …]
|
| D | vxlan.rst | 20 use of statically-configured forwarding entries.
33 entry in the forwarding table. The destination port number is set to
48 forwarding table using the new bridge command.
50 1. Create forwarding table entry::
54 2. Delete forwarding table entry::
58 3. Show forwarding table::
|
| D | bridge.rst | 81 * Forwarding: The port is fully operational and forwards both BPDUs and
84 in the STP process. The data frames forwarding are also disabled.
115 6. Forwarding Ports: After the root bridge is selected and the spanning tree
117 be in the forwarding state (used for data traffic) and which should be in
119 all in the forwarding state. while other bridges have some ports in the
125 designated as the root port. And it is in the Forwarding state, allowing
129 are placed in the Forwarding state. All other ports on the non-root
177 it will start forwarding frames to appropriate destinations based on their
198 switch optimizes the forwarding of multicast traffic. Instead of blindly
204 default. It maintains a Multicast forwarding database (MDB) which keeps track
[all …]
|
| D | switchdev.rst | 15 model for switch devices which offload the forwarding (data) plane from the
154 router port, used to offload L3 forwarding. Two or more ports can be bonded
168 L2 Forwarding Offload
171 The idea is to offload the L2 data forwarding (switching) path from the kernel
173 FDB entry is the {port, MAC, VLAN} tuple forwarding destination.
338 The hardware implementation should be forwarding all registered multicast
345 the kernel, with the device doing the FIB lookup and forwarding. The device
481 interfaces. Some approaches to ensure that the forwarding domain for traffic
484 * If forwarding destinations can be managed per VLAN, the hardware could be
492 forwarding be handled in the software data path.
[all …]
|
| D | mpls-sysctl.rst | 12 possible to configure forwarding for label values equal to or
20 label will be recognized by the kernel and mpls forwarding
|
| /linux-6.8/tools/perf/pmu-events/arch/x86/goldmont/ |
| D | cache.json | 216 …at miss the L2 cache with a snoop hit in the other processor module, data forwarding is required.",
221 …miss the L2 cache with a snoop hit in the other processor module, data forwarding is required. Req…
226 …miss the L2 cache with a snoop hit in the other processor module, no data forwarding is required.",
231 …s the L2 cache with a snoop hit in the other processor module, no data forwarding is required. Req…
266 …at miss the L2 cache with a snoop hit in the other processor module, data forwarding is required.",
271 …miss the L2 cache with a snoop hit in the other processor module, data forwarding is required. Req…
276 …miss the L2 cache with a snoop hit in the other processor module, no data forwarding is required.",
281 …s the L2 cache with a snoop hit in the other processor module, no data forwarding is required. Req…
316 …at miss the L2 cache with a snoop hit in the other processor module, data forwarding is required.",
321 …miss the L2 cache with a snoop hit in the other processor module, data forwarding is required. Req…
[all …]
|
| /linux-6.8/samples/bpf/ |
| D | tc_l2_redirect.sh | 12 IPV6_FORWARDING=$(< /proc/sys/net/ipv6/conf/all/forwarding)
67 sysctl -q -w net.ipv6.conf.all.forwarding=1
81 sysctl -q -w net.ipv6.conf.all.forwarding=$IPV6_FORWARDING
98 sysctl -q -w net.ipv4.conf.ipt.forwarding=1
103 sysctl -q -w net.ipv4.conf.ve1.forwarding=1
114 # test direct egress to ve2 (i.e. not forwarding from
134 sysctl -q -w net.ipv4.conf.ip6t.forwarding=1
140 sysctl -q -w net.ipv4.conf.ve1.forwarding=1
152 # test direct egress to ve2 (i.e. not forwarding from
|
| /linux-6.8/tools/perf/pmu-events/arch/x86/goldmontplus/ |
| D | cache.json | 216 …h) miss the L2 cache with a snoop hit in the other processor module, data forwarding is required.",
221 …miss the L2 cache with a snoop hit in the other processor module, data forwarding is required. Req…
266 …rs miss the L2 cache with a snoop hit in the other processor module, data forwarding is required.",
271 …miss the L2 cache with a snoop hit in the other processor module, data forwarding is required. Req…
316 …h) miss the L2 cache with a snoop hit in the other processor module, data forwarding is required.",
321 …miss the L2 cache with a snoop hit in the other processor module, data forwarding is required. Req…
366 …em miss the L2 cache with a snoop hit in the other processor module, data forwarding is required.",
371 …miss the L2 cache with a snoop hit in the other processor module, data forwarding is required. Req…
416 …h) miss the L2 cache with a snoop hit in the other processor module, data forwarding is required.",
421 …miss the L2 cache with a snoop hit in the other processor module, data forwarding is required. Req…
[all …]
|
| /linux-6.8/Documentation/virt/kvm/s390/ |
| D | s390-diag.rst | 101 DIAG 'X'9C forwarding
110 Forwarding the DIAGNOSE 0x9c initially sent by the guest to yield to
117 0x9c forwarding per second in the purpose of avoiding a DIAGNOSE 0x9c
118 forwarding storm.
119 A value of 0 turns the forwarding off.
|
| /linux-6.8/drivers/net/ethernet/mellanox/mlx5/core/en/tc/act/ |
| D | mirred.c | 31 /* Forwarding non encapsulated traffic between in verify_uplink_forwarding()
48 "devices are both uplink, can't offload forwarding"); in verify_uplink_forwarding()
52 "devices are not the same uplink, can't offload forwarding"); in verify_uplink_forwarding()
149 "can't support more output ports, can't offload forwarding"); in tc_act_can_offload_mirred()
151 "can't support more than %d output ports, can't offload forwarding\n", in tc_act_can_offload_mirred()
170 NL_SET_ERR_MSG_MOD(extack, "devices are not on same switch HW, can't offload forwarding"); in tc_act_can_offload_mirred()
262 "devices are not on same switch HW, can't offload forwarding"); in parse_mirred()
|
| D | mirred_nic.c | 24 "devices are not on same switch HW, can't offload forwarding"); in tc_act_can_offload_mirred_nic()
26 "devices %s %s not on same switch HW, can't offload forwarding\n", in tc_act_can_offload_mirred_nic()
|
| /linux-6.8/net/batman-adv/ |
| D | send.c | 458 * batadv_forw_packet_free() - free a forwarding packet
462 * This frees a forwarding packet and releases any resources it might
481 * batadv_forw_packet_alloc() - allocate a forwarding packet
486 * @skb: The raw packet this forwarding packet shall contain
488 * Allocates a forwarding packet and tries to get a reference to the
492 * Return: An allocated forwarding packet on success, NULL otherwise.
548 * @forw_packet: the forwarding packet to check
550 * This function checks whether the given forwarding packet was claimed by
563 * @forw_packet: the forwarding packet to steal
599 * given hard_iface. If hard_iface is NULL forwarding packets on all hard
[all …]
|
| /linux-6.8/tools/testing/selftests/netfilter/ |
| D | bridge_brouter.sh | 71 # ping netns1, expected to not work (ip forwarding is off)
78 # enable forwarding on both interfaces.
82 ip netns exec ns0 sysctl -q net.ipv4.conf.veth0.forwarding=1
83 ip netns exec ns0 sysctl -q net.ipv4.conf.veth1.forwarding=1
|
| /linux-6.8/include/net/ |
| D | nsh.h | 27 * discussion of MPLS-related forwarding requirements.
39 * a configurable parameter to enable forwarding received SFC OAM
40 * packets unmodified to the next element in the chain. Forwarding OAM
44 * analyze the impact of forwarding an OAM packet for all OAM functions
53 * involved in forwarding an NSH packet MUST decrement the TTL value by
54 * 1 prior to NSH forwarding lookup. Decrementing by 1 from an incoming
128 * the identified SFP for forwarding along an SFP. If re-classification
|
| /linux-6.8/tools/testing/selftests/bpf/ |
| D | test_lwt_seg6local.sh | 137 ip netns exec ${NS1} sysctl net.ipv6.conf.all.forwarding=1 > /dev/null
138 ip netns exec ${NS2} sysctl net.ipv6.conf.all.forwarding=1 > /dev/null
139 ip netns exec ${NS3} sysctl net.ipv6.conf.all.forwarding=1 > /dev/null
140 ip netns exec ${NS4} sysctl net.ipv6.conf.all.forwarding=1 > /dev/null
141 ip netns exec ${NS5} sysctl net.ipv6.conf.all.forwarding=1 > /dev/null
|
| /linux-6.8/tools/testing/selftests/drivers/net/mlxsw/ |
| D | one_armed_router.sh | 45 lib_dir=$(dirname $0)/../../../net/forwarding
162 log_test "fwd mark: forwarding IPv4 packets in software"
169 log_test "fwd mark: forwarding IPv4 packets in hardware"
205 log_test "fwd mark: forwarding IPv6 packets in software"
212 log_test "fwd mark: forwarding IPv6 packets in hardware"
|
| /linux-6.8/Documentation/networking/dsa/ |
| D | dsa.rst | 136 DSA frame header, in order to reduce the autonomous packet forwarding overhead.
633 specific port to be in the forwarding vector. Ports that are unused by the
779 VLAN-unaware bridges). During forwarding and FDB lookup, a packet received on a
885 for incorrect forwarding decisions. In this case, all standalone ports may
899 Offloading the bridge forwarding plane is optional and handled by the methods
902 possible, but the packet forwarding will take place in software, and the ports
907 Concretely, a port starts offloading the forwarding plane of a bridge once it
911 autonomously forwarding (or flooding) received packets without CPU intervention.
914 have already been autonomously forwarded in the forwarding domain of the
916 switch ports part of the same tree ID to be part of the same bridge forwarding
[all …]
|
| D | sja1105.rst | 38 VL Forwarding if VL Lookup no
42 L2 Forwarding yes partially (fully on P/Q/R/S)
46 VL Forwarding Params if VL Forwarding no
48 L2 Forwarding Params yes no
71 The driver supports the configuration of L2 forwarding rules in hardware for
72 port bridging. The forwarding, broadcast and flooding domain between ports can
73 be restricted through two methods: either at the L2 forwarding level (isolate
75 (isolate ports within the same bridge). The final forwarding decision taken by
320 filters should be installed only after the forwarding configuration of the port
|
| /linux-6.8/drivers/net/dsa/sja1105/ |
| D | sja1105_vl.c | 188 * 0 (forwarding) v ------------ |
200 * | VL Forwarding
217 * | to rate-limit re-enter VL Forwarding
224 * | VL Forwarding VL Forwarding
364 /* Discard previous VL Forwarding Table */ in sja1105_init_virtual_links()
371 /* Discard previous VL Forwarding Parameters Table */ in sja1105_init_virtual_links()
418 * the VL Forwarding Table, so no point in putting it in sja1105_init_virtual_links()
462 /* VL Forwarding Table */ in sja1105_init_virtual_links()
471 /* VL Forwarding Parameters Table */ in sja1105_init_virtual_links()
|