Fedora 17 and Network Manager.

[tomh1000]

I'm having a couple of problems with Network Manager. I have two nic cards. One connected to a DSL and the other connect to my network.

First problem. I don't have a screen shot of my network manager GUI but I'll try to do one in text somewhat.
--------------------------------------------------
My nic connect to DSL (eth0)

* DSL Connection
System (eth0)

My nic connect to my Network (eth1)

* System (eth1)
DSL Connection
--------------------------------------------------

So in this example you can see that my DSL is connected on eth0 and System on eth1 which is what it should be. It's a 50/50 change after boot up it looks like this. Sometimes both eth0 and eth1 try to connect to DSL. I guess my first question is, how do I get rid of the "DSL Connection" from eth1 and get rid of the "System" from eth0 so that each nic can only connect to what it should?

Second problem. At times after sevferal hours the GUI only shows one nic and only system. The only way to recover is to reboot and then everything is fine again for a while.

I hope you can understand what I am trying to convey here and thanks for any help you have to offer.

Tom

[jpollard]

I gave up on NetworkManager. I've seen it work with multiple network interfaces but only on F14. After that it seems to screw things up, and having the definitions switched around was one of the symptoms (mine had the default route swapped improperly as one of the problems).

Try disabling it and enable "networks". If the configuration files are normal, then things should get more stable.

[cnobelw]

Hello! I have some serious problems on Fedora17 that the system will restart when the NetworkManager service is stop or start. I'm using the KDE desktop, and I use the command "service NetworkManager stop", or shall I use the command "systemctl stop NetworkManager.service".

[tomh1000]

Originally Posted by jpollard

I gave up on NetworkManager. I've seen it work with multiple network interfaces but only on F14. After that it seems to screw things up, and having the definitions switched around was one of the symptoms (mine had the default route swapped improperly as one of the problems).

Try disabling it and enable "networks". If the configuration files are normal, then things should get more stable.

Yea I was thinking along those same lines. I never had any problems when I use to run network.

Thanks for the reply,
Tom

---------- Post added at 05:04 PM ---------- Previous post was at 07:39 AM ----------

Originally Posted by cnobelw

Hello! I have some serious problems on Fedora17 that the system will restart when the NetworkManager service is stop or start. I'm using the KDE desktop, and I use the command "service NetworkManager stop", or shall I use the command "systemctl stop NetworkManager.service".

I never saw any restarts but I'm not running KDE either. One thing for sure I can't get Network Manager to behave.

[cnobelw]

Originally Posted by tomh1000

Yea I was thinking along those same lines. I never had any problems when I use to run network.

Thanks for the reply,
Tom

---------- Post added at 05:04 PM ---------- Previous post was at 07:39 AM ----------



I never saw any restarts but I'm not running KDE either. One thing for sure I can't get Network Manager to behave.

I use the H3C client ,and the system will reboot when I execute the command "linux1x -k"