<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Jan 24, 2017 at 7:39 PM, A. F. Cano <span dir="ltr"><<a href="mailto:afc@shibaya.lonestar.org" target="_blank">afc@shibaya.lonestar.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Arrgh! The timing of my posting... Found one answer minutes after<br>
sending it.<br>
<br>
On Tue, Jan 24, 2017 at 09:33:09PM -0500, A. F. Cano wrote:<br>
>...<br>
<span class="gmail-">> If someone knows what combination of parameters need to be set and how,<br>
> to provide an open network I'd be willing to try that too. The ones that<br>
> seemed relevant (see below) that I changed all resulted in crashes. I<br>
> probably changed more than I remember now, with the same result.<br>
<br>
</span>I managed to connect by making the link open (no wpa). I commented the<br>
following options: (all the wpa-related ones)<br>
<br>
# wpa=1<br>
# wpa_passphrase=InsideWifI4fonE<br>
# wpa_key_mgmt=WPA-PSK<br>
# wpa_pairwise=TKIP CCMP<br>
<br>
I would still prefer to be able to connect securely... Any hints?<br>
<br>
Thanks.<br>
<span class="gmail-HOEnZb"><font color="#888888"><br>
A.</font></span><br></blockquote><div><br></div><div>I have an original Liva (not the Liva X) which I'm using as a WiFi extender in the back part of my house (I'm actually connected to it now). I'm using Gentoo, and I don't know if the hardware is the same (mine uses the Broadcom FULLMAC WLAN module with brcmfmac43241b4-sdio.bin firmware), but I can't use a kernel newer than 3.18.7 or the WiFi access point stops working after a few hours. I tried doing a kernel bisect to find the offending commit, but ran into a kernel panic on boot in some of the bisects which made it impossible to determine if the problem existed in the bisected version or not. I ran out of time and motivation or I would have done another bisect to find a patch which would revert the kernel panic commit so I could focus back on the WLAN. I didn't try removing security as you did, but that might be an interesting avenue of exploration. This information may not be useful to you, but if it's possible you might try reverting the kernel to 3.18.7 and see if you have any better luck.<br><br></div><div>Karl<br></div></div></div></div>