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 installed suse 9.2 and got the wireless card to connect and the monitor program says its working fine, but it never goes online. i can get online with the ethernet, installed the patched and such but nothing seems to help. the pdf document said kinternet would be in the tray, but ive never seen it nor kow how to activate it.
There are two major steps to making a wireless connection work: associating with the access point (it sounds as though you got that far) and bringing up the interface. SuSE probably has a GUI for it, but try either ifup eth0 or ifconfig eth0 up in the command line.
Post the output of ifconfig and iwconfig to see if you're associated and getting a valid IP and route.
2Gnu is correct, although I might add that your wireless device might have gotten defined as eth0, eth1, or even wlan0, depending on what other network devices are already defined and how the config was set up. Hence, you might have to issue: ifconfig eth0 up OR
ifconfig eth1 up, or ifconfig wlan0 up to get it working.
not newbie enough! i dont know how to enter these commands. i also can't find a newbie guide that explains these things. the included manual doesn't explain anything. they always seem to tell me how to install the os, and thats the end. know of a good newbie guide?
my card is identified as wifi0 in a taskbar applet (i cant find its name) but in the wireless network configuration gui it is called wlan0.
Please consider us your knights in shining armour. I'm guessing its wlan0 and the applet - possibly Kwififmanager - is calling it wifi0. Not very helpful I guess. To get the true
name of the interface you need to open a terminal program (konsole in KDE) and become root. Do this by typing
followed by the password if there is one.
Then type these commands and post back the output.
iwlist wlan0 scanning
and we'll see what we shall see.
wow. i cant believe i was forgetting to log in as root. *sigh* the applet now says wlan0, so im not sure whats going on. im connected to the internet via ethernet cable plugged into the same wireless router, so these results may be somewhat bizarre.
Well the good news is I tihnk you're almost there. The problem you have here is that there are two interfaces grabbing two separate IP addresses. Not a problem if you can bridge and so forth but I'm assuming you just want to get on the net with your wireless connection. So in this case I would remove the wired NIC from the equation altogether, preferably by disabling it in the BIOS. In that way Suse wont assign resources to it on boot an go looking for an Ip for it etc. I would change the nickname of your computer so that it is different from your SSID. Anything will do but at the moment it just confuses the situation. Once you have loaded up without your wired nick you will want to check and see if you are connected. Chances are that you may well be without having to do anything further as it has obtained an IP from your router in the outputs you posted.
If it has not connected then check the commands again that I asked you to run.
Note: You do not need to log in as root (ie. log into KDE with root username) to get any of this working. The only reason you need to become root is to run some of the commands above, even though most can be run by specifying the exact path but thats for another day I guess.
See how you go - remember you're pretty much there - it all looks good.
Just bring down, or deactivate, the unwanted interface: ifconfig eth0 down then bring up the desired one: ifconfig wlan0 up. Again, there's a SuSE GUI if you feel more comfortable with that. The GUI should also give you options to enable (or not) each interface on boot and to either pull an IP address from the DHCP pool on the router or to sued an assigned static address.
Newbie guides abound, but a lot of the information is already on your system. From a console window:
"man command" or "info command" without the quotes will open a file containing instructions for the use of the command. man ifconfig will list out the many ways you can use it. Page up/down to scroll though the manual, "q" to quit.
Not sure what command to use? "apropos subject" will help. apropos network will list all of the commands related to networking - too many, in fact. apropos wireless will give a much more narrow range of options.
IRC. Online chat with other users who can hold your hand as you walk through the steps realtime. X-chat is a decent client that is also available for Windows. Point it to irc.freenode.net and join a channel such as #suse or #atu.
Aside from this fine site, DSLReports.com/forum/unixdsl (All Things UNIX) is very useful and newbie-tolerant. The #ATU folks are mostly DSLR crowd.
Mailing lists and news groups can be a good way to find stuff that someone else already tripped over to save yourself a fall or two.
You don't have to disabled it in the bios or though that would be one way to disable it.
You need to edit the interfaces file.
It's best to get used to using a terminal window such as eterm or xterm to change settings, move or delete files, restart services. That way if you loose your x windows you can still repair you system.
I would suggest learning how to use a text editor such as pico or vim to change settings.
search in google for howto pico or vim.
You need to comment out the other interfaces in the /etc/network/interfaces files.
Commented out means putting a # in front of a line. This way the system scipts over the line when reading the configuration.
e.g to open the interfaces file, open up a terminal window, logon as a super user "type su enter then password" type "less /etc/network/interfaces" this allows you view the file without allowing yourself to make any changes. Press "q" to exit the file.