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.
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Why is iwconfig seeing eth1 as wireless as well as ifconfig?
Can I change how iwconfig calls to wlan0?
I've got ndiswrapper and the driver from windows. Now I just don't know, I've been trying everthing for a while. Need some new ideas.
I have used ndiswrapper in the past and my wireless interface would appear as eth1 also. Now that I have support in the kernel I am using wlan0.
I am not a debian user but on the Fedora side I think you can add aliases to /etc/modprobe.conf or /etc/modules.conf if you want to try that.
In general I would try getting your card to work manually using iwconfig and then update the needed config files to make it work all the time on boot etc.
I see you have an IP address but the interface does not appear to be up. Try some of the items below to and see if you can find more information. One thing to check and use is to specify the channel setting for the iwconfig configuration. Another thing I had to do was try different drivers for my Dell laptop. I was able to find 5 different drivers and one of them finally worked and got ndiswrapper working correctly.
It sounds like you problem may be with either the ndiswrapper or the wireless configuration.
First before we go any futher tell us what version of linux you are using. Better yet from terminal (konsole) type 'uname -a' and that will tell us which kernel you are running. I have run accross some of the later model cards that will not work on any kernels before 2-6-22. I will do more research on your card but it appears that your driver is not working. Also type in terminal 'ndiswrapper -l' and make sure the driver is there.
Well my kernel is 2-6-18, could be some problems there. However the install file requires -16 or higher. I went back and and verified my ndiswrapper install, moved both the .inf and the .sys driver to the same directory as per the install file. the driver shows installed however the -l option gives a bad result. Does this driver need to be in specific directory? Here are the latest screen shots.
You did not tell me which distro you are using but here is a Suse 10.2 installation guide step by step that I referred to on my first install. It is basic and should work with any distro as long as you have ndiswrapper installed. Do not miss a step in the installation and if there is something you do not understand, does not work or if it is a success get back and let us know.
It's Debian Etch on my box and laptop both have 2.6.18. Would I have less problems with a higher Kernel? And do you recommend, I hate to call myself a newbe but, someone with about a year under the belt with linux to start jacking with the kernel? I have a fairly good background w/ MS and can find my way out of a wet paper sack.
As I mentioned before you can find different versions of this driver. I have seen this problem before with the BCM wireless adapter driver you are using. I was able to collect about 5 different drivers from the Dell site (Dell laptop of course) and one of them finally worked with the ndiswrapper.
If you try to locate these that may solve your problem.
After may attempts to rectify this issue, Uninstalling reinstalling. I was able to pull the driver out of my dual booted system, (ntfs-3g). In addition I found that the Module bcm43xx conflicted with ndiswrapper. All of this said, My card will show up yet nothing will broadcast.??? I've blacklisted bcm43xx. My wifi tools are the latest. with KWiFimanager my network is visible, still not connection. in network settings (control center ) my wireless dev shows enabled, however there is not an IP. So I assume that my device thinks it's up (yeah i tried ifdown/up)but not configured or needs sym link or pipe. Why is this such a pain? is there a better kernel patch? BTW 2.6.18-6-686 is my uname -r. agian I'm at a loss.
Is there a way to map out how the ethernet is linked. I noticed in lsmod the ndiswrapper shows no usage, a clue maybe? I can plug my laptop into the router directly (defeats the purpose!!!) and I can go wireless in xp_home bcmwl5 is the driver i pulled out of the win/system32 folder. this thing is teasing me.
Send the output of iwconfig, iwlist scanning, cat /proc/net/wireless, lsmod, lspci, ifconfig -a and dmesg. Again I would try to locate a few different versions of the windows driver and try that and note the results of each one in regards to the output of dmesg, iwconfig, lsmod, iwconfig, ifconfig -a. Also without ndiswrapper running do you see any indication of a wireless card being present? In later kernels you may not need ndiswrapper any longer.