NEXS Test Procedure

Test server

Perform the following tests to verify that the server is correctly installed and operational:

Basic network tests

1. Look at the neighborhood view. You should see a circle with the designation: schoolnet. The XO should be connected (shown as to semicircles outside the circle). If the XO is not connected, click on the circle to connect. NEXO should have supplied the WPA2 key automatically. If not,

enter: schoolnet when prompted. Once connected, continue the tests.

1. From the XO, ping the schoolserver (172.18.0.1). If that succeeds, ping the schoolserver (ping schoolserver). If that suceeds, ping the nameserver (ping 192.168.2.1 or the address you entered for the postinstall.sh script). If that suceeds, ping Google (ping www.google.com).
2. From a browser: access Google. Do a search (e.g. OLPC). Access wiki.laptop.com.
3. From a browser: access the schoolserver (http://schoolserver). You should see the school's Moodle page. If Moodle registration was successful,

you will be logged in (upper right hand on the screen) as the user of the XO showing the courses for the XO owner's grade. If not, you will not be logged in and will see all of the school's courses.

Test the 'server' connection

1. Register the XO. If the XO does not show the registration option (along with restart, shutdown), then you need to use a terminal window. Go to /home/olpc/.sugar/default. Use nano (sudo nano config) to edit the file: config.
2. Delete (ctl + k) the two lines:
   • [Server]
   • backup1
3. Enter ctl + x to exit nano (answer y to save the change). Now reboot the XO and you should see the register option.
4. In a terminal window enter: olpc-netstatus You should see under telepathy the word "gabble". This means the XO is using the AP for it's mesh (XO-XO) connections.
5. Start a second XO. The two XO's should see each other in the neighborhood view. Start Chat on each XO. You should be able to

see each other in the chat room and type messages between the two XOs.

Test Content

1. Select software update on the Sugar Control Panel (XO icon in home view). Verify that Activities on the schoolserver are checked to verify that the set of Activities on the XO are up to date.
2. Select E-Pustakalaya. Verify that the XO has access to the E-Pustakalaya library on the schoolserver.
3. Select a few XO's and connect them to the server. Open the chat activity and chat together.
4. Download a file (Large Video file??) simultaneously in around 5-10 XO's.

Additional Tests

Network and Server

1. Connect to Access Point w/ WPA-2 encryption
2. Register w/ XS
3. Update Activities by using Browse to access activities on the XS
4. Back up files to XS and verify
5. Restore files from XS
6. Use the Activity Updater in the Sugar Control Panel to update E-Paath
7. Install an activity manually: insert a USB key that holds sugar activities. Access the USB key from the Journal and install the Sugar activity
8. Try to access http://www.persiankitty.com , Dansguardian should block it
9. Test that caching working on XS

Activity Updating

1. rm -rf /home/olpc/Activities/E-Paath*, restart Sugar, then go to activity update in the Control Panel. Add only E-Paath activities. Restart Sugar, then check if E-Paath works

XO updating

1. for every point below, check this link to get more info on what to do precisely: http://redmine.olenepal.org/wiki/deployment/NEXO_updating

1 - Update new build through olpc-update from usb-stick 2 - Update new build through olpc-update from an update server 3 - Update by flashing the XO 4 - Updating through NAND-blasting