Aaron Konstam <akonstam <at> sbcglobal.net> writes: > Well there is one more thing you need to do. That is to stop > the /etc/init.d script network. chkconfig network off > will do that. If network is running at the same time as NM I would > expect the connection dropping you experience. I had in fact stopped the network service before running NM - but it still was flaky - it is possible the wireless signal from the AP was weak in my office but I will try this again next week in a stronger signal area. > Forget about trying to configuure wpa_supplicant. NM does that. My Does that mean that the wpa_supplicant.conf generated when NM makes the connection is saved somewhere? If so I would like to be able to get at that file and use it directly - after all with wpa_supplicant then all the network blocks in the config file are tried to look for a connection - so if wpa_supplicant daemon is set to come up at boot then it should "just work" whichever AP you are near that is profiled in the config file. At least that was my intention - that way I don't need to do anything except log in to my KDE session and I should be able to work with it immediately. I guess with NM you still have to choose which wireless to connect to each time you log in?
