michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/subsys/net/lib/Kconfig

53 lines
949 B
Plaintext
Raw Permalink Normal View History

lib: Introduce the CoAP implementation for Zephyr This is a CoAP implementation tailored for Zephyr's requirements, it tries to use memory predictably by exposing its control structures to the user (so the user only pays for the features that are used) and having a lightweight packet representation (the trade-off is that adding options is not as efficient as it could be, if there were more information available). Change-Id: I6f74146c4626a0c554f50b42f163a076e82805ba Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
2016-08-03 20:23:32 +02:00
# Copyright (c) 2016 Intel Corporation
license: Replace Apache boilerplate with SPDX tag Replace the existing Apache 2.0 boilerplate header with an SPDX tag throughout the zephyr code tree. This patch was generated via a script run over the master branch. Also updated doc/porting/application.rst that had a dependency on line numbers in a literal include. Manually updated subsys/logging/sys_log.c that had a malformed header in the original file. Also cleanup several cases that already had a SPDX tag and we either got a duplicate or missed updating. Jira: ZEP-1457 Change-Id: I6131a1d4ee0e58f5b938300c2d2fc77d2e69572c Signed-off-by: David B. Kinder <david.b.kinder@intel.com> Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-01-19 02:01:01 +01:00
# SPDX-License-Identifier: Apache-2.0
lib: Introduce the CoAP implementation for Zephyr This is a CoAP implementation tailored for Zephyr's requirements, it tries to use memory predictably by exposing its control structures to the user (so the user only pays for the features that are used) and having a lightweight packet representation (the trade-off is that adding options is not as efficient as it could be, if there were more information available). Change-Id: I6f74146c4626a0c554f50b42f163a076e82805ba Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
2016-08-03 20:23:32 +02:00
net: Restructure network protocols This commit restructures the network protocols. Changes applied are: - Move lib/iot/ to subsys/net/lib - Move network protocol headers to include/net - Move lib/iot/zoap/link-format.h to include/net/zoap_link_format.h and link-format.c to zoap_link_format.c - Move tests/iot/ to tests/net/lib/ - Adapt sample code - Adapt build system - Modify doxygen paths Change-Id: I37085fa4cc76a8a8e19a499ecb4e87b451120349 Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2016-12-23 22:09:15 +01:00
menu "Network Protocols"
lib: Introduce the CoAP implementation for Zephyr This is a CoAP implementation tailored for Zephyr's requirements, it tries to use memory predictably by exposing its control structures to the user (so the user only pays for the features that are used) and having a lightweight packet representation (the trade-off is that adding options is not as efficient as it could be, if there were more information available). Change-Id: I6f74146c4626a0c554f50b42f163a076e82805ba Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
2016-08-03 20:23:32 +02:00
net: coap: Rename ZOAP library ZOAP library has certain limitations in parsing and preparation of coap messages. It can handle only on single network fragment. If network packet is split between multiple fragments it fails. This patch is just copy and rename of 'zoap' to 'coap'. Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
2017-08-28 11:19:32 +02:00
source "subsys/net/lib/coap/Kconfig"
net: Restructure network protocols This commit restructures the network protocols. Changes applied are: - Move lib/iot/ to subsys/net/lib - Move network protocol headers to include/net - Move lib/iot/zoap/link-format.h to include/net/zoap_link_format.h and link-format.c to zoap_link_format.c - Move tests/iot/ to tests/net/lib/ - Adapt sample code - Adapt build system - Modify doxygen paths Change-Id: I37085fa4cc76a8a8e19a499ecb4e87b451120349 Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2016-12-23 22:09:15 +01:00
source "subsys/net/lib/dns/Kconfig"
iot/dns: Add DNS Client support for Zephyr This commit adds support the DNS client API on top of the new native IP stack. Some features of this implementation are: - Support for IPv4 and IPv6 - Support for multiple concurrent queries. A net_buf structure is required per context. See the DNS_RESOLVER_ADDITIONAL_BUF_CTR configuration variable Origin: Original Jira: ZEP-793 Jira: ZEP-855 Jira: ZEP-975 Change-Id: I351a636462a1b78a412c9bce1ef3cd0fa6223a52 Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2016-10-06 07:07:48 +02:00
net: lib: mqtt: Get rid of _sock suffix As the legacy library has been removed, we no longer need to differentiate betwen MQTT implementations. Therefore align the library folder name with other libraries and remove the `_sock` suffix. Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
2019-02-05 12:36:31 +01:00
source "subsys/net/lib/mqtt/Kconfig"
net: mqtt: Add BSD socket implementation Add new, socket based MQTT implementation, based on MQTT from Nordic nRF5 SDK, introducing the following features: * transport independent MQTT logic, with support for multiple transports * support for multiple MQTT versions (3.1.0 and 3.1.1 supported) * single event handler - no need to keep callback array in RAM * automatic send of Ping Requests, for connection keep-alive * message/event parameters wrapped into strucutres - easier extension for future MQTT versions * no separate thread needed to run MQTT - application only needs to call mqtt_input and mqtt_live periodically Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
2018-06-27 10:41:51 +02:00
net: mqtt-sn: Add MQTT-SN library This commit adds an implementation of MQTT-SN v1.2. The specification is available on oasis-open.org: https://www.oasis-open.org/committees/download.php/66091/MQTT-SN_spec_v1.2.pdf The following things are missing in this implementation: - Pre-defined topic IDs - QoS -1 - it's most useful with predefined topics - Gateway discovery using ADVERTISE, SEARCHGW and GWINFO messages. - Setting the will topic and message after the initial connect - Forwarder Encapsulation Signed-off-by: René Beckmann <rene.beckmann@grandcentrix.net>
2022-10-30 15:09:30 +01:00
source "subsys/net/lib/mqtt_sn/Kconfig"
net: ptp: Initial PTP library implementation This is an initial commit that introduces PTP library in the Zephyr. It adds basic Kconfig symbols for enabling library, CMakeLists.txt for compiling it, public header file, and initial PTP thread definition and library initialization. Implementation of the functional PTP stack will be introduced in following commits. Signed-off-by: Adam Wojasinski <awojasinski@baylibre.com>
2024-05-19 12:31:44 +02:00
source "subsys/net/lib/ptp/Kconfig"
net: tftp: Adding support for TFTP Client. Adding RFC1350 compliant support for TFTP Client in Zephyr. The current implementation is minimal and only supports the ability to get a file from the server. Things for the future include support for putting files to server and adding support for RFC2347. Signed-off-by: Bilal Wasim <bilalwasim676@gmail.com>
2020-04-22 01:40:18 +02:00
source "subsys/net/lib/tftp/Kconfig"
net: Restructure network protocols This commit restructures the network protocols. Changes applied are: - Move lib/iot/ to subsys/net/lib - Move network protocol headers to include/net - Move lib/iot/zoap/link-format.h to include/net/zoap_link_format.h and link-format.c to zoap_link_format.c - Move tests/iot/ to tests/net/lib/ - Adapt sample code - Adapt build system - Modify doxygen paths Change-Id: I37085fa4cc76a8a8e19a499ecb4e87b451120349 Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2016-12-23 22:09:15 +01:00
source "subsys/net/lib/http/Kconfig"
iot: Add HTTP support for Zephyr This commit adds HTTP message handling support for Zephyr. So, no network routines are involved at this level. To add HTTP message handling support for Zephyr, we explored the following options: 1. Importing an external project and perhaps adapting it to fit our requirements. The criteria to pick one codebase among all the available projects are: licensing, correctness and performance. 2. Writing our own implementation from scratch. We decided to import an external project instead of implementing our own parser, mainly due to code maturity and correctness. It could take more time to obtain a production-ready parser from scratch than adapting a state-of-art library. The following is a list of some projects offering similar functionality. lighttpd (many files) * License: revised BSD license * Supported: active * Comments: this parser can't be integrated to Zephyr due to dependencies that currently are not satisficed by our SDK. nginx (src/http/ngx_http_parse.c) * License: 2-clause BSD-like * Supported: very active * Comments: this parser can't be integrated to Zephyr due to dependencies that currently are not satisficed by our SDK. wget (src/http-parse.c) * License: GPL 3.0 * Supported: very active * Comments: this code can't be included in Zephyr due to licensing issues curl (lib/http.c) * License: MIT/X derivate, see: https://curl.haxx.se/docs/copyright.html * Supported: very active * Comment: it must be forked and adapted to run in Zephyr. It is not optimized for low-power devices. nodejs http-parser (http_parser.c) * License: nginx license (2-clause BSD-like) and MIT license * Supported: very active * Comments: optimized with performance in mind. From https://github.com/nodejs/http-parser: "It does not make any syscalls nor allocations, it does not buffer data, it can be interrupted at anytime. It only requires about 40 bytes of data per message stream." So, nodejs/http-parser looks a very good choice for Zephyr. In this commit, we integrate nodejs' parser to Zephyr. Origin: https://github.com/nodejs/http-parser/releases/tag/v2.7.1 https://github.com/nodejs/http-parser/archive/v2.7.1.tar.gz NOTE: This patch reformats the http_parser files to reduce checkpatch warnings. Changes made in this refactoring are available at: Repo: https://gitlab.com/santes/http_parser/commits/refactoring1 Commit: 9ccfaa23f1c8438855211fa902ec8e7236b702b1 Jira: ZEP-346 Jira: ZEP-776 Change-Id: I29b1d47f323a5841cd4d0a2afbc2cc83a0f576f0 Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2016-09-01 04:46:36 +02:00
net: websocket: client: Simple API for Websocket client Implement simple API to do Websocket client requests. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2019-07-31 10:29:34 +02:00
source "subsys/net/lib/websocket/Kconfig"
net: lwm2m: initial library support for LWM2M Origin: SICS-IoT / Contiki OS URL: https://github.com/sics-iot/lwm2m-contiki/tree/lwm2m-standalone-dtls commit: d07b0bcd77ec7e8b93787669507f3d86cfbea64a Purpose: Introduction of LwM2M client library. Maintained-by: Zephyr Lightweight Machine-to-Machine (LwM2M) is a protocol stack extension of the Constrained Application Protocol (CoAP) which uses UDP transmission packets. This library was based on source worked on by Joakim Eriksson, Niclas Finne and Joel Hoglund which was adopted by Contiki and then later revamped to work as a stand-alone library. A VERY high level summary of the changes made: - [ALL] sources were re-formatted to Zephyr coding standards - [engine] The engine portion was re-written due to the heavy reliance on ER-CoAP APIs which are not compatible to the Zephyr CoAP APIs as well as other Zephyr specific needs. - [engine] All LWM2M/IPSO object data is now abstracted into resource data which stores information like the data type, length, callbacks to help with read/write. The engine modifies this data directly (or makes callbacks) instead of all of the logic for this living in each object's code. (This wasn't scaling well as I was implementing changes). - [engine] Related to the above change, I also added a generic set of getter/setter functions that user applications can call to change the object data instead of having to add getter/setting methods in each object. - [engine] The original sources shared the engine's context structure quite extensively causing a problem with portability. I broke up the context into it's individual parts: LWM2M path data, input data and output data and pass only the needed data into each set of APIs. - [content format read/writer] sources were re-organized into single .c/h files per content formatter. - [content format read/writer] sources were re-written where necessary to remove the sharing of the lwm2m engine's context and instead only requires the path and input or output data specific to it's function. - [LwM2M objects] re-written using the new engine's abstractions Signed-off-by: Michael Scott <michael.scott@linaro.org>
2017-07-07 20:04:03 +02:00
source "subsys/net/lib/lwm2m/Kconfig"
net: Add initial SOCKS5 support This adds some very basic SOCKS5 proxy client support. Signed-off-by: Tomasz Gorochowik <tgorochowik@antmicro.com>
2019-02-04 16:09:30 +01:00
source "subsys/net/lib/socks/Kconfig"
net: sntp: Implement SNTP client library The implementation is based on net app API. It sends the request and parses the server reply by following some suggestions mentioned in the secion "SNTP Server Operations" of RFC 4330. The system uptime is used as the transmit timestamp of client request This lib can work on those devices without RTC. Signed-off-by: Aska Wu <aska.wu@linaro.org>
2017-09-05 12:40:39 +02:00
source "subsys/net/lib/sntp/Kconfig"
lib: Introduce the CoAP implementation for Zephyr This is a CoAP implementation tailored for Zephyr's requirements, it tries to use memory predictably by exposing its control structures to the user (so the user only pays for the features that are used) and having a lightweight packet representation (the trade-off is that adding options is not as efficient as it could be, if there were more information available). Change-Id: I6f74146c4626a0c554f50b42f163a076e82805ba Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
2016-08-03 20:23:32 +02:00
endmenu
net: app: Create support for network application API The network application API is a higher level API for creating client and server type applications. Instead of applications dealing with low level details, the network application API provides services that most of the applications can use directly. This commit removes the internal net_sample_*() API and converts the existing users of it to use the new net_app API. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-05-10 21:23:29 +02:00
net: app: Split code for configuring network to a separate lib, "config" net_app library consisted of 2 disjoint parts: a) library to setup/configure networking on the application startup; b) library to setup client and server connections. As the configuration library is universally useful and is a generic Zephyr networking component, split it out to a seperate top-level networking library under net/lib/config/. Fixes: #7658 Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>
2018-06-18 19:57:23 +02:00
menu "Network Libraries"
source "subsys/net/lib/config/Kconfig"
net: app: Create support for network application API The network application API is a higher level API for creating client and server type applications. Instead of applications dealing with low level details, the network application API provides services that most of the applications can use directly. This commit removes the internal net_sample_*() API and converts the existing users of it to use the new net_app API. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-05-10 21:23:29 +02:00
net: sockets: Move under "Network Application Support" heading "Network Application Support" itself is renamed from "Network Applications" and also includes net_app API. Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>
2017-08-15 11:45:00 +02:00
source "subsys/net/lib/sockets/Kconfig"
net: tls: Add credential management subsystem Add TLS credential management subsystem that enables to register TLS credentials in the system. Once specific credentials are registered in the system, they will be available for TLS secure sockets to use. To use a TLS credential with a socket, the following steps have to be taken: 1. TLS credential has to be registered in a system-wide pool, using the API provided in "net/tls_credentials.h" header file. 2. TLS credential (and other TLS parameters) should be set on a socket using setsockopt(). Note, that there is no need to repeat step 1 for different sockets using the same credentials. Once TLS credential is registered in the system, it can be used with mulitple sockets, as long as it's not deleted. Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
2018-07-18 15:05:06 +02:00
source "subsys/net/lib/tls_credentials/Kconfig"
net: app: Create support for network application API The network application API is a higher level API for creating client and server type applications. Instead of applications dealing with low level details, the network application API provides services that most of the applications can use directly. This commit removes the internal net_sample_*() API and converts the existing users of it to use the new net_app API. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-05-10 21:23:29 +02:00
endmenu
net: Add a connection manager preliminary logic It currently only listens to relevant events about network interface to decide whether raising connected or disconnected event. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2019-05-09 08:58:08 +02:00
menu "Network additional services"
net: capture: Add support for network packet capturing Add infrastructure to allow user to configure the system so that all the network packets, that are sent to or received from a specific network interface, are sent to remote system for analysis. The captured network packets are placed as a payload in UDP packet, which is then sent inside a tunnel to a remote host. The host can then receive the packets and for example show them in wireshark. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2021-03-25 09:15:27 +01:00
source "subsys/net/lib/capture/Kconfig"
net: dhcpv4: Implement DHCPv4 server Add basic socket-based implementation of DHCPv4 sever. Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
2024-01-16 17:38:56 +01:00
source "subsys/net/lib/dhcpv4/Kconfig"
net: dhcpv6: Move DHCPv6 files to lib directory For consistency with DHCPv4. Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
2024-01-25 12:47:12 +01:00
source "subsys/net/lib/dhcpv6/Kconfig"
net: Move trickle files to lib The trickle algorithm files are clearly a library so move them under lib/ directory. Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no>
2023-12-09 08:02:22 +01:00
source "subsys/net/lib/trickle/Kconfig"
net: zperf: Extract zperf into library Make a library out of the zperf shell sample. This makes to enable the module in any application, not only the dedicated sample. Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
2022-07-13 09:42:11 +02:00
source "subsys/net/lib/zperf/Kconfig"
net: Add a connection manager preliminary logic It currently only listens to relevant events about network interface to decide whether raising connected or disconnected event. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2019-05-09 08:58:08 +02:00
endmenu
Copy permalink