Some devices can be configured for wireless network connectivity, though the methods available for doing so vary by model.

Don’t put two interfaces on the same subnet! It’s not an AppNeta thing, just one of the fundamentals of routing. So, either set up the wireless interface to be in a separate subnet, or just disconnect the ethernet cable after wireless is set up.

Web admin

  1. Complete device setup.
  2. Log in to web admin.
  3. Click ‘network configuration’.
  4. Click ‘add wi-fi interface’.
  5. Make your changes.
  6. Restart networking.
  7. Check the interface status. The web admin home page shows the status of the wireless interface; there are three possible states: connected, configured but not connected, not configured. The wireless LED, if present, indicates the same three states.
  8. Verify that the new interface acquired an ip address from > Manage Monitoring Points. Look for ‘local network interfaces’ in the right side panel.

Admin API

  1. Complete device setup.
  2. Discover the device hostname at > Manage Monitoring Points.
  3. Find out what interfaces are already configured:
    1. Plug the device hostname into this url.
    2. Under the interface resource open GET /interface/ and click submit.
    3. If you see the wireless interface ‘wlan0’ in the returned list of interfaces, the wireless interface is already configured and you don’t need to go any further.
  4. If you are connecting to an access point that uses WPA2 Enterprise authentication, you might need to upload a CA certificate, client certificate, and/or a client private key before configuring the interface.
    1. Open POST /interface/file/ to upload these files. It also contains a description of the supported formats.
  5. Open POST /interface/ to configure the wireless interface.
  6. Sub in your wireless ssid, key/password, and certificate file names into one of these json objects: WEP, WPA-PSK, WPA2 Enterprise (PEAP), WPA2 Enterprise (TLS)
  7. Paste it into the white box.
  8. Click submit.
  9. In the response, look for 'success': true, which lets you know that the interface was successfully created and configured.
  10. Restart the networking service in order to apply the changes.
    1. Under the service resource open PUT /service/{service_name}/.
    2. Set service_name to ‘networking, action to ‘restart’, and then click submit. You will briefly lose connectivity to the admin API.
  11. Verify that your new interface exists by repeating Step 3.
  12. Verify that the new interface acquired an ip address from > Manage Monitoring Points. Look for ‘local network interfaces’ in the right side panel.

curl

  1. Complete device setup.
  2. Discover the device hostname at > Manage Monitoring Points.
  3. Find out what interfaces are already configured.

    curl -X GET --header "Accept: application/json" "https://HOSTNAME/api/v1/interface/?config_state=active"
    
  4. If you are connecting to an access point that uses WPA2 Enterprise authentication, you might need to upload a CA certificate, client certificate, and/or a client private key before configuring the interface.

    curl -k -X POST --header 'Expect:' --header 'Content-Type: multipart/form-data' --header 'Accept: application/json' -F wpa_ca_cert=@FULL_PATH_TO_FILE -F wpa_client_cert=@FULL_PATH_TO_FILE -F wpa_private_key=@ FULL_PATH_TO_FILE https://admin:ADMINPASS@APPLIANCEIP/api/v1/interface/file/
    
  5. Create a file called wifi-config.json containing one of the objects from the admin API section. Make sure you sub in your details.
  6. Add a new wireless interface.

    curl -k -X POST --header "Content-Type: application/json" --data-binary @wifi-config.json https://admin:ADMINPASS@HOSTNAME/api/v1/interface/
    
  7. Verify that your changes are pending.

    curl -k https://admin:ADMINPASS@HOSTNAME/api/v1/interface/?config_state=pending
    
  8. Restart networking. You will briefly lose connectivity to the admin API.

    curl -k -X PUT --header "Content-Type: application/json" https://admin:ADMINPASS@HOSTNAME/api/v1/service/networking?action=restart
    
  9. Verify that your new interface exists by repeating Step 3.
  10. Verify that the new interface acquired an ip address from > Manage Monitoring Points. Look for ‘local network interfaces’ in the right side panel.

USB

  1. Complete appliance setup.
  2. If you are connecting to an access point that uses WPA2 Enterprise authentication, you might need to upload a CA certificate, client certificate, and/or a client private key before configuring the interface. Since file uploads using usb aren’t currently supported, you’ll need to use curl or the admin API to upload these files.
  3. Download the wireless config file from here, and save it to an empty, fat32-formatted usb stick.
  4. Uncomment the section you need and replace specify the items in arrow brackets.
  5. Insert the usb stick into your appliance. The status led changes from heartbeat to rapid beat. The status returns to a heartbeat once the configuration is completed.
  6. Verify that the new interface acquired an ip address from > Manage Monitoring Points. Look for ‘local network interfaces’ in the right side panel.