maple/prplos
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
65,239 Commits 1 Branch 0 Tags 238 MiB
C 55.7%
Makefile 17.6%
Perl 7.8%
Shell 6.9%
Roff 6.1%
Other 5.7%
dd6f757ff6
Go to file
Petr Štetiar dd6f757ff6 PROVISORY: ci: cdrouter: OSPv2: switch CDRouter-UPnP-IPv46 USP MTP from MQTTv5 to WebSocket 
On the MXL25641-HDK-6 CDRouter-UPnP-IPv46 (generic-ipv6-upnp) package the
job is killed by the 52-min CDRouter cutoff at ~test 61/81 (ipv6_upnp_210),
even though Mozart and Freedom complete the same 81-test package on the
same pipeline / same MR in ~45 min. The killed test was healthy and would
have passed in another ~42 s; only OSPv2 is affected.

Per-test execution times on OSPv2 are essentially identical to the last
known-good run on this job (72f7f516..bd9b1d94 bisect window) - the
regression is not in the tests themselves. CDRouter logs show that on
OSPv2, between every IGD2 and IPv6 test, CDRouter prints

  NOTICE: The EUT is not connected to the test controller
  NOTICE: The EUT did not reconnect within 30 seconds

before starting the next test. ~38 such 30-second waits accumulate
~18.5 min of dead time on top of the otherwise normal ~33-min runtime,
exactly closing the gap to the 52-min cutoff. The regression bisects to
e266163bea ("ci: cdrouter: switch USP testing from STOMP to MQTTv5 as
primary MTP", MR #2579) - the same change that exposed the half-dead
MQTTv5 socket bug tracked in PPW-1837. The CDRouter test controller
reaches the EUT via the configured USP MTP between tests; with MQTTv5 the
socket goes silently half-dead and the reachability probe times out at
30 s before CDRouter gives up and proceeds.

So lets workaround it by switching this one job (and its -Failing sibling
which runs the same package) to WebSocket MTP, mirroring what the
certification jobs already do (see 99912e34). Mozart and Freedom run the
same package without any inter-test waits and are intentionally left
untouched.

Revert this block once the system-level fix for the half-dead MQTTv5
socket (PPW-1837) lands.

References: PPW-1897, PPW-1837, PCF-2565
Assisted-by: claude:opus-4-7:1m-context
Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org>
2026-05-22 13:33:05 +00:00
.devcontainer/ci-env
.github CI: labeler: Add stm32 target 2024-11-28 18:49:21 +00:00
.gitlab PROVISORY: ci: cdrouter: OSPv2: switch CDRouter-UPnP-IPv46 USP MTP from MQTTv5 to WebSocket 2026-05-22 13:33:05 +00:00
.testbed ci: cdrouter: switch USP testing from STOMP to MQTTv5 as primary MTP 2026-04-21 16:00:15 +01:00
.vscode meta: VS Code: add "Git: Always Sign Off" setting 2024-10-03 17:18:51 +02:00
config build: add support for checksec.sh based mitigation reports 2025-07-31 15:20:37 +00:00
include build: exclude checksec report files from rebuild check 2026-02-10 15:26:24 +00:00
LICENSES
package PROVISORY: ca-certificates: install CA Bundle ODL 2026-05-14 14:51:33 +01:00
profiles profiles: qca_ipq95xx: qca: Add support to capture WDIOF_POWERUNDER 2026-05-22 11:10:44 +00:00
scripts scripts: prplos_version.sh: mark development version as 5.0.0 2026-03-25 12:06:34 +01:00
target kernel: move kernel-6.6 file to linux/generic directory 2025-07-31 15:27:59 +00:00
toolchain toolchain: glibc: Update glibc 2.38 to recent HEAD 2025-07-27 19:47:26 +02:00
tools tools: checksec.sh: fix build breakage caused by wrong PKG_MIRROR_HASH 2025-07-31 15:30:00 +00:00
.gitattributes
.gitignore gitignore: ignore local APK keys 2024-05-17 22:03:06 +03:00
.gitlab-ci.yml ci: release,testbed: OSPv2: make firmware filenames UPDK 9.2.3 compliant 2026-01-29 10:46:42 +00:00
BSDmakefile
Config.in
COPYING
feeds.conf.default feeds.conf.default: pin to latest openwrt-24.10 branch states 2025-07-31 15:29:59 +00:00
Makefile build,base-files: propagate prplOS version into build artifacts 2025-07-31 15:18:10 +00:00
README.md README: replace "MacOSX" with "macOS" 2024-04-01 18:46:30 +02:00
rules.mk build: add comments to makefiles 2024-11-28 18:47:03 +00:00

README.md

OpenWrt logo

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

  1. Run ./scripts/feeds update -a to obtain all the latest package definitions defined in feeds.conf / feeds.conf.default

  2. Run ./scripts/feeds install -a to install symlinks for all obtained packages into package/feeds/

  3. Run make menuconfig to select your preferred configuration for the toolchain, target system & firmware packages.

  4. Run 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.

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 #openwrt on oftc.net.

Developer Community

License

OpenWrt is licensed under GPL-2.0