d932d884b2
Mikrotik RouterBOARD 2011 series are AR9344-based wired routers, with optional 2,4GHz 802.11n 2x2:2 Wi-Fi radio, with desktop or rack-mount capability, featuring 5 gigabit Ethernet ports and 5 fast Ethernet ports. Different variants of the board are supported using a single image. Bare-bones RouterBOARD 2011LS is supported using the same image. Specification: - Power: 10-28V input via 5,5/2,1 DC barrel jack, or terminal block on some boards - CPU: AR9344 at 600 to 750MHz (configurable) - RAM: 128MB (64MB in early versions) DDR2 - Flash: 128MB (64MB in early versions) NAND flash - Gigabit Ethernet: 5 ports via AR8327 switch (eth1 to eth5) - Fast Ethernet: 5 ports via AR9344 built-in switch (eth6 to eth10) - SFP: single port through AR8327 switch (SGMII at port 6) - PoE in: passive input up to 28V at eth1 - PoE out: passive output up to 28V at eth10 - USB: optional micro-AB host port or type-A host port - Console: optional Cisco-style RS232 console at the back of the device, on budget devices available as 3.3V UART via testpoints - LCD: 2" touchscreen-equipped LCD (unsupported) Installation: - perform TFTP boot of initramfs image as for netinstall procedure typical for Mikrotik devices - when initramfs image boots, use sysupgrade to perform final installation. If upgrading from ar71xx, clean installation should be performed, as the devices now uses yafut to handle kernel image. TODO: - 64MB NAND variant using K9F1208U0C isn't yet supported, because it needs disabling subpage write support for that chip. A proper solution would be to fix that in kernel, but I don't have this variant to test with currently. - The same is true for GD9FU1G8F3A NAND, which isn't ONFI compliant and needs definition in kernel for proper geometry. - SFP port probes over I²C and gigabit link is possible, but currently the drivers lack support of handling link status information to userspace, including swconfig. Link will appear as always up. Currently, link status logging can detect something, but status both for ports 0 and 6 is logged simultaneously, but "swconfig dev switch0 show" will always show link up on port 6. - Not yet fully known connection to display and touch panel, but some documentation is available (seemingly connected via SPI, according to Mikrotik's open source code at [1]) [1] https://github.com/robimarko/routeros-GPL Signed-off-by: Lech Perczak <lech.perczak@gmail.com> Link: https://github.com/openwrt/openwrt/pull/17617 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> |
||
|---|---|---|
| .devcontainer/ci-env | ||
| .github | ||
| .vscode | ||
| config | ||
| include | ||
| LICENSES | ||
| package | ||
| scripts | ||
| target | ||
| toolchain | ||
| tools | ||
| .gitattributes | ||
| .gitignore | ||
| 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