When passing a section or option value to config_get() which contains characters that happen to be valid variable interpolation expressions, the function returns a nonsensical expression result instead of the expected empty string. When the passed section or option name contains other characters which are not valid within a shell variable name, a substitution error is occuring instead. The issue can be easily reproduced by one of the following examples: root@OpenWrt:~# . /lib/functions.sh root@OpenWrt:~# config load system root@OpenWrt:~# config_get variable invalid-section option root@OpenWrt:~# echo "$variable" section_option:- root@OpenWrt:~# . /lib/functions.sh root@OpenWrt:~# config load system root@OpenWrt:~# config_get variable section invalid-option root@OpenWrt:~# echo "$variable" option:- root@OpenWrt:~# . /lib/functions.sh root@OpenWrt:~# config load system root@OpenWrt:~# config_get variable section invalid@option -ash: eval: syntax error: bad substitution Fix this issue by only performing interpolations when the given section and option arguments are free of illegal characters. Signed-off-by: Jo-Philipp Wich <email@example.com>
|3 years ago|
|.github||5 years ago|
|config||3 years ago|
|include||3 years ago|
|package||3 years ago|
|scripts||3 years ago|
|target||3 years ago|
|toolchain||3 years ago|
|tools||3 years ago|
|.gitattributes||12 years ago|
|.gitignore||3 years ago|
|BSDmakefile||17 years ago|
|Config.in||6 years ago|
|LICENSE||3 years ago|
|Makefile||3 years ago|
|README.md||3 years ago|
|feeds.conf.default||3 years ago|
|logo.svg||3 years ago|
|rules.mk||3 years ago|
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.
To build your own firmware you need a GNU/Linux, BSD or MacOSX system (case sensitive filesystem required). Cygwin is unsupported because of the lack of a case sensitive file system.
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.
gcc binutils bzip2 flex python3 perl make find grep diff unzip gawk getopt subversion libz-dev libc-dev
./scripts/feeds update -ato obtain all the latest package definitions defined in feeds.conf / feeds.conf.default
./scripts/feeds install -ato install symlinks for all obtained packages into package/feeds/
make menuconfigto select your preferred configuration for the toolchain, target system & firmware packages.
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.
The main repository uses multiple sub-repositories to manage packages of
different categories. All packages are installed via the OpenWrt package
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.
For a list of supported devices see the OpenWrt Hardware Database
- Forum: For usage, projects, discussions and hardware advise.
- Support Chat: Channel
- Bug Reports: Report bugs in OpenWrt
- Dev Mailing List: Send patches
- Dev Chat: Channel
OpenWrt is licensed under GPL-2.0