Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So I am having trouble (still) with this linksys card...
I am following the Ubuntu Community ndiswrapper doc https://help.ubuntu.com/community/Wi...er/Ndiswrapper
I am running Ubuntu 7.10 Gutsy 2.6.22-14-generic
ndiswrapper-1.45
ndiswrapper-utils 1.9 (both of which were installed through synaptic off the installation cd)
ndisgtk 0.7.2
All of these are installed and working properly (as far as I can tell)
I have a linksys 802.11b WMP11 ver4 and I got the driver package off the ndiswrapper website. There are three drivers present, but the only one that seems to work is the lsipnds.inf. When loaded, it says "driver loaded, hardware present". wmp11nds.inf returns "driver loaded, no hardware present" and lsicmnds.inf retuns "invalid driver".
So therefore I thought that the only driver I needed was the lsipnds.inf.
I went to the terminal and ran
sudo depmod -a
sudo modprobe ndiswrapper
and
tail /var/log/messages
to check for error messages, of which there were none...
Success!!! No....
When I go to configure the network, there is no network...
I have a (dial-up)modem connection, but no wireless connection
Well, I uninstalled ndiswrapper 1.45 as per the uninstallation instructions and installed ver 1.48, reinstalled the lsipnds.inf driver, and the wireless network was detected!!
Don't know what the deal was, but it seems to be up now...
thanks for replying
ps. there weren't any errors with modprobe ndiswrapper, but wlan0 did not show up on ifconfig... It was strange that ndiswrapper saw my device but ubuntu didn't... I'd better not ask too many questions, just glad it works now...
Short-lived victory, I'm afraid. I can indeed detect my wireless network, but I am unable to ping my router, much less connect to my network.
Initially I thought it was security-related, having to do with encryption (WPA-PSK), so I dropped it down to WEP but couldn't get anything to work... Been playing around with the router settings and network config for a couple hours, but then I realized that if I can't even ping the router then encryption doesn't matter (stupid) so am I right in thinking this has to be a hardware issue?
jb@jb-desktop:~$ modprobe ndiswrapper
jb@jb-desktop:~$ ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:469 errors:0 dropped:0 overruns:0 frame:0
TX packets:469 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:43631 (42.6 KB) TX bytes:43631 (42.6 KB)
wlan0 Link encap:Ethernet HWaddr 00:0F:66:3B:09:5F
inet6 addr: fe80::20f:66ff:fe3b:95f/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:701 errors:0 dropped:0 overruns:0 frame:0
TX packets:910 errors:0 dropped:32 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:82840 (80.8 KB) TX bytes:114236 (111.5 KB)
Interrupt:5 Memory:e8004000-e8004800
wlan0:ava Link encap:Ethernet HWaddr 00:0F:66:3B:09:5F
inet addr:169.254.3.140 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:5 Memory:e8004000-e8004800
jb@jb-desktop:~$ iwconfig
lo no wireless extensions.
wlan0 IEEE 802.11b ESSID:"Cook"
Mode:Managed Frequency:2.437 GHz Access Point: 00:1A:70:44:D0:D9
Bit Rate=1 Mb/s Tx-Power:17 dBm
RTS thr:2347 B Fragment thr:2346 B
Power Management:off
Link Quality:53/100 Signal level:-62 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
no errors from modprobe ndiswrapper
"lo" is a looback extension, and I have no idea why its there
wlan0 is my wireless connection
wlan0:ava doesn't really exist, or so I am told when I try to use/remove it. Makes no sense to me...
OK, now that you seem to have a working ndiswrapper installation, run iwconfig wlan0 to see if the card is associated with the access point.
If not, try bringing up the interface manually - ifconfig wlan0 up
Then, set the wireless parameters with iwconfig mode managed essid <your_ssid> key 012345678
Finally, try to obtain an IP address - dhclient wlan0
Assuming that results in a working connection, put the parameters in the config file for wlan0 to automate connection on boot.
If whatever GUI tool you're using does not save the wireless parameters, then yes, you can edit the stuff in /etc/network/interfaces to allow them to persist through a reboot.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.