Re: F23 Server: unexpected network problem

2015-12-10 Thread Cristian Sava
On Thu, 2015-12-10 at 16:49 -0800, Gordon Messmer wrote: > On 12/09/2015 11:36 PM, Cristian Sava wrote: > > We are in stable stage so I do not expect NIC name changes without > > consistent reason. > > I've never noticed it before, but this does look like a bug in > Fedora. > > On my workstation,

Re: F23 Server: unexpected network problem

2015-12-10 Thread Gordon Messmer
On 12/09/2015 11:36 PM, Cristian Sava wrote: We are in stable stage so I do not expect NIC name changes without consistent reason. I've never noticed it before, but this does look like a bug in Fedora. On my workstation, for instance, /var/log/anaconda/anaconda.journal.log contains: Jul 21 2

Re: F23 Server: unexpected network problem

2015-12-10 Thread Doug H.
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? > > ... >

Re: F23 Server: unexpected network problem

2015-12-09 Thread Cristian Sava
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:3

Re: F23 Server: unexpected network problem

2015-12-09 Thread Cristian Sava
On Wed, 2015-12-09 at 13:52 +, Kseniya Blashchuk wrote: > Yeah, strange a bit, but it seems you have some udev rules > configured. It can cause interface naming mess maybe. > No, nothing configured. That happen on F23 server & workstation installs on real hardware. Steps to reproduce: Install

Re: F23 Server: unexpected network problem

2015-12-09 Thread Gordon Messmer
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

Re: F23 Server: unexpected network problem

2015-12-09 Thread Kseniya Blashchuk
Yeah, strange a bit, but it seems you have some udev rules configured. It can cause interface naming mess maybe. ср, 9 дек. 2015 г. в 16:02, Cristian Sava : > On Wed, 2015-12-09 at 12:02 +, Kseniya Blashchuk wrote: > > Yep, sorry. So you restarted after changing BOOTPROTO? Try looking > > int

Re: F23 Server: unexpected network problem

2015-12-09 Thread Cristian Sava
On Wed, 2015-12-09 at 12:02 +, 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

Re: F23 Server: unexpected network problem

2015-12-09 Thread Kseniya Blashchuk
Yep, sorry. So you restarted after changing BOOTPROTO? Try looking into dmesg or journalctl -n1000 | egrep "eno|eth", or something like that. ср, 9 дек. 2015 г. в 14:52, Cristian Sava : > On Wed, 2015-12-09 at 11:47 +, Kseniya Blashchuk wrote: > > But BOOTPROTO=dhcp is set for eth1. For which

Re: F23 Server: unexpected network problem

2015-12-09 Thread Cristian Sava
On Wed, 2015-12-09 at 11:47 +, Kseniya Blashchuk wrote: > But BOOTPROTO=dhcp is set for eth1. For which interface do you want > static config? Did you restart the networking after you made config > changes? Read again, eth1 is not connected! Only eno1 is in use! C.S. -- users mailing list use

Re: F23 Server: unexpected network problem

2015-12-09 Thread Kseniya Blashchuk
But BOOTPROTO=dhcp is set for eth1. For which interface do you want static config? Did you restart the networking after you made config changes? ср, 9 дек. 2015 г. в 14:39, Cristian Sava : > > > > > Might > > BOOTPROTO=static > > help? > > > > suomi > > No, it does not help > > C.S. > > -- > user

Re: F23 Server: unexpected network problem

2015-12-09 Thread Cristian Sava
> > Might > BOOTPROTO=static > help? > > suomi No, it does not help C.S. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F23 Server: unexpected network problem

2015-12-09 Thread fedora
On 12/09/2015 09:51 AM, Cristian Sava wrote: On Wed, 2015-12-09 at 10:41 +0200, Cristian Sava wrote: I Installed F23 Server with static address but after updating that it got an automatic one. Why that? I consider that extremely dangerous. That was verified and happened on different hardware b

Re: F23 Server: unexpected network problem

2015-12-09 Thread Cristian Sava
On Wed, 2015-12-09 at 10:41 +0200, Cristian Sava wrote: > I Installed F23 Server with static address but after updating that it > got an automatic one. Why that? I consider that extremely dangerous. > That was verified and happened on different hardware boxes. > Do I miss something? Does anyone els

F23 Server: unexpected network problem

2015-12-09 Thread Cristian Sava
I Installed F23 Server with static address but after updating that it got an automatic one. Why that? I consider that extremely dangerous. That was verified and happened on different hardware boxes. Do I miss something? Does anyone else saw that? This is what I have (eno1 wired, eth1 not connected)