On Sat, January 27, 2007 7:16 pm, Chris Mauricio wrote: > On Saturday 27 January 2007 18:01, DJA wrote: >> Chris Mauricio wrote: >> > On Friday 26 January 2007 21:11, DJA wrote: >> >>> Chris >> >> >> >> I just did an FC5 --> FC6 fresh install on my laptop. I have no >> problems >> >> so far getting a connection. I don't know what wlanassistant is, but >> I >> >> use the provided NetworkManager and nm-applet in KDE with not >> problems. >> >> This includes getting a WPA/WPA2 connection using KWallet to manage >> >> passwords. >> > >> > can you describe the network manager utility you are using? I can't >> seem >> > to find it.. perhaps it handles the card differently that what I am >> > using. >> >> http://www.gnome.org/projects/NetworkManager/ >> >> They can describe it better than I. I have been using it since early >> FC5. I know it is part of the FC6 install, although maybe not one of the >> default install packages. I might have added it post install, though it >> certainly is in the Fedora repo's. >> >> It is a service, and I believe is disabled by default. You'll have to >> enable it yourself (system-config-services). There is a sister app for >> it which is a panel applet. It's called KNetworkManager (binary called >> knetworkmanager) for KDE, and I think nm-applet is for Gnome. The old >> GUI control (pre-FC5) is called NetworkManagerInfo (binary is spelled >> like that also). >> >> > I have a combination of KWiFiManager and the standard Network Device >> > Control applet. >> >> I also have used those on occasion when NetworkManager didn't work. But >> I found that KWiFiManager to both flaky, inflexible, and less than >> powerful. Marginally better than just using Wireless Tools. >> >> > I am unfamiliar with KWallet for WPA / WPA2 - a short description >> > would be greatly appreciated! >> > >> > C. >> >> http://docs.kde.org/stable/en/kdeutils/kwallet/index.html >> >> KWallet is the KDE password manager, basically a keyring. You store your >> passwords in KWallet which itself is password protected. It does not >> (necessarily) use the same password associated with the current UID. >> >> In the WiFi context, when you access a password protected AP, KWallet >> will (after asking for it's own password) look for the needed AP >> password and pass it to the AP. It handles WEP, WPA, etc. >> >> It's not perfect, doesn't work for all AP authentication protocols (nor >> do I think yet for VPN's), but like WiFi on Linux in general, gets >> better a month at a time. >> >> -- >> Best Regards, >> ~DJA. > > > OK. I got this working- apparently it is not installed if you only choose > KDE > desktop and leave out gnome. Thanks very kindly! dhcp is working as > expected, it picks up gw on the home network now. Strange as one would > assume > both netowrk managers call the DHCP scripts and just inherit the results > of > ifup and dhcp request, but I guess this turns out not to be the case. > > Need to play with the wallet feature, it seems to NOT want to retain the > wep > key for the network and pass it over when knetworkmanager fires up and > tries > to join the home wifi. > > Thanks very much again, your help is thoroughly appreciated!! > > C. >
Just got back from a week's trip (Portland OR) in which this was my exact problem. FC5, Gnome. Everything came in but no UG on route -n. This was true at the hotel, the clinet site (OHSU hospitals), but strangely I got the free wireless at Powell's books. All of these places had browser click throughs, and I wondered if that was pertinent, but without a default gateway, I obviously didn't get that far. I have to admit, I didn't entire understand the thread (a bit tired and wireless clueless). "Necessary services"? Which? What was Chris's fix again? TIA, -- Lan Barnes SCM Analyst Linux Guy Tcl/Tk Enthusiast Biodiesel Brewer -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
