Closed Luuii closed 10 years ago
Those are the source files in git, but they get copied into /etc/wpa_supplicant/ when I do a build. The .reset one will overwrite the other file if the user resets the device by placing a reset.txt file in the coder_settings folder of the SD Card.
The user can manipulate the contents of this file by editing wpa_supplicant.txt on the sd card (put the sd card in another computer and edit the contents). A sample can be found in /coder_settings/reset_files/wpa_supplicant.txt. Copy that up one directory, edit it with your settings, and next time Coder boots, it will ingest this file as its own configuration and put it in /etc/wpa_supplicant/wpa_supplicant.conf.
Thank you Jason, I am working on it. There is AN another thing, I am experiment the communication with Coder with the USB WIFI, and in this case the URL is 192.168.0.1. But not always appear active the WIFI network device. Sometimes it seems like is not activate it by the coder system, in any case the USB WIFI lights on the led built in. I am asking of what conditions depends the usb device to do a successful connection in Coder via WIFI.
If I would like to change the name of the SSID CoderConfig to an another. Which way will be the best. Maybe could be edit this three files ?
raspbian-addons/etc/wpa_supplicant/wpa_supplicant.conf id_str="anyopen" }
network={ ssid="CoderConfig" mode=1 key_mgmt=NONE id_str="staticadhoc" }
raspbian-addons/etc/wpa_supplicant/wpa_supplicant.conf.reset
Ad-hoc network if it can't find a WiFi connection.
network={ ssid="CoderConfig" mode=1 key_mgmt=NONE id_str="staticadhoc"
raspbian-addons/boot/coder_settings/reset_files/wpa_supplicant.txt
Ad-hoc network if it can't find a WiFi connection.
network={ ssid="CoderConfig" mode=1 key_mgmt=NONE id_str="staticadhoc"