Hello Sharif,

This is a known problem with Fedora Core 11 and it seems to be related to the NetworkManager. It seems like it has to be disabled and then you won't have this problem again. This has also been reported on Fedora Core 10 and not only 11.

1) Login to your server as root

2) Check NetworkManager service status

[root@fedora fedora11]# service NetworkManager status

3) Stop the service

[root@fedora fedora11]# service NetworkManager stop

4) Disable NetworkManager from automatically start successful by executing the chkconfig command

[root@fedora fedora11]# chkconfig –list NetworkManager

NetworkManager  0:off   1:off   2:off   3:off   4:off   5:off   6:off

[root@fedora fedora11]# chkconfig –level 2345 NetworkManager off