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
Hi,
I maybe interpreting this wrong, but maybe the regression in the
autopkgtest of python-dbusmock is pointing in the same direction. That
would make it very reproducible.
Otherwise that regression deserves its own bug report.
Paul
https://tracker.debian.org/pkg/network-manager
I just ran into this issue.
I took a packet capture of the DHCP conversation to debug it, and found
that the DHCP server was responding with a DHCP NAK packet with "address
in use" as the message. And indeed, my system is sending the DHCP REQUEST
with a request for a specific address (which is
I was affected by the same bug (Freebox Revolution from Free (French
ISP) here).
I switched to isc-dhcp-client by creating a file
/etc/NetworkManager/conf.d/dhcp-client.conf containing the 2 following
lines:
[main]
dhcp=dhclient
Then I restarted NetworkManager using this command:
sudo service
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
Package: network-manager
Followup-For: Bug #947613
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
I've got the same problem. Comparing the output of "journalctl -u
NetworkManager" on both versions, the only difference I am able to
spot is that with 1.22.2-1, I have these lines:
déc. 29
Package: network-manager
Version: 1.22.0-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I have an Internet box and connect to it through Wi-Fi.
After upgrading network-manager to 1.22.2-1, my machine does not get
an IPv4 address anymore. Specifically, ifconfig
11 matches
Mail list logo
