if network manager is running and has not been told to not "manage" the connection it will manage the connection. 

You need to probably configure it via network manager or via the ifcfg-* files (making sure to find and set the correct variables to tell network manager to keep its hands off ,or disable network-manager in systemd).

I am still using the ifcfg files and disabling network manager and will be on non-laptops while some variant of those ifcfg-* files still work.

I generally never use ifconfig/ip addr except for a quick test/one time emergency use since those settings do not survive reboot.


On Wed, Mar 23, 2022 at 2:28 PM Geoffrey Leach <geoffleach.gl@gmail.com> wrote:
I have an ethernet connection (to a SiliconDust box) that requires a netmask 255.255.0.0. So, no problem

% ifconfig eno1 192.168.10.6  netmask 255.255.0.0
% ifconfig eno1
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.6  netmask 255.255.0.0  broadcast 192.168.255.255

some time later ...

% ifconfig eno1
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.6  netmask 255.255.255.0  broadcast 192.168.10.255

Any ideas on why the change does not stick?

Thanks
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure