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 im having a nightmare. Ive been using Linux for 1 day now and have picked up quite alot so far. All i want is DHCP to give me IP from my wireless router. Here is my setup:
Fresh install of Slackware v10
I went to my vendor webbie and got the linux supported drivers for wireless card, After a few troubles i consulted some very helpful ppl on irc. After some time I worked out the kernel was wrong so i needed a patch. Installed tha patch and made the drivers and installed them. Then i copyed the firmware to the right place and tested that. all seemes ok. Then i try dhcp and it wont work. I setup my ssid and wep aimed at the router.
From what ive been told I need to make changed to configs so they are loaded everyime i boot. But I am yet to work out what I need to do. Is there any software I can get to setup my wifi card? the card is an Intel: ipw2100-0.56
the iwconfig works, shows eth1 and stuff... but dhcp?
Please someone who knows a possible solution put me out of my missery
And yes ppl tell me now slack is wack but it will do me for the moment!
Last edited by T0n!c-Wate)2; 10-29-2004 at 08:24 PM.
Once you have iwconfig configured and showing the proper mac address, essid, etc. all you should have to do is run "dhcpcd -t 10 wlan0" Note that my wireless is using interface wlan0, so if you're using eth1 or whatever, adjust it accordlingly. Once you figure out the proper settings with iwconfig and get an IP, you can simply add the sequence of commands you used to rc.local, or call a script from rc.local. I wasn't able to get a linux driver for my card, so I used ndiswrapper. Assuming your card is activated on boot, you could use a script similar to:
Obviously, the first 3 lines are loading my ndiswrapper (I have to use "sleep 6" in order to let the module fully load before setting up iwconfig). But all you should have to do is set your iwconfig stuff, and issue a dhcpcd. Your dhcpcd may differ--I chose to use a timeout to prevent hangups if the router is down (-t 10), added the default gateway, and then specified the interface. Adjust it accordingly, and you should be up and running. All I do is call the script from rc.local and I'm up and running on boot.
If dhcpcd doesn't work, then it's either a problem with iwconfig settings or your router's dhcp. You can get all the info from your router by running "iwlist wlan0 scan", again adjusted for whatever interface your using.
Hope this helps.
jesus, u fixed it.. cant thank you enough. It was the dhcp that was failing i think. I did have it probe'd but after a restart maybe i forgot to redo it..
When i tryed dhcp eth0. it just allowed me to carridge return many blank lines. which i press ctrl+c to return to the shell. Very strange. but once i tapped in your version dhcpcd -t 10 -d -G 192.168.0.1 wlan0
..it came streight up. Thank you you just regained my faith in linux
I thing. I like the sound of making scripts. What extention does a script have. How do you link to it? and what do these 2 lines do? guessing they are inside rc.local
No problem...glad it worked for you. Wireless can be problematic--it just takes a little work.
As for scripts:
The line "#!/bin/sh" says that the file is a shell script. It's really the only thing that is necessary in the script, other than the commands you want to run--and these commands can be anything you'd type at the command line. Find yourself typing the same sequence of commands over and over? write a script for it! Any other line in the script that is preceded by a "#" is a comment, and gets skipped.
The line #/etc/rc.d/rc.wlan0 is just the name of the file. I named it "rc.wlan0" to correspond with the rest of the files in /etc/rc.d --It's not really necessary. Scripts can be named anything, no extension, no nothing. Whatever you want. The only thing you have to do is make sure they are executable. As in "chmod -ugo+x yourscriptname" to make it executable by everyone. Once you have a script saved and executable, you just execute it by typing "./yourscript" in the directory that contains the script. If you are trying to run a script in a different directory, add a space after the first "." and then include the full path to the script. Eg. in my rc.local file (which is executed on boot and can include any extra commands/scripts you want to be activated at boot time) I run my rc.wlan0 script with the command ". /etc/rc.d/rc.wlan0" And my wireless is up and running every time I boot. In fact that's all my rc.local file contains--here is is in case this isn't making sense:
# /etc/rc.d/rc.local: Local system initialization script.
# Put any local setup commands in here:
I did have a script call to handle a memory problem I was having with my old video card "rc.mtrr", but I don't need it anymore, so I just commented it out.
Hope all this helps. You should also try googling for shell scripts, bash scripts, etc to see what that turns up...I'm sure there's a lot more info online than what I know--I just started using scripts myself. And if anyone has anymore info, feel free to add or correct me! I'm still learning too.
np, tonic. lol@teacher. I don't really have the first clue about linux--I just help out where I can. Glad this bit helped.
And (scripts==kickass batch files)--exactly. I grew up on old dos (maybe 3.1 if I remember right)...nothing better than a good 'ol batch file.