Skip to content

NEAT-project/neat

Folders and files

NameName
Last commit message
Last commit date

Latest commit

c5f00e1 Β· Dec 14, 2024
Dec 14, 2024
Dec 5, 2024
Dec 14, 2024
Nov 20, 2017
Dec 12, 2022
Dec 14, 2024
Mar 8, 2020
Dec 14, 2024
Sep 5, 2024
Dec 12, 2022
Aug 12, 2016
Aug 21, 2016
Dec 14, 2024
Jan 31, 2017
Dec 8, 2020
Dec 5, 2024
Dec 5, 2024
Feb 1, 2017
Feb 17, 2020
Jan 4, 2018
Jan 4, 2018
Jan 4, 2018
May 9, 2017
Aug 28, 2017
May 11, 2020
Aug 28, 2017
Mar 14, 2018
Sep 28, 2016
Feb 15, 2020
Jan 30, 2018
Aug 28, 2017
Jan 4, 2018
Oct 16, 2015
Aug 28, 2017
Jan 9, 2018
Aug 28, 2017
Jan 3, 2018
Aug 28, 2017
Aug 28, 2017
Aug 28, 2017
Oct 9, 2017
Oct 22, 2016
Dec 21, 2016
Jan 10, 2018
Jan 2, 2018
Dec 4, 2017
Aug 28, 2017
Aug 28, 2017
Aug 28, 2017
Feb 16, 2022
Jul 27, 2017
Aug 28, 2017
Aug 28, 2017
Feb 7, 2020
Jan 9, 2018
Aug 28, 2017
Aug 28, 2017
Jul 27, 2017
Aug 28, 2017
Jan 30, 2018
Jan 30, 2018
Jan 30, 2018
Dec 14, 2024
Aug 28, 2017
Jan 3, 2018
Apr 19, 2017
Aug 12, 2016

Repository files navigation

A New, Evolutive API and Transport-Layer Architecture for the Internet

NEAT supports FreeBSD, Linux, OS X and NetBSD

NEAT internals πŸ”©

NEAT is a callback based library and everything revovles around the neat_ctx struct. This struct has to be initialized before anything else can be done. NEAT uses libuv as event library, and this loop is available to users so that they can hook in and add their own callbacks.

One of the first things done in NEAT after the library has been initialized is to start monitoring the available addresses on all interfaces of the machine. NEAT supports multi-homing and we must therefore have an up-to-date view of the available (and connected) network resources available on a machine. Address events are published using an internal event API, which users also can hook into. It is useful if only a small subset of NEAT is wanted, for example monitoring the preferred lifetime of a v6 address. Look at neat_resolver.c for an example on how to use this API. An address is stored in a platform-independent structure.

After NEAT has been initialized, it is up to the user to do what he or she wants. A typical first step is to resolve a domain name.

Requirements ☝️

  • cmake
  • libuv (version 1.9 or later)
  • ldns
  • ljansson (version 2.7 or later)
  • libmnl (linux only)
  • libsctp-dev (linux only, for kernel SCTP support)
  • swig (for generating Python bindings)
OS Install Dependencies
Debian/Ubuntu* apt-get install cmake libuv1-dev libldns-dev libjansson-dev libmnl-dev libsctp-dev swig
FreeBSD pkg install cmake libuv ldns jansson swig30
OS X brew install cmake libuv ldns jansson swig
* Ubuntu 15.04 and higher

Quickstart πŸš€

$ cd <path-to-neat-src>
$ mkdir build && cd build
$ cmake ..
$ cmake --build .

This will generate makefiles and compile the library and the samples. You will find the shared and the static library in the build directory and the samples in build/examples directory.

For an easy introduction to NEAT, have a look at our tutorial.

You may also look at neat_http_get.c in the samples directory for a practical example.

$ ./client_http_get www.neat-project.org

In order to (optionally) install the neat library simply run.

$ sudo make install

Don't forget to run ldconfig after installing neat the first time.

Read the docs πŸ’‘

Have a look at our documentation!

Buildbots πŸ”₯

We are running buildbots to support our continuous integration process.

If you are only interested in a single branch, just add ?branch=BRANCHNAME to the URL. http://buildbot.nplab.de:28010/waterfall?branch=master

Links πŸ”—

Acknowledgement

This work has received funding from the European Union's Horizon 2020 research and innovation programme under grant agreement No. 644334 (NEAT). The views expressed are solely those of the author(s).