In FC6 network interface doesn't come up if 'service network restart' command is run

rajat · 05-02-2007, 07:58 AM

Hi All,

I'm having 2 Fedora Core 6 machines with kernels 2.6.18 and 2.6.20

I am facing a problem with the eth1 interface on machine with kernel 2.6.20

In the GUI of neat command, the eth1 is configured with an IP address : 172.16.0.189. After having configured this IP the interface is made active in the GUI, by clicking on the activate button. On the command line once I issue commands service network restart and ifconfig, eth1 does not come up. That is the eth1 does not come as active. To confirm this, in the GUI of neat command the same interface is shown as inactive.

I'm facing the similar issue with some of the other virtual interfaces of eth0 on my other FC6 machine with kernel 2.6.18

Strangely, if I do not issue the command service network restart and just make it active in the GUI of neat command and the output of ifconfig shows eth1 as active. Same happens with other interfaces on the other machine.

So the problem is clearly with the service network restart command, which does not bring up or make active these interfaces.

Does anybody else found the similar problem?

Is this really a problem? I mean, do we not require 'service network restart' any longer with FC6 and just setting the interface as active in GUI of neat command is sufficient to make any interface active.
Please help.

Regards,
Rajat

Lenard · 05-02-2007, 08:24 AM

No it is not a problem with the network service, check your ifcfg-eth1 file in /etc/sysconfig/network-scripts for the line: ONBOOT=yes

Sample output;

Code:

# service network restart
Shutting down interface wlan0:                             [  OK  ]
Shutting down loopback interface:                          [  OK  ]
Bringing up loopback interface:                            [  OK  ]
Bringing up interface wlan0:                               [  OK  ]

rajat · 05-03-2007, 12:53 AM

Lenard,

Thanks for pointing me to /etc/sysconfig/network-scripts. The problem of eth1 along with the virtual interfaces eg : eth1:2 also got resolved.

As you suggested, setting ONBOOT=yes in ifcfg-eth1 solved the eth1 problem.
Setting ONPARENT=yes in ifcfg-eth1:2 solved the eth1:2 problem.

Thanks very much.