# Rocky 9.5 Network Manager tools (nmtui nmcli) fail to update the IP address

**URL:** <https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803>\
**Category:** Rocky Linux Help & Support\
**Tags:** rocky-linux-9\
**Created:** [March 6, 2025, 10:28am UTC](https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803 "2025-03-06T10:28:13Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![conradc](https://avatars.discourse-cdn.com/v4/letter/c/a88e57/32.png) [@conradc](https://forums.rockylinux.org/u/conradc)\
**Post date:** [March 6, 2025, 10:28am UTC](https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803/1 "2025-03-06T10:28:13Z")

</div>

Network Manager tools (nmtui nmcli) fail to update the IP address on v9.5

This worked 100% on 9.4, however after upgrade to 9.5 this fails with an error message.

If I manually edit the interface config file for Network Manager, restart the service from the console and then ifdown/ifup the interface, then I can change the IP and other parameters.

---

<div class="post-metadata">

**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\
**Post date:** [March 6, 2025, 10:49am UTC](https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803/2 "2025-03-06T10:49:44Z")

</div>

> [@conradc](#):
>
> fails with an error message

I don’t think that we can explain the message before we see it.

> [@conradc](#):
>
> ifdown/ifup the interface

Is that `nmcli con down $conn-name` and `nmcli con up $conn-name` or some legacy scripts?

> [@conradc](#):
>
> If I manually edit the interface config file for Network Manager

Which files, exactly?

---

<div class="post-metadata">

**Author:** ![conradc](https://avatars.discourse-cdn.com/v4/letter/c/a88e57/32.png) [@conradc](https://forums.rockylinux.org/u/conradc)\
**Post date:** [March 6, 2025, 11:22am UTC](https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803/3 "2025-03-06T11:22:45Z")

</div>

Hi, I am so sorry…

The nmtui error message on trying to change the IP Address under the interface Edit screen:  
Error Message:  
Unable to save connection: 802-3-ethernet.mac-address-denylist: unknown property

nmcli:  
nmcli c modify ens33 ipv4.address 10.255.1.46  
Error: Failed to modify connection ‘ens33’: 802-3-ethernet.mac-address-denylist: unknown property

The NetworkManager interface config path:  
/etc/NetworkManager/system-connection.

The config filename: ens33.nmconnection

---

<div class="post-metadata">

**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\
**Post date:** [March 6, 2025, 11:35am UTC](https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803/4 "2025-03-06T11:35:50Z")

</div>

Fascinating. The `man nm-settings` does list that property for me:

> **802-3-ethernet.mac-address**  
> Alias: mac  
> If specified, this connection will only apply to the Ethernet device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).  
> Format: MAC address
> 
> **802-3-ethernet.mac-address-blacklist**  
> If specified, this connection will never apply to the Ethernet device whose permanent MAC address matches an address in the list. Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).  
> Format: list of MAC addresses
> 
> **802-3-ethernet.mac-address-denylist**  
> If specified, this connection will never apply to the Ethernet device whose permanent MAC address matches an address in the list. Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).  
> Format: list of MAC addresses

Curiously, the `802-3-ethernet.mac-address-blacklist` and `802-3-ethernet.mac-address-denylist` seem identical (but one is not alias of the other).

[Configuring and managing networking | Red Hat Product Documentation](https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/configuring_and_managing_networking/index) does not mention either list.

* * *

I would start by removal of the offending property. Is it really necessary anyway?

---

<div class="post-metadata">

**Author:** ![conradc](https://avatars.discourse-cdn.com/v4/letter/c/a88e57/32.png) [@conradc](https://forums.rockylinux.org/u/conradc)\
**Post date:** [March 6, 2025, 11:47am UTC](https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803/5 "2025-03-06T11:47:37Z")

</div>

I was adding/removing/changing the mac-address. It was only the ip-address that was being changed. In fact, I have never used the mac blacklist or the mac denylist. No entry was added to them.

This always worked with no issues in Rocky 9.4 and before. Only since Rocky 9.5 was installed has this problem been showing up.

---

<div class="post-metadata">

**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\
**Post date:** [March 6, 2025, 11:57am UTC](https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803/6 "2025-03-06T11:57:12Z")

</div>

> [@conradc](#):
>
> It was only the ip-address that was being changed.

However, that operation is most likely something like:

1. Read saved config
2. Modify config
3. Store config

And it seemingly does now:

1. Read garbage
2. Refuse

In other words, there is never “only X to change” – the whole config has to be consistent at every step.

* * *

> [@conradc](#):
>
> This always worked with no issues in Rocky 9.4 and before. Only since Rocky 9.5 was installed has this problem been showing up.

A point update is not always mere “add properties”. It can also change system to be more strict – usually in the name of security.

* * *

I would create new, “fresh”, connections with nmcli and then wipe out the old ones.

---

<div class="post-metadata">

**Author:** ![conradc](https://avatars.discourse-cdn.com/v4/letter/c/a88e57/32.png) [@conradc](https://forums.rockylinux.org/u/conradc)\
**Post date:** [March 6, 2025, 12:11pm UTC](https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803/7 "2025-03-06T12:11:50Z")

</div>

> [@jlehtone](#):
>
> ethernet.mac-address-blacklist

There is not any array in the config named as either mac-black-list or mac-deny-list. There is no entry to edit and nothing was added.

Even the nmtui config editor tool does NOT list these entries.

Why not try it on your own system and see.|

---

<div class="post-metadata">

**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\
**Post date:** [March 6, 2025, 12:27pm UTC](https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803/8 "2025-03-06T12:27:58Z")

</div>

```bash
[root@al9 ~]# nmcli con add con-name example ifname eno2 type ethernet ipv6.method disabled ip4 10.20.30.1/24
Connection 'example' (eba1e409-4b84-4ac6-aca0-a7f1eb667f5b) successfully added.
[root@al9 ~]# nmcli con mod example ip4 10.20.30.22/24
[root@al9 ~]#
[root@al9 ~]# cat /etc/NetworkManager/system-connections/example.nmconnection 
[connection]
id=example
uuid=eba1e409-4b84-4ac6-aca0-a7f1eb667f5b
type=ethernet
interface-name=eno2

[ethernet]

[ipv4]
address1=10.20.30.1/24
address2=10.20.30.22/24
method=manual

[ipv6]
addr-gen-mode=default
method=disabled

[proxy]

```

Oops, the “ip4” _adds_ address. We want only one:

```bash
[root@al9 ~]# nmcli con mod example ipv4.address 10.20.30.33/24
[root@al9 ~]# cat /etc/NetworkManager/system-connections/example.nmconnection 
[connection]
id=example
uuid=eba1e409-4b84-4ac6-aca0-a7f1eb667f5b
type=ethernet
interface-name=eno2

[ethernet]

[ipv4]
address1=10.20.30.33/24
method=manual

[ipv6]
addr-gen-mode=default
method=disabled

[proxy]

```

That is what I saw.

---

<div class="post-metadata">

**Author:** ![conradc](https://avatars.discourse-cdn.com/v4/letter/c/a88e57/32.png) [@conradc](https://forums.rockylinux.org/u/conradc)\
**Post date:** [March 6, 2025, 12:32pm UTC](https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803/9 "2025-03-06T12:32:51Z")

</div>

How about trying that with the nmtui tool. I only tried to use the nmcli because of an error shown in the nmtui tool

---

<div class="post-metadata">

**Author:** ![conradc](https://avatars.discourse-cdn.com/v4/letter/c/a88e57/32.png) [@conradc](https://forums.rockylinux.org/u/conradc)\
**Post date:** [March 6, 2025, 12:57pm UTC](https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803/10 "2025-03-06T12:57:12Z")

</div>

That is how it used to work under Rocky9.4 - I only get the error now with Rocky9.5 (Upgraded from Rocky 9.4).

Trying to make sure the blacklist is empty, then gives an error that the mac-denylist variable does not exist.

typing:  
nmcli c show ens33 | grep list, only shows the mac-blocklist variable.

There is something broken in the command line tools, as if an old library was used when it was compiled.

---

<div class="post-metadata">

**Author:** ![conradc](https://avatars.discourse-cdn.com/v4/letter/c/a88e57/32.png) [@conradc](https://forums.rockylinux.org/u/conradc)\
**Post date:** [March 6, 2025, 1:01pm UTC](https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803/11 "2025-03-06T13:01:16Z")

</div>

My config file is:

cat /etc/NetworkManager/system-connections/ens33.nmconnection  
[connection]  
id=ens33  
uuid=6ec6c696-04f9-30c2-ae18-5a7190807575  
type=ethernet  
autoconnect-priority=-999  
interface-name=ens33  
timestamp=1739862592

[ethernet]

[ipv4]  
address1=10.255.1.44/24,10.255.1.250  
dns=41.208.60.189;196.30.224.60;  
dns-search=cnbbw.co.za;  
may-fail=false  
method=manual

[ipv6]  
addr-gen-mode=default  
method=disabled

[proxy]

---

<div class="post-metadata">

**Author:** ![conradc](https://avatars.discourse-cdn.com/v4/letter/c/a88e57/32.png) [@conradc](https://forums.rockylinux.org/u/conradc)\
**Post date:** [March 6, 2025, 1:48pm UTC](https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803/12 "2025-03-06T13:48:47Z")

</div>

I have found the problem - When Rocky9.4 is upgraded to Rocky9.5, the latest version of NetworkManager is not installed. I had to manually upgrade NetworkManager and NetworkManager-tui to the latest version, and then it started working as expected after the Service was restarted.

---

<div class="post-metadata">

**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\
**Post date:** [March 6, 2025, 2:39pm UTC](https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803/13 "2025-03-06T14:39:01Z")

</div>

That would suggest your system wasn’t updated properly. If you do:

```auto
dnf update

```

then every single package updates, including Network Manager. It would suggest that some packages were only installed/updated manually rather than doing a full update.

---

<div class="post-metadata">

**Author:** ![conradc](https://avatars.discourse-cdn.com/v4/letter/c/a88e57/32.png) [@conradc](https://forums.rockylinux.org/u/conradc)\
**Post date:** [March 6, 2025, 2:41pm UTC](https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803/14 "2025-03-06T14:41:04Z")

</div>

That is exactly what I did to update it from 9.4 to 9.5

This has been the result of updating more than 10 systems, not only the one.

---

<div class="post-metadata">

**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\
**Post date:** [March 6, 2025, 3:33pm UTC](https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803/15 "2025-03-06T15:33:02Z")

</div>

The `dnf up` _should_ install all available updates.  
If it did not, then either “all” updates were not available (a broken mirror?)  
or something did exclude some of the packages.

* * *

> [@conradc](#):
>
> the latest version of NetworkManager is not installed. I had to manually upgrade NetworkManager and NetworkManager-tui to the latest version, and then it started working as expected

A version mismatch between tools. Some new (of 9.5) tools had the ‘802-3-ethernet.mac-address-denylist’ and some old (of 9.4) did not. The ensuing miscommunication between them produced the error.

Ideally, the package dependencies would be strict enough to prevent only some packages updating, but in practice having too many strict requirements is painful too.

---

<div class="post-metadata">

**Author:** ![conradc](https://avatars.discourse-cdn.com/v4/letter/c/a88e57/32.png) [@conradc](https://forums.rockylinux.org/u/conradc)\
**Post date:** [March 6, 2025, 3:36pm UTC](https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803/16 "2025-03-06T15:36:05Z")

</div>

You are welcome to install 9.4 on a system, and then update it to 9.5.

---

<div class="post-metadata">

**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\
**Post date:** [March 6, 2025, 5:31pm UTC](https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803/17 "2025-03-06T17:31:53Z")

</div>

I’ve had 9.0 on my system, and it’s been upgraded through all versions to 9.5 without experiencing this problem. And all other systems I’ve done were 9.3 or 9.4 installs that also didn’t have this problem. This would suggest the problem is with the way you configured the network on these machines previously with whatever settings you were choosing that are non-standard. Usually you just assign an IP address, subnet mask, default route, and DNS configuration. You mentioned doing other stuff, like changing MAC addresses, etc.

That is why nobody else has experienced this problem, and @jlehtone suggested for you to delete your network configurations and set them up as new ones due to the fact you applied non-standard settings that no doubt conflicted and caused your problems. Either that or what he said about the fact you had a mismatch of 9.4 or 9.5 packages that had feature conflicts. Which goes back to what I said before, that your system wasn’t updated properly and had mixed 9.4 and 9.5 packages - although you said you did `dnf update` which cannot be the case, because if I do this, my systems update from 9.4 to 9.5 without mixing Network Manager packages like yours did. I don’t need to try it, because I’ve updated plenty of systems and never experienced this.

---

<div class="post-metadata">

**Author:** ![conradc](https://avatars.discourse-cdn.com/v4/letter/c/a88e57/32.png) [@conradc](https://forums.rockylinux.org/u/conradc)\
**Post date:** [March 6, 2025, 5:46pm UTC](https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803/18 "2025-03-06T17:46:59Z")

</div>

Actually read what I said and an example of the config from the server I had just upgraded to 9.5 from 9.4 - I did not mention that I had configured or used anything MAC related, in fact I stated that the error message mentioned mac, even though I had set nothing at all with respect to the mac.

---

<div class="post-metadata">

**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\
**Post date:** [March 6, 2025, 5:49pm UTC](https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803/19 "2025-03-06T17:49:50Z")

</div>

OK, so then that means it was down to what we already said - mix of 9.4 and 9.5 packages due to the fact the server wasn’t updated properly.

---

<div class="post-metadata">

**Author:** ![conradc](https://avatars.discourse-cdn.com/v4/letter/c/a88e57/32.png) [@conradc](https://forums.rockylinux.org/u/conradc)\
**Post date:** [March 6, 2025, 5:55pm UTC](https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803/20 "2025-03-06T17:55:13Z")

</div>

That can only be presumed - no packages were ever upgraded by them selves, they were only ever upgraded, all at the same time.

[Next page](https://forums.rockylinux.org/t/rocky-9-5-network-manager-tools-nmtui-nmcli-fail-to-update-the-ip-address/17803.md?page=2)
