Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
As a challenge, I've setup a Debian box without a GUI. However, I'm having problems with the wifi. I know this question has probably been asked to death, but none of the internet how-tos work.
My card is a USB zd1211rw (3com branded). I can scan for networks, and find my own WPA network, but can't connect to it. I've setup my '/etc/network/interfaces' file like this:
However, when it tries to connect to the network on boot I don't get any messages about encryption or having connected, only it trying to get a DHCP lease, which of course fails.
Is there a better way (IE one that works) to do this?
Have you looked at the iwconfig man page yet? That tool can be used on CLI level to make a connection and if you want to automate it, you can put it all togeter in a script to launch at logon.
For what it is worth, I have set up wireless N on a headless eBox with a Tp-Link TL-WN861N Wireless N Mini PCI Card.
This has Debian Lenny with the following setup to enable wpa supplicant:
Regards,
Stefan
Well, one problem was that wpa_supplicant wasn't installed. Stupid me assumed every modern distribution installed it, stupid Debian didn't install it by default >.>
I adapted your scripts for my network and no dice. No error messages, but dhclient doesn't get a response. iwconfig tells me I'm associated with my access point, but not connected. I got this working on another box about 4 years ago, it was just a short script. Wish I could remember what I did...
This is a bit harder than wired eh?
Last edited by Joe of Loath; 05-14-2010 at 04:25 PM.
A lot of the drivers and corresponding tools seem to be getting a complete makeover. I wasted most of today trying to revamp my wireless network after a power outage this morning. Turns out I fat fingered the key and it didn't match the existing network. So most of today figuring out why none of my wireless devices could talk to each other, even though they were all basically identical. Because the key on the AP / router didn't match the clients. I'm assuming since using the same script on the clients worked even though it was just a modified version of the existing scripts on those clients.
Got it I initially copied this guide here: http://ubuntuforums.org/showthread.php?t=288753, since it's similar to the one I know worked about 4 years ago. I then realised it didn't work perfectly, and adapted it. Now wpa_supplicant and dhclient simply run at boot.
Thanks for all the help, I'm now even able to run a webserver
Now, lets see how much uptime I can get without the electricity bill going through the roof...
Great to hear you got it solved and thanks for posting the solution (without your adaptations ). I'm sure others can use it as a reference. Please mark your thread as solved using the Thread tools.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.