>>> wlp5s0: WPA: IGTK keyid 1024 pn d0caa82e44b2
>>> WPA: IGTK - hexdump(len=16): [REMOVED]
>>> wpa_driver_nl80211_set_key: ifindex=3 (wlp5s0) alg=4 addr=0x55e7e55d2909
>>> key_idx=1024 set_tx=0 seq_len=6 key_len=16
>>
>> A key_idx=1024 looks wrong, it should be 4 or 5 for IGTK. I tend to
>> think
>>> wlp5s0: WPA: IGTK keyid 1024 pn d0caa82e44b2
>>> WPA: IGTK - hexdump(len=16): [REMOVED]
>>> wpa_driver_nl80211_set_key: ifindex=3 (wlp5s0) alg=4 addr=0x55e7e55d2909
>>> key_idx=1024 set_tx=0 seq_len=6 key_len=16
>>
>> A key_idx=1024 looks wrong, it should be 4 or 5 for IGTK. I tend to
>> think
Hi,
On Thu, 31 Jan 2019 at 09:57, Beniamino Galvani wrote:
> On Thu, Jan 31, 2019 at 02:44:58AM +, Different55 wrote:
> > > Could you please configure a more verbose debug level and paste the
> > > lines related to the IGTK just before "Failed to configure IGTK"?
> > >
> > > Disabling PMF in
On Thu, Jan 31, 2019 at 02:44:58AM +, Different55 wrote:
> > Hi,
> >
> > Could you please configure a more verbose debug level and paste the
> > lines related to the IGTK just before "Failed to configure IGTK"?
> >
> > Disabling PMF in NetworkManager would probably solve the problem:
> >
> > nm
On Mon, Jan 28, 2019 at 10:36:16AM +0100, Andrej Shadura wrote:
> On Wed, 16 Jan 2019 at 21:51, Different55 wrote:
> >
> > Alright, not entirely sure if I did this right but I followed Debian's
> > Building Tutorial to download and build wpa_supplicant with the changes you
> > linked. One except
On Wed, 30 Jan 2019 at 19:57, Kurt Meyer wrote:
>
> wpasupplicant v2:2.7+git20190128+0c1e29f-1 seems to have fixed the issue
> here. I'm using a Broadcom BCM4352 Wi-Fi card.
Wow, that’s very good to hear! Diff, have it fixed it for you? Thanks
in advance for testing.
--
Cheers,
Andrej
wpasupplicant v2:2.7+git20190128+0c1e29f-1 seems to have fixed the issue
here. I'm using a Broadcom BCM4352 Wi-Fi card.
On 1/29/19 1:32 AM, Andrej Shadura wrote:
(Sending this again since the first submission’s got delayed by a filter.)
On Wed, 16 Jan 2019 at 21:51, Different55 wrote:
Alright, not entirely sure if I did this right but I followed Debian's Building
Tutorial to download and build wpa_supplicant
(Sending this again since the first submission’s got delayed by a filter.)
On Wed, 16 Jan 2019 at 21:51, Different55 wrote:
>
> Alright, not entirely sure if I did this right but I followed Debian's
> Building Tutorial to download and build wpa_supplicant with the changes you
> linked. One exce
On Wed, 16 Jan 2019 at 21:51, Different55 wrote:
>
> Alright, not entirely sure if I did this right but I followed Debian's
> Building Tutorial to download and build wpa_supplicant with the changes you
> linked. One exception, I use wpa_supplicant through NetworkManager and could
> not work out
Sure thing! Sadly doesn't seem to make a difference. I've included another log,
this time starting from the time wpa_supplicant was brought back up to a little
bit after I got the popup that the connection had failed.
Thanks,
Diff
‐‐‐ Original Message ‐‐‐
On Saturday, January 26, 2019 2
On Sun, 13 Jan 2019 at 04:18, Different55 wrote:
>
> Package: wpasupplicant
> Version: 2:2.6-21
> Severity: important
>
> Dear Maintainer,
>
> Running vanilla Debian Sid on my laptop here. Upgraded last night and when I
> woke up in the morning my Wifi had stopped working. It refused to connect to
Alright, not entirely sure if I did this right but I followed Debian's Building
Tutorial to download and build wpa_supplicant with the changes you linked. One
exception, I use wpa_supplicant through NetworkManager and could not work out
where I needed to create a wpa_supplicant.conf, so I change
You might try adding this patch and disabling the oper-class IE:
http://lists.infradead.org/pipermail/hostap/2018-August/038792.html
I'd be curious to know if it fixes the problem.
Thanks,
Ben
On 1/14/19 4:35 PM, Different55 wrote:
On Monday, January 14, 2019 10:37 AM, Ben Greear
wrote:
W
On Monday, January 14, 2019 10:37 AM, Ben Greear
wrote:
> What is the model number of your home AP?
>
> Thanks,
> Ben
It is a Comtrend VR-3033
On 1/13/19 9:40 AM, Different55 wrote:
Hi! I'm running Debian Sid and recently upgraded wpasupplicant to 2.7. After
the upgrade finished, NetworkManager popped up saying that the connection to my
home Wifi failed. I was able to connect to my phone's hotspot still. I attached
a relevant bit of
Hi! I'm running Debian Sid and recently upgraded wpasupplicant to 2.7. After
the upgrade finished, NetworkManager popped up saying that the connection to my
home Wifi failed. I was able to connect to my phone's hotspot still. I attached
a relevant bit of a log from journalctl.
I also tried Debi
Hi! I'm running Debian Sid and recently upgraded wpasupplicant to 2.7. After
the upgrade finished, NetworkManager popped up saying that the connection to my
home Wifi failed. I was able to connect to my phone's hotspot still. I attached
a relevant bit of a log from journalctl.
I also tried Debi
Hi,
I'm currently afk, but could you please summarise all information you've
got and send to hos...@lists.infradead.org adding this bug and myself to
Cc:?
Thanks!
--
Cheers,
Andrej
On Sun, 13 Jan 2019, 16:33 Different55
> On Sunday, January 13, 2019 5:21 AM, Andrej Shadura
> wrote:
>
> > I
On Sunday, January 13, 2019 5:21 AM, Andrej Shadura wrote:
> Is that a Broadcom card? "Setting a MAC" in the logs looks suspicious,
> AFAIK Broadcom driver's don’t support that correctly.
>
> By the way, it would be great if you also tested the snapshot
> currently in experimental.
>
> --
>
> C
Hi,
On Sun, 13 Jan 2019 at 04:18, Different55 wrote:
> Dear Maintainer,
>
> Running vanilla Debian Sid on my laptop here. Upgraded last night and when I
> woke up in the morning my Wifi had stopped working. It refused to connect to
> my
> home Wifi anymore, although my phone's hotspot still work
21 matches
Mail list logo
