Merged
Conversation
Reason for change: Modified the documentation for GetSupportedSecurityModes Test Procedure: NA Risks: Medium Priority: P2
… WiFi - Leading to exception (#171) Reason for change: Losing WiFi Signal Monitor Thread context when Toggling WiFi - Leading to exception Test Procedure: Network Reset Risks: Low
…on getsupportedsecuritymodes (#173) Reason for change: Changes the retieveSSID security mode return value as per legacy getsupportedsecuritymodes Test Procedure: retrieveSSID curl Risks: Medium Priority: P1 Signed-off-by: Gururaaja ESR <[email protected]>
* RDKEMW-5174 - SSID Name with length 32 is not connecting Reason for change: The allowed ssid length is 32. Updated to handle it Test Procedure: NA Risks: Medium Priority: P0
* DELIA-68256 - Reset Manual IP is not working Reason for change: Checked for proper ipversion in the input curl request and it is not valid return as bad request. This will address the issue of Network Reset performed for AutoConfig IP when the device is already setup with manual IP, it is not accepting the mode change. Test Procedure: Check setIPSettings curl command Risks: Medium Priority: P2
…aking from DS (#150) Reason for change: - changed the initial monitoring logic to post the internet status change event even when we have single successful connect. - changed the IPv4 and IPv6 thread start only when there is corresponding IPv4 and IPv6 are available. - Removed the m_notify in the switchToInitialCheck().As it is leads to a unnecessary event posting Test Procedure: As mentioned in the jira ticket RDKTV-36415 Risks: Medium Priority: P0 Signed-off-by: Gururaaja ESR <[email protected]>
Reason for change: The crash is happening because of thread is not joined, when wifi is disconnected while the monitorThreadFunction() is running(which sets the m_isRunning to false) and stopWiFiSignalQualityMonitor() is called. So the next time when the thread creation is initiate it leads to a crash. Removed m_isRunning set to false at the end of monitorThreadFunction(), so that the stopWiFiSignalQualityMonitor() will join the thread in the above mentioned scenario Test Procedure: Toggle the wifi switch in the UI and check whether nm_event_thrd crash is observed or not Risks: Medium Priority: P1
Release of 0.20.0
Fixed the issues in the networkmanager - gdbus proxy implementation
* RDKEMW-4918 - Removal of SetPrimaryInterface and other cleanup Reason for change: Removed SetPrimaryInterface support and inherited Iconfiguration to configure the plugin. Also removed activation of networkmanager plugin from legacy plugin Test Procedure: NA Risks: Medium Priority: P1
Reason for change: The issue is because of the logic failure is in accessing the InterfaceList Iterator returned by the Thunder IIteratorType. Addressed the same by resetting the list with Reset() call. Also moved the interface count while loop inside the return code and NULL pointer check Test Procedure: Deep sleep to wake up scenario Priority:P1 Risks: Medium Signed-off-by: Gururaaja E S R <Gururaja_ErodeSriranganRamlingham.comcast.com>
* RDKEMW-2939: add param validation
Reason for Change: ping succeeds with invalid ipversion
- {"jsonrpc":"2.0","id":42,"method":"org.rdk.NetworkManager.1.Ping","params":{"endpoint":"142.250.192.78","ipversion":"invalid"}}
* RDKEMW-2939: param validation for SetStunEndPoint
Reason for Change: invalid param produces SUCCESS
```
{"jsonrpc":"2.0","id":42,"method":"org.rdk.NetworkManager.1.SetStunEndpoint"}
{"jsonrpc":"2.0","id":42,"method":"org.rdk.NetworkManager.1.SetStunEndpoint","params":{"port":0}}
```
* Clean the temporary file
…twork link up (#181) * RDKEMW-5550 Bring Multiple IP address change events with IPv6/IPV4 after network link up Issue Fix
Release of 0.21.0
…an0 LINK_UP (#187) Reason for change: Posting the WIFI connected event when we receive the state as NM_DEVICE_STATE_IP_CONFIG from gnome networkmanager so that we can avoid the delay in postin the events onWiFiStateChanged Test Procedure: Network reset with UI Priority:P1 Risks: Medium
…#188) Reason for change: The issue is happening because of the race condition happening between the 2 threads(connectivityMonitorFunction and the main thread in which switchToInitialCheck executes). Because of the race condition, switchToInitialCheck() was triggered before the m_wlanConnected was set to true. So the execution goes inside [else if (_instance != nullptr && !_instance->m_ethConnected && !_instance->m_wlanConnected)] and no event is actually posted as InitialRetryCount was already set to 1. Made changes to ReportInterfaceStateChange() to set m_wlanConnected to true when the interface is UP and then switchToInitialCheck() is triggered. Test Procedure: Deep sleep to wake up scenario Priority:P1 Risks: Medium Signed-off-by: Gururaaja E S R <Gururaja_ErodeSriranganRamlingham.comcast.com>
Release of 0.22.0
#189) Reason for change - Removal of unnecessary log to avoid log flooding
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.