Hi everyone

On Mon, 06 Jan 2020 19:14:46 +0100 Vincent Bernat <ber...@debian.org> 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.
> 
> When using dhcp=dhclient, I am getting the same NAK, but then the ISC
> DHCP client is using DISCOVER and gets a new IP address.


Looking at
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commits/nm-1-22
there aren't that many commits between 1.22.0 and 1.22.2 so it should be
possible to find the offending commit pretty easily via git bisect for
someone who can reproduce the issue.

Checking the upstream bug tracker,
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/325
seems like the most likely candidate.

There the following commit is mentioned as the culprit:

> 46ad3aa4f39f3ec786a77847c422be9cbf5d61a5 is the first bad commit
> commit 46ad3aa4f39f3ec786a77847c422be9cbf5d61a5
> Author: Beniamino Galvani <bgalv...@redhat.com>
> Date:   Mon Dec 23 15:39:06 2019 +0100
> 
>     dhcp: nettools: start from init-reboot phase when reusing address
>     
>     If we know the address used previously, also tell the client to start
>     from the init-reboot phase, so that it will start with a DHCP request
>     instead of a discover.
>     
>     (cherry picked from commit 6af6f70d812249bdbc27d63fbd9544c57c33d04d)
> 
>  src/dhcp/nm-dhcp-nettools.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)

Anyone willing to check the proposed fix
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/848b869c6ede3a796872a0b5cd8b2398804c3697


Regards,
Michael


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to