Subject: wifi: NetworkManager spams the logs with "state changed new lease" every minute

Hi,

Under Debian/unstable, with a wifi connection from the train,
NetworkManager spams the logs with "state changed new lease"
regularly every minute: what is the cause?

Jun 28 11:57:41 qaa NetworkManager[1264]: <info> [1782640661.4715] dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171
Jun 28 11:58:41 qaa NetworkManager[1264]: <info> [1782640721.4779] dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171
Jun 28 11:59:41 qaa NetworkManager[1264]: <info> [1782640781.4714] dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171
Jun 28 12:00:41 qaa NetworkManager[1264]: <info> [1782640841.4725] dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171
Jun 28 12:01:41 qaa NetworkManager[1264]: <info> [1782640901.4717] dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171
Jun 28 12:02:41 qaa NetworkManager[1264]: <info> [1782640961.4726] dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171
Jun 28 12:03:41 qaa NetworkManager[1264]: <info> [1782641021.4729] dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171
Jun 28 12:04:41 qaa NetworkManager[1264]: <info> [1782641081.4736] dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171
Jun 28 12:05:41 qaa NetworkManager[1264]: <info> [1782641141.4737] dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171
Jun 28 12:06:41 qaa NetworkManager[1264]: <info> [1782641201.4797] dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171
Jun 28 12:07:41 qaa NetworkManager[1264]: <info> [1782641261.4800] dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171
Jun 28 12:08:41 qaa NetworkManager[1264]: <info> [1782641321.4821] dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171
Jun 28 12:09:41 qaa NetworkManager[1264]: <info> [1782641381.4870] dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171
Jun 28 12:10:41 qaa NetworkManager[1264]: <info> [1782641441.4812] dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171
Jun 28 12:11:41 qaa NetworkManager[1264]: <info> [1782641501.4754] dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171
Jun 28 12:12:41 qaa NetworkManager[1264]: <info> [1782641561.4745] dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171
Jun 28 12:13:41 qaa NetworkManager[1264]: <info> [1782641621.4764] dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171
Jun 28 12:14:41 qaa NetworkManager[1264]: <info> [1782641681.4647] dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171
Jun 28 12:15:41 qaa NetworkManager[1264]: <info> [1782641741.4766] dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171

--
Vincent Lef?vre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)

--- PyGate Linux v1.5.18
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Subject: Re: wifi: NetworkManager spams the logs with "state changed new lease" every minute

On 2026-06-28 12:20:38 +0200, Vincent Lefevre wrote:

Under Debian/unstable, with a wifi connection from the train,
NetworkManager spams the logs with "state changed new lease"
regularly every minute: what is the cause?

Jun 28 11:57:41 qaa NetworkManager[1264]: <info> [1782640661.4715] dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171
Jun 28 11:58:41 qaa NetworkManager[1264]: <info> [1782640721.4779] dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171

[...]

The Mistral AI chatbot pointed me to an explanation and the command
"ip addr show wlp0s20f3" to check the valid_lft value.

I could see that the initial values are

valid_lft 120sec preferred_lft 120sec

and when this value reaches 60sec, the lease is renewed.

So, it seems to be an issue with SNCF's DHCP server, which uses
an incredibly low value!

I suppose that a renewal of the lease enough time before the end
of its validity is expected.

--
Vincent Lef?vre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)

--- PyGate Linux v1.5.18
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Subject: Re: wifi: NetworkManager spams the logs with "state changed new lease" every minute

Am 28.06.26 um 12:40 schrieb Vincent Lefevre:

Under Debian/unstable, with a wifi connection from the train,
NetworkManager spams the logs with "state changed new lease"
regularly every minute: what is the cause?

Use a packet sniffer and check the DHCP lease time.

--
Gruá
Marco

Junk-Mail bitte an trashcan@stinkedores.dorfdsl.de

--- PyGate Linux v1.5.18
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Subject: Re: wifi: NetworkManager spams the logs with "state changed new lease" every minute

Vincent Lefevre <vincent@vinc17.net> wrote:

On 2026-06-28 12:20:38 +0200, Vincent Lefevre wrote:

Under Debian/unstable, with a wifi connection from the train, NetworkManager spams the logs with "state changed new lease"
regularly every minute: what is the cause?

Jun 28 11:57:41 qaa NetworkManager[1264]: <info> [1782640661.4715]
dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171 Jun
28 11:58:41 qaa NetworkManager[1264]: <info> [1782640721.4779]
dhcp4 (wlp0s20f3): state changed new lease, address=10.7.0.171

[...]

The Mistral AI chatbot pointed me to an explanation and the command
"ip addr show wlp0s20f3" to check the valid_lft value.

I could see that the initial values are

valid_lft 120sec preferred_lft 120sec

and when this value reaches 60sec, the lease is renewed.

So, it seems to be an issue with SNCF's DHCP server, which uses
an incredibly low value!

It might be a reasonable time on a train, where connections will be
made and dropped all the time. It's only a problem for people who spend
their time looking at logs!

I suppose that a renewal of the lease enough time before the end
of its validity is expected.

--- PyGate Linux v1.5.18
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Subject: Re: wifi: NetworkManager spams the logs with "state changed new lease" every minute

Under Debian/unstable, with a wifi connection from the train,
NetworkManager spams the logs with "state changed new lease"
regularly every minute: what is the cause?

If you can't find the cause and you're using rsyslog, you can at least
filter out those messages. I used to have a Radeon graphics card,
and I had a huge amount of crap in syslog due to Radeon fence code in
the kernel. Adding this to rsyslog.conf before the rules removed it:

#### FILTERS =====================================================
# This apparently comes from Radeon fence code in the kernel.
:msg, contains, " armed on ring " ~
:msg, contains, " signaled from irq context" ~
:msg, contains, " pending" ~
:msg, contains, "alloc_contig_range:" ~

HTH.

--
Karl Vogel I don't speak for anyone but myself

Sent a network diagram that I dramatically simplified to an upset manager
via inter-office mail. In retrospect using crayon was not helping, as my immediate manager pointed out. --Reddit admin, 2 Jun 2026

--- PyGate Linux v1.5.18
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)