...
| Code Block |
|---|
| language | bash |
|---|
| title | ctrl - build instructions |
|---|
|
repo init -u https://code.rdkcentral.com/r/manifests -b kirkstone -m rdkb-bpi-extsrc.xml
repo sync -j`nproc` --no-clone-bundle
Please pick the below machine command based on your requirement
# to build the image with AL_SAP
MACHINE=bananapi4-rdk-broadband FEATURE_TYPE=EasyMesh source meta-cmf-bananapi/setup-environment-refboard-rdkb
# to build the image without AL_SAP
MACHINE=bananapi4-rdk-broadband FEATURE_TYPE=EasyMesh WITHOUT_ALSAP=yes source meta-cmf-bananapi/setup-environment-refboard-rdkb
#to CP the below change for fynecli access for utopia component
https://github.com/rdkcentral/utopia/pull/47
bitbake rdk-generic-broadband-image |
...
- All configured VAPs should be UP and Running
- VAPs should be broadcasting EasyMesh default SSIDs(eg, private_ssid, mesh_backhaul)
- Logs files are generated under /tmp folder
Extender
Build Instructions
| Code Block |
|---|
| language | bash |
|---|
| title | Ext - Build Instructions |
|---|
|
repo init -u https://code.rdkcentral.com/r/manifests -b kirkstone -m rdkb-bpi-ap-extsrc.xml
repo sync -j4 --no-clone-bundle
#CPPlease pick the below changes
cd ~/meta-rdk
git fetch https://code.rdkcentral.com/r/rdk/components/generic/rdk-oe/meta-rdk refs/changes/39/114939/5 && git cherry-pick FETCH_HEAD
cd -
machine command based on your requirement,
#to build the image with AL_SAP
MACHINE=bananapi4-rdk-broadband-ap-extender source meta-cmf-bananapi/setup-environment-refboard-rdkb
bitbake rdk-generic#to build the image without AL_SAP
MACHINE=bananapi4-rdk-broadband-ap-extender FEATURE_TYPE=EasyMesh WITHOUT_ALSAP=yes source meta-cmf-bananapi/setup-environment-refboard-rdkb
bitbake rdk-generic-ap-extender-image |
Extender 1 + STAR Topology
...
2.Ensure mesh backhaul connectivity is established over 5G through wifi1.1 interface.
3.Verify mesh backhaul connection in EM-Contrller side as well.
...
- Check all configured VAPs should be up and running with "iw dev" command
- VAPs should be broadcasting default EasyMesh SSIDS (ie private_ssid, mesh_backhaul)
5. Set static IP for brlan0 interface in Extender1
| Code Block |
|---|
|
ifconfig brlan0 10.0.0.215 netmask 255.255.255.0 up |
- logs files are generated under /tmp folder
56. Test the connectivity to EM-Controller through backhaul
...
Extender2 (For Daisy-Chain )
Prerequisites - One Time Process
1. Ensure Extender 1 is running properly with configured vap's of FH and BH.
2. Make atleast 7 feet distance from Ext1 to Ext2
3. Ensure ieee1905_em_agent,onewifi_em_agent processes are running in Ext2
4. Ensure mesh backhaul connectivity is established over 5G through wifi1.1 interface1. Copy below content to /nvram/InterfaceMap.json file.
| Code Block |
|---|
| language | bash |
|---|
| title | Extender2 InterfaceMap.json |
|---|
| collapse | true |
|---|
|
{
"PhyList": [
{
"Index": 0,
"RadioList": [
{
"Index": 2,
"RadioName": "wifi2",
"InterfaceList": [
{
"InterfaceName": "wifi2",
"Bridge": "brlan0",
"vlanId": 0,
"vapIndex": 3,
"vapName": "private_ssid_6g"
}
]
},
{
"Index": 1,
"RadioName": "wifi1",
"InterfaceList": [
{
"InterfaceName": "wifi1",
"Bridge": "brlan0",
"vlanId": 0,
"vapIndex": 2,
"vapName": "private_ssid_5g"
}
]
},
{
"Index": 0,
"RadioName": "wifi0",
"InterfaceList": [
{
"InterfaceName": "wifi0.1",
"Bridge": "brlan0",
"vlanId": 0,
"vapIndex": 1,
"vapName": "mesh_sta_2g"
},
{
"InterfaceName": "wifi0",
"Bridge": "brlan0",
"vlanId": 0,
"vapIndex": 0,
"vapName": "private_ssid_2g"
}
]
}
]
}
]
} |
2. Edit the AL_MAC_ADDR in /nvram/EasymeshCfg.json. Here, wifi0.1 interface mac address as AL_MAC_ADDR
3. Reboot the device
After reboot,
4. Ensure mesh backhaul connectivity is established over 2.4G through wifi0.1 interface.
| Code Block |
|---|
|
iw dev wifi0.1 info |
5. Verify mesh backhaul connection in Extender1 side as well.
5. Verify mesh backhaul connection in Extender1 side as well.
| Code Block |
|---|
|
iw dev wifi1.1.sta<i> info
iw dev wifi1.1.sta<i> station dump ## This command gives information on connected client ie Extender2. |
| Code Block |
|---|
|
iw dev wifi0.1.sta<i> info
iw dev wifi0.1.sta<i> station dump ## This command gives information on connected client ie Extender2. |
6. Wait for few minutes( for Agent to propagate SSID information from Controller to OneWifi in Extender2) and then check
- Check all configured VAPs should be up and running with "iw dev" command
- VAPs should be broadcasting default EasyMesh SSIDS (ie private_ssid, mesh_backhaul)
7. Set static IP for brlan0 interface in Extender2
| Code Block |
|---|
|
ifconfig brlan0 10.0.0.210 netmask 255.255.255.0 up |
8. Test the connectivity to EM-Controller through backhaul
...
