I like Donn's recommendations. The network configuration GUI tool works ok for me with FC3, but I'm not using WPA (yet), nor ndiswrapper (I'm using the ACX111 driver for my chipset, which is source-only and still beta). That being said, on FC3 the network configuration parameters are found in /etc/sysconfig/network-scripts/ifcfg-wlan0 (for device wlan0, replace with appropriate device name). I think you can simply rename (and edit the contents of) ifcfg-eth[n] to ifcfg-wlan[n] (substitute an appropriate number). Your wired device could be eth0, internal wireless wlan0, and wireless card wlan1. If (when) you use WEP encryption, there's an additional keys-wlan[n] file in the same directory. Once these files are there, the GUI tool should work ok, but keep Donn's warning in mind, and double check the configuration with cl tools. Donn, what do your configuration files looks like with WPA enabled? I haven't found (haven't looked very hard though) documentation for those files yet. Donn Shumway wrote: > Generally, I found that trying to use both command line and GUI tools > (at the same time) is counter-productive. I would avoid the GUI tools > (especially when configuring WiFi). Case in point, the KDE tool > Kwifimanager (or something like that did nothing but get in the way when > configuring my Broadcom chipset. It did not support WPA (which I was > trying to use) and when I would update anything using Kwifi my whole > connection would become flaky of non-existent. > > In answer to your question, what 'ifconfig' show? It should show all you > network connections, including wlan0. > > FWIW, the sympton you describe is one I saw many times when the driver > did not work right. > > What are you AP settings? Are you using WPA or WEP? I suggest you make > this as simple as possible to start. First, turn off any encryption. For > safety, set MAC address filtering on your AP to only accept YOUR MAC > addresses. This should afford some reasonable protection while you are > getting it to work. If you can pre-configure your SSID (in iwconfig, I > think), you could also turn off SSID broadcast on your AP. > > Now, test the connection. If it works you can work on the encryption > part of setup. If not, look in the ndiswrapper wiki for another possible > driver. > > Let us know how it's going. > > On 4/24/05, Mike Hoy > wrote: > > hi, > > last time i stuck a pcmcia wifi card in my computer i was able to detect > the access point but never got an ip address and obviously couldn't get > on the network. > > then craig white and i found out that all we needed to do was add the > network card (eth0) to the Network Applet in Applications -> System > Settings. > > then it worked. > > so i've decided to try getting my on board wifi card working. thanks to > that ndiswrapper thread. :-) > > i have to say it went well. i think it is working. > > i can iwlist wlan0 scan > > and i get the access point info but can't get on the network. > > so i thought why not add this wlan0 to the network applet. but it won't > accept the wlan0 format. it has to be eth(#). > > any suggestions? > > mike hoy > --------------------------------------------------- > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us > > To subscribe, unsubscribe, or to change you mail settings: > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss > > > > > > -- > Donn > "Sarcasm is the safe alternative to expressing anger." > --Richard North Patterson > > -- -Eric 'shubes' "There is no such thing as the People; it is a collectivist myth. There are only individual citizens with individual wills and individual purposes." -William E. Simon (1927-2000), Secretary of the Treasury (1974-1977) "A Time For Truth" (1978), pg. 237 --------------------------------------------------- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change you mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss