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 have exactly same problem. my ssid matches that found both by wpa_supplicant and iwlist wlan0 scanning, both in ascii and hex (made a hexdump of it). non the less, wpa_supplicant reports an ssid missmatch.
I been using linux for a while now, server side, and recently decided to give it a try and use it as my personal OS. One of the early issue i saw is how come there is not a unified set of steps to do things for example trying to get the wireless to work, there is so many links, docs etc that you don't know which one you should follow
I am for sure a linux fan and i consider it my first choice of OS and nothing will change my opinion but i thought that we should unify things, steps, instructions etc... so at least for the new comers it won't be hard to get into linux.
Distribution: Slackware / Debian / *Ubuntu / Opensuse / Solaris uname: Brian Cooney
we should unify things, steps, instructions etc..
This is a hot debate topic.
Part of what makes linux so great is its choice and flexibility. Unfortunately, that also means there are sometimes more than one way to pluck a turkey.
As an end user, there are two ways to deal with this issue. The first way, which is probaly preferable, is when searching for a problem, include the name of your distro in the search parameters so that instructions you find will usually be distro-specific.
The second way, is to try to find vender-nonspecific instructions.... usually this means using the lower level command line tools, rather than using the gui. I always try to give help in this way when I answer questions, because while GUI tools vary from distro to distro, usually the command line tools are a constant
The fascinating thing is the flexibility of the OS and that greatly relies on the fact that processes remain modular. guis and wrappers may be written to actually simplify configurations, but i value the fact that things are build up by many small bricks.
the problem about all this is the incredible complexity of even the most rudimentary tasks (getting characters onto the screen for example). although i enjoy that world, it still can make things annoying if you are set of to accomplish something specific. I for example want to build my own linux, for the experience. basically now i only need X to run and i want X11R7.2 . So now I'm stuck at the WPA2 encryption of my adapter for almost a week and I do not aim to find out how the single parameters of available encryption algorythms interact with the sourcecode of wpa_supplicant in order to deceiver the error messages. i only need that thing to work.
however error messages don't get me any further (the ssid is "Hive", so why is there a ssid missmatch if Hive is found???) and that is extremely frustrating.