Searched refs:IP (Results 1 – 25 of 183) sorted by relevance
12345678
| /Zephyr-Core-3.7.0/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-Core-3.7.0/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-Core-3.7.0/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-Core-3.7.0/doc/connectivity/networking/api/ |
| D | ip_4_6.rst | 13 Miscellaneous defines and helper functions for IP addresses and IP protocols.
|
| /Zephyr-Core-3.7.0/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 | 32 The ``net-tools`` project provides a configure file to setup IP-to-IP tunnel
65 [20210408Z14:33:08.959589] Ether / IP / ICMP 192.0.2.1 > 192.0.2.2 echo-request 0 / Raw
66 [20210408Z14:33:08.976178] Ether / IP / ICMP 192.0.2.2 > 192.0.2.1 echo-reply 0 / Raw
99 The IP address above is the inner tunnel endpoint, and can be changed and
101 containing the captured network packets to the configured IP tunnel, so we
140 <remote> is the (outer) endpoint IP address
141 <local> is the (inner) local IP address
142 <peer> is the (inner) peer IP address
143 Local and Peer IP addresses can have UDP port number in them (optional)
155 The ``2001:db8:200::1`` tells the local IP address for the tunnel,
[all …]
|
| D | networking_with_host.rst | 26 * Here IP packets are exchanged between Zephyr and the host system via serial
32 * Here IP packets are exchanged between Zephyr and the host system via QEMU's
39 * QEMU User Networking is implemented using "slirp", which provides a full TCP/IP
48 * User mode networking emulates a built-in IP router and DHCP server, and
51 the use of a significant number of IP network services without requiring
|
| /Zephyr-Core-3.7.0/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-Core-3.7.0/boards/segger/ip_k66f/doc/ |
| D | index.rst | 3 SEGGER IP Switch Board
9 The Segger IP Switch Board is a Evaluation board based on NXP Kinetis K66 MCU.
18 :alt: IP-K66F
30 For more information about the K66F SoC and IP-K66F board:
35 - `IP-K66F Website`_
36 - `IP-K66F User Guide`_
37 - `IP-K66F Schematics`_
|
| /Zephyr-Core-3.7.0/tests/boards/altera_max10/qspi/ |
| D | README.txt | 2 Altera Nios-II QSPI flash soft IP core.
|
| /Zephyr-Core-3.7.0/tests/boards/altera_max10/sysid/ |
| D | README.txt | 2 Altera Nios-II System ID soft IP core.
|
| /Zephyr-Core-3.7.0/tests/boards/altera_max10/i2c_master/ |
| D | README.txt | 2 Altera Nios-II I2C master soft IP core.
|
| /Zephyr-Core-3.7.0/tests/boards/altera_max10/msgdma/ |
| D | README.txt | 2 Altera Nios-II Modular Scatter Gather DMA (MSGDMA) soft IP core.
|
| /Zephyr-Core-3.7.0/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-Core-3.7.0/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-Core-3.7.0/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-Core-3.7.0/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-Core-3.7.0/scripts/net/ |
| D | README.txt | 49 by the script, as well as Zephyr using native_sim board. IP addresses are
51 The default IP addresses are:
57 The default IP addresses are used by echo_client and mqtt_publisher, but
58 with the echo_server the IP addresses are switched between Zephyr and Docker
60 the echo_server application uses those ending in .2. The script does the IP
|
| /Zephyr-Core-3.7.0/drivers/can/ |
| D | Kconfig.mcan | 9 Enable the Bosch M_CAN CAN IP module driver backend.
|
| /Zephyr-Core-3.7.0/samples/arch/smp/pktqueue/ |
| D | README.rst | 10 (essentially checksum calculation from IP Header Validation) of the Internet protocol
11 suite specified in RFC1812 "Requirements for IP Version 4 Routers" which
14 IP router system.
78 Simulating IP header validation on multiple cores.
|
| /Zephyr-Core-3.7.0/drivers/mdio/ |
| D | Kconfig.sam | 1 # Copyright (c) 2021 IP-Logix Inc.
|
| /Zephyr-Core-3.7.0/subsys/net/pkt_filter/ |
| D | Kconfig | 21 rules on the IP packet.
28 rules on the IP packet.
|
| /Zephyr-Core-3.7.0/samples/net/dns_resolve/ |
| D | README.rst | 5 Resolve an IP address for a given hostname.
10 This application will setup IP address for the device, and then
46 In this sample application, both static or DHCPv4 IP addresses are supported.
47 Static IP addresses are specified in the project configuration file,
75 instance, if using the usual IP addresses assigned to testing, update them
|
12345678
