-
Notifications
You must be signed in to change notification settings - Fork 20
/
Copy pathNOTES.txt
71 lines (50 loc) · 2.6 KB
/
NOTES.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
Notes for TIP WiFi testing related topics.
# To pull the latest upstream lanforge-scripts repo into the wlan-lanforge-scripts
# repository, use this or similar command. This action will probably only be done
# by whoever is curating the wlan-lanforge-scripts repository.
git pull [email protected]:greearb/lanforge-scripts.git
# Testbed setup
Test-Controller system must be able to ssh into the LANforge system w/out a password
(use authorized_keys ssh setup) as both user lanforge and user root.
Test-Controller will need to be able to access the Cloud-SDK machines. Not sure
exact details on this yet.
Serial ports must be make available to non-root users, command like this for each serial port:
chmod a+rwx /dev/ttyUSB0
For each new test-bed hardware config (including LANforge and AP hardware types and radio
layouts), a new directory in testbeds/ should be created, and populated with test-bed specific
LANforge scenario and test configuration files. See 'ben-home' for examples.
See lanforge/lanforge-scripts/gui/README.txt for details on ways to grab the appropriate text,
but you will also need familiarity with LANforge to accomplish this easily.
# Test controller setup. Assuming Fedora-30 or similar is installed.
# Enable vnc, install some things, disable selinux so vnc will work.
./lf_kinstall.pl --do_vnc --do_pkgs --do_selinux 0
# As user lanforge (or other user should work too)
# You will need to put the proper keys in ~/.ssh/ in order to
# do the clone.
mkdir ~/git
cd ~/git
git clone [email protected]:Telecominfraproject/wlan-testing.git
git clone [email protected]:Telecominfraproject/wlan-lanforge-scripts.git
cd wlan-testing/lanforge
ln -s ../../wlan-lanforge-scripts lanforge-scripts
# Make a copy of a test bed similar to what you have, for instance:
cd ~/git/wlan-testing/testbeds
cp -ar example_test_bed my_new_test_bed
# Edit the new test bed details as needed, this may be somewhat tricky
# if your test bed is different from others.
# See ~/git/wlan-lanforge-scripts/gui/README.txt for some hints on setting up
# scenarios and such.
# On LANforge machine, make sure GUI is in auto-start mode:
https://www.candelatech.com/cookbook/misc/autostart
* Create uplink-nat profile.
* Create upstream DUT
* Create AP DUT
* Create scenario that uses uplink-nat profile and upstream-dhcp to provide VR+NAT access to the world.
* Add stations for the radios, properly linked to DUT radio(s).
* Create WCT test, verify it works OK, save scenario
* Interleave sort, set pass/fail limits
* Create AP-Auto test
* configure DUT
* configure radios
* configure advanced (dual-band only in our case)
* configure stability settings