ProGlove Documentation
When providing your network credentials in the network.json file, you can also include additional fields in the file to adjust the network authentication protocols or even provide multiple networks’ details.
Note
Configuring additional network settings using the network.json requires the Gateway firmware version 1.10.0.
Wi-Fi fields
The main field that contains the list of Wi-Fi credentials and settings is wifi_auth and can contain the following fields:
The SSID of the access point, i.e. the network’s name.
The SSID can have maximum 32 characters.
Whether the network is visible or hidden.
Auto-connect priority. Networks with higher priority will be connected to first.
For connections with identical values, the behavior is undefined and left up to the network manager.
The authentication method used.
IP settings for the specific interface
WPA Personal
If you are using the WPA Personal authentication method, in the network.json file, add wpa_psk holding the psk (pre-shared key) field and put your network’s password as value.
WPA Enterprise (EAP)
If you are using the WPA Enterprise authentication method, in the network.json file, add the wpa_eap field that can hold the following fields and values:
The anonymous identity used to talk to the proper RADIUS server.
The identity value can have 0-128 characters.
The domain / realm of the RADIUS server.
The domain value can have 0-128 characters.
The path to a CA root certificate used to authenticate the RADIUS server.
A relative path in the archive to the PEM certificate.
The type of WPA-Enterprise authentication.
EAP-TLS
If you are using the EAP-TLS authentication method, in the network.json file, add the eap_tls field that can hold the following fields and values:
The identity (username) stored in the RADIUS server database to authenticate the client.
The identity value must have 1-128 characters.
The path to the user’s public certificate.
The relative path in the archive to the PEM certificate
The path to the user’s private key.
The relative path in the archive to the PEM certificate
The private key password used to open it.
EAP-TTLS
If you are using the EAP-TTLS authentication method, in the network.json file, add the eap_ttls field that can hold the following fields and values:
The identity (username) stored in the RADIUS server database to authenticate the client.
The identity must have 1-128 characters.
The password associated with the identity.
- EAP_TTLS_INNER_AUTH_PAP
- EAP_TTLS_INNER_AUTH_MSCHAPV2
- EAP_TTLS_INNER_AUTH_MSCHAPV2_NO_EAP
- EAP_TTLS_INNER_AUTH_CHAP
- EAP_TTLS_INNER_AUTH_MD5
- EAP_TTLS_INNER_AUTH_GTC
PEAP
If you are using the PEAP authentication method, in the network.json file, add the peap field that can hold the following fields and values:
The identity (username) stored in the RADIUS server database to authenticate the client.
The identity must have 1-128 characters.
The password associated with the identity.
Interface settings
Important
Interface settings are supported on Gateways with firmware version 2.1.0 and above.
Dynamic Host Configuration Protocol (DHCP) is used by default for IPv4 and IPv6 if no settings are specified.
IP Settings
The following settings are common to IPv4 and IPv6:
The type of IP assignment
The addresses to use in case of a manual method.
See below for IPv4 and IPv6 addresses.
The address to assign to the Gateway.
The IP netmask to use (can be either the IPv4 address or a number).
The address of the network gateway (not to be confused with the ProGlove Gateway device).
The address to assign to the Gateway.
The prefix length of the network.
The address of the network gateway (not to be confused with the ProGlove Gateway device).
External certificates
If your selected authentication method includes required fields like user_cert_path and private_key_path or optional fields like ca_cert_path , you have to include the targeted certificates in the zipped provisioning file.
The example below displays a case where a single network.json file is used for provisioning the Gateway with credentials to connect to multiple networks using four authentication protocols: WPA Personal, EAP-TTLS, PEAP, and EAP-TLS.
There are three external certificates referenced inside the following fields of the network.json file:
To provision the Gateway with these certificates, include the .pem files in the same folder with the network.json file, zip them together and apply the provisioning file.