The Serval Project Wiki

User Tools

Site Tools

You are here: The Serval Project Wiki » content » Serval Mesh » Release Testing » Automatic Wi-Fi mode cycling
Trace: • Automatic Wi-Fi mode cycling
content:servalmesh:testing:wifi_auto_mode_cycling:main_page

Table of Contents

Automatic Wi-Fi mode cycling

Fixture

  1. A Wi-Fi hotspot with no Serval peers associated, called Brian for this test
  2. No Serval Mesh phones running within Wi-Fi range
  3. A workstation (laptop) connected to the Brian Wi-Fi hotspot
  4. Three rooted devices A B C with Release Candidate installed, set up with the following Phone Numbers and Names:
    • 55501 TestA
    • 55502 TestB
    • 55503 TestC
  5. Ensure each device A, B and C is connected in Ad Hoc mode:
    1. Ensure Auto Cycle is OFF (un-check the checkbox if necessary)
    2. Go to Serval main screen → Connect
    3. Ensure Enable Services is ON (check the checkbox if necessary)
    4. Select the mesh.servalproject.org Mesh network
    5. Ensure the mesh.servalproject.org Mesh network shows as On within a few seconds:
      • If it does not, then Select Wi-Fi Ad Hoc mode should also fail, which is the correct place to attach a full diagnostic report
    6. Go to peer list: Serval main screen → Contacts → List Phones On The Mesh)
    7. Ensure that the peer list shows ONLY the other two devices:
      • If any device other than A B C is present, remove it from Wi-Fi range or switch it off
      • If devices A B and C do not all see each other as peers, then Peer list shows all nearby Batphones should also fail, which is the correct place to attach a full diagnostic report

Test

  1. On each device B and C, turn off Serval Mesh:
    1. Go to Serval main screen → Connect
    2. Turn Enable Services to OFF (un-check the checkbox)
    3. ASSERT The mesh.servalproject.org Mesh network disconnects: the On indicator disappears within a few seconds
  2. On device A:
    1. Go to Serval main screen → Connect
    2. Turn Auto Cycle to ON (check the checkbox)
    3. Select the Brian Open or Secured network
    4. ASSERT Device A associates to Brian network and is reachable from workstation, eg, using the ping command
  3. On device B:
    1. Turn Enable Services to ON (check the checkbox)
    2. Select the Brian Open or Secured network
    3. ASSERT Device B associates to Brian network and is reachable from workstation, eg, using the ping command
    4. Turn Enable Services to OFF (un-check the checkbox)
    5. ASSERT Device B remains associated to Brian network and is reachable from workstation, eg, using the ping command
  4. On device A:
    1. Select the ap.servalmesh.org HotSpot network
    2. ASSERT After a few seconds, ap.servalproject.org HotSpot network is marked as Connected
  5. ASSERT Device A cycles through the following Wi-Fi modes automatically:
    1. ap.servalproject.org Mesh
    2. ASSERT Device A is visible as an Access Point from other nodes on the network, eg, on Networks menu or using sudo iwlist wlan0 scan command
    3. Wait up to five minutes
    4. mesh.servalproject.org Mesh
    5. Wait up to five minutes
    6. Brian Open or Secured
    7. ASSERT Device A associates as client of Brian network and is reachable from workstation, eg, using the ping command
    8. ASSERT Device A remains in Client mode until Brian disassociates, which can be simulated by manually turning off Wi-Fi on device A:
      • EITHER Pull down Android status bar and un-check Wi-Fi box
      • OR Go to Android Wi-Fi settings menu and un-check Wi-Fi box
    9. Off
    10. Wait up to five minutes, repeat from top

Results

content/servalmesh/testing/wifi_auto_mode_cycling/main_page.txt · Last modified: 19/09/2013 22:17 by Andrew Bettison

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution 4.0 International
CC Attribution 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki