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.
You seem to have a functional wireless card on eth1, is that not the one you're trying to use?
When I try to activate the card and connect I get the following error:
Could you be a bit more specific about the commands you're using here? Also, what kernel are you using? If it is one of the newer kernels, there is a chance that the native linux Broadcom driver, bcm43xx, is being used. Have a look at the output of lsmod to see. If it is there you need to choose either that or ndiswrapper since they will conflict with each other.
Some time ago I was using the ipw2200 linux driver which definately requires firmware and confused the two.
Specific firmware is not required for ndiswrapper. I do apologise.
I did install ndiswrapper for a friend over the weekend - a broadcom chipset.
Your iwconfig confirms that ndiswrapper is working correctly and that your card is alive.
Keeping in mind the post from hangdog42, you only need to assign an IP address and a gateway, if required, or do;
dhcpcd wlan0 to assign dhcp.
You can prevent conflicting kernel modules from loading in your init scripts, or blacklist them. Otherwise, unset them in your kernel config and recompile.
Slackware is easy in this respect, but I don't have a lot of experience with Debian. Someone else could help you there.
Last edited by The_Outlander; 07-23-2006 at 07:35 PM.
Hi thanks for you replies, and sorry for not replying sooner. Unfortunately I have somehow managed to lose the ethernet connection as well now (Eth0). I am not sure what I have done but I am going to have to reconfigure the networking completely.
For what its worth, I was troubleshooting with a friend yesterday, and when he made some changes, and restarted his X server, his eth0 went down. He said it happens every now and again, and he got it working again right away by doing " ifup eth1 " because he said, it switches back and forth between eth0 and eth1, he does not know why -- but he is in Debian testing, if that makes a difference..
An update - I looked around the forums again (here and at Ubuntu) and found a shell script that one of the Ubuntu crowd had prepared. It basically automates the process of installing and configuring ndiswrapper. This still didn't work for me but the author provided a short troubleshooting section and I tried out his suggestions.
In the terminal I entered "dhclient" as root, and I suddenly had a connection. I can't believe how long it has taken me to figure this out. My own fault for not taking the time to research it properly.