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
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
Dan Williams <d...@redhat.com> writes:
> On Wed, 2017-05-03 at 22:33 +0200, Julien Cubizolles wrote:
>> It turns out that the problem lies with NetworkManager, I managed to
>> get
>> the wifi working with wpa_supplicant.
>
> That's odd. Any idea what that wa
Julien Cubizolles <j.cubizol...@free.fr> writes:
> I can't connect anymore to my home wifi since upgrading my machine from
> Ubuntu 16.10 to Ubuntu 17.04.
It turns out that the problem lies with NetworkManager, I managed to get
the wifi working with wpa_supplicant.
Julien.
I can't connect anymore to my home wifi since upgrading my machine from
Ubuntu 16.10 to Ubuntu 17.04.
The problem exists with kernel 4.10.0-20-generic from Ubuntu, and
remains with kernel 4.11.0-rc6 that I built from
linux-wireless. However, I can connect to a wifi network without
authentication.
Amitkumar Karwar writes:
> Could you check if attached patch fixes your connection problem with WPA AP?
It seems ok so far. I have set my home router back from WPA2 to WPA and
I can successfully connect. I'll let you know if I experience some
problems with it.
Thanks for
Amitkumar Karwar writes:
> Thanks for the logs. We found one bug in our code. We expect vendor
> specific IE at the beginning of IE buffer otherwise connection is
> rejected.
> We will prepare a fix and get back.
Thanks a lot for making my laptop usable again. I'll be
Amitkumar Karwar writes:
> Thanks for the logs. I compared your network manager log with the one
> on my setup. Both are same. Basically network manager log doesn't show
> security info (WPA/WPA2, encryption mode etc). So we can't rely on
> that.
> I checked your kernel log
Dan Williams writes:
> He actually meant the wpa_supplicant configuration file, not the
> supplicant's dbus config file. But when driven by NetworkManager, there
> is no supplicant configuration file.
Sorry about that.
> Instead, you can find out what config NM is pushing to
Amitkumar Karwar writes:
> Hi Julien,
>
>>Yes, I'm using NetworkManager, version 1.0.4-ubuntu5, and I'm guessing
>>it's using wpa_supplicant. I deleted the configuration for this network
>>and created it again. The network is configured for WPA in
>>NetworkManager but I
Dan Williams <d...@redhat.com> writes:
> On Mon, 2015-10-26 at 16:51 +0100, Julien Cubizolles wrote:
>> I can't connect anymore to my home wifi since upgrading my machine from
>> Ubuntu 15.04 to Ubuntuy 15.10. I was previously running kernel 4.3.0-rc2
>> from kernel.org
I can't connect anymore to my home wifi since upgrading my machine from
Ubuntu 15.04 to Ubuntuy 15.10. I was previously running kernel 4.3.0-rc2
from kernel.org without any problem. After the upgrade, and with the
same kernel, I couldn't connect anymore. I built 4.3.0-rc7, and the
problem remains.
Amitkumar Karwar akar...@marvell.com writes:
Thanks for reporting this. We will take a look at this right away.
We don't have significant changes after 4.2.0-rc3.
Well there were the two patches you pointed at that fixed a very serious
problem for me. Actually are these included in some
I'm running kernel 4.2.0-rc3 with the following patches to the mwifiex
driver, thanks to your advice.
Do you have following USB chipset specific fixes included?
http://www.spinics.net/lists/linux-wireless/msg129129.html
http://www.spinics.net/lists/netdev/msg334367.html
I've recently noticed
Amitkumar Karwar akar...@marvell.com
writes:
This looks like a command timeout problem probably caused due to a bug in
firmware.
How frequently do you see this problem? Are there any specific steps to
recreate it?
Surprisingly, it's reproducible:
loading
Amitkumar Karwar akar...@marvell.com
writes:
Hi Julien,
Thanks for reporting the problem. We now have a separate mechanism for
debug logs and don't support dynamic debugging anymore.
Issue below command to enable logs and share them.
echo 0x
I'm running vanilla kernel 4.2.0-rc3 on a Microsoft Surface Pro. The
wifi (module mwifiex) freezes the whole system after a few seconds of
use. The problem appeared around kernel 3.19.
I've tried to get some debug info with the dynamic debugging method,
using the following:
--8---cut
17 matches
Mail list logo