Background

Our LANforge WebGUI solution is used to support real client testing for access points. WebGUI combines with InterOp which gives the benefits of testing with real clients with customizable testing and reporting.

We have support for various kinds of real clients:

-      Android clients.
-      iOS clients.
-      Windows Machines.
-      Linux Machines.
-      MacOS Machines.

Testbed Setup

Hardware

1. USB Cables
2. Mobile Devices[Android, iPhone], Laptops[Linux, Windows, MacOS]
3. Switches
4. AP/Routers
5. LANforge Traffic Generator (CT523c/Noah2)
6. Ethernet Cables
7. USB Hubs

Configuration

After your testbed is configured, pick a non-existing and unique realm number, and cluster your InterOp devices by following the cookbooks below according to your device:

• Android: InterOp Setup for Android

• Linux: Installing LANforge Server on Ubuntu or Linux Machine

• Windows: Installing LANforge Server on a Windows Machine

• MacOS: Installing LANforge Server on a MacOS Machine

Once all the devices are clustered, they should show in the Status and Resource Mgr tab.

LANforge Upgrade

1. . The WebGUI uses the webGUI_update_dependencies.py in the lanforge-scripts/py-scripts/ directory to install packages required for the GUI. To upgrade the scripts directory, run the command line below in the lanforge terminal.

   sudo ./lf_kinstall.pl --do_lanforge 

2. . Upgrade the LANforge and interOp devices from the Resource Manager tab by selecting the LANforge and clustered devices.

   NOTE: LANforge WebGUI works after LANforge 5.4.7, Kernel version 6.2.16+.

Upgrade runtime logs can be found in the file 1. /root/var/log/lf_upgrade_stderr.txt and 2. /root/var/log/lf_upgrade_stdout.txt.

3. Once the upgrade is finished, the LANforge should auto-reboot.

WebGUI Licensing

The WebGUI needs special licensing. Check to verify correct licenses.

1. Navigate to the Control button highlighted in top left corner of LANforge Manager GUI and select Install License . The left-hand column shows the current installed license. There should be a WEBGUI row there.

2. If not installed and the license is handy, paste your new license in the right-hand side, click the OK button below, and reboot the machine by opening the terminal and typing: sudo reboot

Installing WebGUI Dependencies

1. After reboot, open a terminal and run:

cd /home/lanforge
su: [ENTER]
Password: [type in password and hit ENTER]
./lf_kinstall.pl --update_pip --do_webui --lfver 5.5.2
(instead of 5.5.2, replace with your correct LANforge version)

This command will update the python dependencies used in WebGUI by running the python script in /home/lanforge/scripts/py-scripts/webGUI_update_dependencies.py.

This upgrade takes approx 5-10 minutes to complete. Once completed, messages indicating completion of install should appear in the terminal.

2. Lastly, run (with your correct LANforge version, same as the one used above): sudo ./lf_kinstall.pl --do_webui --lfver 5.5.2 .
   This command fulfills dependences related to Django and Migrations.

3. After the terminal looks like the above, type in sudo reboot to reboot system.

Hosting WebGUI

1. After reboot, the LANforge should become reachable again. Open the LANforgeGUI via VNC or RDP.
   a. Click here to learn how to connect to LANforge via VNC Viewer

2. Open any browser (on a laptop on same network as LANforge) and type in
   

[Your LANforge IP]:5454. eg: '192.168.200.217:5454'
NOTE: You cannot use ‘localhost’ for the URL, it must be the management IP.

3. Click on Admin button in the top-right corner and login with user: lanforge and password: lanforge.

4. Add a tester if wanted. Under the RESOURCES tab, click + Add to add a tester. Pick their credentias.

5. Input Email, Password, and Name for tester.

6. To choose which panels should show up in the WebGUI, click on CHAMBER TESTS (right hand side) and App selections . This is where to choose if the Interop , DFS or Chamber View Tests panel show up in the WebGUI.
   

7. Now, the WebGUI login page will only display the panels which the tester has selected, and the tester can now start using the webGUI with their credentials.

8. Once logged in, input the management IP address of the testbed to be accessed and click Connect

9. Welcome to WebGUI!