Add cram test to cover bSTAMLD feature.
Actually only Freedom platform is supporting it.
References: FEAT-116
Closes: PPM-3602
Signed-off-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com>
EHTCapabilities & EHTOperations DM parameters under Device.WiFi.Radio
contain raw data from the 802.11 EHT Operations Information Element.
This new test ensures that when 11be is enabled on a radio,
these APIs are working correctly;
also, when 11be is removed from the list of
Radio.i.OperatingStandards
the explicit disabling of 11be
is translated in the output of the APIs
For 5/6GHz adding channels to
Radio.i.StaticPuncturing.DisabledSubchannels
and testing the impact on the CurrentEhtOperatingIE
Closes: PPM-3537
Signed-off-by: Iacob Juc <iacob.juc_ext@softathome.com>
Signed-off-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com>
Due to a limitation in the cram tool regarding the maximum number of
test cases allowed in a single script (PCF-2222), the 101-mlo.t test
may fail.
As a temporary workaround, let's split the test into two parts.
References: PCF-2222
Signed-off-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com>
Add cram test to cover APMLD feature.
Actually only Freedom platform is supporting it.
References: FEAT-124
Closes: PPM-3347
Signed-off-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com>
Problem:
- After provisioning apmld through DataElements, APMLD group is showing without LinkIDs
- apmld link ids are unset, although link is active at nl80211 level
Cause:
- primaryLink role setting is conditioned by mld link already configured via fsm
- but once fsm run is finished, the link Id/role is not reloaded (therefore lost)
- sometimes, amxd transaction fails (with reason "invalid action" (ongoing transaction)
when trying to save SSID MldLinkID and MLDRole
Fix:
- allow primaryLink role setting at api level, regardless underlying conf applying logic
- update radio's relative apmld linkIds when radio is up or when no reconf is already valid
- postpone commiting MLDLinkID and MLDRole (with apMld dm), to next event loop run,
to let the potentially running transaction be finalized
References: PPM-3709
Signed-off-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com>
Adapt the test expectation with additional datamodel objects
following the introduction of new LCM plugin
References: PCF-2122
Signed-off-by: Nabil BIZID <nabil.bizid@softathome.com>
Add a the 038-lcm-syslog.t test which tests the cthulhu-syslog plugin
References: PCF-2122
Signed-off-by: Jef Steelant <jef.steelant_ext@softathome.com>
Integrates following changes:
- pWHM: changing TransmitPower value has no impact on txpower from iw info (b5ea0192)
References: PPW-331
Signed-off-by: prplbot <bot@prplfoundation.org>
Problem:
After integrating UPDK 9.2.3, the static puncturing test
103-pwhm-static-puncturing.t started to fail.
Cause:
UPDK 9.2.3 drivers now announce MLO support, but the feature
is not fully integrated yet (missing APMLD support).
Temporary solution:
Disable the test until MLO and static puncturing are fully
integrated on OSPv2.
References: PPW-1453
Signed-off-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com>
Problem: CRAM test for the CaptivePortal module was failing on OpenWrt 24.10.
Cause: Cram test expected HTTP 307 Temporary Redirect, but occasionally received
200 OK due to a timing issue while openNDS was starting to intercept traffic.
Solution: Added a 1-second delay and updated the test to verify CaptivePortal.State
instead of CaptivePortal.Status, ensuring validation occurs only after openNDS is actively intercepting traffic.
References: PCF-1943
Signed-off-by: Girdhari Yadav <girdhari.yadav_ext@softathome.com>
PPM-3660 lists the missing default configurations
in both wnc-freedom and OSPv2: new VAPs beyond classic six (priv+guest)
are deployed without WPA3-CM in Security.ModesAvailable.
On OSPv2, defaults from vendor module remove WPA3-CM from
Security.ModesAvailable even for priv+guest on 6GHz.
Security.ModesAvailable is writeable, so fix it at runtime for now.
Closes:PPM-3352
References: PPM-3660
Signed-off-by: Iacob Juc <iacob.juc_ext@softathome.com>
Signed-off-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com>
input operation :
* Disable MLO so RSN Override 2 parameters are not present in
hostapd.conf
* Enable Priv VAPs; configure secMode to WPA3-CM
* Enable MLO so RSN Override 2 parameters are present in hostapd.conf
* Restore MLO Configuration and Security Configuration
* Disable all VAPs to return to initial state
outputs :
* reading from pwhm the Security.ModesAvailable field and check they
contain the WPA3-Personal-Compatibility parameter
* reading from pwhm to see that pwhm accepts WPA3-Personal-Compatibility
as rval for Security.ModeEnabled=X
*testing an arbitrary hostapd.conf (5GHz)
for the absence or presence of an arbitrary config parameters
(rsn_override_key_mgmt when 11BE is disabled)
RSNOverride 1 always present in 5GHz, never in 6GHz
*testing 5GHz and 6GHz hostapd.conf for
rsn_override_key_mgmt_2 when 11BE is enabled
References: PPM-3352
Signed-off-by: Iacob Juc <iacob.juc_ext@softathome.com>
Signed-off-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com>
kjhdsq
With MLO enabled on BH VAPs, their behavior has changed slightly,
so the cram tests need to be adjusted accordingly.
Closes: PPM-3789
Signed-off-by: Igor Plesser <i.plesser@inango-systems.com>
During the execution of 110-prplmesh-dataelements.t we should restore
all AccessPoint.*.Security.ModeEnabled to their default value.
Otherwise it may impact any later test involving MLO
Closes: PPM-3350
Signed-off-by: Iacob Juc <iacob.juc_ext@softathome.com>
Signed-off-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com>
Test interaction between pwhm datamodel and hostapd.conf
input operations:
* enable only PRIV AccessPoint on DUT
needed to put radios in Status==UP
indexes are platform dependend.
* write to WiFi.Radio.{5/6GHz}.StaticPuncturing.DisabledSubChannels
outputs:
* grep punct_bitmap in hostapd.conf file
hostapd.conf file is platform dependendt - two copies of the test
Closes: PPM-3350
References: FEAT-116, FEAT-137
Signed-off-by: Iacob Juc <iacob.juc_ext@softathome.com>
Signed-off-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com>
Update references to OSPv2 image names in YAML configurations to match
the new naming convention, which was introduced in UPDK 9.2.3, providing
single build for both A-Step and B-Step OSPv2 hardware revisions.
New A-Step: prplos-intel_x86-lgm-PRPL_OSP_v2-tb341_wav700_fullimage.fit
New B-Step: prplos-intel_x86-lgm-PRPL_OSP_v2-wgrtd159be_b_wav700_fullimage.fit
References: PCF-2202
Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org>
Update mxl_wlan_hostap_ng_wav700 profile for below changes:
1) 6 GHz & Wi-Fi 7 Features
* Added 320 MHz bandwidth support for ACS/AFC.
* Enhanced TPE IE handling, AFC integration for UNII-5/UNII-7
bands, and regulatory compliance updates.
* Fixes for OWE security, WPA3 mixed mode, and enterprise security checks for 6 GHz BSS.
2) Multi-Link Operation (MLO) Enhancements
2.1) Firmware:
* Significant work on triband MLO support, including state machine
alignment, sibling STA handling, and OTF (on-the-fly) link assignments.
* Improvements for MLD VAP creation, PMKSA caching, and GTK rekey synchronization across links.
2.2) Software:
* MLO NL & PWHM OS alignment
3) AFC & ACS Improvements
* Introduced AFC patches for automated frequency coordination, timeout logic, and TX-power ranking.
* Airties ACS enhancements: smart channel selection, exclusion list support, and dynamic failsafe handling.
4) Firmware Updates
* Added Link Adaptation probing logic (r1462).
* Multiple fixes for FW crashes, throughput issues, and
calibration handling.
* Power optimization features like CPU sleep mode and QuickLatch adjustments.
5) Security & RSN Overriding
* RSNE/RSNXE override support for AP.
* WPA3/RSNO improvements for certification compliance.
* RADIUS backports enforcing Message-Authenticator attribute.
6) Certification & Compliance
* Adjustments for Wi-Fi 6/6E/7 certification programs (MU EDCA, EPCS, WMM, AFC compliance).
* Added Veriwave test configurations and sigma script updates.
7) New features
* Qos V2 MSCS & SCS support
* AT & T requirement : Support Neighbor diagnostics (TR-181 new Data Model)
* AT & T ZWDFS implementation & Bug fixes
Update OSPv2 profiles for below changes:
* Single build config provides images for both B-Step and A-Step boards
* Removed OSPv2 B step profile
* PON subsystem version bump to 2.1.4
* Linux kernel minor version upgrade from 5.15.185 to 5.15.194
* Fix done in Linux sources for ipv6 speedtest improvement
* Fix done in obudpst sources for ipv6 speedtest improvement
* Fix PON mode string representation from "GPON" to "G-PON"
* Updated version information in FIT image header of kernel and rootfs
* Fix failover issue after firmware upgrade failure
* Updated queue length and shaper of VANI0 interface to enhance WiFi to PON performance
* Allow firstboot
Fixes: PPW-946, PCF-2202, PPW-1093, PCF-2053
Signed-off-by: Bhavesh Bharadiya <bnbharadiya@maxlinear.com>
Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org> [cram test update]
* Add Multi-AP profile and VLAN ID tracking
Add support for tracking and reporting Multi-AP profile and primary
VLAN ID information in wpa_supplicant. This information is extracted
from the Multi-AP IE in association responses and included in the
connection event messages.
Changes:
- Store Multi-AP profile and primary VLAN ID from association response
- Add new fields to wpa_supplicant structure for tracking these values
- Include Multi-AP profile and VLAN ID in WPA_EVENT_CONNECTED messages
- Add debug logging for Multi-AP profile and VLAN ID values
- Reset values on new association attempts
This enables upper layer applications to be aware of the Multi-AP
configuration and VLAN segmentation being used, which is essential
for proper EasyMesh network management and monitoring.
Fixes: PCF-2290
Signed-off-by: Marvin Lu <marvin.lu@wnc.com.tw>
Problem - Failure action as set in FailAction is taken when
repeated process kill exceeds MaxFailNum parameter.
Process respawn parameters were tested in previous
005-amx-respawn-reset.t testcase which upon failure increases the
CurrentTestInterval. ProcessMonitor detects the Health of the
process based on this CurrentTestInterval.
This CurrentTestInterval after failure was around 120 seconds for
tr181-qos process. Increased time for tr181-qos process observed
would be due to some small varying additional time taken by it to
come up at the expected monitoring interval (possibly due to
additional tasks handled by tr181-qos process compared to other process)
for example tr181-pcp process had CurrentTestInterval as 60 seconds as
per 006-amx-monitoring-change-subject.t.err file.
Due to this reason the issue reported in PPW-1228 is observed. Here
NumProcessRespawn for tr181-qos was expected as 1 but found 0 because
FailAction was invoked while Health was still in Bad state, RESTART
FailAction for tr181-qos was taken which respawns the process and
clears NumProcessRespawn and MaxNumFailed attributes.
Solution - Instead of waiting for the increased CurrentTestInterval
for the Health to trun into Good state and proceed with further
testcases, TestInterval parameter is reduced to 10 seconds from 60
seconds. This improves updating the Health status of the process.
Additionally MaxFailNum is increased to higher value at the start of
the tests to avoid unexpected FailActions and reverted at the end of
testcase. Also adding update to log CurrentTestInterval and Health
for all amx-processmonitoring cram testcases.
Fixes: PPW-1228
Signed-off-by: Hari Sriram <hari.s@capgemini.com>
in WANManager, a new parameter called `LastSuccessfulMode` is added.
This paramter must be mapped to `Device.X_PRPLWARE-COM_WANManager.LastSuccessfulMode`
References: PPW-964
Signed-off-by: ahmed sassi <ahmed.sassi_ext@softathome.com>
Integrates following changes:
- DeviceInfo: manager is listing the process stats for all the processes even for killed one (7ead0454)
- ci: baf: update autogenerated files (dd4ae718)
References: PPW-1081
Signed-off-by: prplbot <bot@prplfoundation.org>
In commit 692e2f967a ("ci: cram: 065-upnp.t: fix random failures in
netstat check") the check was fixed, but got broken again in commit
b0ee814f61 ("upnp: extending the cram tests"). So lets fix it again.
References: PPW-454
Fixes: b0ee814f61 ("upnp: extending the cram tests")
Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org>
OSPv1 board was removed quite some time ago and replaced with OSPv2
successor, so lets cleanup the CI bits a bit to keep the tree tidy.
References: PCF-1134
Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org>
prplOS Network Functionality Test Plan v1.2.0 added following prplOS
4.1.0 mandatory tests which were enabled in Mandatory package and
removed from Candidate package.
* 1.2.10
* 1.2.25
* 1.2.27
* 1.2.28
* 1.3.7
* 1.4.2
* 1.4.3
* 1.4.4
* 1.5.4
* 1.5.5
* 1.5.6
* 1.5.7
* 1.5.14
* 1.5.15
* 1.5.16
* 1.5.17
Test plan packages v1.1.0 are being removed as they're not being used
anymore.
prplOS Network Test Plan timeout was increased to 1h 45min as the test
runtime increased to 1h 40min, 5 min is kept as buffer. The prplOS
Network Test Plan v1.2.0 mandatory tests require more time to complete
than the previous 70 minute timeout allowed. Candidate tests are
shorter, approx. 47 minutes on average, so having 52 minute timeout.
Closes: PCF-2275
Link: https://prplfoundation.org/wp-content/uploads/prplOS-Network-Functionality-Test-Plan-v1.2.0.pdf
Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org>
Most VAP profiles currently leave the BridgeInterface parameter empty.
Set BridgeInterface to the correct value for Home, Guest, and Backhaul VAPs.
Closes: PPM-3724
Signed-off-by: Igor Plesser <i.plesser@inango-systems.com>
- wrong sha was merged for this PPW-1122 this commit is to use the right
one
Integrates following changes:
- timingila : component uses obsolete X_PRPL-COM vendor prefix (1cfab769)
- ci: baf: update autogenerated files (995cfea4)
References: PPW-1122
Signed-off-by: ahmed sassi <ahmed.sassi_ext@softathome.com>
