Home
last modified time | relevance | path

Searched full:tunnels (Results 1 – 25 of 228) sorted by relevance

12345678910

/kernel/linux/linux-6.6/Documentation/networking/
Dl2tp.rst31 and whether it is a control or data packet. When tunnels and sessions
37 operations when establishing tunnels and sessions. The procedure looks
117 sockets are used to implement unmanaged L2TPv3 tunnels (iproute2's "ip
120 unmanaged tunnels later in this document.
363 L2TPv2/L2TPv3 IPv4/IPv6 tunnels and userspace must use the appropriate
426 - Tunnels are managed using a tunnel management socket which is a
441 Unmanaged L2TPv3 tunnels
445 tunnels. Unmanaged tunnels have no userspace tunnel socket, and
452 ``iproute2`` has commands for managing static L2TPv3 tunnels; do ``ip
469 # cat /debug/l2tp/tunnels
[all …]
Dbareudp.rst30 This creates a bareudp tunnel device which tunnels L3 traffic with ethertype
38 The multiproto mode allows bareudp tunnels to handle several protocols of the
Dvxlan.rst17 Unlike most tunnels, a VXLAN is a 1 to N network, not just point to
78 $ ethtool --show-tunnels eth0
/kernel/linux/linux-5.10/Documentation/networking/
Dl2tp.rst31 and whether it is a control or data packet. When tunnels and sessions
37 operations when establishing tunnels and sessions. The procedure looks
117 sockets are used to implement unmanaged L2TPv3 tunnels (iproute2's "ip
120 unmanaged tunnels later in this document.
363 L2TPv2/L2TPv3 IPv4/IPv6 tunnels and userspace must use the appropriate
426 - Tunnels are managed using a tunnel management socket which is a
441 Unmanaged L2TPv3 tunnels
445 tunnels. Unmanaged tunnels have no userspace tunnel socket, and
452 ``iproute2`` has commands for managing static L2TPv3 tunnels; do ``ip
469 # cat /debug/l2tp/tunnels
[all …]
Dbareudp.rst30 This creates a bareudp tunnel device which tunnels L3 traffic with ethertype
38 The multiproto mode allows bareudp tunnels to handle several protocols of the
Dvxlan.rst17 Unlike most tunnels, a VXLAN is a 1 to N network, not just point to
78 $ ethtool --show-tunnels eth0
/kernel/linux/linux-5.10/Documentation/admin-guide/
Dthunderbolt.rst9 responsible for enumerating routers and establishing tunnels. A
71 The firmware automatically creates tunnels for Display Port and
76 The firmware automatically creates tunnels for the USB controller and
86 device must be authorized by the user before PCIe tunnels are created
105 The ``authorized`` attribute reads 0 which means no PCIe tunnels are
110 This will create the PCIe tunnels and the device is now connected.
128 to the ``authorized`` attribute and the PCIe tunnels will be created in
138 Now the device is connected (PCIe tunnels are created) and in addition
148 on the key, the device is connected and the PCIe tunnels are created.
149 However, if the challenge fails no tunnels are created and error is
/kernel/linux/linux-5.10/tools/testing/selftests/bpf/
Dwith_tunnels.sh4 # setup tunnels for flow dissection test
14 echo "tunnels before test:"
28 echo "tunnels after test:"
/kernel/linux/linux-6.6/tools/testing/selftests/bpf/
Dwith_tunnels.sh4 # setup tunnels for flow dissection test
14 echo "tunnels before test:"
28 echo "tunnels after test:"
/kernel/linux/linux-6.6/Documentation/admin-guide/
Dthunderbolt.rst9 responsible for enumerating routers and establishing tunnels. A
74 The firmware automatically creates tunnels for Display Port and
79 The firmware automatically creates tunnels for the USB controller and
93 device must be authorized by the user before PCIe tunnels are created
112 The ``authorized`` attribute reads 0 which means no PCIe tunnels are
117 This will create the PCIe tunnels and the device is now connected.
135 to the ``authorized`` attribute and the PCIe tunnels will be created in
145 Now the device is connected (PCIe tunnels are created) and in addition
155 on the key, the device is connected and the PCIe tunnels are created.
156 However, if the challenge fails no tunnels are created and error is
/kernel/linux/linux-6.6/drivers/thunderbolt/
Dtb.c24 * @tunnel_list: List of active tunnels
102 * Find all DP tunnels that go through all the same USB4 links in tb_attach_bandwidth_group()
103 * as this one. Because we always setup tunnels the same way we in tb_attach_bandwidth_group()
104 * can just check for the routers at both ends of the tunnels in tb_attach_bandwidth_group()
655 * Find all DP tunnels that cross the port and reduce in tb_available_bandwidth()
948 * tunnels and know which switches were authorized already by in tb_scan_port()
1002 * Create USB 3.x tunnels only when the switch is plugged to the in tb_scan_port()
1004 * and want to discover existing USB 3.x tunnels before we create in tb_scan_port()
1056 * PCIe and DMA tunnels do not consume guaranteed in tb_deactivate_and_free_tunnel()
1066 * tb_free_invalid_tunnels() - destroy tunnels of devices that have gone away
[all …]
/kernel/linux/linux-6.6/tools/testing/selftests/drivers/net/netdevsim/
Dudp_tunnel_nic.sh159 ethtool --show-tunnels $NSIM_NETDEV | grep "$pp_expected" >/dev/null
163 ethtool --show-tunnels $NSIM_NETDEV
202 cnt=$(ethtool --show-tunnels $NSIM_NETDEV | grep -c "$pp_expected")
206 ethtool --show-tunnels $NSIM_NETDEV
255 ethtool -h | grep show-tunnels 2>&1 >/dev/null && HAS_ETHTOOL=y
323 msg="tunnels destroyed"
363 msg="remove tunnels"
875 msg="tunnels destroyed 1"
901 msg="tunnels destroyed 2"
941 msg="tunnels destroyed"
/kernel/linux/linux-5.10/tools/testing/selftests/drivers/net/netdevsim/
Dudp_tunnel_nic.sh159 ethtool --show-tunnels $NSIM_NETDEV | grep "$pp_expected" >/dev/null
163 ethtool --show-tunnels $NSIM_NETDEV
202 cnt=$(ethtool --show-tunnels $NSIM_NETDEV | grep -c "$pp_expected")
206 ethtool --show-tunnels $NSIM_NETDEV
255 ethtool -h | grep show-tunnels 2>&1 >/dev/null && HAS_ETHTOOL=y
322 msg="tunnels destroyed"
362 msg="remove tunnels"
867 msg="tunnels destroyed 1"
892 msg="tunnels destroyed 2"
932 msg="tunnels destroyed"
/kernel/linux/linux-5.10/samples/bpf/
Dtest_ipip.sh109 # tcp check _same_ IP over different tunnels
131 # tcp check _same_ IP over different tunnels
153 # tcp check _same_ IP over different tunnels
175 echo "Testing IP tunnels..."
/kernel/linux/linux-6.6/net/ipv6/
DKconfig209 Support for IPv6-in-IPv6 and IPv4-in-IPv6 tunnels described in
299 tunnels mechanism. Also enable support for advanced local
328 tunnels mechanism.
339 Header using the lightweight tunnels mechanism.
/kernel/linux/linux-5.10/drivers/thunderbolt/
Dtb.c20 * @tunnel_list: List of active tunnels
349 * Find all DP tunnels that cross the port and reduce in tb_available_bandwidth()
617 * tunnels and know which switches were authorized already by in tb_scan_port()
655 * Create USB 3.x tunnels only when the switch is plugged to the in tb_scan_port()
657 * and want to discover existing USB 3.x tunnels before we create in tb_scan_port()
702 * PCIe and DMA tunnels do not consume guaranteed in tb_deactivate_and_free_tunnel()
712 * tb_free_invalid_tunnels() - destroy tunnels of devices that have gone away
992 * Tear down all DP tunnels and release their resources. They in tb_disconnect_and_release_dp()
1250 /* tunnels are only present after everything has been initialized */ in tb_stop()
1253 * DMA tunnels require the driver to be functional so we in tb_stop()
[all …]
Dtunnel.h26 * tunnels may be %NULL or null adapter port instead.
34 * @list: Tunnels are linked using this field
/kernel/linux/linux-5.10/drivers/net/ethernet/mellanox/mlxsw/
Dspectrum_ipip.c169 /* Linux demuxes tunnels based on packet SIP (which must match tunnel in mlxsw_sp_ipip_fib_entry_op_gre4_rtdp()
224 /* Tunnels with unset local or remote address are valid in Linux and in mlxsw_sp_ipip_tunnel_complete()
225 * used for lightweight tunnels (LWT) and Non-Broadcast Multi-Access in mlxsw_sp_ipip_tunnel_complete()
226 * (NBMA) tunnels. In principle these can be offloaded, but the driver in mlxsw_sp_ipip_tunnel_complete()
/kernel/linux/linux-6.6/drivers/net/ethernet/mellanox/mlxsw/
Dspectrum_ipip.c208 /* Linux demuxes tunnels based on packet SIP (which must match tunnel in mlxsw_sp_ipip_decap_config_gre4()
228 /* Tunnels with unset local or remote address are valid in Linux and in mlxsw_sp_ipip_tunnel_complete()
229 * used for lightweight tunnels (LWT) and Non-Broadcast Multi-Access in mlxsw_sp_ipip_tunnel_complete()
230 * (NBMA) tunnels. In principle these can be offloaded, but the driver in mlxsw_sp_ipip_tunnel_complete()
422 /* Linux demuxes tunnels based on packet SIP (which must match tunnel in mlxsw_sp_ipip_decap_config_gre6()
/kernel/linux/linux-5.10/net/l2tp/
DKconfig21 tunnels. One IP tunnel may carry thousands of individual PPP
26 over L2TP tunnels. L2TPv3 is defined in RFC 3931
/kernel/linux/linux-6.6/net/l2tp/
DKconfig21 tunnels. One IP tunnel may carry thousands of individual PPP
26 over L2TP tunnels. L2TPv3 is defined in RFC 3931
/kernel/linux/linux-5.10/net/ipv6/
DKconfig208 Support for IPv6-in-IPv6 and IPv4-in-IPv6 tunnels described in
298 tunnels mechanism. Also enable support for advanced local
327 tunnels mechanism.
/kernel/linux/linux-5.10/net/mpls/
Dmpls_iptunnel.c3 * mpls tunnels An implementation mpls tunnels using the light weight tunnel
304 MODULE_DESCRIPTION("MultiProtocol Label Switching IP Tunnels");
/kernel/linux/linux-6.6/net/mpls/
Dmpls_iptunnel.c3 * mpls tunnels An implementation mpls tunnels using the light weight tunnel
304 MODULE_DESCRIPTION("MultiProtocol Label Switching IP Tunnels");
/kernel/linux/linux-5.10/Documentation/admin-guide/sysctl/
Dnet.rst324 Controls if fallback tunnels (like tunl0, gre0, gretap0, erspan0,
326 (a) value = 0; respective fallback tunnels are created when module is
328 (b) value = 1; [kcmd value: initns] respective fallback tunnels are
331 (c) value = 2; [kcmd value: none] fallback tunnels are not created
337 Not creating fallback tunnels gives control to userspace to create

12345678910