Searched full:tunnel (Results 1 – 25 of 38) sorted by relevance
12
| /Documentation/networking/ |
| D | l2tp.rst | 27 An L2TP tunnel carries one or more L2TP sessions. Each tunnel is
30 to/from L2TP. Fields in the L2TP header identify the tunnel or session
40 1) Create a tunnel socket. Exchange L2TP control protocol messages
41 with the peer over that socket in order to establish a tunnel.
43 2) Create a tunnel context in the kernel, using information
47 tunnel socket in order to establish a session.
57 Tunnel Sockets
62 To create a tunnel socket for use by L2TP, the standard POSIX
65 For example, for a tunnel using IPv4 addresses and UDP encapsulation::
69 Or for a tunnel using IPv6 addresses and IP encapsulation::
[all …]
|
| D | bareudp.rst | 11 The Bareudp tunnel module provides a generic L3 encapsulation support for
12 tunnelling different L3 protocols like MPLS, IP, NSH etc. inside a UDP tunnel.
30 This creates a bareudp tunnel device which tunnels L3 traffic with ethertype
44 For an IPv4 tunnel the multiproto mode allows the tunnel to also handle
49 For MPLS, the multiproto mode allows the tunnel to handle both unicast
55 The OVS or TC flower layer must set the tunnel information in SKB dst field before
57 bareudp device extracts and stores the tunnel information in SKB dst field before
|
| D | gtp.rst | 12 of a GTP tunnel endpoint.
17 GTP is the Generic Tunnel Protocol, which is a 3GPP protocol used for
24 such a tunnel between that external data network and the phone. The
25 tunnel endpoints thus reside on the phone and in the gateway. All
35 is translated into GTP *without breaking the end-to-end tunnel*. So
39 or P-GW (LTE), which terminates the tunnel, decapsulates the packet
53 The module implements the function of a tunnel endpoint, i.e. it is
70 to handle the tunnel establishment, authentication etc. and only the
159 Local GTP-U entity and tunnel identification
166 instance) per IP address. Tunnel Endpoint Identifier (TEID) are unique
[all …]
|
| D | segmentation-offloads.rst | 17 * IPIP, SIT, GRE, and UDP Tunnel Offloads
62 tunnel protocols is still supported.
65 IPIP, SIT, GRE, UDP Tunnel, and Remote Checksum Offloads
69 contain additional headers such as an outer tunnel. In order to account
78 refer to the tunnel headers as the outer headers, while the encapsulated
82 IPIP/SIT Tunnel::
89 UDP/GRE Tunnel::
96 In addition to the above tunnel types there are also SKB_GSO_GRE_CSUM and
97 SKB_GSO_UDP_TUNNEL_CSUM. These two additional tunnel types reflect the
101 Finally there is SKB_GSO_TUNNEL_REMCSUM which indicates that a given tunnel
[all …]
|
| D | vxlan.rst | 13 destination port. This document describes the Linux kernel tunnel
62 The following NIC features may indicate support for UDP tunnel-related
79 Tunnel information for eth0:
|
| D | ip_dynaddr.rst | 17 received by the tunnel.
|
| D | nf_conntrack-sysctl.rst | 217 If this option is enabled, the lightweight tunnel netfilter hooks are
|
| D | representors.rst | 216 Tunnel encapsulation and decapsulation are rather more complicated, as they
217 involve a third netdevice (a tunnel netdev operating in metadata mode, such as
|
| D | checksum-offloads.rst | 141 most tunnel types have flags controlling its use. For instance, VXLAN has the
|
| D | phonet.rst | 69 The virtual TUN tunnel device driver can also be used for Phonet. This
|
| /Documentation/devicetree/bindings/i2c/ |
| D | google,cros-ec-i2c-tunnel.yaml | 5 $id: http://devicetree.org/schemas/i2c/google,cros-ec-i2c-tunnel.yaml#
18 those devices we need to tunnel our i2c commands through the EC.
28 const: google,cros-ec-i2c-tunnel
52 i2c-tunnel {
53 compatible = "google,cros-ec-i2c-tunnel";
|
| /Documentation/devicetree/bindings/display/bridge/ |
| D | google,cros-ec-anx7688.yaml | 17 the EC and therefore its node should be a child of an EC I2C tunnel node
18 (See google,cros-ec-i2c-tunnel.yaml).
54 compatible = "google,cros-ec-i2c-tunnel";
|
| /Documentation/netlink/specs/ |
| D | ethtool.yaml | 11 name: udp-tunnel-type
763 name: tunnel-udp-entry
772 enum: udp-tunnel-type
774 name: tunnel-udp-table
787 nested-attributes: tunnel-udp-entry
789 name: tunnel-udp
794 nested-attributes: tunnel-udp-table
796 name: tunnel-info
805 nested-attributes: tunnel-udp
1632 name: tunnel-info-get
[all …]
|
| D | ovs_flow.yaml | 342 MPLS tunnel attributes.
531 name: tunnel
533 nested-attributes: tunnel-key-attrs
593 name: tunnel-info
724 start of the l3 header depending on the value of l3 tunnel flag in the
737 name: tunnel-key-attrs
738 enum-name: ovs-tunnel-key-attr
739 name-prefix: ovs-tunnel-key-attr-
|
| D | fou.yaml | 123 doc: Get tunnel info.
|
| D | ovs_vport.yaml | 59 name-prefix: ovs-tunnel-attr-
|
| D | rt_route.yaml | 155 type: binary # tunnel specific nest
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | maxim,max96717.yaml | 19 interconnects. The device cans operate in pixel or tunnel mode. In pixel mode
20 the MAX96717 can select the MIPI datatype, while the tunnel mode forward all the MIPI
|
| D | maxim,max96714.yaml | 19 interconnects. The device cans operate in pixel or tunnel mode. In pixel mode
20 the MAX96714 can select individual video stream, while the tunnel mode forward all
|
| /Documentation/devicetree/bindings/mfd/ |
| D | google,cros-ec.yaml | 157 "^i2c-tunnel[0-9]*$":
159 $ref: /schemas/i2c/google,cros-ec-i2c-tunnel.yaml#
229 "^i2c-tunnel[0-9]*$": false
|
| /Documentation/networking/device_drivers/ethernet/chelsio/ |
| D | cxgb.rst | 304 on an AMD Opteron system with HyperTransport PCI-X Tunnel chipset.
306 If your AMD Opteron system uses the AMD-8131 HyperTransport PCI-X Tunnel
311 AMD states, "Under highly specific conditions, the AMD-8131 PCI-X Tunnel
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-thunderbolt | 30 de-authorize PCIe tunnel by writing 0 to authorized
55 dponly Automatically tunnel Display port (and USB). No
57 usbonly Automatically tunnel USB controller of the
|
| /Documentation/networking/device_drivers/ethernet/intel/ |
| D | iavf.rst | 207 - Tunnel filters are not supported in ADq. If encapsulated packets do arrive
208 in non-tunnel mode, filtering will be done on the inner headers. For example,
209 for VXLAN traffic in non-tunnel mode, PCTYPE is identified as a VXLAN
|
| /Documentation/virt/uml/ |
| D | user_mode_linux_howto_v2.rst | 255 to be part of the group associated with the tunnel device.
430 ``GREIRB``) tunnel which will connect the UML instance to a ``GRE``
453 multiplex connections as each GRE tunnel is terminated directly on
458 ensure that the tunnel is not misconfigured.
491 This will configure an Ethernet over L2TPv3 fixed tunnel which will
501 As the tunnel is fixed these are not negotiated and they are
527 no way to multiplex connections as each L2TPv3 tunnel is terminated
542 pre-up ip l2tp add tunnel remote 127.0.0.1 \
548 ip l2tp del tunnel tunnel_id 2
|
| /Documentation/admin-guide/ |
| D | thunderbolt.rst | 171 When a device is de-authorized the PCIe tunnel from the parent device
304 It is possible to tunnel any kind of traffic over a Thunderbolt link but
|
12