Home
last modified time | relevance | path

Searched refs:IP (Results 1 – 25 of 167) sorted by relevance

1234567

/Zephyr-Core-3.5.0/subsys/net/l2/virtual/ipip/
DKconfig5 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.5.0/tests/net/lib/lwm2m/interop/
Ddocker-test.sh10 IP="--ip=192.0.2.2 --ip6=2001:db8::2"
13 start_configuration "$IP $FWD" || return $?
/Zephyr-Core-3.5.0/doc/connectivity/networking/api/
Dip_4_6.rst13 Miscellaneous defines and helper functions for IP addresses and IP protocols.
/Zephyr-Core-3.5.0/drivers/can/
DKconfig.mcan10 This driver supports the Bosch m_can IP. This IP is built into the
/Zephyr-Core-3.5.0/doc/connectivity/networking/
Dusbnet_setup.rst23 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
Darmfvp_user_networking_setup.rst16 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).
Dnetwork_monitoring.rst32 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 …]
Dnetworking_with_host.rst26 * 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.5.0/boards/arm/ip_k66f/doc/
Dindex.rst3 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.5.0/tests/boards/altera_max10/i2c_master/
DREADME.txt2 Altera Nios-II I2C master soft IP core.
/Zephyr-Core-3.5.0/tests/boards/altera_max10/qspi/
DREADME.txt2 Altera Nios-II QSPI flash soft IP core.
/Zephyr-Core-3.5.0/tests/boards/altera_max10/sysid/
DREADME.txt2 Altera Nios-II System ID soft IP core.
/Zephyr-Core-3.5.0/tests/boards/altera_max10/msgdma/
DREADME.txt2 Altera Nios-II Modular Scatter Gather DMA (MSGDMA) soft IP core.
/Zephyr-Core-3.5.0/drivers/wifi/esp_at/
DKconfig.esp_at102 prompt "ESP IP Address configuration"
105 Choose whether to use an IP assigned by DHCP Server or
106 configure a static IP Address.
111 Use DHCP to get an IP Address.
116 Setup Static IP Address.
123 string "ESP Station mode IP Address"
/Zephyr-Core-3.5.0/drivers/ethernet/
DKconfig.enc424j60032 int "IP buffer timeout"
36 that the driver will wait from the IP stack to get
DKconfig.w550033 int "IP buffer timeout"
38 that the driver will wait from the IP stack to get
/Zephyr-Core-3.5.0/subsys/net/l2/wifi/
DKconfig32 bool "Check IP Assignment for TWT"
35 This option enables check for valid IP address before TWT setup.
37 enter deep sleep without having a valid IP, this can result in device
38 being unreachable (IP Level) or unable to receive down link traffic
40 interface has a valid IP address might be desirable in most scenarios.
/Zephyr-Core-3.5.0/boards/riscv/niosv_g/doc/
Dindex.rst9 …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.5.0/boards/riscv/niosv_m/doc/
Dindex.rst9 …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.5.0/boards/arm/ip_k66f/
DKconfig.board5 bool "Segger IP-K66F"
/Zephyr-Core-3.5.0/scripts/net/
DREADME.txt49 by the script, as well as Zephyr using native_posix 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.5.0/samples/arch/smp/pktqueue/
DREADME.rst10 (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.5.0/drivers/mdio/
DKconfig.sam1 # Copyright (c) 2021 IP-Logix Inc.
/Zephyr-Core-3.5.0/subsys/net/pkt_filter/
DKconfig21 rules on the IP packet.
28 rules on the IP packet.
/Zephyr-Core-3.5.0/samples/net/dns_resolve/
DREADME.rst5 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

1234567