connman-services manual

critical

Image Types:
basesdk-amd64 / hmi-armhf / hmi-arm64 / hmi-amd64 / sdk-amd64
Image Deployment:
APT, OSTree
Type:
functional

Description

Tests Network connection management: ensuring that ConnMan can connect to actual networks is part of strategic network management functionality.

Pre Conditions

  1. The device must have wifi, otherwise skip this test.
  2. Please note that connman disables wifi by default on a fresh image. To enable:
    3. $ connmanctl enable wifi
  3. If it's already enabled, connmanctl will give the error "Error wifi: Already enabled" that may be ignored.

Execution Steps

  1. Run the ConnMan CLI Interface:
    2. $ connmanctl
  2. When run without arguments, connmanctl will launch in interactive mode with a "connmanctl>" prompt.
  3. Scan wifi:
    4. $ scan wifi
  4. Wait for "Scan completed for wifi" before continuing (this may take a few seconds and will appear above connmanctl prompt).
  5. Turn on the agent, to manage additional information if required:
    6. $ agent on
  6. connmanctl should return "Agent registered".
  7. List services available:
    8. $ services
  8. Select required service and use the "service ID" (second column) to connect:
    9. $ connect <service ID>
  9. If it's connecting to a wifi service that needs additional information connmanctl will output an "Agent RequestInput (…)" line followed by a prompt for the required information, such as "Passphrase? ".
  10. Ensure ConnMan returns "Connected <service ID>" before continuing.
  11. Quit from connmanctl interactive mode with:
    12. $ quit
  12. Use the tool to test different kind of security and ConnMan technology: Ethernet, Wi-Fi, cellular and Bluetooth.

Expected

If success "Connected <service ID>" will be printed by connmanctl, otherwise "Agent ReportError <service ID>" will be printed.

Notes

  • Warning: Connman changes are persistent (over reboot!). After finishing testing, it might be wise to perform the dhcp test to ensure that the network is in a sensible state.
  • For ALL tests the enable step will give an "In progress" error if the device is already enabled. This is to be expected.
  • When testing the SDK image in VirtualBox with an Asus USB-N10 Wireless adapter, firmware-realtek needs to be installed on the host.