Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Notices
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.
The first thing to check is that your device itself works. You can check this with the command "/usr/sbin/iwlist scan". If you see a number of access points, the kernel driver is loaded and your device are probably operable.
Next the device needs to authenticate with the access point. Assuming that you are using wpa authentication, you can run as root "wpa_cli -p <path/to/wpa//var/run/directory> -i <interface-name>"
If you are using ndiswrapper, on suse, this command probably will be:
wpa_cli -p /var/run/wpa_supplicant -i ndiswrapper
I tried getting my desktop to work, but it wouldn't authenticate. I have my older laptop what wouldn't either even though it had in the past. The problem turned out that someone stole my essid number. After changing the essid of my network and making it unique, both were able to authenticate. ( Oddly my new laptop had no problem ). This probably won't be your situation, but I thought I would mention it in case your network still uses the default, which might not be unique.
After you verify that the device works and authenticates, it may be a network setup problem rather than a wireless problem. Some things to check are:
/sbin/ifconfig <wireless-device>
Does the device have an IP address? You can try "ifrenew-dhcp <device-name>"
Are your wireless device and your NIC device on the same subnet?
/etc/resolv.conf: Does this file list your ISP's dns servers (nameservers)?
DHCP should supply this information, however you can get this info from the router and choose not to have dhcp change it.
/sbin/route
Is the default gateway listed and does it use your wireless device?
192.168.1.0 * 255.255.255.0 U 0 0 0 wlan1
loopback * 255.0.0.0 U 0 0 0 lo
default 192.168.1.1 0.0.0.0 UG 0 0 0 wlan1
dhclient ra0 and ra1 report the following:
Quote:
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
Bind socket to interface: No such device
If you did not get this software from ftp.isc.org, please
get the latest from ftp.isc.org and install that before
requesting help.
If you did get this software from ftp.isc.org and have not
yet read the README, please read it before requesting help.
If you intend to request help from the dhcp-server@isc.org
mailing list, please read the section on the README about
submitting bug reports and requests for help.
Please do not under any circumstances send requests for
help directly to the authors of this software - please
send them to the appropriate mailing list as described in
the README file.
On the speed, take a look for an entry in /etc/sysconfig/network/ifcfg-<devicename>
From the manpage:
Quote:
## Type: string
## Default: "auto"
#
# Usually the highest bitrate available gets used. If you have specific needs
# to set a bitrate, you can do it here (rates are in Mbit/s). Bitrates above
# 11 are only available for cards compliant to 802.11a or 802.11g standards.
WIRELESS_RATE=''
## Type: string
## Default: ""
#
# You can define up to 4 WEP encryption keys. You can use WEP with open and
# sharedkey authentication. The key can be entered in different formats:
# Either directly in hex digits, with or without dashes, or in the key's ASCII
# representation (prefix s: ), or as a passphrase which will be hashed (prefix
# h: ). The amount of hex digits resp. length of the ASCII key depends on the
# key size being used: 10 hex digits or 5 ASCII characters for 64 bit keys, 26
# hex digits or 6 to 13 ASCII characters for 128 bit keys (see
# WIRELESS_KEY_LENGTH below). Examples:
#
# WIRELESS_KEY_0="0123-4567-89"
# WIRELESS_KEY_0-"s:hello"
# WIRELESS_KEY_0="h:mysecretphrase"
#
# You can also use 1, 2, or 3 as suffix for multiple key settings. This
# is usually not necessary. Leave empty if you do not want WEP.
WIRELESS_KEY=''
## Type: list(40,104)
## Default: 104
#
# Defines the length in bits for all keys used. There are currently 40 and 104
# bit keys supported. Sometimes they are also called 64 resp. 128 bits
# (depends on whether you count the 24 bit initialization vetor or not).
# This variable is only meaningful if you enter the key as passphrase.
WIRELESS_KEY_LENGTH=''
## Type: list(0,1,2,3)
## Default: 0
# Sets the default WEP key. The default key is used to encrypt outgoing
# packets, incoming ones are decrypted with the key number specified in the
# packet. This defaults to 0.
WIRELESS_DEFAULT_KEY=''
Ndiwwrapper devices are usually named wlan0 or wlan1, etc.
Have you run through the device configuration in Yast2 -> Network -> Devices. There are also some options to go through in the bottom of the screen.
Maybe you could compare some items from my edited ifcfg-wlan0 file:
The default is "auto". Check it to make sure that a lower rate isn't listed. I had a very low rate in the field once. I don't know why, but it is something to check. You may also try changing the channel that your network uses. Check the output of "sudo /usr/sbin/iwlist scan" and see if someone else is using the same frequency. Perhaps there is an interference problem that is causing the low bit rate.
Auto is what you want. I wanted you to check if a low bitrate was explicitly listed instead. It isn't so that isn't the problem. If your wireless router has a web interface, check if it is set to a low bit rate. Are others using the same wireless frequency? Perhaps changing to a different channel might help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.