User Tools

Site Tools


meta:infobox:start

Infoboxes

Below is a collection of information boxes for inclusion in other wiki pages.

Migration Required

Include with: {{page>meta:infobox:migration&noheader&nofooter&noeditbtn}}


Migration Required!
An updated equivalent of this page needs to be created in the new Wiki.


Work in Progress

Include with: {{page>meta:infobox:wip&noheader&nofooter&noeditbtn}}


Work in Progress!
This page is a continuous work in progress. You can edit this page to contribute information.


Locked

Include with: {{page>meta:infobox:locked&noheader&nofooter&noeditbtn}}


Locked Page!
This page is read-only and cannot be edited. You should use it to retrieve content for new pages.


Under Construction

Include with: {{page>meta:infobox:construction&noheader&nofooter&noeditbtn}}


Under Construction!
This page is currently under construction. You can edit the article to help completing it.


Important Information

Include with: {{page>meta:infobox:important&noheader&nofooter&noeditbtn}}


Important Information!
This section covers actions that might affect the security or performance of your device. Follow carefully.


Unverified Information

Include with: {{page>meta:infobox:unverified&noheader&nofooter&noeditbtn}}


Unverified Information!
This page or section contains unverified information. Remove this notice if you can ensure its correctness.


Outdated Information

Include with: {{page>meta:infobox:outdated&noheader&nofooter&noeditbtn}}


Outdated Information!
This article contains information that is outdated or no longer valid. You can edit this page to update it.


Historic Information

Include with: {{page>meta:infobox:historic&noheader&nofooter&noeditbtn}}


Historic information!
This page contains archived information that is only kept for research purposes. The contents are most likely outdated.


Cleanup Required

Include with: {{page>meta:infobox:cleanup&noheader&nofooter&noeditbtn}}


Cleanup Required!
This page or section needs cleanup. You can edit this page to fix wiki markup, redundant content or outdated information.


Dangerous

Include with: {{page>meta:infobox:dangerous&noheader&nofooter&noeditbtn}}


Warning!
This section describes actions that might damage your device or firmware. Proceed with care!


Attention: Trunk!

Include with: {{page>meta:infobox:attention_trunk&noheader&nofooter&noeditbtn}}


The development branch can contain experimental code that is under active development and should not be used for production environments. Snapshot images may support additional hardware; however, it is experimental, considered unstable, and sometimes won't compile.

Prebuilt snapshot images do not come with any web interface or GUI. You will need to be comfortable using a command line and remote shell to install one yourself → How to install LuCI


432 Warning

For dataentries: Include with {{section>meta:infobox:432_warning#infobox_for_dataentries&noheader&nofooter&noeditbutton}}


This device is NOT RECOMMENDED for future use with OpenWrt due to low flash/ram.
DO NOT BUY DEVICES WITH 4MB FLASH / 32MB RAM if you intend to flash an up-to-date and secure OpenWrt version (18.06 or later) onto it! See 4/32 warning for details.

1) This device does not have sufficient resources (flash and/or RAM) to provide secure and reliable operation.
This means that even setting a password or changing simple network settings might not be possible any more, rendering the device effectively useless. See OpenWrt on 4/32 devices what you can do now.

2) OpenWrt support for this device will end after 2019.
19.07 will be the last official build for 4/32 devices. After 19.07, no further OpenWrt images will be built for 4/32 devices. See OpenWrt on 4/32 devices what you can do now.


For ToHs: Include with {{section>meta:infobox:432_warning#infobox_for_tohs&noheader&nofooter&noeditbutton}}


DO NOT BUY DEVICES WITH 4MB FLASH / 32MB RAM if you intend to flash an up-to-date and secure OpenWrt version (18.06 or later) onto it! See 4/32 warning for details.

1) 4/32 devices do not have sufficient resources (flash and/or RAM) to provide secure and reliable operation. See OpenWrt on 4/32 devices what you can do now.

2) OpenWrt support for 4/32 devices will end after 2019. After 19.07, no further OpenWrt images will be built for 4/32 devices. See OpenWrt on 4/32 devices what you can do now.


Broadcom Wireless

