[arm-allstar] VERY IMPORTANT

[Doug Crompton]

I run wireless here on several nodes and there is nothing changed in the
custom file after updates. I am not clear on the snippet you sent as that
is NOT in the standard custom file. The custom file is created by the
wireless setup in the ADMIN menu. It creates segments like this -

network={
    ssid="DMXNETNET"
    #psk="some_passphrase"
    psk=c0a491d008f1a39cfe1f93ab3bd7a946dd7f0c2e43a52054c1a48034eb4bfc17
}

If you are doing something custom beyond that then yes you do in fact need
to manually edit the file and not use the standard setup to do it.


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*



On Mon, Oct 30, 2017 at 11:13 AM, "Tony Ross via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> On 10/29/2017 11:03 PM, "Doug Crompton via arm-allstar" wrote:
>
> The recent wpa_supplicant update required a reboot which was not forced. As
>> reliable as the Pi's are sometimes we forget that it is occasionally a
>> good
>> thing to reboot. I have had servers running well over a hundred days and
>> in
>> one case almost a year! It is highly recommended that all users update and
>> then reboot their systems whenever that is convenient.
>>
>
> Apparently the wpa_supplicant update re-writes the
> /etc/wpa_supplicant/wpa_supplicant_custom-wlan0.conf file using a simple
> wpa_passphrase implementation. This broke the wifi on my node until I
> manually edited the above file from a backup as follows:
>
> network={
>         ssid="thessid"
>         psk=thepsk
>         proto=RSN
>         key_mgmt=WPA-PSK
>         pairwise=CCMP
>         auth_alg=OPEN
> }
>
> .... just in case someone else might be experiencing a similar issue.
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org