Thanks for the reply. It seems that the root of my problem was that the connection defaulted to Automatic. Changing that to Manual seems to have resolved the issue.
On Wed, 23 Mar 2022 14:47:47 -0500 Roger Heflin rogerheflin@gmail.com wrote:
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 LeachThanks for the reply. It
seems that the root of my problem was that the connection defaulted to Automatic. Changing that to Manual seems to have resolved the issue.
On Wed, 23 Mar 2022 14:47:47 -0500 Roger Heflin rogerheflin@gmail.com wrote:
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
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