Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1691993 - Frequent IPv4 address changes result in constant SSH loss
Summary: Frequent IPv4 address changes result in constant SSH loss
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 29
Hardware: armv7hl
OS: Linux
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
Reported: 2019-03-23 03:53 UTC by Jeffrey Walton
Modified: 2023-09-12 01:45 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-11-27 21:38:05 UTC
Type: Bug

Attachments (Terms of Use)
DHCP server lease history (49.76 KB, image/png)
2019-03-23 03:53 UTC, Jeffrey Walton
no flags Details

Description Jeffrey Walton 2019-03-23 03:53:22 UTC
Created attachment 1547189 [details]
DHCP server lease history

This is kind of a shitty report. My apologies for that.

I have a Raspberry Pi 3B+ running Fedora 29, fully patched. Every half hour the RPI3 acquires a new IP address. This causes my SSH session to freeze. Once I get the "connection dropped" message I can use the new IP address and SSH back into the device. Ad infinitum.

I can duplicated the problem with both the armv7hl and aarch64 minimal images. The issue only occurs when using Fedora's images. I use Minimal images because the board is headless. I don't know if the issue affects GNOME or XFCE based images. I have a lot of IoT gadgets, and they use different OSes. Other OSes don't witness the problem.

The report is filled against Network Manager, but I suspect it is a confluence of components and events. The info below tries to describe the components and events.


I have an internal DHCP server that only provides 172.16.*.* IPv4 leases. The server is IPFire firewall. DHCP leases expire in one hour to promote aggressive scavenging of leases.

There is also a Verizon gateway [upstream] in the network. The Verizon gateway also has a DHCP server that only provides 192.168.1.* IPv4 leases. Verizon traffic is blocked on the internal network.

Verizon gateway also has a Wireless access point. I don't use wireless on these devices. All of the devices are tethered using ethernet. All of the devices lack the password to join the network. (I don't even bother configuring or fixing wifi problems since ethernet is available).

The Fedora machine seems to be OK if I leave the hostname as "localhost". This morning I was connected over SSH for about 10 hours when the machine was named localhost. When I renamed the machine "rpi3b" the problem surfaced again. The IP address changed 3 times in the last 2 hours.

The typical sequence of SSH sessions using a non-localhost name are:

    ssh  # or whatever the starting IP address is
    <work 30 minutes, session killed>
    ssh  # incremented by 1
    <work 30 minutes, session killed>
    ssh  # incremented by 1
    <work 30 minutes, session killed>
    ssh  # incremented by 1
    <work 30 minutes, session killed>

When the problem occurs my DHCP server does not show a MAC address during DHCP registration. This is unusual; see attached image.

The issue was raised on the Fedora ARM mailing list but I have not been able to resolve it. Also see "Raspberry Pi 3B+ with Aarch64 image changing IP every half hour", .

Stuart D. Gathman suggested this may be an IPv6 privacy option and cited, but disabling IPv6 did not help. IPv6 is not configured, and it is not clear to me how IPv6 is affecting IPv4.

Comment 1 Beniamino Galvani 2019-03-23 14:45:38 UTC
Can you please set level=DEBUG in the [logging] section of /etc/NetworkManager/NetworkManager.conf, restart the NM service with "systemctl restart NetworkManager", reproduce the issue and then attach the output of "journalctl -u NetworkManager -b" ?

Comment 2 Ben Cotton 2019-10-31 19:44:29 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2019-11-27 21:38:05 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Red Hat Bugzilla 2023-09-12 01:45:16 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days

Note You need to log in before you can comment on or make changes to this bug.