On 08/01/2020 16:07, Michael Biebl wrote:
Anyone willing to check the proposed fix
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/848b869c6ede3a796872a0b5cd8b2398804c3697
Hi,
I tested the proposed patch on top of debian's 1.22.2-1 version. This
patch does NOT fix the
Hi everyone
On Mon, 06 Jan 2020 19:14:46 +0100 Vincent Bernat wrote:
> So, I suppose this is a because of randomizatio of the MAC address on
> wifi networks. I don't see anytrhing special in the NEWS file about
> this. Previously, the hardware MAC address was used to do the DHCP
> request.
>
>
Hello Michael,
I was able to hit the bug again. It seems I have to go to another wifi
network, then back to my home network to hit the bug. On the
client-side, I get:
janv. 06 18:57:13 zoro NetworkManager[75721]: [1578333433.9474] dhcp4
(wlp3s0): activation: beginning transaction (timeout in
❦ 29 décembre 2019 13:40 +01, Michael Biebl :
> Can you provide a full, verbose debug log:
>
> https://wiki.gnome.org/Projects/NetworkManager/Debugging
>
> Which dhcp client do you use: internal, isc-dhcp-client, ...?
I am using the internal client. Unfortunately, I am not able to
reproduce the
On 29/12/2019 13:40, Michael Biebl wrote:
Can you provide a full, verbose debug log:
https://wiki.gnome.org/Projects/NetworkManager/Debugging
Which dhcp client do you use: internal, isc-dhcp-client, ...?
I made more tests and noticed that when I upgrade from 1.22.0-2 to
1.22.2-1, the IPv4
Can you provide a full, verbose debug log:
https://wiki.gnome.org/Projects/NetworkManager/Debugging
Which dhcp client do you use: internal, isc-dhcp-client, ...?
signature.asc
Description: OpenPGP digital signature
6 matches
Mail list logo