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.
I've installed a wireless card with the ACX100 chipset and it is working just fine with my Suse 8.2 distro, using the acx100.sourceforge-projekt driver - as long as i know the essid, channel etc for the AP, which obvieosly is no problem as long as I am connecting to my own AP at home.
What I would like now was for the card to be able to scan for AP's in range so that i can connect to a public AP at my college, at a café or likevise, without having all the settings that need to be set in iwconfig.
For now the iwconfig settings are being loaded by a hotplug-script, while I am not able to set any of the wireless settings in any of the dir's or files that Suse normaly uses for setting wireless or other network settings.
Hopping somebody can help me out on this one, or at least make it clear to me, that it's not a possebility...
The acx100 open source driver is a bit beta, they've come a long long way, but its usually a beast to blackbox a driver. I know a true Monitor mode isn't that high up on their priority list. Usually if you set a card's mode to managed and its essid to "any" it'll snag a signal by itself, but then you'll still have to fire up dhcp manually.
I was told once that the "few tricks" I've learned about some wireless chipsets was not all that valuable and would soon be obsolete, *sniffle* that's really going to bring me down
One thing I *do* know is that monitor mode has been in the open source acx100 driver for quite a few versions now as well as "iwconfig <dev> ap xx:xx:xx:xx:xx:xx". Actually, the driver still purports to be an "alpha" release (not beta), but is really quite useable on a day to day basis, monitor mode included, try downloading the latest version, acx100-0.2.0pre6_plus_fixes_10, kismet works quite well with this driver and has since about the end of October.
I discovered over 15 discreet networks driving down the middle of a 16 lane highway at 75 mph (actually my daughter was driving, heh) with this driver and kismet...it works.