Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| network:firmware:overview [2024/02/16 05:38] – created system | network:firmware:overview [2025/04/15 05:15] (current) – [Include your own files] system | ||
|---|---|---|---|
| Line 8: | Line 8: | ||
| ====== OpenWrt Overview ====== | ====== OpenWrt Overview ====== | ||
| ===== Introduction ===== | ===== Introduction ===== | ||
| - | * The intended audience of this page is someone | + | * This page is aimed at people |
| - | * OpenWrt is a very popular project that allows you to build your own Linux based firmware | + | * OpenWrt is a very popular project that allows you to create |
| - | * They have pre-built firmware images | + | * There are pre-built firmware images for many hardware models |
| - | * You can also compile your own custom | + | * You can also compile your own firmware using the OpenWrt SDK (Software Development Kit) |
| - | * Without duplicating existing documentation you can visit the project' | + | * Without duplicating |
| ===== OpenWrt with MESHdesk and APdesk ===== | ===== OpenWrt with MESHdesk and APdesk ===== | ||
| - | * MESHdesk and APdesk | + | * MESHdesk and APdesk |
| - | * It simply | + | * It only adds three additional |
| - The MESHdesk package. | - The MESHdesk package. | ||
| - The MESHdesk Luci application. | - The MESHdesk Luci application. | ||
| - | - Some additional files e.g. a custom banner and logo. | + | - Some additional files, e.g. a custom banner and logo. |
| - | * Although | + | * While we will cover these elements |
| ===== MESHdesk package ===== | ===== MESHdesk package ===== | ||
| - | * OpenWrt follows the same pattern as most other Linux distributions | + | * OpenWrt follows the same pattern as most other Linux distributions: It has a package manager (opkg) that is used to install software |
| - | * This package manager also takes care of dependencies. | + | * This package manager also takes care of the dependencies. |
| - | * Packages can be installed after the device | + | * Packages can be installed after the device |
| - | * We will compile our own OpenWrt firmware that have the MESHdesk package | + | * We will later compile our own OpenWrt firmware that includes |
| - | * To build your own OpenWrt firmware | + | * To create |
| - | * The OpenWrt SDK allows | + | * With the OpenWrt SDK you can: |
| - | - Select the specific device you want to build firmware | + | - Select the specific device |
| - | - Select the packages you want to include | + | - Select the packages you want to include |
| - | - Include your own additional files with the firmware. | + | - Include your own additional files in the firmware. |
| - | * This is exactly what we will be doing later on. | + | * This is exactly what we will do later. |
| ===== MESHdesk Luci package ===== | ===== MESHdesk Luci package ===== | ||
| - | * OpenWrt can work fine without | + | * OpenWrt can also work without |
| - | * There is however | + | * However, there is a web interface called Luci, which is an add-on to OpenWrt. |
| - | * The firmware | + | * It is included by default in the firmware |
| - | * The nightly | + | * However, it is not included in the nightly |
| - | * Luci has various sub items e.g. modules, applications, | + | * Luci has various sub-items, e.g. modules, applications, |
| - | * We will add an application to Luci (the MESHdesk Luci Application) | + | * We will add an application to Luci (the MESHdesk Luci application) |
| - | * This application | + | * This application |
| - | + | <panel type=" | |
| - | {{: | + | {{: |
| + | </ | ||
| ===== Include your own files ===== | ===== Include your own files ===== | ||
| - | * When building | + | * If you create |
| - | * These files are ad-hoc | + | * These files are ad-hoc |
| - | * We will later show how you can include for instance your own logo and a custom banner for the SSH and terminal login screens. | + | * We will show later how you can, for example, include your own logo and a custom banner for the SSH and terminal login screens. |
| - | + | ||
| - | This brings us to the end of the introduction to OpenWrt. | + | |
| - | + | ||
| - | Next will be getting the environment ready for the OpenWrt SDK. | + | |
| - | + | ||
| - | ====== OpenWrt Overview ====== | + | |
| - | ===== Introduction ===== | + | |
| - | * The intended audience of this page is someone who is familiar with Linux but new to the OpenWrt world. | + | |
| - | * OpenWrt is a very popular project that allows you to build your own Linux based firmware which you can use on embedded devices. | + | |
| - | * They have pre-built firmware images available for many hardware models which you can download from their website. | + | |
| - | * You can also compile your own custom firmware using the OpenWrt SDK (Software Development Kit) | + | |
| - | * Without duplicating existing documentation you can visit the project' | + | |
| - | + | ||
| - | ===== OpenWrt with MESHdesk and APdesk ===== | + | |
| - | * MESHdesk and APdesk makes use of OpenWrt. | + | |
| - | * It simply adds three additional items to it. | + | |
| - | - The MESHdesk package. | + | |
| - | - The MESHdesk Luci application. | + | |
| - | - Some additional files e.g. a custom banner and logo. | + | |
| - | * Although we will cover these items later again when we do hands-on compiling, going through them in the overview will make things a bit more familiar later on. | + | |
| - | + | ||
| - | ===== MESHdesk package ===== | + | |
| - | * OpenWrt follows the same pattern as most other Linux distributions where it has a package manager (opkg) that is used to install software onto the device. | + | |
| - | * This package manager also takes care of dependencies. | + | |
| - | * Packages can be installed after the device is flashed and running with OpenWrt or it can included during compile time to be part of the firmware image. | + | |
| - | * We will compile our own OpenWrt firmware that have the MESHdesk package included later on. | + | |
| - | * To build your own OpenWrt firmware you make use of the OpenWrt SDK (Software Developer Kit). | + | |
| - | * The OpenWrt SDK allows you to: | + | |
| - | - Select the specific device you want to build firmware | + | |
| - | - Select the packages you want to include with the firmware. | + | |
| - | - Include your own additional files with the firmware. | + | |
| - | * This is exactly what we will be doing later on. | + | |
| - | + | ||
| - | ===== MESHdesk Luci package ===== | + | |
| - | * OpenWrt can work fine without any web interface. | + | |
| - | * There is however a web interface available called Luci which is an add-on to plain OpenWrt. | + | |
| - | * The firmware which you can download from the OpenWrt website has it included by default. | + | |
| - | * The nightly builts of the development branch however do not have it included. | + | |
| - | * Luci has various sub items e.g. modules, applications, | + | |
| - | * We will add an application to Luci (the MESHdesk Luci Application) | + | |
| - | * This application will allow someone to enable or disable central management of the OpenWrt device using the Luci web interface. | + | |
| - | + | ||
| - | {{: | + | |
| - | + | ||
| - | ===== Include your own files ===== | + | |
| - | * When building your own OpenWrt firmware using the SDK it makes provisioning to also include | + | |
| - | * These files are ad-hoc and include those not part of a package but those that you still want to have included as part of the firmware. | + | |
| - | * We will later show how you can include for instance | + | |
| This brings us to the end of the introduction to OpenWrt. | This brings us to the end of the introduction to OpenWrt. | ||
| - | Next will be getting | + | Next, we will prepare |
| - | [[network: | + | [[network: |