When finishing the pwhm-wpa3-cm.t test script, MLDUnits are currently
restored to the same values as in Freedom (0: Private MLD, 1: Guest
MLD).
However, MLO is not yet supported on OSPv2, so MLDUnits should instead
remain at their default value (-1, as set through MXL UPDK).
Closes: PPW-1713
References: PCF-2395
Signed-off-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com>
After re-enabling the wifi-scheduler script, update the test to:
- Add backhaul interfaces
- Use the correct prplMesh AccessPoint creation method
- Use the generic wifi_dm helper
- Adapt AP status checks to keep the script generic
References: PPW-774
Signed-off-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com>
The test was hardcoded to expect wan and br-lan as interface names,
but the actual kernel/netdev interface name that showed up in the mangle table was eth1.
Instead of resolving the interface name at test time (hardcoded),
we resolve it at test run time as a dynamic resolution by
walking through the data model to extract the real netdev name whatever the project (ospv2/freedom)
the test now emit OK if this check passes or FAIL with explicit message if the check fails.
Tracked-by: PPW-1998
Signed-off-by: Yousfi Neji <yousfi.neji_ext@softathome.com>
Integrates:
- d12d632a: ("fix reload-time crash in AMX bus and interface handling", 2026-06-05)
References: PPW-2041
Signed-off-by: ahmed sassi <ahmed.sassi_ext@softathome.com>
When removing the last BSS of an AP MLD, the associated MLD
control interface may be left unused, leaving its control
socket lingering.
Invoke hostapd_cleanup_unused_mlds() after BSS removal to
clean up unused MLD objects. This ensures that stale MLD
state and control sockets are properly release
Fixes: PCF-2605
Signed-off-by: Marvin Lu <marvin.lu@wnc.com.tw>
Remove the deprecated Device.DeviceInfo.Reboots.reboot() RPC and its input
parameters (Cause, Reason) from the obuspa.expected fixture.
This change aligns the test expectations with the current reboot-service
model where the reboot() RPC is no longer exposed.
References: PPW-1960
Signed-off-by: ahmed sassi <ahmed.sassi_ext@softathome.com>
Integrates following changes:
reboot-service:
- reboot-service: Reboots.reboot() should not be part of the GSDM (26b126f7)
tr181-device:
- tr181-device: Reboots.reboot() is now protected (29c3f3c9)
References: PPW-1960
Signed-off-by: prplbot <bot@prplfoundation.org>
uboot-tools (pylibfdt) failed to compile with:
fatal error: Python.h: No such file or directory
Add python3-dev to the apt-get install step to provide the
missing header.
Reference: PPW-2121
Signed-off-by: Mouna Aloui <mouna.aloui@softathome.com>
Integrates:
-Update the CRAM test expectations to use the correct parameter name Stats.NACK instead of the misspelled Stats.NAK
References: PPW-1952
Signed-off-by: FAOUZI YAHYA <faouzi.yahya_ext@softathome.com>
Integrates:
-Update the obuspa expected fixture to add:
Device.SoftwareModules.ExecutionUnit.{i}.EnvVariableNumberOfEntries
Device.SoftwareModules.ExecutionUnit.{i}.HostObjectNumberOfEntries
References: PPW-1954
Signed-off-by: Antoine Philippe <antoine.philippe@softathome.com>
Integrates:
-Update the obuspa expected fixture to include
Device.SoftwareModules.ExecEnv.{i}.ApplicationDataNumberOfEntries
for timingila.
References : PPW-1954
Signed-off-by: ahmed sassi <ahmed.sassi_ext@softathome.com>
Context:
========
A first attempt to reorganize the pwhm usp tests for PPW-1606 was
introduced in commit 7560c16e81.
However, CI was failing because some required alias definitions were
missing from the OSPv2 cram tests. The change was reverted in commit
c7ea8021e0.
Let's rework the change and include the missing alias definitions so
the test reorganization is handled properly.
Initial problem:
================
During the integration of PPM-3671, the 103-apmld.t script started
failing due to an incorrect security mode set by previous tests.
Cause:
======
The security mode was unexpectedly modified during the execution of
102-pwhm-usp.t while toggling AP1. This happens because prplMesh now
runs in controller mode as part of PPM-3671.
Solution:
=========
When testing pure PWHM features, prplMesh should not be running to
avoid conflicts. This was previously the case, except for the AP1
toggling step executed in wifi-usp.t.
Move the USP-related test cases to more appropriate locations:
- USP socket creation and PWHM USP event checks (AP1 toggling):
moved to 100-pwhm.t where prplMesh is kept stopped
- prplMesh connection to the PWHM direct socket:
moved to 110-prplmesh-dataelements.t
- 102-pwhm-usp.t is so removed from fast track test scripts
Closes: PPW-1606
References: PPM-3671
Signed-off-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com>
Move AssociatedDeviceNumberOfEntries to match the current HomePlug data model output ordering in obuspa.expected.
Refrences: PPW-1953
Signed-off-by: ahmed sassi <ahmed.sassi_ext@softathome.com>
Updating the test 005-build-config during PCF-2624.
Update the test to add CONFIG_FWI_FLASH_PARTITIONS="u-boot,kernel,rootfs"
References: PCF-2624, PPW-2154
Signed-off-by: Hela Saadani <hela.saadani_ext@softathome.com>
New packages ivykis and liburing appear in the expected build config
because upstream openwrt/packages commit 8fcf45d05a changed syslog-ng
to depend on an external ivykis package (instead of the previously
embedded copy). ivykis in turn pulls in liburing when io_uring support
is enabled in the kernel.
References: PCF-1982
Signed-off-by: Hela Saadani <hela.saadani_ext@softathome.com>
Fix rx_len_adj to avoid leaking the ethernet FCS into the actual frame
data in single line mode (the default)
Fixes: https://github.com/openwrt/openwrt/issues/20983
Signed-off-by: Markus Petri <devel@isjunk.org>
Link: https://github.com/openwrt/openwrt/pull/21045
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
(cherry picked from commit 487178f8b003bf2e06b9f989b46f8b5c36181910)
(cherry picked from commit d9c5716d1d75e652d57b42a514b20145a24eee18)
e51d568 wireless-regdb: update regulatory rules for Botswana (BW) for 2022
5afc632 wireless-regdb: update regulatory rules for Sint Marteen (SX) for 2018
b484a31 wireless-regdb: Update regulatory info including bandwidth for Costa Rica (CR) for 2023
39e5e04 wireless-regdb: Permit lower 6 GHz band for Kazakhstan (KZ)
a827d3a wireless-regdb: update regulatory database based on preceding changes
Link: https://github.com/openwrt/openwrt/pull/20544
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
(cherry picked from commit b4a8ba2e88681af12287eea2d18c4f7de25e280e)
(cherry picked from commit e382fc552a5afaa18e98b8971cf515c1e7ef5248)
This fixes the following security problems:
CVE-2025-14282: Avoid privilege escalation via unix stream forwarding in Dropbear server.
CVE-2019-6111: This allowed a malicious server to overwrite arbitrary local files.
This backports two upstream merged PRs:
https://github.com/mkj/dropbear/pull/391https://github.com/mkj/dropbear/pull/394
and this upstream commit:
48a17cff6a
Link: https://github.com/openwrt/openwrt/pull/21192
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
(cherry picked from commit 0f52a05723988633882d6c52122009ce11f8956b)
cudy ap3000-v1 did not work correctly in failsafe mode
because the address 192.168.1.1 was missing on the eth0 inteface.
it was reachable via it's IPv6 link-local address however.
this commit fixes the issue.
Fixes: https://github.com/openwrt/openwrt/issues/20750
Signed-off-by: Martin Nadvornik <martin.nadvornik@gmx.at>
Link: https://github.com/openwrt/openwrt/pull/21172
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
(cherry picked from commit e5cd6461c905184db8f49692f931b20fec4b819e)
(cherry picked from commit 58a0211f8201ab622b7b11d31629d6d755bd6526)
The ports are physically labelled in reverse order on the device.
This patch aligns logical names with physical ones.
LED order on front of device is correct after this patch.
Fixes: 9d66b8b312fb6a4087244ee3ee10e1ba1623df81
Signed-off-by: Thibaut VARÈNE <hacks@slashdirt.org>
Link: https://github.com/openwrt/openwrt/pull/20528
(cherry picked from commit 887cab883bc4b3e104b70e74af775522d060e1d4)
Signed-off-by: Thibaut VARÈNE <hacks@slashdirt.org>
Link: https://github.com/openwrt/openwrt/pull/21173
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
(cherry picked from commit 7aa929881e444ebc0ec0ae6cf027144db26392d1)
Currently its only possible to disable port forwarding only for specific
keys, via the OpenSSH-style restriction in `authorized_keys` file.
In some use cases it might be feasible to disable such features globally
on service level, so lets add new LocalPortForward and RemotePortForward
config knobs.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Link: https://github.com/openwrt/openwrt/pull/21071
(cherry picked from commit 83f6177dbf44fa92ecf6d2e1cda9f92cfc5fe849)
[ fix conflict error ]
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
(cherry picked from commit 3c97c4a44cbeb767281f3260c1f6da4772432807)
Fix Totolink X6000R image failing to upgrade via sysupgrade due to an
incorrect upgrade case. The fallback upgrade path used the NAND upgrade
routine, which caused the "layout volume not found" error on NOR flash
devices. By adding a specific case for this board, sysupgrade now uses
`default_do_upgrade`, which is compatible with the NOR flash layout.
Fixes: 7cd10ad
Signed-off-by: Ayra Hikari <ayrahikari@linuxmail.org>
(cherry picked from commit 7cd10add2de3c8227cf7383c7ca5cf3b12eeb822)
Link: https://github.com/openwrt/openwrt/pull/20674
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
(cherry picked from commit 30b7a5f27aa34aa3392a5f6e1e54b02d30934cde)
Specification :
- SOC : Mediatek MT7981B (1.3GHz)
- RAM : 256MB
- Flash : 16MB SPI NOR
- Ports : 4 LAN (1G) & 1 WAN (1G)
- WIFI : MediaTek dual-band WiFi 6
- 2.4 GHz : b/g/n/ax, MIMO 2x2
- 5 GHz : a/n/ac/ax, MIMO 2x2
- Buttons : Reset & WPS/Mesh
- LEDS : WAN (Green), Status (Red & Blue)
- Power : 12V1A
Install via OEM web ui:
Upload the sysupgrade image to firmware upgrade page on OEM web ui
Install via recovery / revert to stock firmware:
1. Unplug from power
2. Download the Sysupgrade (for openwrt installation) or OEM Factory image (for revert to stock firmware)
3. Set your computer ethernet IP to 192.168.1.X, subnet 255.255.255.0 (X=your chosen ip number ranging from 2-254)
4. Press and hold reset button while turn on / plug power adapter to the router. Wait untill ALL LAN green LED turn on, then release the reset button.
5. Plug the LAN cable from your computer into LAN 1 port then open web browser, and type in the address column : 192.168.1.1
6. Upload the sysupgrade / oem factory image
7. Wait until the router finished flashing (the router will reboot)
8. Set ethernet ip to dhcp
9. Open 192.168.1.1 (for openwrt install) / 192.168.0.1 (for OEM firmware)
Signed-off-by: Ari Kurniawan <noobhek@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/20035
(cherry picked from commit 7cd10add2de3c8227cf7383c7ca5cf3b12eeb822)
Signed-off-by: Ari Kurniawan <noobhek@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/20674
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
(cherry picked from commit 8db7b6ff53042848cb9212069b3ebec33076c38a)
warning print "ath11k c000000.wifi: failed to flush transmit queue 0"
is observed during busy times.
The mac80211 fallback implementation of `flush_sta` does not handle the per STA queues well.
This is fixed by providing a ath11k specific implementation of flush_sta telling the firmware to flush a given station.
The draining of the transmit queues should therefore stop correctly, even if new packets arrive in the mean time.
An upstream ath11k RFC is available at:
https://patchwork.kernel.org/project/linux-wireless/patch/GV1P250MB14333A5BF24623C4753A10E1E8E0A@GV1P250MB1433.EURP250.PROD.OUTLOOK.COM/
The patch was tested on a Xiaomi AX3600.
Signed-off-by: Florian Maurer <f.maurer@outlook.de>
Tested-by: Florian Maurer <f.maurer@outlook.de>
Co-authored-by: Benjamin Berg <benjamin@sipsolutions.net>
Tested-by: Flole <flole@flole.de>
Link: https://github.com/openwrt/openwrt/pull/20293
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
(cherry picked from commit 8faa9dedb40dd0d7f7ebe59fddb2d33ed7a75190)
Signed-off-by: Felix Baumann <felix.bau@gmx.de>
Link: https://github.com/openwrt/openwrt/pull/20667
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
(cherry picked from commit f415748ba8e979757595d8619feddc3ec8aca788)
Since kernel 6.1, the Watchguard Firebox T10 can't boot anymore due to
increased kernel size.
This commit introduces the zImage loader from 7d768a9 to boot the kernel.
This is required, since the U-Boot version used in this device appears
to have a hard limit of 16MB for the kernel size it can handle. The
current kernel size is around 17MB, though, due to kernel page alignment
required for memory protection.
(cherry-picked from commit be7aa5bda40ee05b1dd0b4f4a1bf88e653ef875a)
Signed-off-by: Shine <4c.fce2@proton.me>
Link: https://github.com/openwrt/openwrt/pull/21130
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
(cherry picked from commit 9123a0c358d0b5275fcd99c3001f47020d27425b)
This PR fixes support for Cudy r700.
Original PR: https://github.com/openwrt/openwrt/pull/18532
Fixed:
- WAN port functionality;
- RESET button;
- Status LED;
- LAN port names consistent with the chassis;
- Merged partitions "debug", "backup" & "firmware" to one partition "firmware" ("debug" & "backup" contained unimportant data);
- Removed redundant DTS elements.
Installation:
To install OpenWRT, you need the intermediate firmware from Cudy. (U-boot is locked). After installing the intermediate firmware, you can install OpenWRT via sysupgrade.
Recovery:
TFTP available.
1. Place the recovery.bin in the serving directory of your TFTP server.
2. Set your IP to 192.168.1.88/24.
3. Press the “Reset” button of Cudy router and hold it. Before the Cudy router is powered on and before TFTP start to download the firmware, don't release the “Reset” button.
4. Power on the Cudy router.
5. You can release the reset button only when TFTP starts downloading firmware.
6. When the SYSTEM LED turns solid green, the upgrade is complete.
Fixes: 75403dd1d05b ("ramips: add support for Cudy R700")
Link: https://github.com/openwrt/openwrt/pull/20756
(cherry picked from commit 35a86267e90312f24fd11553cd5a5db0736b79ca)
Signed-off-by: Marcin Leksmark <lexmark3200@wp.pl>
Link: https://github.com/openwrt/openwrt/pull/21068
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
(cherry picked from commit 22391baf99634fc9f24d47a5ca475a654f444cd3)
This is the same hardware as the Cudy WR2100 that's
had support for some time now, just without the WLAN
hardware.
This PR is mostly copied from the commit that added
support for the WR2100, here: 3501db9
Specifications:
SoC: MT7621
CPU: 880 MHz
Flash: 16 MiB
RAM: 128 MiB
Ethernet: 5x Gbit ports
Installation:
There are two known options:
The Luci-based UI.
Press and hold the reset button during power up.
The router will request 'recovery.bin' from a TFTP server at
192.168.1.88.
Both options require a signed firmware binary.
A signed firmware can be found in GitHub PR #18532.
R4 & R5 need to be shorted (0-100Ω) for the UART to work.
Link: https://github.com/openwrt/openwrt/pull/18532
Signed-off-by: David DeGraw <degraw@fastmail.com>
(cherry picked from commit 75403dd1d05bea1b65349ebb9f8b7deb40b9c802)
Link: https://github.com/openwrt/openwrt/pull/21068
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
(cherry picked from commit 4a3409f628e2aebabac02c81750b25373c22d992)
This patch adds support for Cudy C200P.
Because v24.10 stable has no regulator definition, so we cannot make simple cherry-pick. We need another DTS file.
Specifications:
SoC: MediaTek MT7621AT
RAM: 256 MB (DDR3)
Flash: 16 MB (NOR)
POE Chip: IP804AR
Interfaces:
Switch: 1 WAN, 4 LAN (Gigabit)
Gigabit RJ45 PoE Ports on 2~5
Max Power on a Single PoE Ports 30W
PoE Ports : The PoE ports comply with IEEE 802.3at/af standards.
Ports: 1 USB-A 3.0 Ports
LED:
System
PoE Max Status
Link/ACT/PoE Status of Each PoE Port
Physical Buttons:
Reset Button
Power Input:
DC Jack
Power Methods:
DC: 54V 1.11A
802.3at/af PoE
Passive PoE: 24/48V
Max Power Consumption (W):
Total: 60W
PoE: 55W
PoE (when USB Device is plugged in): 50W
No PoE: 5W
Installation:
To install OpenWRT, you need the intermediate firmware from Cudy. (U-boot is locked). After installing the intermediate firmware, you can install OpenWRT via sysupgrade.
Recovery:
TFTP available.
1. Place the recovery.bin in the serving directory of your TFTP server.
2. Set your IP to 192.168.1.88/24.
3. Press the “Reset” button of Cudy router and hold it. Before the Cudy router is powered on and before TFTP start to download the firmware, don't release the “Reset” button.
4. Power on the Cudy router.
5. You can release the reset button only when TFTP starts downloading firmware.
6. When the SYSTEM LED turns solid green, the upgrade is complete.
Serial:
1. Serial connection parameters: 115200 / 8N1
2. Serial connection voltage: 3.3V
PoE is not supported at the time of PR. The IP804R chip is not yet supported by OpenWRT.
Signed-off-by: Marcin Leksmark <lexmark3200@wp.pl>
Link: https://github.com/openwrt/openwrt/pull/21064
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
(cherry picked from commit a9858a9632b06bc0a998e55c8338af56fa797d42)
