Hello Lennert and David
Sorry for jumping and recalling directly your conversation, but this
already contains a lot of relevant information.
I am an user of two Linksys EA4500 running mwl8k driver on Marvell
88W8366 v48 bot 2.4 and 5.0 Ghz radio.
I run LEDE 17.01.1
I have always hit the problem you
Dan Williams writes:
> Just to test, could you add:
>
> auth_alg=OPEN
> key_mgmt=WPA-PSK
> scan_ssid=1
>
> to the block and retry with the supplicant? I don't know why those
> would make a difference but they might.
They don't: wpa_supplicant still connects with these settings.
On Sat, May 06, 2017 at 03:47:50AM +1000, Ian W MORRISON wrote:
> The following patch was sent to linux-wireless@vger.kernel.org and
> various wifi driver developers however I've just realized that I
> should have sent it to driverdev-de...@linuxdriverproject.org. It was
> reviewed on 01 May with t
On Fri, Apr 28, 2017 at 08:50:05AM +1000, Ian W MORRISON wrote:
> This patch is to remove the re-positioned call to kfree() in
> drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c which otherwise
> results in segmentation fault.
>
> Signed-off-by: Ian W Morrison
> ---
> drivers/staging/rtl8723bs/
Use memdup_user() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
drivers/net/wireless/ti/wlcore/debugfs.c | 13 +++--
1 file changed, 3 insertions(+), 10 deletions(-)
diff --git a/drivers/net/wireless/ti/wlcore/debugfs.c
b/drivers/net/wireless/ti/wl
Use memdup_user() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
drivers/net/wireless/ath/wil6210/debugfs.c | 12
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/drivers/net/wireless/ath/wil6210/debugfs.c
b/drivers/net/wireless/ath
On Sat, 2017-05-06 at 10:41 +0200, Julien Cubizolles wrote:
> Dan Williams writes:
>
>
> > Just to test, could you add:
> >
> > auth_alg=OPEN
> > key_mgmt=WPA-PSK
> > scan_ssid=1
> >
> > to the block and retry with the supplicant? I don't know why those
> > would make a difference but they mi
Dan Williams writes:
> Ok, at this point the only thing I can think of is the MAC
> randomization that NM has. Please see:
>
> https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/
>
> and look at the section "Randomization during Wi-Fi scanning" where it
> sa
