/openbmc/linux/Documentation/networking/ |
H A D | openvswitch.rst | 63 but the forwarding behavior is correct. (If userspace can 65 forwarding behavior, then it could set up a flow anyway.)
|
H A D | ieee802154.rst | 47 a Mesh Addressing header to support sub-IP forwarding, a Fragmentation header
|
H A D | snmp_counter.rst | 79 address is not a local address and IP forwarding is not enabled 87 happen when IP forwarding is enabled and the destination IP address is 1572 First, generate InAddrErrors. On server B, we disable IP forwarding:: 1574 $ sudo sysctl -w net.ipv4.conf.all.forwarding=0 1590 forwarding on server B, Server A sent packets to server B, then server B 1596 forwarding:: 1598 $ sudo sysctl -w net.ipv4.conf.all.forwarding=1 1626 We enabled IP forwarding on server B, when server B received a packet
|
/openbmc/linux/tools/testing/selftests/drivers/net/mlxsw/ |
H A D | devlink_trap_l2_drops.sh | 8 lib_dir=$(dirname $0)/../../../net/forwarding
|
H A D | devlink_trap_control.sh | 40 lib_dir=$(dirname $0)/../../../net/forwarding
|
H A D | devlink_trap_l3_drops.sh | 40 lib_dir=$(dirname $0)/../../../net/forwarding
|
H A D | tc_restrictions.sh | 4 lib_dir=$(dirname $0)/../../../net/forwarding
|
H A D | sch_red_core.sh | 73 lib_dir=$(dirname $0)/../../../net/forwarding
|
/openbmc/linux/Documentation/PCI/ |
H A D | boot-interrupts.rst | 74 The legacy interrupt forwarding mechanism exists today in a number of
|
/openbmc/u-boot/arch/arm/cpu/armv7/ |
H A D | start.S | 339 orrlt r0, r0, #(0x1 << 27) @ L2 PLD data forwarding disable
|
/openbmc/linux/Documentation/networking/device_drivers/ethernet/ti/ |
H A D | cpsw_switchdev.rst | 37 segregated ports - no forwarding in HW.
|
/openbmc/linux/Documentation/driver-api/pci/ |
H A D | p2pdma.rst | 12 One of the biggest issues is that PCI doesn't require forwarding
|
/openbmc/openbmc-tools/openbmctool/ |
H A D | README.md | 54 - <https://www.rsyslog.com/storing-and-forwarding-remote-messages/>
|
/openbmc/linux/tools/testing/selftests/net/ |
H A D | srv6_end_next_csid_l3vpn_test.sh | 520 ip netns exec "${nsname}" sysctl -wq net.ipv6.conf.all.forwarding=1
|
H A D | srv6_end_x_next_csid_l3vpn_test.sh | 460 ip netns exec "${nsname}" sysctl -wq net.ipv6.conf.all.forwarding=1
|
H A D | fib_nexthops.sh | 163 ip netns exec ${n} sysctl -qw net.ipv6.conf.all.forwarding=1 164 ip netns exec ${n} sysctl -qw net.ipv6.conf.default.forwarding=1
|
/openbmc/linux/drivers/net/usb/ |
H A D | cdc_mbim.c | 342 is_router = !!in6_dev->cnf.forwarding; in do_neigh_solicit()
|
/openbmc/bios-bmc-smm-error-logger/ |
H A D | .clang-tidy | 172 bugprone-forwarding-reference-overload,
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | reporting-regressions.rst | 30 #. Optional, but recommended: when sending or forwarding your report, make the 107 When CCing for forwarding your report to the list, consider directly telling the 213 your report on the radar of these people by CCing or forwarding each report to
|
/openbmc/docs/designs/mctp/ |
H A D | mctp-kernel.md | 47 such as message assembly/disassembly, packet forwarding, and physical interface 685 A network can be configured for "forwarding" mode. In this mode, packets may be 689 As per DSP0236, packet reassembly does not occur during the forwarding process. 811 mctp network set <network-id> forwarding <on|off>
|
H A D | mctp-userspace.md | 22 routing of MCTP messages from external endpoints, and handling the forwarding
|
/openbmc/linux/net/bridge/netfilter/ |
H A D | Kconfig | 70 local input, forwarding and local output. See the man page for
|
/openbmc/linux/tools/testing/selftests/drivers/net/netdevsim/ |
H A D | devlink.sh | 4 lib_dir=$(dirname $0)/../../../net/forwarding
|
/openbmc/linux/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
H A D | switch-driver.rst | 86 The driver supports the configuration of L2 forwarding rules in hardware for
|
/openbmc/linux/Documentation/networking/device_drivers/ethernet/freescale/ |
H A D | dpaa.rst | 158 provides a big performance boost for the forwarding scenarios, allowing
|