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.
OK, so say I got a new wireless PCI card, I have a Red Hat 9
system with an ethernet interface (eth0), and I have a screwdriver.
I power down, snap the new card into an empty slot, and power up.
What happens now? I have tried to use the RH Network Configuration
GUI tool, with not so great results. On the web I've gleaned various
different things about editing /etc/modules.conf. I don't even know
what driver to use, or if I did know that, what exactly that means
or what I should do about it.
So - what steps does one go through to make a new wireless card
work on a linux system? If it helps, my new card is a NetGear MA311.
What do I edit, what do I click? This sounds like a stupid question, but
I simply can't find the answer anywhere, spelled out in simple, general terms.
Thank you, thank you, thank you.
This helped a lot. I write this from my newly wireless
machine. But I'm still not entirely happy.
First, I lose connectivity every time I reboot, and have to
enter the Network Configuration GUI tool, highlight eth1,
and click the big green "Activate" button. Then I'm fine.
What actual shell command(s) get executed when I push this
button? How can I configure the machine just to bring up eth1
upon boot, like any other ethernet connection?
And more generally, I have the same complaint I always do after
I finally, arduously, figure something out on my linux system: why
on earth was this so arcane? Every time I want to get my linux
machine to pick its nose, I post questions here, I grovel around
in google, I find some posting from two and a half years ago from
someone who did something similar, I grep, I edit, I soft link
configuration files, then, if I'm willing to ignore some persistent and
unsettling yet cryptic error messages, it more or less kind of works.
And when I recently bought a windoze laptop, I started unpacking it
at the beginning of Battlestar Galactica, and only diddled with it
during the commercial breaks, and by the time the show was over,
it was doing stuff my linux machine STILL doesn't do.
(Sorry it took so long to respond.)
The command that the gui probably passes is
ifconfig eth0 up
for dcph. or
ifconfig eth0 ipaddress
for a static ip.
as far as getting it each time(runs and reads a readme on installing gigabit eth for my motherboard)
heh, i'm suprised I didn't remember that. As you have read, you need to edit your modules.conf file that should be in /etc/
Follow the format the rest of that file has. I think on my computer it actually had me add it to another file, but the modules.conf file told me which it shouldn't be that bad.
and your problem with linux seems to be hardware? Well, if we all storm the gates of hardware companies and make them write the damn drivers for 3 OSes(win32,*BSD and *nix) we will all be very happy. unfortunantly the problem is that since we have such a small market share. Another problem may be the way configurations are done. You had to learn how to screw with window's hardware configurations. You also have to learn how to do that in linux BUT in linux things are rather cryptic because the OS was based upon something that was meant to be a server....something meant to be powerful. With power comes complications but it is simple enough to get around that. I should say, if you're not using something such as redhat that keeps you in the dark. You have to dig in to be able to do something in slack and that makes you learn what the heck is going on and that makes it so that as time goes on you start answering more questions then you're asking.
However, that is pretty much my opinion and I have not actually used redhat but I have used mandrake and I can vouch for slackware being more indepth. Please tell me what kind of things that you would want to do on your linux box that you can do on your windows box/laptop.
Last edited by Onemessedupjedi; 02-04-2004 at 07:25 PM.