PREFER_IPV4_ADDRESS is broken on IPv6-only hosts, as it causes busybox utilities (ping, traceroute, ntpd) to forcibly use the A record instead of the AAAA record when resolving a DNS name. This obviously fails when there is no IPv4 connectivity. Since IPv6-only hosts or routers will only become more common over time, disable PREFER_IPV4_ADDRESS to support this use-case. As a side-effect, disabling PREFER_IPV4_ADDRESS changes the default resolution behaviour of busybox utilities on dual-stack hosts. Busybox utilities now simply use the order given by getaddrinfo(), so they will now prefer IPv6 addresses when resolving a name with both A and AAAA records if there is IPv6 connectivity. This is in line with RFC 6724. PREFER_IPV4_ADDRESS was likely intended to work around naive implementations of getaddrinfo() that could return AAAA records first, even on an IPv4-only host. But both musl (since 1.1.3) and glibc correctly implement RFC 6724 for getaddrinfo() and check connectivity to determine the correct order in which to return records. On IPv4-only hosts, getaddrinfo() will return A records first, so there is no need for the PREFER_IPV4_ADDRESS hack. See also: https://bugs.busybox.net/show_bug.cgi?id=12381 Fixes: FS#84 Fixes: FS#2608 References: https://github.com/openwrt/openwrt/pull/4167 Signed-off-by: Alexander Traud <email@example.com> Signed-off-by: Baptiste Jonglez <firstname.lastname@example.org>
|2 days ago|
|.github||3 years ago|
|LICENSES||3 months ago|
|config||3 months ago|
|include||21 hours ago|
|package||21 hours ago|
|scripts||2 days ago|
|target||21 hours ago|
|toolchain||2 weeks ago|
|tools||6 days ago|
|.gitattributes||9 years ago|
|.gitignore||2 months ago|
|BSDmakefile||3 months ago|
|COPYING||3 months ago|
|Config.in||3 months ago|
|Makefile||2 months ago|
|README.md||2 months ago|
|feeds.conf.default||2 weeks ago|
|rules.mk||2 days 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.
binutils bzip2 diff find flex gawk gcc-6+ getopt grep install libc-dev libz-dev make4.1+ perl python3.6+ rsync subversion unzip which
./scripts/feeds update -a to obtain all the latest package definitions
defined in feeds.conf / feeds.conf.default
./scripts/feeds install -a to install symlinks for all obtained
packages into package/feeds/
make menuconfig to select your preferred configuration for the
toolchain, target system & firmware packages.
make to 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
OpenWrt is licensed under GPL-2.0