NetworkManager Is Driving Me Crazy!

[Matthew Saltzman]

On Thu, 2008-03-20 at 16:34 -0400, Rick Bilonick wrote:
> On Thu, 2008-03-20 at 16:02 -0400, Matthew Saltzman wrote:
> > On Thu, 2008-03-20 at 15:13 -0400, Rick Bilonick wrote:
> > > When I first set up Fedora 8, I had some problems getting wlan0 (via
> > > ndiswrapper) working. Now I can prevent wlan0 from being activated, even
> > > when I'm using a wired connection via eth0. 
> > > 
> > > I connect wirelessly at home and wired at the office. When I'm in the
> > > office, I have to turn off NetworkManager (using services), kill
> > > wpa_supplicant and nm-applet, and change config-services-network for
> > > wlan0 so it's not being controlled by NetworkManager. This lets me
> > > activate and use eth0. This works fine for about 30-60 minutes and then
> > 
> > Is this because you have a static address at work?
> > 
> > > wlan0 gets activated and screws up accessing the network. Then I have to
> > > deactivate wlan0 and eth0, and re-activate eth0 so I can use the network
> > > again. I have to do this over and over. 
> > > 
> > > I have no clue as to why wlan0 is being activated with eth0 already
> > > being activated and I don't know what program is causing this to happen.
> > > I suspect it's something to do with NetworkManager because I never had
> > > this problem before using NM. But I don't know for sure.
> > > 
> > > How can I prevent wlan0 from being activated???
> > 
> > In NM, you can turn off all wireless interfaces by right-clicking the
> > applet and unchecking "enable wireless".  Then NM should connect to your
> > wired network only.
> > 
> > The advance release of NetworkManager-0.7.0-0.6.7.svn3370.fc8 at
> > http://koji.fedoraproject.org/koji/ seems to have the ability to connect
> > to the interface described in ifcfg-ethX as an option, rather than
> > connecting via DHCP.
> 
> Yes, I forgot to add that eth0 is using a static address. I had tried
> turning off networking and wireless in the nm-applet but this did not
> stop wlan0 from activating. That's why I killed nm-applet,
> wpa_supplicant and turned off NetworkManager. I don't know what else to
> do.

Try the Koji packages, for one thing.  They allow you to use a static
address defined in ifcfg-ethX, and they may be better about your
spontaneous start problem.  If they don't help with that, try the NM
mailing list at gnome.org.

It's hard to see how a program that isn't running could turn on an
interface, though.  If you prevent NM from running at boot (chkconfig
NetworkManager off), do you have the same problem?

> 
> Rick B.
> 
> 
-- 
                Matthew Saltzman

Clemson University Math Sciences
mjs AT clemson DOT edu
http://www.math.clemson.edu/~mjs