On Thu, 2015-12-10 at 09:36 +0200, Cristian Sava wrote: > On Wed, 2015-12-09 at 12:39 -0800, Gordon Messmer wrote: > > On 12/09/2015 12:41 AM, Cristian Sava wrote: > > > I Installed F23 Server with static address but after updating > > > that > > > it > > > got an automatic one. Why that? > > ... > > > [root@s217 network-scripts]# cat ifcfg-eno1 > > > HWADDR=00:1E:67:8B:B9:31 > > ... > > > [root@s217 network-scripts]# cat ifcfg-eth1 > > > HWADDR=00:1E:67:8B:B9:30 > > ... > > > [root@s217 network-scripts]# ip addr > > > 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc > > > fq_codel > > > state DOWN group default qlen 1000 > > > link/ether 00:1e:67:8b:b9:31 brd ff:ff:ff:ff:ff:ff > > > 3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc > > > fq_codel > > > state UP group default qlen 1000 > > > link/ether 00:1e:67:8b:b9:30 brd ff:ff:ff:ff:ff:ff > > > > > > > If you want to know why the system behaves as it does, you'll have > > to > > give us a complete list of the changes you've made after > > installation. > > Right now, it's clear that you have a dual-port NIC and that you've > > tried to rename your interfaces, but it's not clear what steps > > you've > > taken to do that. Your interfaces are eth0 and eno1, and eno1 (the > > active interface) has the MAC address that's defined in the > > configuration for eth1, which specifies DHCP. > > > > My suggestion is that, if you *must* rename your interfaces, then > > you > > should specify "net.ifnames=0 biosdevname=0" as boot parameters > > when > > you > > install the system. Don't try to fix the system, just start over > > from > > the beginning. > > Thank you for the tip. > > I did: > 1)Install F23 server (nothing else! no desktop, no options) > 2)I configured eno1 with static IP (the only connected NIC!) and > leaved > eth1 with default config (dhcp, not connected). > 3)I added basic X support (no custom configs) > 4)I rebooted and updated several times > 5)All was working as expected (the remote access was ok) > 6)Power off > 7)Power on after a few days > 8)I manually updated & rebooted (I used "dnf update") > 9)*** The problem *** > > [root@s217 ~]# rpm -qa | grep NetworkManager > NetworkManager-1.0.6-8.fc23.x86_64 > NetworkManager-libnm-1.0.6-8.fc23.x86_64 > [root@s217 ~]# rpm -q initscripts > initscripts-9.65-1.fc23.x86_64 > [root@s217 ~]# > > We are in stable stage so I do not expect NIC name changes without > consistent reason. It sounds like you don't need NetworkManager, so maybe: systemctl stop NetworkManager.service systemctl disable NetworkManager.service systemctl enable network.service systemctl start network.service Not at all sure that this is a currently "accepted" practice, but I run a simple single static interface and no wifi so this seems to work best for me. My setup is F23 but it was an upgrade from F22 so there could be some less than standard stuff still in there. -- Doug H. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
