Searched full:ip (Results 1 – 25 of 418) sorted by relevance
12345678910>>...17
| /Documentation/networking/dsa/ |
| D | configuration.rst | 87 ip addr add 192.0.2.1/30 dev lan1
88 ip addr add 192.0.2.5/30 dev lan2
89 ip addr add 192.0.2.9/30 dev lan3
92 ip link set eth0 up
95 ip link set lan1 up
96 ip link set lan2 up
97 ip link set lan3 up
105 ip link set eth0 up
108 ip link set lan1 up
109 ip link set lan2 up
[all …]
|
| D | b53.rst | 67 ip link add link eth0 name eth0.1 type vlan id 1
68 ip link add link eth0 name eth0.2 type vlan id 2
69 ip link add link eth0 name eth0.3 type vlan id 3
72 ip link set eth0 up
73 ip link set eth0.1 up
74 ip link set eth0.2 up
75 ip link set eth0.3 up
78 ip link set wan up
79 ip link set lan1 up
80 ip link set lan2 up
[all …]
|
| /Documentation/networking/ |
| D | ipddp.txt | 2 AppleTalk-IP Decapsulation and AppleTalk-IP Encapsulation
9 AppleTalk-IP (IPDDP) is the method computers connected to AppleTalk
10 networks can use to communicate via IP. AppleTalk-IP is simply IP datagrams
14 IP over an AppleTalk network or you can provide IP gatewaying functions
17 You can currently encapsulate or decapsulate AppleTalk-IP on LocalTalk,
23 Compiling AppleTalk-IP Decapsulation/Encapsulation
26 AppleTalk-IP decapsulation needs to be compiled into your kernel. You
27 will need to turn on AppleTalk-IP driver support. Then you will need to
28 select ONE of the two options; IP to AppleTalk-IP encapsulation support or
29 AppleTalk-IP to IP decapsulation support. If you compile the driver
[all …]
|
| D | ipvlan.txt | 23 using IProute2/ip utility.
25 ip link add link <master> name <slave> type ipvlan [ mode MODE ] [ FLAGS ]
33 bash# ip link add link eth0 name ipvl0 type ipvlan
35 bash# ip link add link eth0 name ipvl0 type ipvlan mode l2 bridge
37 bash# ip link add link eth0 name ipvlan type ipvlan mode l2 private
39 bash# ip link add link eth0 name ipvlan type ipvlan mode l2 vepa
121 ip netns add ns0
122 ip netns add ns1
125 ip link add link eth0 ipvl0 type ipvlan mode l2
126 ip link add link eth0 ipvl1 type ipvlan mode l2
[all …]
|
| D | vrf.txt | 3 The VRF device combined with ip rules provides the ability to create virtual
14 the use of higher priority ip rules (Policy Based Routing, PBR) to take
60 e.g, ip link add vrf-blue type vrf table 10
61 ip link set dev vrf-blue up
70 ip ru add oif vrf-blue table 10
71 ip ru add iif vrf-blue table 10
74 ip route add table 10 unreachable default metric 4278198272
82 ip link set dev eth1 master vrf-blue
94 ip route add table 10 ...
144 $ ip link add dev NAME type vrf table ID
[all …]
|
| D | gtp.txt | 12 tunneling User-IP payload between a mobile station (phone, modem)
23 technology-dependent protocol stack for transmitting the user IP
35 public internet, but can also be any private IP network (or even
36 theoretically some non-IP network like X.25).
47 able to decapsulate tunneled IP packets in the uplink originated by
48 the phone, and encapsulate raw IP packets received from the external
51 It *only* implements the so-called 'user plane', carrying the User-IP
111 on the inner (user) IP layer, or on the outer (transport) layer.
114 the User IP payload, nor for the outer IP layer. Patches or other
150 instance) per IP address. Tunnel Endpoint Identifier (TEID) are unique
[all …]
|
| D | ipsec.txt | 5 1. IPcomp: Small IP packet won't get compressed at sender, and failed on
13 payload, the IP datagram MUST be sent in the original non-compressed
14 form. To clarify: If an IP datagram is sent non-compressed, no
17 the decompression processing cycles and avoiding incurring IP
21 Small IP datagrams are likely to expand as a result of compression.
23 where IP datagrams of size smaller than the threshold are sent in the
|
| D | batman-adv.rst | 8 operate on the IP basis. Unlike the batman daemon, which exchanges information
31 iproute2 tool ``ip``::
33 $ ip link add name bat0 type batadv
37 $ ip link set dev eth0 master bat0
44 $ ip link set dev eth0 nomaster
90 IP address which can be either statically configured or dynamically (by using
93 NodeA: ip link set up dev bat0
94 NodeA: ip addr add 192.168.0.1/24 dev bat0
96 NodeB: ip link set up dev bat0
97 NodeB: ip addr add 192.168.0.2/24 dev bat0
[all …]
|
| D | l2tp.txt | 3 more sessions over an IP tunnel. It is commonly used for VPNs
4 (L2TP/IPSec) and by ISPs to tunnel subscriber PPP sessions over an IP
14 L2TPv3 IP encapsulation.
29 change for L2TPv3 is that it can be carried directly over IP with no
50 provides L2TPv3 IP encapsulation (no UDP) and is implemented using a
70 such as "ip" and "ifconfig". If only IP frames are passed over the
71 tunnel, the interface can be given an IP addresses of itself and its
72 peer. If non-IP frames are to be passed over the tunnel, the interface
79 present in data frames - it is inferred from the IP connection on
166 request. The "ip" utility of iproute2 has commands for managing static
[all …]
|
| D | cdc_mbim.txt | 50 Establishing a MBIM IP session reequires at least these actions by the
55 - configure IP interface
163 mapped to MBIM IP session 0.
166 Multiplexed IP sessions (IPS)
168 MBIM allows multiplexing up to 256 IP sessions over a single USB data
169 channel. The cdc_mbim driver models such IP sessions as 802.1q VLAN
170 subdevices of the master wwanY device, mapping MBIM IP session Z to
177 VLAN links prior to establishing MBIM IP sessions where the SessionId
181 For example, adding a link for a MBIM IP session with SessionId 3:
183 ip link add link wwan0 name wwan0.3 type vlan id 3
[all …]
|
| /Documentation/filesystems/nfs/ |
| D | nfsroot.txt | 53 nfsroot=[<server-ip>:]<root-dir>[,<nfs-options>]
58 <server-ip> Specifies the IP address of the NFS server.
59 The default address is determined by the `ip' parameter
61 servers for IP autoconfiguration and NFS.
66 IP address.
82 ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>:
83 <dns0-ip>:<dns1-ip>:<ntp0-ip>
85 This parameter tells the kernel how to configure IP addresses of devices
86 and also how to set up the IP routing table. It was originally called
87 `nfsaddrs', but now the boot-time IP configuration works independently of
[all …]
|
| /Documentation/devicetree/bindings/mmc/ |
| D | renesas,sdhi.txt | 5 "renesas,sdhi-sh73a0" - SDHI IP on SH73A0 SoC
6 "renesas,sdhi-r7s72100" - SDHI IP on R7S72100 SoC
7 "renesas,sdhi-r7s9210" - SDHI IP on R7S9210 SoC
8 "renesas,sdhi-r8a73a4" - SDHI IP on R8A73A4 SoC
9 "renesas,sdhi-r8a7740" - SDHI IP on R8A7740 SoC
10 "renesas,sdhi-r8a7743" - SDHI IP on R8A7743 SoC
11 "renesas,sdhi-r8a7744" - SDHI IP on R8A7744 SoC
12 "renesas,sdhi-r8a7745" - SDHI IP on R8A7745 SoC
13 "renesas,sdhi-r8a774a1" - SDHI IP on R8A774A1 SoC
14 "renesas,sdhi-r8a774c0" - SDHI IP on R8A774C0 SoC
[all …]
|
| /Documentation/devicetree/bindings/sifive/ |
| D | sifive-blocks-ip-versioning.txt | 1 DT compatible string versioning for SiFive open-source IP blocks
4 strings for open-source SiFive IP blocks. HDL for these IP blocks
9 IP block-specific DT compatible strings are contained within the HDL,
10 in the form "sifive,<ip-block-name><integer version number>".
16 Until these IP blocks (or IP integration) support version
17 auto-discovery, the maintainers of these IP blocks intend to increment
19 interface to these IP blocks changes, or when the functionality of the
20 underlying IP blocks changes in a way that software should be aware of.
26 match on these IP block-specific compatible strings.
33 IP block-specific compatible string (such as "sifive,uart0") should
|
| /Documentation/devicetree/bindings/media/xilinx/ |
| D | video.txt | 1 DT bindings for Xilinx video IP cores
4 Xilinx video IP cores process video streams by acting as video sinks and/or
8 Each video IP core is represented by an AMBA bus child node in the device
9 tree using bindings documented in this directory. Connections between the IP
18 The following properties are common to all Xilinx video IP cores.
21 AXI bus between video IP cores, using its VF code as defined in "AXI4-Stream
22 Video IP and System Design Guide" [UG934]. How the format relates to the IP
23 core is described in the IP core bindings documentation.
|
| D | xlnx,video.txt | 1 Xilinx Video IP Pipeline (VIPP)
7 Xilinx video IP pipeline processes video streams through one or more Xilinx
8 video IP cores. Each video IP core is represented as documented in video.txt
9 and IP core specific documentation, xlnx,v-*.txt, in this directory. The DT
11 mappings between DMAs and the video IP cores.
|
| /Documentation/networking/device_drivers/qualcomm/ |
| D | rmnet.txt | 8 IP mode. Physical transports include USB, HSIC, PCIe and IP accelerator.
12 multimedia messaging service (MMS) or IP media subsystem (IMS). Hardware sends
24 MAP header has the same endianness of the IP packet.
35 packets are standard IP packets.
70 packets and either ACK the MAP command or deliver the IP packet to the
73 MAP header|IP Packet|Optional padding|MAP header|IP Packet|Optional padding....
74 MAP header|IP Packet|Optional padding|MAP header|Command Packet|Optional pad...
|
| /Documentation/devicetree/bindings/clock/ti/ |
| D | dra7-atl.txt | 3 The ATL IP is used to generate clock to be used to synchronize baseband and
4 audio codec. A single ATL IP provides four ATL clock instances sharing the same
16 Since the clock instances are part of a single IP this binding is used as a node
17 for the DT clock tree, the IP driver is needed to handle the actual configuration
18 of the IP.
27 Binding for the IP driver:
28 This binding is used to configure the IP driver which is going to handle the
29 configuration of the IP for the ATL clock instances.
33 - reg : base address for the ATL IP
75 /* binding for the IP */
|
| /Documentation/devicetree/bindings/gpu/ |
| D | samsung-rotator.txt | 5 * "samsung,s5pv210-rotator" for Rotator IP in S5PV210
6 * "samsung,exynos4210-rotator" for Rotator IP in Exynos4210
7 * "samsung,exynos4212-rotator" for Rotator IP in Exynos4212/4412
8 * "samsung,exynos5250-rotator" for Rotator IP in Exynos5250
10 - reg : Physical base address of the IP registers and length of memory
|
| D | samsung-g2d.txt | 5 (a) "samsung,s5pv210-g2d" for G2D IP present in S5PV210 & Exynos4210 SoC
6 (b) "samsung,exynos4212-g2d" for G2D IP present in Exynos4x12 SoCs
7 (c) "samsung,exynos5250-g2d" for G2D IP present in Exynos5250 SoC
9 - reg : Physical base address of the IP registers and length of memory
|
| /Documentation/devicetree/bindings/fpga/ |
| D | altera-pr-ip.txt | 1 Altera Arria10 Partial Reconfiguration IP
4 - compatible : should contain "altr,a10-pr-ip"
10 compatible = "altr,a10-pr-ip";
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-ocores.txt | 7 For Opencore based I2C IP block reimplemented in
8 FU540-C000 SoC. Please refer to sifive-blocks-ip-versioning.txt
12 Mutually exclusive with opencores,ip-clock-frequency
13 - opencores,ip-clock-frequency: frequency of the controller clock in Hz;
30 - if clock-frequency is present and neither opencores,ip-clock-frequency nor
36 - if opencores,ip-clock-frequency is present it specifies i2c controller
47 opencores,ip-clock-frequency = <20000000>;
|
| /Documentation/devicetree/bindings/media/ |
| D | allegro.txt | 1 Device-tree bindings for the Allegro DVT video IP codecs present in the Xilinx
2 ZynqMP SoC. The IP core may either be a H.264/H.265 encoder or H.264/H.265
3 decoder ip core.
11 "allegro,al5e-1.1", "allegro,al5e": encoder IP core
12 "allegro,al5d-1.1", "allegro,al5d": decoder IP core
|
| /Documentation/netlabel/ |
| D | cipso_ipv4.rst | 13 IP Security Option (CIPSO) draft from July 16, 1992. A copy of this
22 The CIPSO/IPv4 protocol engine applies the CIPSO IP option to packets by
24 system through the socket to have the CIPSO IP option applied. The socket's
28 configured to use CIPSO for packet labeling then a CIPSO IP option will be
34 The CIPSO/IPv4 protocol engine validates every CIPSO IP option it finds at the
35 IP layer without any special handling required by the LSM. However, in order
|
| /Documentation/networking/device_drivers/freescale/ |
| D | gianfar.txt | 10 the 8548) has the ability to perform TCP, UDP, and IP checksums
13 the driver only supports checksumming for TCP/IP and UDP/IP
35 to align the IP header to a 16-byte boundary, when supported by
|
| /Documentation/devicetree/bindings/ |
| D | xilinx.txt | 1 d) Xilinx IP cores
3 The Xilinx EDK toolchain ships with a set of IP cores (devices) for use
10 Each IP-core has a set of parameters which the FPGA designer can use to
14 device drivers how the IP cores are configured, but it requires the kernel
20 properties of the device node. In general, device nodes for IP-cores
24 compatible = "xlnx,(ip-core-name)-(HW_VER)"
36 (ip-core-name): the name of the ip block (given after the BEGIN
48 Typically, the compatible list will include the exact IP core version
49 followed by an older IP core version which implements the same
89 Some IP cores actually implement 2 or more logical devices. In
[all …]
|
12345678910>>...17