[SOLVED] network.service

ferrari · 11-01-2017, 02:11 AM

The ens0 interface is down. After you changed the config file naming, did you restart wicked (or reboot)?

Try bringing up the interface with

Code:

ifup ens0

then once that's done check that there is a valid IP address assigned again.

nordsense · 11-01-2017, 02:24 AM

Yes I did reboot. I do not see ens0 anywhere.

ferrari · 11-01-2017, 02:25 AM

I meant ens3, as your output shows.

nordsense · 11-01-2017, 02:28 AM

I changed ifcfg-eth0 to ifcfg-ens3 rebooted and ran ifup ens3 and I got this

ferrari · 11-01-2017, 02:30 AM

Your image of the ifcfg-* config files still show ifcfg-eth0, rather ifcfg-ens3. I think you should review the links I gave in my initial reply. You do need some basic Linux and networking knowledge, otherwise things are gong to be a struggle.

nordsense · 11-01-2017, 02:31 AM

I changed it back to ifcfg-ens3. You confused me when you said:

he ens0 interface is down. After you changed the config file naming, did you restart wicked (or reboot)?

Try bringing up the interface with

ifup ens0
then once that's done check that there is a valid IP address assigned again.

nordsense · 11-01-2017, 02:33 AM

sI changed ifcfg-eth0 to ifcfg-ens3 rebooted and ran ifup ens3 and I got this

ferrari · 11-01-2017, 02:34 AM

Ok, make sure that the configuration file matches the actual interface name, then try to bring it up manually, and check the status again.

ferrari · 11-01-2017, 02:35 AM

Report back with output from

Code:

ls -l /etc/sysconfig/network-scripts/ifcfg-*

nordsense · 11-01-2017, 02:39 AM

Quote:

Originally Posted by ferrari

Report back with output from

Code:

ls -l /etc/sysconfig/network-scripts/ifcfg-*

I do not know what you mean by "bring it up manually". Here is the screen shot of that output

ferrari · 11-01-2017, 02:42 AM

I mean using the ifup command. I note that you still have ifcfg-eth0:0 present. If it's needed at all, it should be ifcfg-ens3:0. That will cause issues otherwise.

nordsense · 11-01-2017, 02:59 AM

Hello

ifup ens3 returns the same [/etc/sysconfig/network-scripts/ifup-eth] Device eth0 does not seem to be present, delaying initialization. I am wondering why this ifup ens3 command keeps talking about eth0...I have triple checked and the configuration file is indeed named ens3. I have also changed eth0:0 to ifcfg-ens3:0, brought it up manually and rebooted. Still not able to connect.

ferrari · 11-01-2017, 03:06 AM

You need to share your actual configuration in ifcfg-ens3 and ifcfg-ens3:0. Did you change the 'DEVICE=' and 'NAME=' entries to match the actual device node name? I suspect not.

nordsense · 11-03-2017, 12:54 AM

Dear ferrari

I want to thank you for taking time to look over this problem for the last couple of days. I changed the DEVICE= name to match the node name; also ONBOOT=no so I switched this to ONBOOT=yes and now I am able to SSH.

Thank you

ferrari · 11-03-2017, 01:55 AM

Glad to have been of help. It would probably have been a good idea to have had you share the configuration from the start. Anyway, good to know its working as expected now.