Example JSON for Wireless
The following examples show configurations for wireless interfaces with DHCP and various authentication methods. These can be used with the POST /interface/ Monitoring Point API endpoint. Also, note that:
- For each example, all fields except the last require a comma at the end. The last field must not have a comma.
- For certificate and key file names, you only have to specify the file name, not the path.
- For any of the examples below, include “wpa_scan_ssid”: “1” when connecting to an access point that does not broadcast its SSID.
WEP
{
"method": "dhcp",
"name": "wlan0",
"wpa_key_mgmt": "NONE",
"wpa_ssid": "<wireless ssid>",
"wpa_wep_key0": "<wireless key>",
"wpa_wep_tx_keyidx": "0"
}
WPA-PSK
{
"method": "dhcp",
"name": "wlan0",
"wpa_key_mgmt": "WPA-PSK",
"wpa_psk": "<wpa passphrase>",
"wpa_ssid": "<wireless ssid>"
}
WPA2 Enterprise (PEAP)
For WPA2 Enterprise, if a private CA certificate is required for authentication, include the following line. Note that all lines except the last have a trailing comma:
“wpa_ca_cert”: “<ca cert file>”
{
"method": "dhcp",
"name": "wlan0",
"wpa_ap_scan": "1",
"wpa_eap": "PEAP",
"wpa_group": "CCMP",
"wpa_pairwise": "CCMP",
"wpa_identity": "<username>",
"wpa_password": "<password>",
"wpa_key_mgmt": "WPA-EAP",
"wpa_phase2": "auth=MSCHAPV2",
"wpa_proto": "RSN",
"wpa_ssid": "<wireless ssid>"
}
WPA2 Enterprise (TLS)
{
"method": "dhcp",
"name": "wlan0",
"wpa_ap_scan": "1",
"wpa_eap": "TLS",
"wpa_group": "CCMP",
"wpa_pairwise": "CCMP",
"wpa_identity": "<username>",
“wpa_password”: “<password>“,
"wpa_key_mgmt": "WPA-EAP",
"wpa_phase2": "auth=MSCHAPV2",
"wpa_proto": "RSN",
"wpa_ssid": "<wireless ssid>",
"wpa_ca_cert": "<ca cert file>",
"wpa_client_cert": "<client cert file>",
"wpa_private_key": "<client private key file>",
"wpa_private_key_passwd": "<client private key password>"
}