Searched refs:IP (Results 1 – 25 of 209) sorted by relevance
123456789
| /Zephyr-latest/subsys/net/l2/virtual/ipip/ |
| D | Kconfig | 5 bool "IP-to-IP tunneling support"
8 Add a IP-to-IP tunnel driver. If this is enabled, then a network
12 Also application needs to setup IP addresses etc. to the IP-to-IP
25 module-str = Log level for IP-to-IP tunnel
26 module-help = Enables IP-to-IP driver to output debug messages.
|
| /Zephyr-latest/doc/connectivity/usb/host/ |
| D | usbip.rst | 3 USB/IP protocol support
9 New USB support includes initial support for the USB/IP protocol. It is still
13 USB/IP uses TCP/IP. Both of the underlying connectivity stacks, USB and
17 In the USB/IP protocol, a server exports the USB devices and a client imports
18 them. USB/IP support in the Zephyr RTOS implements server functionality and
21 USB/IP protocol is described in `USB/IP protocol documentation`_.
23 To use USB/IP support, make sure the required modules are loaded on the client side.
62 USB/IP with native_sim
65 The preferred method to develop with USB/IP support enabled is to use
67 USB/IP requires a network connection, see :ref:`networking_with_native_sim`
[all …]
|
| /Zephyr-latest/tests/net/lib/lwm2m/interop/ |
| D | docker-test.sh | 10 IP="--ip=192.0.2.2 --ip6=2001:db8::2"
13 start_configuration "$IP $FWD" || return $?
|
| /Zephyr-latest/samples/net/lwm2m_client/ |
| D | docker-test.sh | 10 IP="--ip=192.0.2.2 --ip6=2001:db8::2"
13 start_configuration "$IP $FWD" || return $?
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | ip_4_6.rst | 13 Miscellaneous defines and helper functions for IP addresses and IP protocols.
|
| /Zephyr-latest/snippets/usbip-native-sim/ |
| D | README.rst | 3 USB/IP on Native Simulator Snippet (usbip-native-sim)
13 This snippet allows to configure USB device samples with USB/IP support on a
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | usbnet_setup.rst | 23 interface, we need to assign IP addresses and set up a routing table for
36 We need to set it up and assign IP addresses as explained in the following
39 Choosing IP addresses
42 To establish network connection to the board we need to choose IP address
46 application. IP addresses usually set in the project configuration files
70 Next step is to assign IP addresses to the new Linux host interface, in
95 From the host we can test the connection by pinging Zephyr IP address of
|
| D | armfvp_user_networking_setup.rst | 16 User mode networking emulates a built-in IP router and DHCP server, and routes
19 a significant number of IP network services without requiring administrative
25 allowing it to be automatically assigned with an IP address ``172.20.51.1``.
41 * You can use TCP and UDP over IP, but not ICMP (ping).
|
| D | network_monitoring.rst | 34 The ``net-tools`` project provides a configure file to setup IP-to-IP tunnel
67 [20210408Z14:33:08.959589] Ether / IP / ICMP 192.0.2.1 > 192.0.2.2 echo-request 0 / Raw
68 [20210408Z14:33:08.976178] Ether / IP / ICMP 192.0.2.2 > 192.0.2.1 echo-reply 0 / Raw
101 The IP address above is the inner tunnel endpoint, and can be changed and
103 containing the captured network packets to the configured IP tunnel, so we
144 <remote> is the (outer) endpoint IP address
145 <local> is the (inner) local IP address
146 <peer> is the (inner) peer IP address
147 Local and Peer IP addresses can have UDP port number in them (optional)
159 The ``2001:db8:200::1`` tells the local IP address for the tunnel,
[all …]
|
| /Zephyr-latest/samples/net/secure_mqtt_sensor_actuator/ |
| D | README.rst | 37 without security, using a static IP address.
69 - Default config: Secure MQTT, dynamic IP address (DHCP)
72 - Secure MQTT, static IP address
75 - Unsecure MQTT, static IP address
79 Using the default config, the application will use DHCP to acquire an IP address and attempt
97 local broker hostname/IP address.
103 - A DHCP server can be installed on the host PC to handle assigning an IP to the board
113 **Static IP Config:**
116 a static IP address config.
117 The device, gateway, and DNS server IP addresses should be set according to
[all …]
|
| /Zephyr-latest/samples/net/mqtt_sn_publisher/ |
| D | Kconfig | 12 string "IP of the MQTT-SN gateway. Only used if NET_SAMPLE_MQTT_SN_STATIC_GATEWAY=n."
19 string "IP of the Broadcast address"
|
| /Zephyr-latest/subsys/net/ |
| D | Kconfig | 9 bool "Link layer and networking (including IP)"
15 and is the basis for higher level protocols (e.g. IP protocols).
|
| /Zephyr-latest/tests/boards/altera_max10/i2c_master/ |
| D | README.txt | 2 Altera Nios-II I2C master soft IP core.
|
| /Zephyr-latest/tests/boards/altera_max10/qspi/ |
| D | README.txt | 2 Altera Nios-II QSPI flash soft IP core.
|
| /Zephyr-latest/tests/boards/altera_max10/sysid/ |
| D | README.txt | 2 Altera Nios-II System ID soft IP core.
|
| /Zephyr-latest/include/zephyr/dt-bindings/clock/ |
| D | renesas_rzg_clock.h | 55 #define RZ_CLOCK(IP, ch, clk, div) \ argument
56 ((RZ_IP_##IP << RZ_IP_SHIFT) | ((ch) << RZ_IP_CH_SHIFT) | ((clk) << RZ_CLOCK_SHIFT) | \
|
| /Zephyr-latest/tests/boards/altera_max10/msgdma/ |
| D | README.txt | 2 Altera Nios-II Modular Scatter Gather DMA (MSGDMA) soft IP core.
|
| /Zephyr-latest/drivers/ethernet/ |
| D | Kconfig.enc424j600 | 32 int "IP buffer timeout"
36 that the driver will wait from the IP stack to get
|
| D | Kconfig.w5500 | 33 int "IP buffer timeout"
38 that the driver will wait from the IP stack to get
|
| /Zephyr-latest/drivers/wifi/esp_at/ |
| D | Kconfig.esp_at | 103 prompt "ESP IP Address configuration"
106 Choose whether to use an IP assigned by DHCP Server or
107 configure a static IP Address.
112 Use DHCP to get an IP Address.
117 Setup Static IP Address.
124 string "ESP Station mode IP Address"
|
| /Zephyr-latest/boards/intel/niosv_g/doc/ |
| D | index.rst | 9 …V/g Hello World Example Design system and this complete system is consisted of following IP blocks:
13 Nios® V/g Processor Intel® FPGA IP
14 JTAG UART Intel® FPGA IP
15 On-Chip Memory Intel® FPGA IP
|
| /Zephyr-latest/boards/intel/niosv_m/doc/ |
| D | index.rst | 9 …V/m Hello World Example Design system and this complete system is consisted of following IP blocks:
13 Nios® V/m Processor Intel® FPGA IP
14 JTAG UART Intel® FPGA IP
15 On-Chip Memory Intel® FPGA IP
|
| /Zephyr-latest/drivers/can/ |
| D | Kconfig.mcan | 9 Enable the Bosch M_CAN CAN IP module driver backend.
|
| /Zephyr-latest/drivers/dma/ |
| D | Kconfig.nxp_sdma | 9 Enable driver for NXP's SDMA IP.
|
| /Zephyr-latest/drivers/ethernet/dwc_xgmac/ |
| D | Kconfig | 50 Number hardware queues supported by the XGMAC IP
56 Enable receive checksum offload for TCP/UDP/IP packets
62 Enable transmit checksum offload for TCP/UDP/IP packets
|
123456789
