We’ve recently started seeing some authentication issues with the Coverity server.
So, per Coverity support's advice, we should avoid using the admin account in CI and use a regular Coverity user instead.
So let's configure the prplbot credentials as the Coverity user that commits issues to the Coverity server.
References: PCF-2428
Signed-off-by: Mouna ALOUI <mouna.aloui@softathome.com>
Integrates following changes:
- Reordered the initialization sequence so that pools_update_all_status() is called only after the backend is successfully started
Previously, updating the pool status before the backend was fully operational could lead to a race condition and intermittent test failures (44149ea3)
References: PPW-1169, PPW-1071
Signed-off-by: prplbot <bot@prplfoundation.org>
Updated the container architecture name from x86-64 to amd64 to
align with the available containers in the registry for this
architecture. Also updating the script expectation to match all
possible architecture.
References: PCF-2143
Signed-off-by: Nabil BIZID <nabil.bizid@softathome.com>
Remove all containers at the end of the test,
so the next test can start with a clean system.
References: PCF-2143
Signed-off-by: Robin NELISSEN <robin.nelissen@softathome.com>
When using the init script, the process will forcefully stop
cthulhu after a certain timeout. This behavior can cause issues
during testing, as the time needed to fully stop all containers
and shut down cthulhu depends on the number of installed processes
and the configured graceful timeout for stopping each container.
Containers are stopped sequentially.
This commit modifies the behavior to send a signal to stop cthulhu,
avoiding forceful termination if the shutdown of all containers
is not fully completed.
References: PCF-2143
Signed-off-by: Nabil BIZID <nabil.bizid@softathome.com>
The local management test is simulating a box reboot. This
requires adding some additional wait time in order for the LCM
agent to fully start all containers after running the start
script.
References: PCF-2143
Signed-off-by: Nabil BIZID <nabil.bizid@softathome.com>
Adapt datamodel expectation with additional datamodel objects
following the introduction of new components and feature.
References: PCF-2143
Signed-off-by: Nabil BIZID <nabil.bizid@softathome.com>
cthulhu-pcm and cthulhu-lpm plugins are introduced, introducing new
datamodel and new config.
Updating the expected config
References: PCF-2143
Signed-off-by: Nabil BIZID <nabil.bizid@softathome.com>
Integrates following changes:
- accesspoint: store assocRequests with MLD MACAddress if present (8224e903)
References: PPW-1568
Signed-off-by: prplbot <bot@prplfoundation.org>
When configuring the regulatory domain, it must be applied to all
radios. Applying it to only one will produce an inconsistent state,
which should have caused the failures seen in PPW-303.
Closes: PPW-303
Signed-off-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com>
Updates OBUSPA to v10.0.14
Prpl specific updates:
* Removed 005-increase_max_usp_msg_len.patch, as not required since the
new default in OBUSPA is 5MB.
* Added 009-remove-add-certificate-support.patch, as AddCertificate()
data model element is not intended to be provided by OBUSPA in Prpl
OBUSPA changes since v10.0.6:
- Changes introduced in v10.0.13 could cause FactoryReset() to hit an
assert. The cause has been fixed.
- Websocket server thread prevents graceful shutdown after disabling it,
or after duplicate messages in its send queue
- Removed automatic creation of the default database directory during
make install (GitHub Issue #148)
- If USP database file is corrupt, a new database is created using the
factory reset configuration
- R-GET.0 not working for invalid object names in path
- Memory leak with WebSockets MTP, if from_id does not match EID in
Sec-WebSocket-Extensions header
- 'obuspa -c add' CLI command now supports setting child parameters.
Example:
`obuspa -c add
'Device.LocalAgent.Subscription.(NotifType=Event,ReferenceList="Device.",Enable=true)'`
- SIGTERM signal handler to cleanly shutdown
- USP_SIGNAL_Reboot API function to initiate shutting down, then
rebooting the device
- USP_LOG_GetLogLevel and USP_LOG_SetLogLevel API functions to
atomically access the log level at runtime
- Compilation failure when #include'ing only usp_api.h
(enable_callstack_debug should be declared in usp_api.h)
- Race hazard preventing graceful shutdown. Occurs if re-initiating
shutdown whilst in the process of shutting down
- Race hazard causing USP Broker to reject all messages from a USP
Service. Occurs when USP Service disconnects, then immediately
reconnects over UDS MTP, whilst USP Broker is waiting for a synchronous
USP response
- Code has been updated to use the latest v1.5.2 release of protobuf-c
- A certificate file in the MUTABLE_CERT_DIR that did not contain Alias
could be left open. Note: This cannot occur if the certificate was added
using Device.LocalAgent.AddCertificate().
- Device.LocalAgent.AddCertificate() support. See QUICK_START_GUIDE.md
for how to use this feature.
- can_mtp_connect vendor hook should also control Bulk Data Collection
report generation
- Compilation failure with recent USP_PROCESS_DoWorkSync changes when
REMOVE_USP_BROKER is defined
- Removed Clang static analyzer false positives
- Device.Security.Certificate may be removed from OBUSPA's data model
using the define REMOVE_DEVICE_SECURITY_CERTIFICATE in vendor_defs.h.
This does not affect Device.LocalAgent.Certificate, which still reports
the trust store certificates.
- Configure options to enable address sanitizer (--enable-asan) and
thread sanitizer builds (--enable-tsan) have been added. These options
are disabled by default.
- To support compilation of OBUSPA data model plug-ins, the build
process now installs header files to $(includedir)/obuspa
- USP Command and Event arguments should not be allowed to be registered
more than once
- 'obuspa -c' output has been made cleaner, containing only logs from
the data model thread
- The m4-extra directory and AX_CHECK_XXX autotools macros (added in
v10.0.8) have been removed, as they filter rather than stop the build if
unsupported compiler options are used.
- Functions to access the data model from vendor threads
(USP_PROCESS_DoWorkSync, USP_PROCESS_DM_GetParameterValue,
USP_PROCESS_DM_SetParameterValue)
- Configure option (--enable-hardening) to enable compiler hardening
flags (disabled by default)
- Concurrent CLI invocations can get stuck
- Maximum allowed MTP frame size received has been increased to 5MB
(from 64K)
- Suppress annoying warnings when using OBUSPA CLI commands
- MQTT client should not disconnect if no Response Topic
- R-GET.0 not applied for partial paths
- USP Services should not reuse group_ids registered by internal data
model providers
- Crash if object creation notification contains too many keys
Closes: PCF-2366
Signed-off-by: Richard Holme <richard.holme@vantiva.com>
Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org>
Issue:
liblua.so.5.1.5 is missing libm.so.6 in its DT_NEEDED entries, this under-linking resulted in undefined 'sinh' symbols during unit tests.
Fix:
Add a patch (package/utils/lua/patches/055-honor-libs.patch) to ensure $(LIBS) is included when building liblua.so
Reference: PPW-1186, PCF-2425
Signed-off-by: Mabrouka <mabrouka.benbelgacem_ext@softathome.com>
Currently the tr181-upnpdiscovery feed Makefile passes PKG_CONFIG and
CONFIG_PACKAGE_procd during Build/Compile, but omits both arguments
during Build/Install and Build/InstallDev.
This leaves compile and install with different inputs and can trigger
wrong install-time behavior for procd-related script handling.
So lets fix Build/Install and Build/InstallDev by restoring
PKG_CONFIG and CONFIG_PACKAGE_procd so install receives the same
arguments as compile.
Fixes: PPW-1590
Fixes: df71d4d87b ("profiles: prpl_core: feed_prplos: tr181-upnpdiscovery: Issues reported by Coverity")
Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org>
Adding altname check test for wan interface "eth1" to prevent
PCF-2381 regressions in the future.
It simply checks whether altname value for wan interface "eth1" is "sfp0".
Signed-off-by: Bhavesh Bharadiya <bnbharadiya@maxlinear.com>
Currently prpl_core does not enable CONFIG_KERNEL_PROC_PAGE_MONITOR and
CONFIG_KERNEL_SLUB_DEBUG, so /proc/<pid>/smaps, smaps_rollup and
/proc/slabinfo are not exposed in runtime images, which means memory
analysis falls back to RSS-only attribution without shared-page
accounting, PSS-based reporting or kernel slab allocation visibility.
Add CONFIG_KERNEL_PROC_PAGE_MONITOR=y and CONFIG_KERNEL_SLUB_DEBUG=y to
prpl_core diffconfig so builds expose the procfs interfaces needed for
PSS collection, shared memory analysis and kernel slab cache reporting.
Note: CONFIG_KERNEL_SLUB_DEBUG=y is used instead of CONFIG_KERNEL_SLABINFO=y
to avoid the forced selection of CONFIG_KERNEL_SLUB_DEBUG_ON, which
enables runtime slab debug checks (sanity_checks, red_zone, poison,
store_user) on every allocation at boot. With SLUB_DEBUG alone,
/proc/slabinfo is available but the debug checks remain dormant unless
explicitly activated via the slub_debug= kernel parameter.
References: PCF-2379
Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org>
- Check WiFi.bSTAMLDMaxLinks & Radio.*.Capabilities.WiFi7STARole
- Check default APMLDConfig & bSTAMLDConfig. as now pwhm sets these
configs according to the driver capabilities
- Replace all ba-cli get/set with wifi_dm new helper
References: PPM-3655, PPM-3349, PPW-1284
Closes: PPM-3830, PPW-1325
Signed-off-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com>
Problems:
- WiFi7 STARole has no MLO modes support detection, although bSTAMLD is
functional
- missing dynamic detection APMLD/bSTAMLD MaxNumMLDs and
MaxNumLinksPerMLD
- newly created APMLD/bSTAMLD instances have APMLDConfig/bSTAMLDConfig
mlo modes set with value -1 (driver defaults), which is meaningless
with regards to EM spec
Causes:
- STA ifType was not parsed in nl80211 EXT_CAP, for MLO related
attibutes: EML_CAPABILITY and MLD_CAPA_AND_OPS
- EML_CAPABILITY and MLD_CAPA_AND_OPS are only filled by mac80211 for
AP ifType, but left empty for STA ifType
- wrong definition of APMLDConfig/bSTAMLDConfig mlo modes
Fix:
- properly detect MLO support per iftype based on available of
both nl80211 attribs EML_CAPABILITY and MLD_CAPA_AND_OPS
- read STR and NSTR default enabling from mac80211
- set properly WiFi7 APRole and STARole mlo modes support,
- deduce STARole EMLSR support with consideration of APRole (same cap
on driver side)
- deduce NSTR support with consideration of EMLMR/MLMR
- read maxNumSimultenousLinks (num auxiliary links) from driver side
- update MaxNumMLDs and MaxNumLinksPerMLD per typed MLD
- set WiFi.bSTAMLDMaxLinks with bSTAMLD capa maxLinksPerMld
- set write-once flag on MLDID of APMLD and bSTAMLD instance to allow
defining default configs with instances and APMLDConfig
(/bSTAMLDConfig)
- when pwhm creates new instances of APMLD/bSTAMLD (based on
SSID.MLDUnit settings), the initial APMLDConfig/bSTAMLDConfig mlo modes
are set driver capabilities (WiFi7 APRole/STARole mlo modes) that will
be used by default in the driver
CRAM tests:
- Update obuspa.t script
Integrates:
- 93f848f36: ("pwhm: mld: initialize APMLDConfig/bSTAMLDConfig mlo modes using driver capabilities", 2026-02-10)
- 649998b2a: ("pwhm: mld: config APMLD/bSTAMLD MLO modes with boolean params", 2026-02-10)
- 5583c685c: ("pwhm: mld: allow defining default APMLDs and bSTAMLDs with mlo configs", 2026-02-10)
- 4b4758c57: ("pwhm: bstamld: fix missing dm param bSTAMLDMaxLinks", 2026-02-10)
- d8b1340e6: ("pwhm: nl80211: fix detecting APMLD/bSTAMLD MaxNumMLDs and MaxNumLinksPerMLD", 2026-02-10)
- ec46bd4f8: ("pwhm: mld: add apis to set MaxNumMLDs and MaxNumOfLinksPerMLD on typed MLD", 2026-02-10)
- 19ec3d89e: ("pwh: nl80211: fix detecting mlo modes capabilities of WiFi7 APRole/STARole", 2026-02-10)
References: PPM-3655 PPM-3349 PPW-1284 PPW-1325
Signed-off-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com>
MxL's vendor module is overriding ModesAvailable and missing WPA3-CM.
Let's enable it manually for the OSPv2 tests for now. It should be
added by default once PCF-2259 is implemented.
References: PCF-2259, PPM-3352
Signed-off-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com>
prplMesh controller can read configuration from pwhm or from NBAPI.
This test covers both input methods.
Initial state assumption (based on default configuration) :
Controller is reading config from pwhm
Operations :
Restart prplMesh
Enable Priv VAPs
Read Security.ModeEnabled - default values
Write WPA3-Personal-Compatibility to
enabled VAPs - 3 Priv VAPs
Check that Controller Reads new values, propagates them to the Agent,
and Agent does not overwrite them not-overwrite is a double
negation that means agent writes the same value as before. A change
would imply that either:
1. Agent incorrectly reported capability - Controller downgraded security
mode
2. Controller did not read the configuration and pushed a teardown for
the Radiox instead
Switch Controller to NBAPI configuration
Push WPA3-Personal from NBAPI
Push WPA3-Personal-Compatibility from NBAPI
Restore Config to default values
Increase the testbed timeout. 5min are required to run the test.
Closes : PPM-3352
Signed-off-by: Iacob Juc <iacob.juc_ext@softathome.com>
Signed-off-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com>
Integrates:
- 092fed67: ("extender-config: prplmesh-process-manager: Support Agent only mode in Extender", 2026-01-26)
References: PCF-2183, FEAT-27
Signed-off-by: Hela Saadani <hela.saadani_ext@softathome.com>
Added new CRAM test process-manager.t and update current related
tests to compatible with newly added component.
References: PCF-2183, FEAT-27
Signed-off-by: Volodymyr Martysh <v.martysh@inango-systems.com>
Problem:
The same prplmesh static puncturing cram test is used on OSPv2 and
Freedom.
Some steps verify the 5 GHz private VAP using AccessPoint index 3,
which is specific to Freedom. On OSPv2, the correct index is 1.
Solution:
Keep the existing script unchanged for Freedom and add a new OSPv2
specific version with the corrected AccessPoint index.
References: FEAT-72
Signed-off-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com>
Integrates following changes:
reboot-service:
- procd: restore original scripts to be used in non-procd environments (cf706db3)
- ci: baf: update autogenerated files (2e688709)
amx-faultmonitor:
- procd: restore original scripts to be used in non-procd environments (a250d8ea)
- ci: baf: update autogenerated files (2c350254)
oopsmonitor:
- procd: restore original scripts to be used in non-procd environments (accacf52)
- ci: baf: update autogenerated files (df75bb5c)
amx-processmonitor:
- procd: restore original scripts to be used in non-procd environments (4a58aeb5)
- ci: baf: update autogenerated files (b22cf195)
packet-interception:
- procd: restore original scripts to be used in non-procd environments (8a2bf4cc)
- ci: baf: update autogenerated files (aab59e17)
multisettings:
- procd: restore original scripts to be used in non-procd environments (ce34c3df)
- ci: baf: update autogenerated files (b90c3fb7)
gmap-server:
- procd: restore original scripts to be used in non-procd environments (d7a1340b)
- ci: baf: update autogenerated files (a617ba46)
tr181-sfp:
- procd: restore original scripts to be used in non-procd environments (480d1b38)
- ci: baf: update autogenerated files (f7673c70)
tr181-captiveportal:
- procd: restore original scripts to be used in non-procd environments (a0721bee)
- Fix on PPW-1067 - To replace static start/stop init order with config options (558d26e3)
- ci: baf: update autogenerated files (886f0651)
pcm-manager:
- procd: restore original scripts to be used in non-procd environments (2f10f2fa)
- ci: baf: update autogenerated files (c4c62fbd)
References: FEAT-67, PPW-1066, PPW-1068
Signed-off-by: prplbot <bot@prplfoundation.org>
A wrong PKG-HASH value was added during the integration of PPW-3522
References: PPW-1555, PPW-3522
Signed-off-by: Hela Saadani <hela.saadani_ext@softathome.com>
Including 006_set_attributes.t testcase for
ConnectionTrackingQuery entry creation failures.
Adding script to verify failure conditions while providing invalid
parameter data types for existing ConnectionTrackingQuery entry.
References: PPW-1204
Signed-off-by: Hari Sriram <hari.s@capgemini.com>
Integrates:
- 9391a89: ("A new configurable parameter called CustomArguments (WiFi.DaemonMgt.Daemon.{}.ExecutionSettings.CustomArguments) is being introduced to allow defining a higher logging level and redirecting logs to syslog for the daemons (hostapd, wpa_supplicant) that are started by PWHM. The new log files will store the logs from these daemons as follows:", 2025-10-03)
References: PPM-3522
Signed-off-by: Blessy Sara John <blessysara.j@tataelxsi.co.in>
Signed-off-by: Hela Saadani <hela.saadani_ext@softathome.com>
Integrates:
- 086ac8cb: ("Introduced a new configurable parameter CustomArguments (WiFi.DaemonMgt.Daemon.{}.ExecutionSettings.CustomArguments) to allow to define higher logging lovel and redirecting the logs to syslog. Changing CustomArguments will restart the relative process to make them applied", 2025-10-03)
- 34552261: ("ci: baf: update autogenerated files", 2026-01-10)
References: PPM-3522
Signed-off-by: Hela Saadani <hela.saadani_ext@softathome.com>
Updating PWHM cram test scripts and checking logfile for wpa_supplicant and hostapd
Closes: PPM-3522
Signed-off-by: Sajith Joseph <sajithjoseph@tataelxsi.co.in>
