Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Following some of the threads here and other places I was able to install ndiswrapper for the Dell 1390 MiniPCI WLAN card, the light now comes on, and the wireless manager can measure the signal (albeit with SU login to config sub menu). However, selecting Network Manager from the menu does not launch anything -- nothing happens. YaST says it's installed.
So, should I abandon hope for Network Manager and configure the wireless connection with YaST on the card itself?
As soon as I entered knetworkmanager into the terminal I received indications Network Manager was already running. I looked at the System Tray of the Kicker I noticed two incons representing a network wall socket and plug (so that's what that is). So I clicked that and a list of nearby wireless networks show up. CLOSE, but still a problem.
I attempted to connect using the correct passphrase(key) and the progress bar gets to about 57% configured and quits. Still no network access, but REALLY close. What might be wrong?
Selected YaST Details, Wireless Card
Module Name: ndiswrapper
Network Setup Method: User Controlled with Network Manager
Firewall Zone: Internal Zone
Device Activation: On Cable Connection
Bring down the wired interface (if one is running):
ifconfig eth0 down
Bring up the wireless interface:
ifconfig wlan0 up
Set the wireless:
iwconfig wlan0 mode managed essid <your_ssid> key <your_wep_key>
Obtain an IP address:
If that works, maybe someone more familiar with NM and SuSE can help you with the GUI pieces. If not, post the output of ifconfig and iwconfig, along with any errors.
I believe networkmanager is just the backend. The frontend (on my suse 10.2/KDE is Knetworkmanager.
with mine, the plug and socket applet means it's connected to a wired network, whereas small blue bar graph signifies a wireless network.
I configured the network connection in yast (network devices, network card) and chose "on cable connection" for the wired device and "at boot up" for the wireless.
I had a problem with the computer connecting to a "phantom" wired network (no cable plugged in!) and the wireless activating to 57% and no further. Double clicking the wifi network bar after right-clicking the applet would connect the wireless network with no problem.
I re-configured the wired network in yast to be a "manual connection". Since then the phantom wired network no longer prevents the wireless from connecting at bootup.
I think Knetworkmanager (or the backend) has problems with WEP keys (did with mine at least). Finally I removed the WEP security and did a MAC address filter on the router for the family's 4 computers.
I took a visit to the log file:
and noticed something funny:
Mar 15 21:12:40 linux-3zps NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point '2WIRE313'.
Mar 15 21:12:40 linux-3zps NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Mar 15 21:12:40 linux-3zps NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Mar 15 21:12:41 linux-3zps NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction.
Mar 15 21:12:41 linux-3zps NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Mar 15 21:12:41 linux-3zps NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface wlan0
Mar 15 21:12:41 linux-3zps NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface wlan0
Mar 15 21:13:26 linux-3zps NetworkManager: <info> Device 'wlan0' DHCP transaction took too long (>45s), stopping it.
Mar 15 21:13:27 linux-3zps NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) started...
When I checked my 2WIRE DSL modem DHCP was not enabled! So I copied down the assigned IP address (and network mask) and switched the Network Address Setup for the wireless card to the Static Address Setup -- plugged in the values and wha-la! After clicking finish I was able to click on my network in Network Manager, supplied the WEP key and the blue bars and the Wallet showed up.
So NOW I am connected to the home network BUT my browser will not hook up to anything. SO IT IS CLOSE, but something is still off.
must be some incompatibility between my 2WIRE DSL modem and my setup -- getting blue bars, the wlan0 card gets loaded instead of eth0 (set device activation to manual). NetworkManager and the KWallet are starting as expected. Watching the log files -- Network manager complained about the hard-coded gateway/nameservers. So left the IP Address as Static but the Hostname and Name Server as DHCP.
The NetworkManager log file reaches Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete. The blue bars show up (I entered the WEP key into 0 position of the WEP Keys list. It all LOOKS OK, I can even see traffic on my DSL monitor -- BUT my attempts to access the internet with Konqueror yield the dreaded *Unknonwn host* message.
Distribution: PCLinuxOS 2007 on my laptop and Suse 10.2 on my desktop.
I had all kinds of problems in Suse 10.2 with knetworkmanager. Kinternet worked a dream with Suse 10.0, but my laptop wireless hasn't been as stable since I upgraded to 10.2. No idea why...
If the blue bars are up, you're connected! I had a problem with my router not supporting IPv6 and had to turn of this option in Firefox (via about:config) in order for my browser to work. This may have been your problem with Konqueror.
If you still have problems with Fedora, it is your router. Mine is a D-link ADSL router and due to its inherent problems, GAIM refuses to work, Firefox only works with IPv6 disabled and Kubuntu won't update unless I change the DNS settings manually every time I log on!
I got my wireless card (Dell 1390) to work just fine in Fedora 6, although perhaps I owe some credit to all the *practice* I got with ndiswrapper on SuSE 10.2.
The information on the ndiswrapper wiki (installation and troubleshooting) was most helpful.
I was able to follow the compile instructions (make) even-though I had no idea what I was doing -- other than I knew I was compiling.
The troubleshooting page looks like it was written for the Dell laptop.
I had previously downloaded the very large installation file from Dell Support for my card. I expanded and halted the installation and grabbed a copy of the DRIVER folder and ignored the megabytes of everything else (its a big download).
I still have a couple of glitches to work out with NetworkManager. My current routine is:
1. open a terminal and su -
2. modprobe ndiswrapper
3. go to the system tray in the upper task bar (Gnome/Fedora) and de-select enable networks, then enable them again.
The first time step 3 was performed I was prompted to set up the password manager thingy and input the ESSID and WEP passphrase. To my surprise the passphrase format was a key selection, I had been selecting the first (128) choice, but my key worked great with the second choice 64/128 hex something.
Sorry I can't be more accurate -- doing this from memory.
Steps one two and three need to be repeated each time -- but there are some low level cures (rc scripts) which can remedy this, but I haven't tried them yet so I don't want to mislead anyone.
Once the password manager has been fed, you never need to supply the key again.
If you have been following this thread this post represents the END OF THE STORY.
Just to recap, I attempted to use openSuSE 10.2. My limited experience with openSuSE suggests there is definately a *tiered* experience going on there -- but its a fine product, I wish them luck. Perhaps I could have gotten my network card and NetworkManager to work on that platform if I had selected the correct encryption for my WEP passkey (doh!)
Anyway, I switched to Fedora 6 (FC6)and was pleasantly surprised that it recognized my ATI Radeon Mobility graphics card, which openSuSE did not. With openSuSE I was going to have to download/compile/etc. well...stuff.
Anywho...I now have Fedora hooking me up through my Dell 1390 wireless card everytime I boot. If your experience is like mine -- you have wandered through many posts and tales of woe about this baby. So check out the posts above for the install notes about *ndiswrapper* and the three step thing I was stuck in for awhile. Then try this (FC6 only): edit the file
and add these two lines to the bottom of the file:
The password manager dialog will appear after you boot up and log-in.
If at some point in the future you apply a package/update to the kernel you may need to recompile and install ndiswrapper. So, save all those source files,drivers and instructions in a convenient place on the hard drive.