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>
This change was temporary reverted because we dont have a procedure on how to properly migrate this incompatible change and test also need to be temporary
reverted.
Tracked-by: PPW-1371
Implements: PCF-2118
Refereces: FEAT-32
Signed-off-by: Ruslana Popovych <ruslana.popovych@globallogic.com>
Following changes were made during datamodel alignment with v2.19.1 release:
Device.DHCPv4.Server.Pool.{i}.WINSServers - renamed from X_PRPLWARE-COM_WINSServer
Implements: PCF-2070
References: FEAT-32
Signed-off-by: Anatolii Rybchych <anatolii.rybchych@globallogic.com>
Following changes were made during datamodel alignment with v2.19.1 release:
Device.DHCPv4.Client.{i}.DSCPMark - renamed from DSCP
Device.DHCPv4.Client.{i}.Stats. removed %protected flag
Device.DHCPv4.Server.Pool.{i}.Client.{i}.IPv4Address.{i}.IsStatic - not standard, added prefix
Device.DHCPv4.Server.Pool.{i}.WINSServers - renamed from X_PRPLWARE-COM_WINSServer
Device.DHCPv6.Client.{i}.DSCPMark - renamed from DSCP
Device.DHCPv6.Server.Pool.{i}.DSCPMark - renamed from DSCP
Implements: PCF-2070,PCF-2072,PCF-2118,PCF-2119
References: FEAT-32
Signed-off-by: AnatoliiRybchych <anatolii.rybchych@globallogic.com>
Integrates following changes:
- procd: restore original scripts to be used in non-procd environments (33f97e11)
- Fix on PPW-1067 - To replace static start/stop init order with config options (10354199)
- ci: baf: update autogenerated files (54507338)
- procd: restore original scripts to be used in non-procd environments (5c5f4468)
- Fix on PPW-1067 - To replace static start/stop init order with config options (0f5828e4)
- ci: baf: update autogenerated files (b98f1835)
- procd: restore original scripts to be used in non-procd environments (7b20dc70)
- Fix on PPW-1067 - To replace static start/stop init order with config options (a7c572d0)
- ci: baf: update autogenerated files (a0bdb1d4)
- procd: restore original scripts to be used in non-procd environments (4fd06973)
- ci: baf: update autogenerated files (ab2e4597)
- ci: enable unit tests (f3ffa9c2)
- procd: restore original scripts to be used in non-procd environments (263791e6)
- Fix on PPW-1067 - To replace static start/stop init order with config options (f9f3b2c3)
- ci: baf: update autogenerated files (86ccbca)
- procd: restore original scripts to be used in non-procd environments (2873daa3)
- Fix on PPW-1067 - To replace static start/stop init order with config options (46f4d197)
- ci: baf: update autogenerated files (ee673993)
- procd: restore original scripts to be used in non-procd environments (f9196323)
- ci: baf: update autogenerated files (b0578cc0)
References: PPW-1068, PPW-1066, FEAT-67, PPW-1067
Signed-off-by: prplbot <bot@prplfoundation.org>
tr181-syslog:
- procd: restore original scripts to be used in non-procd environments (feb49955)
- Fix on PPW-1067 - To replace static start/stop init order with config options (b67200c6)
- ci: baf: update autogenerated files (5b54d7ec)
tr069-manager:
- procd: restore original scripts to be used in non-procd environments (66a2c391)
- ci: baf: update autogenerated files (be939cac)
ssh-server:
- procd: restore original scripts to be used in non-procd environments (577c5123)
- ci: baf: update autogenerated files (8535b193)
tr181-firewall:
- procd: restore original scripts to be used in non-procd environments (da8f2536)
- ci: baf: update autogenerated files (ca1ba113)
tr181-mqttbroker:
- procd: restore original scripts to be used in non-procd environments (5aaf7c8b)
- ci: baf: update autogenerated files (f30e24ff)
tr181-dnssd:
- procd: restore original scripts to be used in non-procd environments (efc630c1)
- ci: baf: update autogenerated files (8ed24c58
tr181-upnp:
- procd: restore original scripts to be used in non-procd environments (c6fdf5e8)
- ci: baf: update autogenerated files (56294770)
tr181-dynamicdns
- procd: restore original scripts to be used in non-procd environments (285f61a1)
- Fix on PPW-1067 - To replace static start/stop init order with config options (72fd5b0c)
- ci: baf: update autogenerated files (0d4a787a)
tr181-periodicfileupload
- procd: restore original scripts to be used in non-procd environments (01a90c20)
- ci: baf: update autogenerated files (3b1938b1)
tr181-bulkdata
- procd: restore original scripts to be used in non-procd environments (69165ca8)
- ci: baf: update autogenerated files (11cb45f9)
References: FEAT-67, PPW-1068, PPW-1066
Signed-off-by: prplbot <bot@prplfoundation.org>
Signed-off-by: faouzi yahya <faouzi.yahya_ext@softathome.com>
Integrates:
- amx-fcgi: changed service startup scripts to be started and monitored by procd for auto-respawn (72710426)
- ci: baf: update autogenerated files (6ecae4e8)
- acl-manager: changed service startup scripts to be started and monitored by procd for auto-respawn (b8a9d8d7)
- ci: baf: update autogenerated files (16037553)
References: PCF-2139, PPW-760
Signed-off-by: Hela Saadani <hela.saadani_ext@softathome.com>
- tr181-upnpdiscovery: changed service startup scripts to be started and monitored by procd for auto-respawn (779bb046)
- ci: baf: update autogenerated files (62a581eb)
- tr181-homeplug: changed service startup scripts to be started and monitored by procd for auto-respawn (a59055db)
- ci: baf: update autogenerated files (b9734015)
- tr181-gnimanager: changed service startup scripts to be started and monitored by procd for auto-respawn (a0435dfb)
- ci: baf: update autogenerated files (2e680d97)
- tr181-flashmonitor: changed service startup scripts to be started and monitored by procd for auto-respawn (85ea1924)
- ci: baf: update autogenerated files (27d35500)
- baf: remove dependency on libamxj (7adeec6b)
- baf: remove unused config options (016fc484)
- tr181-conntrack-query: changed service startup scripts to be started and monitored by procd for auto-respawn (769119bd)
- ci: baf: update autogenerated files (6fe9a4b5)
- tr181-conmon: changed service startup scripts to be started and monitored by procd for auto-respawn (dc775dba)
- ci: baf: update autogenerated files (f29b73fb)
- baf: introduce the baf.yml file (1fc201d0)
- ci: include the ci templates (a87d2606)
- ci: baf: update autogenerated files (8de5a768)
- netmodel-clients: changed service startup scripts to be started and monitored by procd for auto-respawn (3fd13549)
- ci: baf: update autogenerated files (5a0168a3)
- baf: introduce the baf.yml file (28c20c60)
- ci: include the ci templates (8d88ec67)
- ci: baf: update autogenerated files (92e5ab80)
- gmap-client: changed service startup scripts to be started and monitored by procd for auto-respawn (abd1d6dd)
- ci: baf: update autogenerated files (810474f8)
- data-model-mapper: changed service startup scripts to be started and monitored by procd for auto-respawn
- tr181-gatewayinfo: changed service startup scripts to be started and monitored by procd for auto-respawn
- tr069-discovery: changed service startup scripts to be started and monitored by procd for auto-respawn
- usp-discovery: changed service startup scripts to be started and monitored by procd for auto-respawn
- tr181-rest-api : corrected uci-defaults to fix lighttp server failure with amx-fcgi socket procd migration changes
References: PCF-2139
Signed-off-by: Hela Saadani <hela.saadani_ext@softathome.com>
Currently all missed components are migrated to procd as part of Overflow ticket [PCF-2139] except amx-shutdown-wait since amx-shutdown-wait doesnt seems to be init based start-up script, It does have only logic to handle shutdown all amx process in a customized way, Hence it doesnt seems to be eligible for procd based migration and doesnt take care further
Hence Updated the testcase 010-procd-spawned-process.t to have only "amx-shutdown-wait" still using amx_init_functions.sh (non-procd based) and removed all other services which are successfully migrated to procd to scope with procd migrated services verification
Implements:PCF-2139
Signed-off-by: Sathishkumar Selvam <sathishkumar.selvam@capgemini.com>
1). 110-data-model-mapper.t: After procd integration, Datamodel mapper ipk installation Usage prompt message missed causing cram failure.
Problem - Previously, data-model-mapper used a custom AMX-based init script that displayed a usage prompt as "Usage : /etc/init.d/data-model-mapper [start|boot|debuginfo|stop|shutdown|restart]" upon successful IPK installation. After migrating data‑model‑mapper to procd, the earlier AMX‑based init script’s usage prompt is no longer displayed during IPK installation. The CRAM test relied on this prompt for pattern matching, leading to test failures.
Solution - Instead of cross verifing the usage prompt for data-model-mapper ipk installation, Updated the CRAM test to stop validating the deprecated usage prompt and instead verify installation success using the IPK installation exit status, which aligns with current procd behavior.
2). ubus-datamodel-list.t: Cleaning up data-model-mapper ipk installation on 110-data-model-mapper.t itself doesnt retain running data-model-mapper process after procd migration causing cram failures with its datamodel verification on ubus-datamodel-list.t
Problem - Previously once data-model-mapper installed via ipk without procd, even if its being cleaned up after its operations at the end of 110-data-model-mapper.t test case, running data-model-mapper process would still be available , hence its datamodels later being able to verified at ubus-datamodel-list.t cram test. But after migrating to procd, procd seems taking care to clean up the running process to ensure proper cleanup, due to which cram verifying data-model-mapper datamodels later at ubus-datamodel-list.t cram test getting failed now
Solution - Removing the datamodel-mapper DM elements on ubus-datamodel-list.t help to remediate this cram failure as datamodel mapper completely uninstalled with its cleanup on earlier phase itself.
Implements:PCF-2139
Signed-off-by: Sathishkumar Selvam <sathishkumar.selvam@capgemini.com>
Previously several components - acl-manager,amx-fcgi,gmap-client,data-model-mapper,netmodel-clients,tr069-discovery,tr181-conmon,tr181-conntrack-query,tr181-flashmonitor,tr181-gatewayinfo,tr181-gnimanager,tr181-homeplug,usp-discovery,cthulhu,rlyeh,timingila,tr181-upnpdiscovery were missed during procd init script conversion process, so adding the missing procd init‑script integration in order to enable auto-respawn/procd monitoring for all these services as part of overflow ticket [PCF-2139]
Integrates:
- timingila: changed service startup scripts to be started and monitored by procd for auto-respawn (069ecb08)
- ci: baf: update autogenerated files (a1a1bec1)
- rlyeh: changed service startup scripts to be started and monitored by procd for auto-respawn (04c843e7)
- ci: baf: update autogenerated files (5c24ceec)
- cthulhu: changed service startup scripts to be started and monitored by procd for auto-respawn (5d090638)
- ci: baf: update autogenerated files (a64091b0)
References:PCF-2139
Signed-off-by: Sathishkumar Selvam <sathishkumar.selvam@capgemini.com>
100-pwhm.t:
-----------
Add hostapd socket checks after each interface state change;
other C2 requirements are implicitly covered by the apmld test.
Replace ba-cli get/set calls with the new wifi_dm helper and use
it for synchronous enable/disable operations, reducing test
duration from ~4m40s to ~1m30s (PPW-1301 #2, #3).
Verify the full interface name when reading status (PPW-1301 #4).
wifi-apmld.t:
-------------
ci: cram: warm apply: add main link interface removal new checks
Add hostapd restart check during the execution of the test
Add the check of wpactrl sockets after each operation
References: FEAT-125
Closes: PPM-3689
Signed-off-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com>
