control: clone -1 -2
control: reassign -2 wpassupplicant
control: found -2 2:2.9.0-11
control: affects -2 network-manager
control: retitle -2 activation failure with long interface names
Am 24.03.20 um 11:19 schrieb Alkis Georgopoulos:
> On 3/24/20 11:07 AM, Andrej Shadura wrote:
>> Could you
On 3/24/20 11:07 AM, Andrej Shadura wrote:
Could you please provide more background? It’s not quite clear to me how
this commit fixes the issue.
Hello Andrej,
I'm happy to provide the "end user" side of the story, but I can't
provide the "developer" side, as it's the Realtek engineers that
On 24/03/2020 10:07, Andrej Shadura wrote:
On 24/03/2020 03:41, Alkis Georgopoulos wrote:
The two-liner patch made it upstream:
http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563
It would be awesome if it was cherrypicked/backported, as it's rather
significant
On 24/03/2020 03:41, Alkis Georgopoulos wrote:
The two-liner patch made it upstream:
http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563
It would be awesome if it was cherrypicked/backported, as it's rather
significant and it solves this issue.
Could you please
On 3/24/20 8:07 AM, Michael Biebl wrote:
I'd prefer a separate, new bug report against wpasupplicant.
The original bug report is about disabling mac randomization, so afaics
a different issue from yours.
My problem was exactly the one described here.
With MAC randomization enabled, network
Am 24.03.20 um 06:37 schrieb Alkis Georgopoulos:
> On 3/24/20 5:22 AM, Michael Biebl wrote:
>> You should file a bug report against wpasupplicant.
>> Andrew, the wpasupplicant maintainer, is not reading network-manager bug
>> reports.
>
>
> Thank you Michael,
>
> I was thinking of:
> 1) Getting
On 3/24/20 5:22 AM, Michael Biebl wrote:
You should file a bug report against wpasupplicant.
Andrew, the wpasupplicant maintainer, is not reading network-manager bug
reports.
Thank you Michael,
I was thinking of:
1) Getting feedback from someone affected by this bug (like me) that
this
Hi
Am 24.03.20 um 03:41 schrieb Alkis Georgopoulos:
> The two-liner patch made it upstream:
>
> http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563
>
>
> It would be awesome if it was cherrypicked/backported, as it's rather
> significant and it solves this issue.
You
The two-liner patch made it upstream:
http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563
It would be awesome if it was cherrypicked/backported, as it's rather
significant and it solves this issue.
I reported this to Realtek and they pinpointed it to a bug in wpasupplicant.
I tested the patch and it works fine for 8812au, 88x2bu and 8821cu.
I then reported it to launchpad in case it makes it for Ubuntu 20.04:
https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1867908
If others
FWIW, I almost completely gave up before I ran into the NM bugzilla
describing how some drivers break with rand-mac.
I even went and bought a USB dongle to try and get Debian (or
anything) running on wifi, but that didn't work either because the
driver suffers the same problem than wl.
I have
The Ubuntu bug for this issue is https://launchpad.net/bugs/1681513
Jérôme, yes, I want there to be an on/off switch for this feature in
at least GNOME before we re-enable this privacy feature in Ubuntu.
Thanks,
Jeremy Bicha
I was hit by this too.
This is what I understand:
This setting is enabled by default for privacy/security reasons. It
makes connection fail with some HW/drivers due to the drivers
themselves, so the rootcause is not in network-manager itself.
This results in poor user experience for
Package: network-manager
Version: 1.6.2-3
Severity: wishlist
Dear Maintainer,
I think that Network-Manager default settings should be changed to default to
non-random MAC addresses on WiFi. Even though there are security reasons for
enabling this by default, this results in less "out of the box"
14 matches
Mail list logo
