Skip to content

RDKBWIFI-202: Implementation of Traffic Separation in unified-wifi-mesh#848

Open
siddharth-nair-dtdl wants to merge 1 commit intordkcentral:developfrom
siddharth-nair-dtdl:RDKBWIFI-202
Open

RDKBWIFI-202: Implementation of Traffic Separation in unified-wifi-mesh#848
siddharth-nair-dtdl wants to merge 1 commit intordkcentral:developfrom
siddharth-nair-dtdl:RDKBWIFI-202

Conversation

@siddharth-nair-dtdl
Copy link

Reason for change: Added traffic seperation TLV implementation
Test Procedure: Verify build is successfull and check if traffic seperation is functional
Risks: Medium
Priority: P2

@siddharth-nair-dtdl siddharth-nair-dtdl requested a review from a team as a code owner January 23, 2026 09:52
@github-actions github-actions bot added the community contribution Contributions from community. label Jan 23, 2026
return webconfig_hal_vap_apply_by_name(ctrl, data, vap_names, num_vaps);
}

#ifdef EM_APP
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this defined under EM_APP?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The encode, decode and translation functions are all defined under EM_APP in ccsp-one-wifi.

wifi_util_error_print(WIFI_CTRL,"%s:%d: START : Number of VAPS =%d \n",__func__, __LINE__,getTotalNumberVAPs());
char update_status[128];
for(UINT index = 0; index < getTotalNumberVAPs(); index++)
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not as per coding guideline.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Multiple places the { is in the next line. It should be consistent with the coding guideline of having the { braces in the same line as that of for/if


if(isVapPrivate(apIdx))
{
if((strncmp(vapInfo->u.bss_info.ssid,data->em_config.traffic_separation_policy.ssids[0].ssid,sizeof(data->em_config.traffic_separation_policy.ssids[0].ssid))==0) && (vapInfo->vlan_id == data->em_config.traffic_separation_policy.ssids[0].vlan_id))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Multiple comparison in one line, break it up into multipe lines.

continue;
}
strncpy(vapInfo->u.bss_info.ssid,data->em_config.traffic_separation_policy.ssids[0].ssid,sizeof(data->em_config.traffic_separation_policy.ssids[0].ssid));
strncpy(vapInfo->bridge_name,"brlan0",sizeof(vapInfo->bridge_name));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is the bridge_name hardcoded? Generic comment for all the change

Reason for change: Added traffic seperation TLV implementation
Test Procedure: Verify build is successfull and check if traffic seperation is functional
Risks: Medium
Priority: P2
wifi_util_error_print(WIFI_CTRL,"%s:%d: START : Number of VAPS =%d \n",__func__, __LINE__,getTotalNumberVAPs());
char update_status[128];
for(UINT index = 0; index < getTotalNumberVAPs(); index++)
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Multiple places the { is in the next line. It should be consistent with the coding guideline of having the { braces in the same line as that of for/if

wifi_util_info_print(WIFI_CTRL,"%s:%d: ssids_num =%d \n",__func__, __LINE__,data->em_config.traffic_separation_policy.ssids_num);

if(isVapPrivate(apIdx))
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not correct coding guideline

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please correct everywhere

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

community contribution Contributions from community.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants