Knowledge Arcana: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
The purpose of this page is to provide a dump of random useful facts which are not easily found anywhere else and are not easily categorized | The purpose of this page is to provide a dump of random useful facts which are not easily found anywhere else and are not easily categorized | ||
* There is a special network for IoT devices, in case you're working with a device that can't make it past the | == IoT Network / UAS-Special == | ||
* There is a special network for IoT devices, in case you're working with a device that can't make it past the EULA acceptance. | |||
*In Raspberry Pi you can drop this in /etc/wpa-supplicant/wpa-supplicant.conf and restart networking. Following that, the device should automatically load. | *In Raspberry Pi you can drop this in /etc/wpa-supplicant/wpa-supplicant.conf and restart networking. Following that, the device should automatically load. |
Revision as of 14:11, 16 July 2017
The purpose of this page is to provide a dump of random useful facts which are not easily found anywhere else and are not easily categorized
IoT Network / UAS-Special
- There is a special network for IoT devices, in case you're working with a device that can't make it past the EULA acceptance.
- In Raspberry Pi you can drop this in /etc/wpa-supplicant/wpa-supplicant.conf and restart networking. Following that, the device should automatically load.
Here is the /etc/wpa-supplicant/wpa-supplicant.conf config
country=GB ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev update_config=1 network={ ssid="uas-special" scan_ssid=1 psk="askflayorcoreyforpassword" mode=0 proto=WPA2 key_mgmt=WPA-PSK pairwise=CCMP group=CCMP auth_alg=OPEN id_str="nameofthedevice" priority=1 }