For dataentries: Include with {{section>meta:infobox:broadcom_wifi#infobox_for_dataentries&noheader&nofooter&noeditbutton}}


Devices with Broadcom WiFi chipsets have limited OpenWrt supportability (due to limited FLOSS driver availability for Broadcom chips). Consider this when chosing a device to buy, or when deciding to flash OpenWrt on your device because it is listed as supported. See Broadcom WiFi for details.


For ToHs: Include with {{section>meta:infobox:broadcom_wifi#infobox_for_tohs&noheader&nofooter&noeditbutton}}


Devices with Broadcom WiFi chipsets have limited OpenWrt supportability (due to limited FLOSS driver availability for Broadcom chips). Consider this when chosing a device to buy, or when deciding to flash OpenWrt on your device because it is listed as supported. See Broadcom WiFi for details.


Broadcom DSL

For dataentries: Include with {{section>meta:infobox:broadcom_dsl#infobox_for_dataentries&noheader&nofooter&noeditbutton}}


DSL will not work at all on devices with BCM63xx DSL chipset (due to unavailability of FLOSS driver for Broadcom chips). Consider this when chosing a device to buy, or when deciding to flash OpenWrt on your device because it is listed as supported.
See Broadcom DSL, Unsupported: DSL modem and Broadcom BCM63xx for details.


For ToHs: Include with {{section>meta:infobox:broadcom_dsl#infobox_for_tohs&noheader&nofooter&noeditbutton}}


DSL will not work at all on devices with BCM63xx DSL chipset (due to unavailability of FLOSS driver for Broadcom chips). Consider this when chosing a device to buy, or when deciding to flash OpenWrt on your device because it is listed as supported. See Broadcom DSL, Unsupported: DSL modem and Broadcom BCM63xx for details.


Upgrade packages

Include with {{page>meta:infobox:upgrade_packages_warning&noheader&nofooter&noeditbtn}}


Blindly upgrading packages (manually or via script) can lead you into all sorts of trouble.

Just because there is an updated version of a given package does not mean it should be installed or that it will function properly. Inform yourself before doing any upgrades to determine if it is safe to upgrade. Avoid upgrading core packages,


There are two ways to manage/install packages in OpenWrt: With the LuCI web interface Software menu (System > Software), and via the command line interface (CLI). Both methods invoke the same CLI opkg executable, and as of OpenWrt 19.07.0, the LuCI interface now has an 'Updates' tab with a listing of packages that have available upgrades. The LuCI Upgrade… button performs the same opkg upgrade command that is discussed in this article. The same warnings apply to upgrading packages using LuCI and the CLI.


Generally speaking, the use of opkg upgrade is very highly discouraged, It should be avoided in almost all circumstances. In particular, bulk upgrading is very likely to result in major problems, but even upgrading individual packages may cause issues. It is also important to stress that this is distinctly different from the sysupgrade path for upgrading OpenWrt releases (major versions as well as maintenance upgrades). opkg upgrade will not update the OpenWrt version, only sysupgrade can do that – the two are not equivalent.

Unlike the 'big distros' of Linux, OpenWrt is optimized to run on systems with limited resources. This includes the opkg package manager, which does not have built-in ABI (Application Binary Interface) compatibility and kernel version dependencies verification. Although sometimes there may be no issues, there is no guarantee and the ugprade can result in various types of incompatibilities that can range from minor to severe, and it may be very difficult to troubleshoot. In addition, the opkg upgrade process will consume flash storage space. Since it does not (and cannot) overwrite the original (stored in ROM), it must store the upgraded packages in the r/w overlay.

In the vast majority of cases, any security patches of significant importance/risk will be rapidly released in an official stable maintenance release to be upgraded using the sysupgrade system. This is the recommended method for keeping up-to-date.

Those looking to be on the bleeding edge can consider using the snapshot releases, but should be mindful of the differences between stable and snapshot. Or, alternatively, build a custom image with the desired updated packages included in that image. The remaining users who still want to use opkg upgrade should only do so with selected individual packages (do not bulk update, do not blindly update) and they should be aware that problems may occur that could necessitate a complete reset-to-defaults to resolve.

If you're already having issues, or wish to 'undo' the upgraded packages: create a backup (optional; can be restored after the reset is complete) and then perform a reset to defaults (firstboot).

If you do chose to upgrade packages, especially with a script: You have been warned. Don't complain on the forum and be ready to deal with the consequences, troubleshooting, and resolution yourself.


This website uses cookies. By using the website, you agree with storing cookies on your computer. Also you acknowledge that you have read and understand our Privacy Policy. If you do not agree leave the website.More information about cookies
meta/infobox/start.txt · Last modified: 2019/04/28 02:27 by vgaetera