CBR2-2255: Observing multiple "RDKB_PROCESS_CRASHED : rsync_dropbear_…#349
Open
rirfha948 wants to merge 3 commits into
Open
CBR2-2255: Observing multiple "RDKB_PROCESS_CRASHED : rsync_dropbear_…#349rirfha948 wants to merge 3 commits into
rirfha948 wants to merge 3 commits into
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR targets a boot-time issue where Dropbear/sshd ends up listening only on IPv6 (triggering repeated RDKB_PROCESS_CRASHED : rsync_dropbear_... logs), with specific focus on ETHWAN/IPv4 behavior.
Changes:
- Adjusts the Technicolor/SG417DBCT
do_start()logic that derives the CM IPv4 address used to build Dropbear listen parameters.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…process" logs
Reason for change: Dropbear listening on IPv6 address
Reverting a part of change " RDKB-57087: dummy wan0 interface removal"
Test Procedure:
- Drop bear should listening on ARM interface IP
- Crash log should not be seen in CBR2 during bootup
- In ETHWAN mode, forward SSH should be possible with IPV4
Priority: P1
- [] Is this a User Story (US)?
This is a bug ticket
- [x] Have all dependent PRs from other components been listed ?
- [x] Does the commit message include both the User Story ticket and the Subtask ticket?
- [x] Will be all changes related to the User Story squashed and merged in a single commit?
- [x] Has the PR been raised only after completing all changes for the User Story (no partial changes)?
- [x] Has code development for the User Story been completed?
- [x] If yes, has the Gerrit topic or list of all dependent PRs across components (including meta-layer changes) been shared?
https://gerrit.teamccp.com/#/c/953000/
- [x] Is there a validation log available in the Jira ticket for verifying builds with the updated generic-srcrev.inc across all platforms?
rirfha948
force-pushed
the
topic/CBR2-2255
branch
from
cf08283 to
c114eed
Compare
Comment on lines
158
to
161
| if [ -f "/nvram/ETHWAN_ENABLE" ];then | ||
| # CM_IPV4=`ifconfig privbr:0 | grep "inet addr" | awk '/inet/{print $2}' | cut -f2 -d:` | ||
| # else | ||
| CM_IPV4=`ip -4 addr show dev $CMINTERFACE scope global | awk '/inet/{print $2}' | cut -d '/' -f1` | ||
| else | ||
| CM_IPV4=`ifconfig privbr:0 | grep "inet addr" | awk '/inet/{print $2}' | cut -f2 -d:` |
snayak002c
approved these changes
Jun 23, 2026
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
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.
…process" logs
Reason for change: Dropbear listening on IPv6 address
Reverting a part of change " RDKB-57087: dummy wan0 interface removal"
Test Procedure:
Drop bear should listening on ARM interface IP
Crash log should not be seen in CBR2 during bootup
In ETHWAN mode, forward SSH should be possible with IPV4 Priority: P1
[] Is this a User Story (US)? This is a bug ticket
Have all dependent PRs from other components been listed ?
Does the commit message include both the User Story ticket and the Subtask ticket?
Will be all changes related to the User Story squashed and merged in a single commit?
Has the PR been raised only after completing all changes for the User Story (no partial changes)?
Has code development for the User Story been completed?
If yes, has the Gerrit topic or list of all dependent PRs across components (including meta-layer changes) been shared? https://gerrit.teamccp.com/#/c/953000/
Is there a validation log available in the Jira ticket for verifying builds with the updated generic-srcrev.inc across all platforms?