lede
Here are 165 public repositories matching this topic...
-
Updated
May 6, 2020 - Shell
It's a nice interface, would be interesting to give potential users an impression before they compile it on their own.

 is not mentioned in the README.
It would be appropiate to mention the config option in the beginning of the README as well as dedicate a brief section to explain how it works.
Reserved for Google Code-In 2020.
Depends on openwisp/openwisp-utils#98.
Use the decorators mentioned in the issue linked above to silence the output of noisy tests.
The following NetJSON:
{
"interfaces": [
{
"type": "virtual",
"name": "tap0",
"mac": "{{ mac_address }}"
}
]
}Won't validate. This sucks big time!
We should find a solution for this problem. Maybe we can evaluate the variables with javascript. I don't know.
-
Updated
Jul 18, 2019 - C
-
Updated
Jan 14, 2018 - C
-
Updated
Oct 13, 2018 - Go
-
Updated
Mar 21, 2019 - Shell
The Extension Registry is just a stub.
Two things must be done asap:
- add existing extensions
- define how to register extensions
-
Updated
Nov 9, 2019 - Shell
building "testing" or "unstable" libremesh via chef is using 18-06-1 (or master) openwrt. but some package-repos are still with 17.06-brunch. please change!
IMAGE_HASH=5fcf314cbc5f146
BIN_DIR=/tmp/tmp_lyvy_kb
J=4
REPOS=src/gz openwrt_core http://downloads.o
-
Updated
Mar 5, 2019
Improve this page
Add a description, image, and links to the lede topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the lede topic, visit your repo's landing page and select "manage topics."
Is it possible to have LINUX container(LXC,LXD) compiled into OpenWRT?
The LXDUI is a project allows users to manage LXC in a Web UI.
If you have these 2 enabled in OpenWrt, that would be fatastic.