On Wed, 2015-12-09 at 12:02 +0000, Kseniya Blashchuk wrote: > Yep, sorry. So you restarted after changing BOOTPROTO? Try looking > into dmesg or journalctl -n1000 | egrep "eno|eth", or something like > that. Yes, I allways rebooted. Again, that config was working well until recent updates. For now, I get (eth1 not connected): [root@s217 ~]# journalctl -n1000 | egrep "eno|eth" Dec 09 13:36:24 s217.mydomain.me systemd-udevd[559]: Error changing net interface name 'eth1' to 'eno1': File exists Dec 09 13:36:24 s217.mydomain.me systemd-udevd[559]: could not rename interface '3' from 'eth1' to 'eno1': File exists Dec 09 13:36:31 s217.mydomain.me NetworkManager[838]: <info> ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-eno1 (8daf047d- e944-4305-b47f-6f2104edf9a2,"eno1") Dec 09 13:36:31 s217.mydomain.me NetworkManager[838]: <info> ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-eth1 (0d9c850a- 1545-481c-897f-84d4475e0377,"eth1") Dec 09 13:36:32 s217.mydomain.me NetworkManager[838]: <info> Loaded device plugin: NMVethFactory (internal) Dec 09 13:36:32 s217.mydomain.me NetworkManager[838]: <info> (eno1): new Ethernet device (carrier: OFF, driver: 'e1000e', ifindex: 2) Dec 09 13:36:32 s217.mydomain.me NetworkManager[838]: <info> (eno1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Dec 09 13:36:32 s217.mydomain.me kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready Dec 09 13:36:32 s217.mydomain.me kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready Dec 09 13:36:32 s217.mydomain.me NetworkManager[838]: <info> (eth1): new Ethernet device (carrier: OFF, driver: 'e1000e', ifindex: 3) Dec 09 13:36:32 s217.mydomain.me NetworkManager[838]: <info> (eth1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Dec 09 13:36:32 s217.mydomain.me kernel: IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready Dec 09 13:36:32 s217.mydomain.me kernel: IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready Dec 09 13:36:35 s217.mydomain.me kernel: e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Dec 09 13:36:35 s217.mydomain.me kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready Dec 09 13:36:35 s217.mydomain.me NetworkManager[838]: <info> (eth1): link connected Dec 09 13:36:35 s217.mydomain.me NetworkManager[838]: <info> (eth1): device state change: unavailable -> disconnected (reason 'carrier- changed') [20 30 40] Dec 09 13:36:35 s217.mydomain.me NetworkManager[838]: <info> Auto- activating connection 'eth1'. Dec 09 13:36:35 s217.mydomain.me NetworkManager[838]: <info> (eth1): Activation: starting connection 'eth1' (0d9c850a-1545-481c-897f- 84d4475e0377) Dec 09 13:36:35 s217.mydomain.me NetworkManager[838]: <info> (eth1): device state change: disconnected -> prepare (reason 'none') [30 40 0] Dec 09 13:36:35 s217.mydomain.me NetworkManager[838]: <info> (eth1): device state change: prepare -> config (reason 'none') [40 50 0] Dec 09 13:36:35 s217.mydomain.me NetworkManager[838]: <info> (eth1): device state change: config -> ip-config (reason 'none') [50 70 0] Dec 09 13:36:35 s217.mydomain.me NetworkManager[838]: <info> Activation (eth1) Beginning DHCPv4 transaction (timeout in 45 seconds) Dec 09 13:36:35 s217.mydomain.me dhclient[1239]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6 (xid=0x21a0ce6c) Dec 09 13:36:41 s217.mydomain.me dhclient[1239]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6 (xid=0x21a0ce6c) Dec 09 13:36:41 s217.mydomain.me dhclient[1239]: DHCPREQUEST on eth1 to 255.255.255.255 port 67 (xid=0x21a0ce6c) Dec 09 13:36:41 s217.mydomain.me NetworkManager[838]: <info> (eth1): DHCPv4 state changed unknown -> bound Dec 09 13:36:41 s217.mydomain.me NetworkManager[838]: <info> (eth1): device state change: ip-config -> ip-check (reason 'none') [70 80 0] Dec 09 13:36:41 s217.mydomain.me nm-dispatcher[1300]: Dispatching action 'pre-up' for eth1 Dec 09 13:36:41 s217.mydomain.me NetworkManager[838]: <info> (eth1): device state change: ip-check -> secondaries (reason 'none') [80 90 0] Dec 09 13:36:41 s217.mydomain.me NetworkManager[838]: <info> (eth1): device state change: secondaries -> activated (reason 'none') [90 100 0] Dec 09 13:36:41 s217.mydomain.me NetworkManager[838]: <info> Policy set 'eth1' (eth1) as default for IPv4 routing and DNS. Dec 09 13:36:41 s217.mydomain.me NetworkManager[838]: <info> (eth1): Activation: successful, device activated. Dec 09 13:36:41 s217.mydomain.me nm-dispatcher[1300]: Dispatching action 'up' for eth1 Dec 09 13:45:22 s217.mydomain.me dhclient[1239]: DHCPREQUEST on eth1 to 111.222.333.193 port 67 (xid=0x21a0ce6c) Dec 09 13:45:22 s217.mydomain.me NetworkManager[838]: <info> (eth1): DHCPv4 state changed bound -> bound Dec 09 13:45:22 s217.mydomain.me nm-dispatcher[1853]: Dispatching action 'dhcp4-change' for eth1 Dec 09 13:54:12 s217.mydomain.me dhclient[1239]: DHCPREQUEST on eth1 to 111.222.333.193 port 67 (xid=0x21a0ce6c) Dec 09 13:54:12 s217.mydomain.me NetworkManager[838]: <info> (eth1): DHCPv4 state changed bound -> bound Dec 09 13:54:12 s217.mydomain.me nm-dispatcher[2313]: Dispatching action 'dhcp4-change' for eth1 Dec 09 14:03:00 s217.mydomain.me dhclient[1239]: DHCPREQUEST on eth1 to 111.222.333.193 port 67 (xid=0x21a0ce6c) Dec 09 14:03:00 s217.mydomain.me NetworkManager[838]: <info> (eth1): DHCPv4 state changed bound -> bound Dec 09 14:03:00 s217.mydomain.me nm-dispatcher[2779]: Dispatching action 'dhcp4-change' for eth1 Dec 09 14:12:59 s217.mydomain.me dhclient[1239]: DHCPREQUEST on eth1 to 111.222.333.193 port 67 (xid=0x21a0ce6c) Dec 09 14:12:59 s217.mydomain.me NetworkManager[838]: <info> (eth1): DHCPv4 state changed bound -> bound Dec 09 14:12:59 s217.mydomain.me nm-dispatcher[3286]: Dispatching action 'dhcp4-change' for eth1 [root@s217 ~]# [root@s217 ~]# ip route default via 172.18.0.1 dev eth1 proto static metric 100 172.18.0.0/16 dev eth1 proto kernel scope link src 172.18.174.77 metric 100 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 111.222.333.193 via 172.18.0.1 dev eth1 proto dhcp metric 100 [root@s217 ~]# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: <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: eth1: <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 inet 172.18.174.77/16 brd 172.18.255.255 scope global dynamic eth1 valid_lft 1039sec preferred_lft 1039sec inet6 fe80::21e:67ff:fe8b:b930/64 scope link valid_lft forever preferred_lft forever 4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 52:54:00:62:c8:4a brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 500 link/ether 52:54:00:62:c8:4a brd ff:ff:ff:ff:ff:ff [root@s217 ~]# But if I move the connection to eth1 (eno1 not connected) and reboot ... surprise ... now I have eth0!!! [root@s217 network-scripts]# ls ifcfg-* ifcfg-eno1 ifcfg-eth1 ifcfg-lo [root@s217 network-scripts]# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default gateway 0.0.0.0 UG 100 0 0 eth0 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0 111.222.333.192 0.0.0.0 255.255.255.224 U 100 0 0 eth0 [root@s217 network-scripts]# ip route default via 111.222.333.193 dev eth0 proto static metric 100 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 111.222.333.192/27 dev eth0 proto kernel scope link src 111.222.333.217 metric 100 [root@s217 network-scripts]# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:1e:67:8b:b9:31 brd ff:ff:ff:ff:ff:ff inet 111.222.333.217/27 brd 111.222.333.223 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::21e:67ff:fe8b:b931/64 scope link valid_lft forever preferred_lft forever 3: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 00:1e:67:8b:b9:30 brd ff:ff:ff:ff:ff:ff 4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 52:54:00:62:c8:4a brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 500 link/ether 52:54:00:62:c8:4a brd ff:ff:ff:ff:ff:ff [root@s217 network-scripts]# So after changing the connection I have configuration virtually moved eno1-->eth0 and eth1-->eno1 and I have static address. Fedora 23 is not in beta stage, so I do not think it is ok. C.S. -- 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
