Page History

Linux Platform (

RPi4)

Build steps for compilation on

RPi4 with Raspbian OS:

Prerequisites

1. Install the Raspian Pi OS from the “Raspberry Pi Imager”

1. software. Select the

1. RPi4 Os (64-bit) image. 

2. After installation below are additional packages to be installed for build, db and execution.

Build Instructions

1.  In a working directory git clone the OneWifi in generic folder and unified-wifi-mesh repository
   bashRDark
   
   
2. Run the makefile of OneWifi with setup option to pull in other dependent repository.

1. This is a one time operation. 
   bashRDark
   
   
2. Build the

1. OneWifi with make command
   bashRDark
   
   
2. Build easymesh components in

1. the unified-wifi-mesh

1. folder
   a. Controller
   bashRDark
   

1. b. CLI
   bashRDark
   c. Agent
   bashRDark

RDK Platform

Prerequisites

1. Setup a RDK build machine capable of doing RDK builds as mentioned here

2. It is recommended to get access to RDK licensee account as mentioned here
   

Linux Platform (

RPi4)

Execution Steps

Prerequisites

OneWifi related

• Install bridge utils 
  • sudo apt-get install bridge-utils
• Mask running of wpa_supplicant with below commands and ensure that wpa_supplicant is not running after these steps using ps command.
  • sudo systemctl stop wpa_supplicant
  • sudo systemctl disable wpa_supplicant
  • sudo systemctl mask wpa_supplicant
  • sudo systemctl status wpa_supplicant 

• • 
    
• Configure brlan0 interface, IP Tables, DHCP 

  • Enable brlan0 interface and configure ip address

    • bashRDark
  • #IP tables command
    • bashRDark /proc/sys/net/ipv4/ip_forward" ashraf@raspberrypi:~/easymesh_project $ sudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE ashraf@raspberrypi:~/easymesh_project $ sudo iptables -A FORWARD -i eth0 -o brlan0 -m state --state RELATED,ESTABLISHED -j ACCEPT ashraf@raspberrypi:~/easymesh_project $ sudo iptables -A FORWARD -i eth0 -o brlan0 -j ACCEPT]]>
  • #dnsmasq for DHCP in background or in a different terminal
    • bashRDark

DB Setup commands (On controller)

• Setup mysql database one time running below command. Choose "n" for Remove anonymous users and Remove test database.
• sudo mysql_secure_installation
  • bashRDark
• Setup "OneWifiMesh" database with the below

• commands 
  • #Login to MariaDB monitor
    • sudo mysql -u root -p
  • #In MariaDB console
    • create database OneWifiMesh;
    • use OneWifiMesh;
    • show tables;                        ==> should show no tables
    • bashRDark create database OneWifiMesh; Query OK, 1 row affected (0.001 sec) MariaDB [(none)]> use OneWifiMesh; Database changed MariaDB [OneWifiMesh]> show tables; Empty set (0.001 sec) MariaDB [OneWifiMesh]>]]>
• Reset database and check tables are created
  • #In a separate window run easy mesh ctrl with <username of db>@<password> to connect to DB.
    sudo ./onewifi_em_ctrl root@root
    
    #In a separate window run easy mesh cli and run reset command "reset eth0 pi4" as specified below to reset the database
    sudo ./onewifi_em_cli
    <<OneWifiMeshCli>>: reset eth0 pi4
  • #After this in MariaDB Console you if you run "show tables;" you will see 7 tables created with NetworkSSIDList and NetworkList tables Initialized.
    • # All other tables will be empty
      MariaDB [OneWifiMesh]> show tables;
      +-------------------------+
      | Tables_in_OneWifiMesh   |
      +-------------------------+
      | BSSList                              |
      | DeviceList                         |
      | NetworkList                      |
      | NetworkSSIDList              |
      | OperatingClassList          |
      | RadioList                           |
      | STAList                              |
      +------------------------+

Now, kill the cli and ctrl windows.

Running instructions

• Run Easy mesh Controller and cli in separate windows. 
  • sudo ./one_wifi_em_ctrl root@root
  • sudo ./one_wifi_em_cli
• Run OneWifi first in a separate window and then run easy mesh agent
  • sudo ./OneWifi -c
  • sudo ./one_wifi_em_agent
• Check Below commands on cli window to see Agent configured 
  • <<OneWifiMeshCli>>:get_device OneWifiMesh
  • <<OneWifiMeshCli>>:get_radio OneWifiMesh
  • <<OneWifiMeshCli>>:get_bss OneWifiMesh
  • <<OneWifiMeshCli>>:get_ssid OneWifiMesh
• Check on the Agent that it is beaconing with the configured SSID

RDK Platform

Flashing

This section outlines two methods for flashing: Flashing using bmaptool (flashing steps in a Linux environment) and using balenaEtcher App (flashing in Windows).

Flashing using bmaptool

 Flashing using BalenaEtcher

To flash the image on an SD card in Windows, you will need to download the BalenaEtcher application: https://www.balena.io/etcher/.
*Note: Prefer to use a 32GB SD card, and there should be a minimum of 12GB of free space available in the device. Be sure to remove all other portable flash drives/hard drives/SD cards from your computer before flashing the RDK image.

• Open the application.
• Select the image.
• Select the drive containing your SD card.
• Click “Flash” to copy the image onto the SD card.

Install SD Card and Connect Your Device

• Insert the SD card into the microSD card slot on the underside of RPi4 and connect all the devices.
• Plug the USB power supply into a socket and connect it to your RPi4’s power port. A red LED light indicates that the RPi4 is connected to power and is booting.
• Type “root” when the login prompt is displayed
• Run following in the terminal to know IP address
  • $ ifconfig
• ssh to the RPi4 using ip address: ssh root@<RPi's ip address>

Validate OneWifi

ifconfig

Version.txt

Check for WiFi database

OneWifi status

All process status

OneWifi related DataModel

cat /rdklogs/logs

Core file:-

Should not observe

OneWifi core files in tmp folder.

WiFi tick mark , SSID, password,

channel, ssid advertisement, bandwidth, security mode in RDKB webui

Edit Wifi configuration like SSID,

password,

channel, ssid advertisement, bandwidth and security mode in webui

 On reboot, changed data should be persisted

On Factory reset of wifi, all default values to be

restored 

 Uptime: