9de5dc5636
This version bump brings following improvement requested via PCF-1666:
Get requests that contain paths spanning multiple USP Services (eg Device.) result in a get
request to each USP Service containing a list of all fully resolved parameters. It is more
efficient to perform a get of the top level DM element(s) registered by each USP Service.
Then apply max_depth and read permissions to the parameters returned, before combining into
a final Get Response to the original Get Request.
Additionally this bump to obuspa version 9.0.7 brings following changes
since version 9.0.3:
* obuspa version 9.0.7
Added:
* HardwareVersion can also be specified by an environment variable
(USP_BOARD_HW_VERSION)
Fixed:
* Crash that could occur once at startup if the controller trust
permissions table contained invalid data
* obuspa version 9.0.6
Added:
* Example vendor layer plug-in and documentation (in quick start guide)
* obuspa version 9.0.5
Fixed:
* Compilation failure when building for pure USP Service
* Subscription ID should be immutable
* OpenSSL should be initialized only once
* obuspa version 9.0.4
Added:
* USP Broker support for registration of parameters, events and USP
commands (USP 1.4)
* Bulk Data Collection over MQTT
Fixed:
* Event and OperationComplete subscriptions to 'Device.' on a USP
Broker now set subscriptions on each USP Service containing only
the DM elements that were registered (PCF-1666)
* USP Conformance test 11.11 failure: MQTT PUBLISH frames should not
be sent until SUBACK frame indicates successfully subscribed
Since the obuspa version 9.0.4 brought a new Bulk Data Collection over
MQTT feature, the obuspa.t cram test was updated with expected new
datamodel Device.BulkData.Profile.{i}.MQTT. addition.
Closes: PCF-1666
Signed-off-by: Steven Corby <steven.corby@vantiva.com>
Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org> [commit facelift, test update]
|
||
|---|---|---|
| .devcontainer/ci-env | ||
| .github | ||
| .gitlab | ||
| .testbed | ||
| .vscode | ||
| config | ||
| include | ||
| LICENSES | ||
| package | ||
| profiles | ||
| scripts | ||
| target | ||
| toolchain | ||
| tools | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| BSDmakefile | ||
| Config.in | ||
| COPYING | ||
| feeds.conf.default | ||
| Makefile | ||
| README.md | ||
| rules.mk | ||
OpenWrt Project is a Linux operating system targeting embedded devices. Instead of trying to create a single, static firmware, OpenWrt provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developers, OpenWrt is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.
Sunshine!
Download
Built firmware images are available for many architectures and come with a package selection to be used as WiFi home router. To quickly find a factory image usable to migrate from a vendor stock firmware to OpenWrt, try the Firmware Selector.
If your device is supported, please follow the Info link to see install instructions or consult the support resources listed below.
An advanced user may require additional or specific package. (Toolchain, SDK, ...) For everything else than simple firmware download, try the wiki download page:
Development
To build your own firmware you need a GNU/Linux, BSD or macOS system (case sensitive filesystem required). Cygwin is unsupported because of the lack of a case sensitive file system.
Requirements
You need the following tools to compile OpenWrt, the package names vary between distributions. A complete list with distribution specific packages is found in the Build System Setup documentation.
binutils bzip2 diff find flex gawk gcc-6+ getopt grep install libc-dev libz-dev
make4.1+ perl python3.7+ rsync subversion unzip which
Quickstart
-
Run
./scripts/feeds update -ato obtain all the latest package definitions defined in feeds.conf / feeds.conf.default -
Run
./scripts/feeds install -ato install symlinks for all obtained packages into package/feeds/ -
Run
make menuconfigto select your preferred configuration for the toolchain, target system & firmware packages. -
Run
maketo build your firmware. This will download all sources, build the cross-compile toolchain and then cross-compile the GNU/Linux kernel & all chosen applications for your target system.
Related Repositories
The main repository uses multiple sub-repositories to manage packages of
different categories. All packages are installed via the OpenWrt package
manager called opkg. If you're looking to develop the web interface or port
packages to OpenWrt, please find the fitting repository below.
-
LuCI Web Interface: Modern and modular interface to control the device via a web browser.
-
OpenWrt Packages: Community repository of ported packages.
-
OpenWrt Routing: Packages specifically focused on (mesh) routing.
-
OpenWrt Video: Packages specifically focused on display servers and clients (Xorg and Wayland).
Support Information
For a list of supported devices see the OpenWrt Hardware Database
Documentation
Support Community
- Forum: For usage, projects, discussions and hardware advise.
- Support Chat: Channel
#openwrton oftc.net.
Developer Community
- Bug Reports: Report bugs in OpenWrt
- Dev Mailing List: Send patches
- Dev Chat: Channel
#openwrt-develon oftc.net.
License
OpenWrt is licensed under GPL-2.0