| /net-tools-3.6.0/tinydtls-0.8.2/ |
| D | dtls_config.h.in | 6 /* Define to 1 if building with ECC support. */
9 /* Define to 1 if building with PSK support */
12 /* Define to 1 if you have the <arpa/inet.h> header file. */
15 /* Define to 1 if you have the <assert.h> header file. */
18 /* Define to 1 if you have the <fcntl.h> header file. */
21 /* Define to 1 if you have the `fls' function. */
24 /* Define to 1 if you have the <inttypes.h> header file. */
27 /* Define to 1 if your system has a GNU libc compatible `malloc' function, and
28 to 0 otherwise. */
31 /* Define to 1 if you have the <memory.h> header file. */
[all …]
|
| D | tinydtls.h.in | 6 * Permission is hereby granted, free of charge, to any person
8 * files (the "Software"), to deal in the Software without
9 * restriction, including without limitation the rights to use, copy,
11 * of the Software, and to permit persons to whom the Software is
12 * furnished to do so, subject to the following conditions:
35 /** Defined to 1 if tinydtls is built with support for ECC */
38 /** Defined to 1 if tinydtls is built with support for PSK */
41 /** Defined to 1 if tinydtls is built for Contiki OS */
|
| D | configure.in | 2 # Process this file with autoconf to produce a configure script.
6 # Permission is hereby granted, free of charge, to any person
8 # files (the "Software"), to deal in the Software without
9 # restriction, including without limitation the rights to use, copy,
11 # of the Software, and to permit persons to whom the Software is
12 # furnished to do so, subject to the following conditions:
33 [AC_DEFINE(WITH_CONTIKI,1,[Define to 1 if building for Contiki.])
62 [AC_DEFINE(DTLS_ECC, 1, [Define to 1 if building with ECC support.])
69 [AC_DEFINE(DTLS_PSK, 1, [Define to 1 if building with PSK support])
96 [Define to 1 if struct sockaddr_in6 has a member sin6_len.])], [],
[all …]
|
| /net-tools-3.6.0/tinydtls-0.8.2/doc/ |
| D | Doxyfile.in | 3 # This file describes the settings to be used by the documentation system
30 # The PROJECT_NUMBER tag can be used to enter a project or revision number.
36 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
38 # If a relative path is entered, it will be relative to the location
43 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
52 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
54 # information to generate all constant output in the proper language.
65 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
67 # the file and class documentation (similar to JavaDoc).
68 # Set to NO to disable this.
[all …]
|
| /net-tools-3.6.0/mbedtls-2.4.0/doxygen/ |
| D | mbedtls.doxyfile | 3 # This file describes the settings to be used by the documentation system
29 # to put quotes around the project name if it contains spaces.
33 # The PROJECT_NUMBER tag can be used to enter a project or revision number.
48 # Doxygen will copy the logo to the output directory.
52 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
54 # If a relative path is entered, it will be relative to the location
59 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
68 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
70 # information to generate all constant output in the proper language.
81 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
[all …]
|
| /net-tools-3.6.0/libcoap/doc/ |
| D | Doxyfile.in | 3 # This file describes the settings to be used by the documentation system
37 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
52 # to the output directory.
56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
58 # entered, it will be relative to the location where doxygen was started. If
63 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 4096 sub-
73 # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
74 # characters to appear in the names of generated files. If set to NO, non-ASCII
81 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
83 # information to generate all constant output in the proper language.
[all …]
|
| /net-tools-3.6.0/ |
| D | README.legacy | 6 tunslip6 can be used in host side to create a tun device that
7 is connected to a unix socket that qemu is providing. This
8 way it is possible to pass packets between host and target
11 You need to connect tunslip6 to the second qemu serial line
18 2) Start qemu, use the listener demo app. Note that you need to
21 You might need to set the platform and ARCH like this if simple_uart
35 4) Send data to listener
43 loop-slip.sh. So to simplify things you need three terminals
55 After running these scripts you do not need to manual restart
62 to work, you need to run radvd or similar tool in host side.
[all …]
|
| D | README.md | 7 Here are instructions how to communicate between Zephyr that is running
10 For setting up routing and NAT rules to allow access to external networks, please see
13 You need to run *socat* and *tunslip* to create a minimally working
30 After running these scripts you do not need to manually restart
33 In the Qemu side, you need to compile the kernel with proper config.
54 tool in net-tools directory to communicate with it.
58 The IP stack responds to ping requests if properly configured.
62 You can attach wireshark to tap0 interface to see what data is being
66 to run the echo-server sample in Zephyr, and then test the TCP stack using
71 This script will send numbers to the echo-server program, read them back,
[all …]
|
| D | README NAT.md | 3 This page describes how you can set up a networking rules that allows you to run Zephyr applications
4 build to native_posix or QEMU targets and get them to access public Internet.
11 run simulated Ethernet driver that attaches itself to a network interface called zeth.
14 In order to have networking with Zephyr, you need to configure IP address on linux kernel side,
18 Optionally, having dnsmasq to serve as small stand-alone DHCP and DNS server helps.
24 At minimun, you need following Kconfig settings for your *native_posix* application to have
67 # Note that you need to run it realtime (-rt) so responses don't timeout,
75 # it is easier to open a x-terminal to this serial port when you start the application
79 You might need to supply also `-attach_uart_cmd` parameter, in case default X-terminal is not
|
| /net-tools-3.6.0/libcoap/ |
| D | LICENSE.GPL | 6 Everyone is permitted to copy and distribute verbatim copies
11 The licenses for most software are designed to take away your
12 freedom to share and change it. By contrast, the GNU General Public
13 License is intended to guarantee your freedom to share and change free
14 software--to make sure the software is free for all its users. This
15 General Public License applies to most of the Free Software
16 Foundation's software and to any other program whose authors commit to
18 the GNU Lesser General Public License instead.) You can apply it to
21 When we speak of free software, we are referring to freedom, not
22 price. Our General Public Licenses are designed to make sure that you
[all …]
|
| D | CONTRIBUTE | 2 # Developer information for contributing to libcoap #
9 Any contributions have to be made dual licensed under the terms of the
23 Please refer also to the libcoap website for additional information
39 want to discuss some patches, please write it to the mailing list. Please
40 avoid personal mailings to the maintainer (or some other contributor) if
42 You can subscribe to the list here:
57 To start any contributing you first have to clone the git tree from the main
65 development branch! To do so you have to first checkout the 'develop' branch
80 At some point you will have to generate patches to post them on the mailing
81 list (and/or push your changes into your public Git tree). It's a good idea to
[all …]
|
| D | ChangeLog | 20 to fixed point arithmetic and removed clock_offset.
25 to calculate retransmission timeout.
37 calculation and renamed transmission parameters according to
42 * major rework to get Contiki and lwip running
59 * net.c (coap_cancel): Handling of 7.31 responses to cancel
81 return value has changed to allow distinguishing whether or not
85 additional parameter now is used to provide the offset into the
93 introduces new compiler flags WITH_POSIX and WITH_LWIP to
112 * pdu.c: option codes for Accept and Size1 according to coap-18
119 * net.c (wellknown_response): applied patch from chrysn to
[all …]
|
| D | configure.ac | 6 # Please run 'autogen.sh' to let autoconf produce a configure script.
41 # nowadays, have to be considered fully arbitrary, as the explanation provided #
42 # in the official documentation is confusing to say the least, and can be, in #
48 # How to work with the libtool versioning?
50 # Follow the followings steps from top to bottom. This means allways start at point 1
51 # if you plan to make a release and change the values.
63 # changed since the last update, increment current, and set revision to 0
66 # removed or changed. This implies also a API change! You mostly have to change
68 # --> Set 'LT_LIBCOAP_REVISION' to 0.
73 # --> Increase the 'LT_LIBCOAP_AGE' value only if the changes made to the ABI are
[all …]
|
| /net-tools-3.6.0/tinydtls-0.8.2/sha2/ |
| D | README | 5 While this is my "release" version, due to lack of additional
6 official test vectors against which to verify this implementation's
26 The interface is similar to the interface to SHA-1 found in the OpenSSL
40 data is handled. The NIST document describes how to handle sub-byte
49 implementation designed to use only 32-bit words (emulating the
57 however, that suggest ways to speed things up without breaking
58 portability. I also welcome suggestions to improve portability.
91 included in the inttypes.h header file. Those wanting to use inttypes.h
92 need to define this either in sha.h or at compile time.
95 to edit both sha2.h and sha2.c and define things by hand in the appropriate
[all …]
|
| /net-tools-3.6.0/virtual-hub/ |
| D | README.md | 3 The idea of virtual-hub is to setup a 802.15.4 network for multiple
5 pipes and redirect them to other QEMUs simulating a physical
10 with a simbolic link. Here we try to expand this concept to how many
21 To run the virtual-hub you will need to pass an csv file
28 possibility to simulate different topologies between the QEMU nodes.
37 When building the zephyr application it is necessary to enable the
39 to 1 on CMakeLists.txt from the target projects.
41 Finally, We need to setup the pipe id using `QEMU_PIPE_ID` to reference
57 from the file refers to the node with `QEMU_PIPE_ID` defined with 1. In the
58 same way the second line and column from the file refers to the node with
[all …]
|
| /net-tools-3.6.0/python-websocket-server/ |
| D | README.md | 14 like SSL etc. The project is focused mainly on making it easy to run a
25 3. `pip install websocket-server` (might not be up-to-date)
32 You can get a feel of how to use the websocket server by running
36 Then just open `client.html` in your browser and you should be able to send and receive messages.
56 *`port`* - The port clients will need to connect to.
58 …ctions only from the current machine. If you wish to allow all network machines to connect, you ne…
60 *`loglevel`* - logging level to print. By default WARNING is used. You can use `logging.DEBUG` or `…
74 … a callback function that will be called for every new `client` connecting to us | function …
77 | `send_message()` | Sends a `message` to a specific `client`. The message is a simple s…
78 | `send_message_to_all()` | Sends a `message` to **all** connected clients. The message is a si…
[all …]
|
| D | LICENSE | 5 Permission is hereby granted, free of charge, to any person obtaining a copy
6 of this software and associated documentation files (the "Software"), to deal
8 to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 copies of the Software, and to permit persons to whom the Software is
10 furnished to do so, subject to the following conditions:
|
| /net-tools-3.6.0/mbedtls-2.4.0/ |
| D | ChangeLog | 7 with RFC-5116 and could lead to session key recovery in very long TLS
12 mbedtls_x509write_csr_der() when the signature is copied to the buffer
19 * Added hardware entropy selftest to verify that the hardware entropy source
21 * Added a script to print build environment info for diagnostic use in test
23 * Added the macro MBEDTLS_X509_MAX_FILE_PATH_LEN that enables the user to
29 to configure the minimum number of bytes for entropy sources using the
33 * Fix for platform time abstraction to avoid dependency issues where a build
35 configuration consistency checks to check_config.h
36 * Fix dependency issue in Makefile to allow parallel builds.
47 * Fixed pthread implementation to avoid unintended double initialisations
[all …]
|
| D | apache-2.0.txt | 19 "control" means (i) the power, direct or indirect, to cause the
28 including but not limited to software source code, documentation
33 not limited to compiled object code, generated documentation,
34 and conversions to other media types.
38 copyright notice that is included in or attached to the work
46 separable from, or merely link (or bind by name) to the interfaces of,
51 to that Work or Derivative Works thereof, that is intentionally
52 submitted to Licensor for inclusion in the Work by the copyright owner
53 or by an individual or Legal Entity authorized to submit on behalf of
56 to the Licensor or its representatives, including but not limited to
[all …]
|
| D | README.md | 21 …r development are CMake and Make. Those systems are always complete and up-to-date. The others sho…
28 …to be in a specific order, for example the GNU linker wants `-lmbedtls -lmbedx509 -lmbedcrypto`. A…
34 Once yotta is installed, you can use it to download the latest version of mbed TLS from the yotta r…
42 …om downloading a tarball of the standalone edition, then you'll first need to generate the yotta m…
46 …otta module in the `yotta/module` directory within it. You can then change to that directory and b…
51 In any case, you'll probably want to set the yotta target before building unless it has already bee…
57 …efiles sometimes require some manual changes or export statements in order to work for your platfo…
59 In order to build from the source code using Make, just enter at the command line:
63 In order to run the tests, enter:
67 The tests need Perl to be built and run. If you don't have Perl installed, you can skip building th…
[all …]
|
| /net-tools-3.6.0/libcoap/m4/ |
| D | ax_check_compile_flag.m4 | 14 # ACTION-SUCCESS/ACTION-FAILURE are shell commands to execute on
17 # If EXTRA-FLAGS is defined, it is added to the current language's default
19 # the flags: "CFLAGS EXTRA-FLAGS FLAG". This can for example be used to
20 # force the compiler to issue an error when a bad flag is given.
22 # INPUT gives an alternative input source to AC_COMPILE_IFELSE.
46 # gives unlimited permission to copy, distribute and modify the configure
53 # This special exception to the GPL applies to versions of the Autoconf
56 # exception to the GPL to apply to your modified version as well.
|
| D | ax_check_link_flag.m4 | 14 # ACTION-SUCCESS/ACTION-FAILURE are shell commands to execute on
17 # If EXTRA-FLAGS is defined, it is added to the linker's default flags
19 # EXTRA-FLAGS FLAG". This can for example be used to force the linker to
22 # INPUT gives an alternative input source to AC_LINK_IFELSE.
46 # gives unlimited permission to copy, distribute and modify the configure
53 # This special exception to the GPL applies to versions of the Autoconf
56 # exception to the GPL to apply to your modified version as well.
|
| /net-tools-3.6.0/libcoap/examples/ |
| D | coap-client.txt.in | 24 *coap-client* is a CoAP client to communicate with 6LoWPAN devices via
35 The local address of the interface that has to be used.
38 The block size to be used in GET/PUT/POST requests (value must be a
42 option in its response to a GET request, coap-client will automatically
50 File to send with PUT/POST (use '-' for STDIN).
54 (Note that the string passed to *-m* is compared case-insensitive.)
57 A filename to store data retrieved with GET.
60 The port to listen on.
63 Subscribe to the resource specified by URI for the given 'duration' in
82 The verbosity level to use (default: 3, maximum is 9).
[all …]
|
| /net-tools-3.6.0/tinydtls-0.8.2/sha2/testvectors/testvectors/ |
| D | vector004.dat | 1 …to the proposition that all men are created equal. Now we are engaged in a great civil war, testi…
|
| /net-tools-3.6.0/mbedtls-2.4.0/yotta/data/example-benchmark/ |
| D | README.md | 15 …nt board, or another board supported by mbed OS (in which case you'll have to substitute frdm-k64f…
21 1. Connect the FRDM-K64F to the computer with the micro-USB cable, being careful to use the "OpenSD…
23 2. Navigate to the mbedtls directory supplied with your release and open a terminal.
37 …m-k64f-gcc/test/mbedtls-test-example-benchmark.bin` to your mbed board and wait until the LED next…
39 6. Start the serial terminal emulator and connect to the virtual serial port presented by FRDM-K64F…
98 …n used or not, can lead to significant differences in performance, and so results from the program…
100 The figures may also slightly change from execution to execution due to variations in the timing fu…
|
