| commit | 2773023cd78f1bca8292c113fa2a87d22e385a60 | [log] [tgz] |
|---|---|---|
| author | Buke Po <bukepo@gmail.com> | Mon Jun 19 10:43:59 2017 +0800 |
| committer | Jonathan Hui <jonhui@nestlabs.com> | Sun Jun 18 19:43:59 2017 -0700 |
| tree | be9f12dc3ff35f7f06de51fd1d70a8328d05e115 | |
| parent | a24e8defc3c4c3fb68b10cd2f0b2b0d27f8227a4 [diff] |
Fix memory leak in patch for libcoap (#53) * fix memory leak in libcoap patch * set dst of pdu
Per the Thread 1.1.1 Specification, a Border Router connects a 802.15.4 network to networks at different layers, such as WiFi or Ethernet. A Thread network requires a Border Router to connect to other networks.
A Thread Border Router minimally supports the following functions:
OpenThread's implementation of a Border Router is called OpenThread Border Router (OTBR). OTBR includes a number of features, including:
Note: This is an early MVP release of OpenThread Border Router that will be improved over time. See the Roadmap page to view major fixes in progress, or the Issues page to report bugs and request enhancements.
Pull requests are encouraged and welcome. See theCONTRIBUTING.mdfile for more information.
The Border Agent binds to both Thread and WAN (WiFi, Ethernet) interfaces, to support an External Thread Commissioner in authenticating and joining Thread devices."
It also provides support for the NCP design, where Thread functions are offloaded to an NCP and OTBR runs on the host side. In this design, the Border Agent communicates with the NCP via wpantund and Spinel. A Border Agent Proxy provides an interface between Spinel and OpenThread's CoAP client and server components on the NCP. For communication with an external Commissioner, the Border Agent uses standard UDP sockets.
The Border Agent utilizes the following third-party components:
OTBR also provides the following services:
Third-party components for Border Router Services include Simple Web Server and Material Design Lite for the framework of the web UI.
We follow philosophy of Scripts to Rule Them All. Validated platforms include:
# Install dependencies ./script/bootstrap # Build and install border router and wpantund ./script/setup
Edit /etc/wpantund.conf according to the comments. Basically only path to NCP‘s serial port is required. Plug in the NCP mode OpenThread device and check the corresponding device file of it. Here’s an example when the device's serial port is /dev/ttyUSB0.
Config:NCP:SocketPath "/dev/ttyUSB0"
All border router services will be automatically started on next boot. Or you can start immediately by:
./script/server
Now you can access border router's Web UI through browsers and explore its features.
There are numerous avenues for OTBR support:
openthread tagTo learn more about OpenThread, see the OpenThread repository.
We would love for you to contribute to OpenThread Border Router and help make it even better than it is today! See the CONTRIBUTING.md file for more information.
OpenThread Border Router follows the Semantic Versioning guidelines for release cycle transparency and to maintain backwards compatibility. OpenThread's versioning is independent of the Thread protocol specification version but will clearly indicate which version of the specification it currently supports.
OpenThread Border Router is released under the BSD 3-Clause license. See the LICENSE file for more information.
Please only use the OpenThread name and marks when accurately referencing this software distribution. Do not use the marks in a way that suggests you are endorsed by or otherwise affiliated with Nest, Google, or The Thread Group.