How To: Manual Network Configuration without the need for Network Manager

[kevdog]

In setting up their wireless connection for the first time, Im discovering many individuals having problems connecting through Network Manager or other GUI wireless connection tools. In fact my Network Manager is intermittently buggy, connecting sometimes and not others. This guide benefits all users in case the GUI tools are not working, and is useful for testing a wireless connection during initial installation of wireless drivers since it provides for good debugging output.

Clarification to those about to read this Guide
1. This method provides the most low level method to establish your network connection. It is the least common denominator. It does not use any reference to the /etc/network/interfaces file, as this file requires a method that is more high level.
2. If you are interested in making modifications to your /etc/network/interfaces guide to establish your connection, possibly Weiman01's guide covering this topic would be more applicable to your situation: http://ubuntuforums.org/showthread.php?t=318539. This method however uses processes that are more high level. If editing or use of the /etc/network/interfaces file fails, I would recommend reading the guide provided below, as it is "lower level".

Unencrypted/ WEP / WPA (PSK and EAP-TLS) connections will be covered in this guide.
This guide is for anyone attempting to establish a network connection manually at the command line.

Pre-requisites
1. Properly installed network driver -- This guide can be used to troubleshoot driver installation to see if it is properly functioning
2. The ESSID of your router must be broadcasted and not hidden
3. Knowlege of your wireless cards driver (please see Prerequisite #4 to determine driver). Those using the r8187/r818x driver please see the end of the guide
4. Knowledge of your wireless card's Interface Name - The user must know the proper interface of the wireless connection (wlan0, eth1, rausb1, etc). To discover this information, at command line type:


lshw -C network

There may be multiple interfaces listed, however look under the section appropriate to your wireless device for the line labeled logical name. Here is an example:



*-network
description: Wireless interface
product: BCM4306 802.11b/g Wireless LAN Controller
vendor: Broadcom Corporation
physical id: 0
bus info: pci@06:00.0
logical name: wlan0
version: 03
serial: 00:12:17:35:17:10
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+lsbcmnds driverversion=1.48rc1+Cisco-Linksys ,LLC.,02/1 ip=192.168.1.101 latency=64 multicast=yes wireless=IEEE 802.11g
resources: iomemory:3c000000-3c001fff irq:11


In the example above the interface name is wlan0. I will refer to the interface name throughout the rest of this guide as <interface>.

Attention All Users: Please Read
****All users of Atheros or Intel Chipsets (ipw****) -- Although lshw may list your interface as wmaster0 or wifi0 -- PLEASE NOTE this refers to the actual assigned interface name to the device, HOWEVER you interact through an assigned VIRTUAL INTERFACE!!!. Your will NEVER USE wmaster0 or wifi0 as the device name. If you type iwconfig, this may give you information on the assigned virtual interface used to access the physical device. -- BOTTOM LINE -- You will never use wmaster0 or wifi0 as the interface name, rather some other interface such as wlan0 of eth1. Please check ifconfig or iwconfig for cross referencing!!


***Please note -- as there exist exceptions to every rule, an exception applies to Atheros chipset employing the madwifi kernel module. Atheros cards are typically identified as wifi0. This is the physical logical name of the device. When working with madwif modules however, one or more virtual interfaces are made for every actual device. All configurations must be completed using the virutal interface device rather than the actual interface to the device. In most cases, Atheros chipsets will need to use the ath0 interface rather than the wifi0 interface.

For people first setting up their connection, please note that the above also lists the driver used for the network card. In the example above, the driver used is ndiswrapper. If your network device comes back UNCLAIMED or there is no driver listed, then you have not correctly installed the driver for your device. You must review the procedures for installation of your wireless driver.

For those wanting to use static IP addresses, please see section at bottom of guide regarding configuration for static IP addresses

__________________________________________________ __________________________
Unencrypted Connection

All commands typed at the command line:


sudo ifconfig <interface> down
sudo dhclient -r <interface>
sudo ifconfig <interface> up
sudo iwconfig <interface> essid "ESSID_IN_QUOTES"
sudo iwconfig <interface> mode Managed
sudo dhclient <interface>

__________________________________________________ __________________________
WEP Connection

You must have either your 64bit or 128 bit HEX Key or the ASCII Equivalent of your HEX Key.



sudo ifconfig <interface> down
sudo dhclient -r <interface>
sudo ifconfig <interface> up
sudo iwconfig <interface> essid "ESSID_IN_QUOTES"
sudo iwconfig <interface> key HEX_KEY <<<-------- If using ASCII Equivalent, this is s:ASCII_KEY (please make note of the prefix s:)
****Additional Comand that may be needed -- sudo iwconfig <interface> key open <<<----See note below
sudo iwconfig <interface> mode Managed
sudo dhclient <interface>

***The security mode may be open or restricted, and its meaning depends on the card used. With most cards, in open mode no authentication is used and the card may also accept non-encrypted sessions, whereas in restricted mode only encrypted sessions are accepted and the card will use authentication if available.
__________________________________________________ __________________________
WPA Connection - WPA-PSK or WPA2-PSK (PSK=Pre-Shared Key) or WPA-EAP-TLS

For uses of Ra-based chipsets: rt61, rt73, rt2500 please skip directly to the WPA Section entitled WPA with Ra based chipsets

Requirements: In most cases the wpa_supplicant package is required in order to connect via WPA. If you have a working ethernet or unencrypted/WEP wireless connection, this package may be installed via:

sudo aptitude install wpasupplicant

If only wireless is available, I would recommend that an unencrypted connection first by established and tested first before directly proceeding to make a WPA connection. WPA adds another layer of complexity.

WPA-PSK - Covers WPA(1) and WPA(2)

1. Creation of /etc/wpa_supplicant.conf file

At command line:

gksu gedit /etc/wpa_supplicant.conf

Inside the file add the following for WPA(1):


ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="ESSID_IN_QUOTES"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk="ASCII PSK Password in Quotes"
pairwise=TKIP
group=TKIP
}

For WPA(2) (see this thread: http://ubuntuforums.org/showthread.php?t=607410):


ctrl_interface=/var/run/wpa_supplicant

network={
ssid="ESSID_IN_QUOTES"
psk="ASCII PSK Password in Quotes"
key_mgmt=WPA-PSK
proto=RSN WPA
pairwise=CCMP TKIP
group=CCMP TKIP
}


***Word of caution -- In some cases I have found WPA(2) to have different settings than the above. Some Broadcom cards use the pairwise/group TKIP cipher for WPA2 rather than CCMP. I would suggest all initially use WPA(1) and then later convert to WPA2 since some variations to the above may be needed

**WPA2 capabilities must also be built-into the driver set used with your hardware. If using ndiswrapper with an old windows driver, the driver may not contain code for wpa2.

2. Connect via command line


sudo ifconfig <interface> down
sudo dhclient -r <interface>
sudo wpa_supplicant -D<****see footer below***> -i<interface> -c/etc/wpa_supplicant.conf -dd

***Note that starting with the -dd flag will create a lot of debuggin output.
If you choose to use the -dd flag to troubleshoot your connection, you must
open up a separate terminal and type the rest of the commands listed below in a
separate terminal window. You can also replace the -dd flag with the -B flag to
send the process to the background, avoiding the need to open up a separate
terminal window (however no debugging output will be generated)

sudo dhclient <interface>


***footer
The value listed here is dependent on the driver you have installed. Typing man wpa_supplicant at command line will give you the full gamut of choices however most recent versions of wpa_supplicant only recognize wext as the appropriate value (Despite all the information on the internet). If you would like to verify what drivers besides wext your installed version of wpa_supplicant recognizes, type at the command line:
wpa_supplicant -l
And look specifically at the section called drivers:

Here is what my stock wpa_supplicant lists for its drivers:

drivers:
wext = Linux wireless extensions (generic)
atmel = ATMEL AT76C5XXx (USB, PCMCIA)
wired = wpa_supplicant wired Ethernet driver

Other drivers can be compiled into wpa_supplicant if you compile wpa_supplicant, however please not that in recent kernel versions this is unnecessary. wext will work for ndiswrapper, madwifi, intel, etc.

WPA-PSK with Ra Based Chipsets

Ra cards do not require the wpa_supplicant package to use WPA. Here is how to connect from the command line with these cards:
References: http://ubuntuforums.org/showthread.php?t=400236&highlight=serial+monkey, http://rt2x00.serialmonkey.com/wiki/index.php/Debian_rt2500_Howto#Using_WPA

WPA-PSK(1)


sudo ifconfig <interface> down
sudo dhclient -r <interface>
sudo ifconfig <interface> up
sudo iwconfig <inteface> essid "ESSID_IN_QUOTES"
sudo iwpriv <interface> set AuthMode=WPAPSK
sudo iwpriv <interface> set EncrypType=TKIP
sudo iwpriv <interface> set WPAPSK="YOUR_WPA_PSK_KEY"
sudo dhclient <interface>


For WPA-PSK(2), I have no working configuration yet. If someone would like to help me refine these instructions for WPA2 with Ra-based chipsets, I would appreciate your help!

WPA EAP-TLS
Information Provided Referenced from http://www.codealias.info/technotes/wpa2_eap-tls_authentication_linux_client_setup
Thanks to CodeAlias for Providing Information

1. Prepare TLS Certificates

EAP-TLS requires client TLS certificates to be installed in the system. You need to ask the administrators in your institution to provide you your own TLS certificate.

In the most common cases, your admin will issue you a .p12 file and a password.

We need to create three files from this .p12 certificate

These files are cacert.pem, cert.pem and key.pem (The names may vary). Assuming that your certificate file name is example.p12, run the following :


openssl pkcs12 -in example.p12 -out cacert.pem -cacerts -nokeys
openssl pkcs12 -in example.p12 -out cert.pem -clcerts -nokeys
openssl pkcs12 -in example.p12 -out key.pem -nocerts


Put the three generated files somewhere in the file system of your wireless device (e.g /etc/certs)

2. Configuration of the wpa_supplicant.conf file

Edit the wpa_supplicant configuration file (e.g. /etc/wpa_supplicant.conf), ant put the following:



network={
ssid="ESSID_IN_QUOTES"
scan_ssid=1
key_mgmt=WPA-EAP
pairwise=CCMP TKIP
group=CCMP TKIP
eap=TLS
identity="XXXXX@yourdomain.com"
ca_cert="/etc/certs/cacert.pem"
client_cert="/etc/certs/cert.pem"
private_key="/etc/certs/key.pem"
private_key_passwd="YOUR-PASSWORD"
}


---“YOUR-PASSWORD” is the password provided by your administrator when your received your .p12 certificate

3. Connect via the command line


sudo ifconfig <interface> down
sudo dhclient -r <interface>
sudo wpa_supplicant -D<****see footer below***> -i<interface> -c/etc/wpa_supplicant.conf -dd

***Note that starting with the -dd flag will create a lot of debuggin output.
If you choose to use the -dd flag to troubleshoot your connection, you must
open up a separate terminal and type the rest of the commands listed below in a
separate terminal window. You can also replace the -dd flag with the -B flag to
send the process to the background, avoiding the need to open up a separate
terminal window (however no debugging output will be generated)

sudo dhclient <interface>


***footer
The value listed here is dependent on the driver you have installed. Typing man wpa_supplicant at command line will give you the full gamut of choices however most recent versions of wpa_supplicant only recognize wext as the appropriate value (Despite all the information on the internet). If you would like to verify what drivers besides wext your installed version of wpa_supplicant recognizes, type at the command line:
wpa_supplicant -l
And look specifically at the section called drivers:

Here is what my stock wpa_supplicant lists for its drivers:

drivers:
wext = Linux wireless extensions (generic)
atmel = ATMEL AT76C5XXx (USB, PCMCIA)
wired = wpa_supplicant wired Ethernet driver

Other drivers can be compiled into wpa_supplicant if you compile wpa_supplicant, however please not that in recent kernel versions this is unnecessary. wext will work for ndiswrapper, madwifi, intel, etc.
__________________________________________________ __________________________
A successful connection in all cases will similarly result in: (Example Provided Below):

user@computer:~$ sudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:12:17:35:17:10
Sending on LPF/wlan0/00:12:17:35:17:10
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 192.168.1.1
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.101 -- renewal in 299133 seconds.

The computer in this example has received an IP address of 192.168.1.101

__________________________________________________ __________________________
Users of RTL 8180, RTL8185, RTL 8187 using the built in native r8187 / r818x drivers

By default the r8187 and r818x drivers are blacklisted due to a know bug. These drivers are usuable however with a twist to the above methods

If you want to try using these drivers, please load the kernel modules:


sudo modprobe r818x
sudo modprobe r8187


These drivers require a bogus or extra letter be suffixed to the essid name in order for these drivers to work
For example if your are trying to connect to a router with essid=Router, at he command line you would type essid=Routerx. Notice the extra x or bogus character. I have provided an example using the unencrypted connection procedure below, however this extra character needs to be used if attempting to connect to all network types (unencrypted/ WEP / WPA)



sudo ifconfig <interface> down
sudo dhclient -r <interface>
sudo ifconfig <interface> up
sudo iwconfig <interface> essid "Routerx"
sudo iwconfig <interface> mode Managed
sudo dhclient <interface>

If these drivers work for you, and you would like these drivers to load automatically at startup for you, avoiding to have to type sudo modprobe everytime, please edit your blacklist file:



gksu gedit /etc/modprobe.d/blacklist


And comment out (or prefix the following lines with a # sign). You want the following lines to appear as below:


#blacklist r8187
#blacklist r818x



__________________________________________________ __________________________
Static IP Addresses

Im going to give an example of how to configure your interface using a static IP address using an unencrypted wireless connection. The two lines highlighted below however can be used with WEP and WPA connections. Values in italics must be customized to meet your particular situation



sudo ifconfig <interface> down
sudo dhclient -r <interface>
sudo ifconfig <interface> 192.168.1.100 netmask 255.255.255.0 up
sudo route add default gw 192.168.1.1
sudo iwconfig <interface> essid "ESSID_IN_QUOTES"
sudo iwconfig <interface> mode Managed


If when using static IP addresses you are getting a problem with name resolution, you will have to specifiy specific dns (domain name servers) in order to translate URLs to IP addresses. Unfortunately there is not an easy way to configure this from the command line. This requires that you edit the /etc/resolv.conf file and manually enter the domain name server(s) you want to use. In many cases users can specifiy their router, their internet service providers dns servers, or use opendns (or use all three). Up to three nameservers can be specified.


sudo gedit /etc/resolv.conf
and add the nameservers you want to use, one to a line, in the following format.

nameserver <nameserver>

***Spaceboy909 has also reported that when using this technique with static IP addresses, network manager has to be uninstalled because it keeps trying to reset the connection. In order to uninstall networkmanager:

In Ubuntu:


sudo aptitude uninstall network-manager-gnome


In Kbuntu:


sudo aptitude uninstall knetworkmanager

__________________________________________________ _________________________
Setting the Wireless Interface to Connect at Boot ***Courtesy of Maricaibo

If you are successful in bringing up the Interface Manually, the commands may be placed inside the /etc/rc.local file to run the commands at boot, and establish a wireless connection. There is no GUI to give visual confirmation of the connection. The user should type ifconfig at the command line to verify an IP address has indeed been granted by the router.

The process of adding the commands to the /etc/rc.local file is documented below (this connects to an unencrypted network -- to connect to a WEP or WPA encrypted network, some modifications as used above will need to be added):


gksu gedit /etc/rc.local

This opens up the file in the gedit utility and allows you to make changes and save the file



ifconfig <wired network connection interface> down
ifconfig <wireless network connection interface> down
dhclient -r <wireless_interface>
iwconfig <wireless_interface> essid <router name>
iwconfig <wireless_interface> mode Managed
ifconfig <wireless_interface> up
dhclient <wireless_interface>


Be sure this text goes into the /etc/rc.local file BEFORE the line reading "exit 0".

Save and close the /etc/rc.local file.

Open up a Terminal window (the shell) and type in:



sudo chmod +x /etc/rc.local


This command turns the rc.local file into an executable that will run at startup. Here's an example of what the /etc/rc.local file should contain. Your device names may be different:



#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

ifconfig eth0 down
ifconfig wlan0 down
dhclient -r wlan0
iwconfig wlan0 essid "ESSID_IN_QUOTES"
iwconfig wlan0 mode Managed
ifconfig wlan0 up
dhclient wlan0

exit 0


NOTE: The first line in the rc.local file downs your wired connection, so if for some reason you need the wired connection back just open up a Terminal window (shell) and type:

sudo <wired_interface> up
sudo dhclient <wired_interface>
__________________________________________________ __________________________
Useful Commands

ifconfig - lists IP address (similar to ipconfig in Windows)
iwlist scan - shows wireless networks that are available in the area along with basic encryption information
lshw -C network - Shows interface and driver associated with each networking device
lspci -nn - Shows hardware connected to the pci bus
lsusb - Shows USB connected hardware
lshw -C usb - Additional info on USB related hardware (good for USB dongles)
cat /etc/modprobe.d/blacklist - List modules that will not be loaded by the Operating System at boot time
lsmod - lists currently loaded kernel modules. (Example usage - lsmod | grep ndiswrapper)
route -n - Lists kernel IP routing table -- Good for troubleshooting problems with the gateway (netstat -rn = equivalent command)
sudo route add default gw 192.168.1.1 - Example of how to set the default gateway to 192.168.1.1
sudo route del default gw 192.168.1.1 - Example of how to delete the default gateway setting
sudo modprobe ***** - Loads the kernel module **** . (Example usage - sudo modprobe ndiswrapper, sudo modprobe r818x, sudo modprobe ath_pci)
sudo modprobe -r **** - Unloades the kernel module ****. (Example usage - sudo modprobe -r ndiswrapper)
sudo ifup/ifdown <interface> - Brings up/down the interface and clears the routing table for the specified interface
sudo ifconfig <interface> up/down - Brings up/down the interface for the specified interface
sudo dhclient <interface> - Request IP address from DNS server for specified interface
sudo dhclient -r <interface> - Release IP address associated with specified interface
sudo iptables -L - Lists firewall rules
dmesg | more - Lists boot log -- good for troubleshooting problems with modules/drivers not being loaded
uname -r - Displays kernel version
/etc/iftab (Feisty and pre-releases (Edgy, etc)) - /etc/udev/rules.d/70-persistent-net.rules (Gutsy) - File which assigns logical names (eth0, wlan0, etc) to MAC addresses
cat /etc/resolv.conf - Lists DNS servers associated with network connections (Network Manager)
/etc/dhcp3/dhclient.conf - File which sets or modifies dns (domain name servers) settings

__________________________________________________ __________________________
WPA_SUPPLICANT.CONF - Good Description and Explanations of All Available Options that can be Placed with the wpa_supplicant.conf file
http://hostap.epitest.fi/cgi-bin/viewcvs.cgi/hostap/wpa_supplicant/wpa_supplicant.conf?revision=HEAD

__________________________________________________ __________________________
References for Specific Wireless Chipsets - Please see Link if Your Specific Chipset is Not Working with Above Tutorial's Instructions

Official Broadcom site for bcm43xx firmware - http://linuxwireless.org/en/users/Drivers/b43
Broadcom 64bit Drivers for Use with Ndiswrapper - http://www.linuxant.com/driverloader/drivers.php
Broadcom Guid for Ubuntu Hardy/Intrepid and Ibex -- A very informative sight! - http://linuxfans.betaserver.org/index.php?option=com_content&view=article&id=46:broadcom-guide-for-ubuntu-hardy-and-newer&catid=34:guides&Itemid=61 - Author Ayuthia

Ra chipsets - Serial Monkey Drivers - rt2500, rt73, rt61, rt2570 drivers - http://ubuntuforums.org/showthread.php?t=400236&highlight=serial+monkey - Author diepruis
rt2500 chipsets with the Serial Monkey rt2500 CVS driver - http://ubuntuforums.org/showthread.php?t=584657&highlight=rt2500 - Author zoiks
Ralink RT2860 (m)PCI(e) (RT2760/RT2790/RT2860/RT2890) - http://ubuntuforums.org/showthread.php?t=1045703 - Author Fass
Rutilt - A Network Manager Like GUI for Ra Chipsets - http://ubuntuforums.org/showthread.php?t=554089&highlight=rutilt - Author sulilogs
Ndiswrapper Official Compatibility Reference - http://linuxfans.betaserver.org/ndis_drivers/toc.html - Author Ayuthia (Borrowed from the Ex-Official Ndiswrapper Site)
Ndiswrapper installation for Broadcom chipsets - http://ubuntuforums.org/showthread.php?t=475963 - Author Jamie Jackson
Ndiswrapper General Installation Guide - SVN, Troubleshooting Tips (My Personal Guide) - http://ubuntuforums.org/showthread.php?t=574501 - Author KevDog
Madwifi website for certain Atheros Chipsets - http://madwifi.org/ -- If your Atheros chipset is listed on this website - it should work out of the box with installation of the linux restricted drivers package for your kernel version
Atheros 5006eg Chipset work-around - Card apparently listed as 5007eg - http://ubuntuforums.org/showpost.php?p=4259805&postcount=14 - Author ugm6hr
Does your madwifi connection keep dropping??? Possible solution -- http://ubuntuforums.org/showthread.php?t=540101 = Author robnz/tranalbert
Realtek win98 driver - http://www.majorgeeks.com/Realtek_RTL8187_USB_Wireless_LAN_ME2000XP_d5165.ht ml - For use with ndiswrapper if native r818x, r8187 driver is buggy
Realtek win98 driver installation - http://ubuntuforums.org/showthread.php?t=493958&highlight=8187 - Author Panurge
Realtek - Installation with Native Driver - http://ubuntuforums.org/showthread.php?t=567505
Realtek 8187B Native Patch for Realtek 818x USB Devices -- Relevant only to rtl8187B USB wireless devices - Toshiba Laptops - http://www.datanorth.net/~cuervo/rtl8187b/ - Author Cuervo

__________________________________________________ __________________________
Wireless Security
WPA with EAP-TLS - http://www.codealias.info/technotes/wpa2_eap-tls_authentication_linux_client_setup

__________________________________________________ __________________________
Other Interesting Sites

Control Programs Kept in Swap vs Memory - http://ubuntuforums.org/showpost.php?p=4088251&postcount=150
If your Wireless Freezes after Suspend/Resume - Check here - http://ubuntuforums.org/showpost.php?p=2796307&postcount=12 - Author Harty83
DNS related problems?? - Configuration for OpenDNS servers - http://ubuntuforums.org/showthread.php?t=543659 - Author noob12
Turn off/Disable IPv6 - http://ubuntuforums.org/showthread.php?t=282034 - Author handy
General Linux Page Discussing Network Setups - Default Gateways - http://linux-ip.net/html/basic-changing.html
Log Files -- Your Friend to Debug almost anything on your System - https://help.ubuntu.com/community/LinuxLogFiles#head-90a79f52ee3f6d766a16e1ee67f98267e009db55
Using OpenVPN to bridge networks - http://ubuntuforums.org/showthread.php?t=752127 - Author SpaceTeddy

[JustinAllen]

Excellent post! Worked as advertised! I had been using the NetworkManager but all of a sudden, it stopped wanting to connect to my wireless. These instructions got me connected once again. Thanks a lot!!

[Beggar]

After upgrading to gutsy my WIFI broke after the first reboot. The output from the first command is:



darren@BeggarBox:~$ sudo lshw -C network
*-network
description: Network controller
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0b:00.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=ipw3945 latency=0 module=ipw3945
...


Notice it is not given a logical name. How do I set it back to being eth1? /etc/iftab seems to be the best option, but I dont know the mac address. Any ideas?

It doesn't seem like /etc/iftab is used anymore, back to square one....

[kevdog]

Beggar

Interesting situation you present, cant say that Ive ever seen your situation before .. so its kind of neat. What does
dmesg

say after you boot. Anything about the interface. Does
ifconfig
lend any clues.

My forte is not with the ipw drivers. I think noob12 is much better in this area than I.

[ivanpetrov]

My wireless (eth1) has gone upon the latest "partial upgrade" of the gutsy preview I've been using for a couple of weeks.

~$ dmesg|grep ipw2200
[ 18.384000] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.0kmprq
[ 18.384000] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[ 18.628000] ipw2200: Detected Intel PRO/Wireless 2915ABG Network Connection
[ 18.872000] ipw2200: Unable to load ucode: -62
[ 18.872000] ipw2200: Unable to load firmware: -62
[ 18.872000] ipw2200: failed to register network device
[ 18.872000] ipw2200: probe of 0000:02:01.0 failed with error -5

[kevdog]

If you have an older kernel version installed (ie you upgraded from feisty), press the ESC key when booting to enter the grub menu and see if you can use the ipw driver in an older kernel version. One other option, although its pretty drastic would be to compile your own vanilla kernel. I think (not certain), that the ipw drives are included by default, but confirm this. The masterkernel thread is a good place to start in the forums.

[Beggar]

Mine loads fine, but then I found this little gem a few lines down.



[ 16.088000] ipw3945: Radio Frequency Kill Switch is On:
[ 16.088000] Kill switch must be turned off for wireless networking to work.


Might be hard for me to turn my kill switch off however, considering I don't have one...

----

Scratch that, I didnt notice it, but since the gutsy upgrade my function keys work. Apparently right after the upgrade I used fn-f2 instead of ctrl-f2, fn-f2 is my computers wifi killswitch.
Boy do I feel stupid. I only spent 5+ hours trying to fix that. Hard to debug something you dont think works suddenly getting fixed on you...

[ivanpetrov]

If you have an older kernel version installed (ie you upgraded from feisty), press the ESC key when booting to enter the grub menu and see if you can use the ipw driver in an older kernel version...

Luck would have it, I just removed the older kernels yesterday. Have rebooted a couple of times since then with everything working fine. But ran the latest updates (some sort of a partial upgrade) just today, and that did the wireless in.

Oh well, gonna have another look. Thanks for your suggestions.

[nosneros]

Hi,

Just wanted to say thanks for the post, kevdog.

I just followed your advice to connect to my girlfriend's WRT54G v8 with WPA1. It was working under Windows, but not (K)ubuntu. The only oddity I found is that I have to use the wext driver instead of ipw when running wpa_supplicant, even though I have an Intel 2915 card in my laptop. I found that out by reading the output of wpa_supplicant with the -Dipw option.

Thanks again!

[kevdog]

Hmm, I guess you are right

wext is for any generic linux driver.
ipw is for the intel ipw 2100 and 2200 driver.

Good thing you read the man pages since this part of configuring the wpa_supplicant.conf file can be a little tricky

[madgreek]

I installed Mepis 6.5.02 on my Dell Inspiron 1721 last week. I gave Vista the boot and Mepis installed real easy and connected to my Linksys router w/no issues. Today, I downloaded Kubuntu 7.10 and tried to set it up to dual boot. I ran into some problems and finally threw my hands up and just installed it over Mepis. I couldn't get connected to the wireless router. Then I tried Mepis again and was able to dual boot both Kubuntu and mepis (happy days!), however, now I can't connect to the wireless on Mepis. Right now I am connected wired into the access point.

I ran you scripts and here is what I saw....

iwconfig wlan0 essid Gameserver
root@1[/]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Bit Rate=54 Mb/s Tx-Power:32 dBm
RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

sit0 no wireless extensions.

root@1[/]# ifconfig wlan0 down
root@1[/]# dhclient -r wlan0
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

Listening on LPF/wlan0/00:1c:26:91:c7:ec
Sending on LPF/wlan0/00:1c:26:91:c7:ec
Sending on Socket/fallback
root@1[/]# ifconfig wlan0 up
root@1[/]# ifconfig wlan0 essid "Gameserver"
essid: Unknown host
ifconfig: `--help' gives usage information.
root@1[/]# iwconfig wlan0 essid "Gameserver"
root@1[/]# iwconfig wlan0 mode Managed
root@1[/]# dhclient wlan0
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

Listening on LPF/wlan0/00:1c:26:91:c7:ec
Sending on LPF/wlan0/00:1c:26:91:c7:ec
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
root@1[/]#

Please help!!!

[kevdog]

What does
iwlist scan show

Make sure you take down your wired interface when trying to connect, such as
sudo ifconfig eth0 down

Also can you post
lshw -C network

[madgreek]

Here you go!

root@2[eleni]# sudo ifconfig eth0 down
root@2[eleni]# iwlist wlan0 scan
wlan0 Scan completed :
Cell 01 - Address: 00:13:46:1F:A4:3E
ESSID:"default"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:7/100 Signal level:-91 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:1A:70:F6:C6:99
ESSID:"Gameserver"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:93/100 Signal level:-36 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0

root@2[eleni]# lshw -C network
*-network
description: Wireless interface
product: Dell Wireless 1390 WLAN Mini-PCI Card
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0b:00.0
logical name: wlan0
version: 01
serial: 00:1c:26:91:c7:ec
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper driverversion=1.38 firmware=Broadcom,10/12/2006, 4.100.15.5 link=no multicast=yes wireless=IEEE 802.11g
resources: iomemory:fe8fc000-fe8fffff irq:19
*-network DISABLED
description: Ethernet interface
product: BCM4401-B0 100Base-TX
vendor: Broadcom Corporation
physical id: 0
bus info: pci@03:00.0
logical name: eth0
version: 02
serial: 00:1c:23:8a:f6:f8
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=b44 driverversion=0.97 link=no multicast=yes
resources: iomemory:fe5fe000-fe5fffff irq:22

[kevdog]

What driver are you using bcmwl5??

Once the eth0 interface is down, can you repeat the unencrypted manual commands for wlan0 and see what happens??

[BC7333]

After upgrading to gutsy my WIFI broke after the first reboot. The output from the first command is:



darren@BeggarBox:~$ sudo lshw -C network
*-network
description: Network controller
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0b:00.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=ipw3945 latency=0 module=ipw3945
...


Notice it is not given a logical name. How do I set it back to being eth1? /etc/iftab seems to be the best option, but I dont know the mac address. Any ideas?

It doesn't seem like /etc/iftab is used anymore, back to square one....

I remarked out # the last line in /etc/udev/rules.d/70-persistent-net.rules, rebooted and wireless started working. Seems upgrade replaced iftab but then setup rules.d with two interface names for the same mac address...

Here the files before I remarked out the redundant entry in rules.d

/etc/iftab

Code:

# This file is no longer used and has been automatically replaced.
# See /etc/udev/rules.d/70-persistent-net.rules for more information.
#

# This file assigns persistent names to network interfaces.
# See iftab(5) for syntax.

##eth0 mac 00:09:5d:15:60:23 arp 1
#wlan0 mac 00:19:D2:BB:50:59 arp 1

/etc/udev/rules.d/70-persistent-net.rules

Code:

# This file maintains persistent names for network interfaces.
# See udev(7) for syntax.
#
# Entries are automatically added by the 75-persistent-net-generator.rules
# file; however you are also free to add your own entries.

# Converted from /etc/iftab on upgrade
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:09:5d:15:60:23", ATTRS{type}=="1", NAME="eth0"

# Converted from /etc/iftab on upgrade
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:19:D2:BB:50:59", ATTRS{type}=="1", NAME="wlan0"


# PCI device 0x8086:0x4222 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:19:d2:bb:50:59", NAME="eth1"

[madgreek]

Same error!

root@1[/]# ifconfig wlan0 up
root@1[/]# iwconfig wlan0 essid "Gameserver"
root@1[/]# iwconfig wlan0 mode Managed
root@1[/]# dhclient wlan0
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

Listening on LPF/wlan0/00:1c:26:91:c7:ec
Sending on LPF/wlan0/00:1c:26:91:c7:ec
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


How do I find what the driver is?

[kevdog]

Look in the /etc/ndiswrapper folder. There should be a subdirectory, and inside this subdirectory I believe is contained the driver.

Are you broadcasting the essid on the router? No MAC filtering on the router correct??

[kthakar]

What are the steps to connect to a network with hidden ESSID (WEP) using command line?

[kevdog]

The commands are the same, however Im not sure if this will work. Its something about the drivers and Linux. So basically Im saying is that Im not certain ubuntu can connect to any router with hidden ssid broadcast.

[madgreek]

eleni@1[~]$ cd /etc
eleni@1[etc]$ cd ndis*
eleni@1[ndiswrapper]$ ls
bcmwl5 lsbcmnds

The SSID is being broadcasted. Not sure about MAC filtering. I see a MAC address for the Router Lan settings and another for the Router Wan settings. Encryption is WEP. I can get to the point where it asks me for the key. I put it in and it gets to 28% complete and fails. I have tried connected to some unprotected wireless networks and the same thing happens. 28% and quits. My sound doesn't work either and that was working before I did the dual boot setup.

[kevdog]

Where are you getting the 28% stuff -- From the command line Im not familar with that output at all.

What is in the lscmnds subfoler??

[madgreek]

There is an icon in the tray where you can click to connect to a wireless network. When I tell it to connect it starts connecting until it gets to 28% and then fails. It does this on any wireless network, not just my router.

[nismoskys]

followed all the directions step by step, but I'm still getting "No DHCPOFFERS received."

*posted a thread on my question instead -> http://ubuntuforums.org/showthread.php?p=3592180#post3592180

[kevdog]

No icon is involved in these instructions -- if your having a problem with the icon, these instuctions are not for you!

I see that you are getting no dhcp offers. What is the sgnal strength reported for your router for

iwlist scan

[nismoskys]

Quality:76/100 Signal level:-47dBm Noise level:-96 dBm

[nismoskys]

anything??

[madgreek]

I am not using the icon with these instructions. It won't connect when I follow the instructions. When I use the GUI to manually set addresses, DNS, and Gateway or if I set it to automatic, there is a Icon to click to see available wireless networks. I can see the network, but when it tries to connect it only gets to 28%.

Here is the scan

wlan0 Scan completed :
Cell 01 - Address: 00:13:46:1F:A4:3E
ESSID:"default"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:4/100 Signal level:-93 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:1A:70:F6:C6:99
ESSID:"Gameserver"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:93/100 Signal level:-36 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0

[kevdog]

I wish I could help you guys more, since it seems like you guys are doing everything right. Ive seen random problems like this before, and its always something I would never think to do that would fix it -- like uninstall a different package, or disable ipv6. Try disabling ipv6, not sure if this is going to help. Ive also seen some cards struggle with 64 bit wep (some driver problem) so I dont know if you are effected by this. Have you tried ascii based wep authentication:
sudo iwconfig wlan0 key s:ASCII

With WEP, are you using the first hex key??
You can set your key index with the following command:
sudo iwconfig wlan0 key [1] XXXXXXX (or s:ASCII) key [1]

[Rbleattler]

dude i love you, you're now my best friend in the world!

[underscoredavid]

Kevdog

Here's one for you.
I have two identical network cards. (ipw3945)

One is working A-OK.
The other is showing up in the system, but with no logical name, and no mac address. I've checked the wireless switches, bios settings for the card - and it is enabled...

Here's what I get for "lshw -C network"

*-network
description: Network controller
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0b:00.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list
configuration: driver=ipw3945 latency=0 module=ipw3945
*-network
description: Wireless interface
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0c:00.0
logical name: eth1
version: 02
serial: 00:1b:77:60:79:85
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ipw3945 driverversion=1.2.2mp.ubuntu1 firmware=14.2 1:0 () ip=10.10.1.9 latency=0 module=ipw3945 multicast=yes wireless=IEEE 802.11g

Obviously - the bottom one is working, top is not.

Where would I even start to get a logical name assigned to this. Querying "dmesg" doesn't give me anything interesting (errors) about this card.

I've tried other forums, threads, and this is the closest one I could find relevent. ANY help at all is appreciated.

Thanks.

[kevdog]

Just some random thoughts

Do you need two wireless cards running at the same time?? Ok I guess I could think of some situations this might be needed but just a thought.

If the working wireless card is removed, does the other card work.

Ive used two different wireless cards plugged into two separate pcmcia slots before, (atheros and broadcom), however I didnt use them at the same time. I brought one interface down and the other up. Your situation is slightly different since your not even getting an interface name assigned.

I guess first step is to verify the first card actually works.

[underscoredavid]

Just some random thoughts

Do you need two wireless cards running at the same time?? Ok I guess I could think of some situations this might be needed but just a thought.

If the working wireless card is removed, does the other card work.

Ive used two different wireless cards plugged into two separate pcmcia slots before, (atheros and broadcom), however I didnt use them at the same time. I brought one interface down and the other up. Your situation is slightly different since your not even getting an interface name assigned.

I guess first step is to verify the first card actually works.


The card actually works - I've used both by themselves in the same install with no problems. However, once there are two cards present, only one works.

As far as the need - if I don't want to buy another card, for what I'm trying to do/play with, yeah, this situation I need two.

Thanks for responding, you're the first in about a million posts all over the place - any ideas on where to start after verifying the card functions correctly?

[kevdog]

Are these two pcmcia slots?? Just wondering if one slot is given priority over the other.

Couple things to try, say you got the same scenario as you presented above, what if you bring the interface down, modprobe -r the ipw module, then modprobe the ipw module, then check with lshw -C network? Which card is assigned the interface name. What if you switch the cards?

How many times in lsmod | grep ipw is the ipw driver listed?

[underscoredavid]

Are these two pcmcia slots?? Just wondering if one slot is given priority over the other.

Couple things to try, say you got the same scenario as you presented above, what if you bring the interface down, modprobe -r the ipw module, then modprobe the ipw module, then check with lshw -C network? Which card is assigned the interface name. What if you switch the cards?

How many times in lsmod | grep ipw is the ipw driver listed?


These are two mini-pci express cards (Intel 3945abg) - I'm getting the feeling slot 2 is getting priority. If I switch the cards, it seems to follow that slot. It's the first slot I'm having problems with.

I've verified this slot works however, because, in the windows side of this install - it works flawlessly - except, I have no use for two cards in windows.

Under "lsmod" i've only got the driver coming up once.

When I "modprobe -r ipw3945" then "lshw" - both cards show up as unclaimed network controllers.

When I "modprobe ipw3945" - both cards show up again, the second one w/ the logical name/mac/etc... the other, with just the same basic info. This is the same as it was before.

[kevdog]

Im just shooting from the hip here b/c I googled around and found nothing similar to your problem except my experience (which isnt exactly similar). However just wondering if there are windows xp drivers available for your device. Here is what Im thinking. Im not sure if you are hardware limited and only one device is going to work at a time, or its more a driver issue where two devices cant use the same driver at once. I just dont know. What if however we could make one device use the native ipw driver and the other ndiswrapper. Im not sure if this would work.

Here is what I was thinking however
Most likely the card not show is interface eth0
The card in slot two is interface eth1

You could probably confirm this by taking out the card in slot 2 and just using slot 1 and see if the device is assigned eth0.

You could then probably add some aliases in /etc/modules like the following:
alias eth0 ndiswrapper
alias eth1 ipw3945

Here is a reference although I dont if I completely understand everything:
http://linux.about.com/od/lkm_howto/a/hwtlkm06t03.htm


One last random thought
What if you just type
sudo ifconfig eth0 up

What happens??

[underscoredavid]

Im just shooting from the hip here b/c I googled around and found nothing similar to your problem except my experience (which isnt exactly similar). However just wondering if there are windows xp drivers available for your device. Here is what Im thinking. Im not sure if you are hardware limited and only one device is going to work at a time, or its more a driver issue where two devices cant use the same driver at once. I just dont know. What if however we could make one device use the native ipw driver and the other ndiswrapper. Im not sure if this would work.

Here is what I was thinking however
Most likely the card not show is interface eth0
The card in slot two is interface eth1

You could probably confirm this by taking out the card in slot 2 and just using slot 1 and see if the device is assigned eth0.

You could then probably add some aliases in /etc/modules like the following:
alias eth0 ndiswrapper
alias eth1 ipw3945

Here is a reference although I dont if I completely understand everything:
http://linux.about.com/od/lkm_howto/a/hwtlkm06t03.htm


One last random thought
What if you just type
sudo ifconfig eth0 up

What happens??

The ndiswrapper route is a no-go. That limits what I'm trying to do with the card. (Monitoring mode/injection/etc...). You may have hit it on the head w/ the two cards not being able to use the same driver, though I'm not proficient enough to know/find out.

As far as eth0 is concerned - that's actually the integrated broadcom nic and hasn't given me any problems.

Looks like I may be buying a PCMCIA card or another mini-pci express card for this setup. That sucks.

Thanks for your help though!

[kevdog]

What if you just type
sudo ifconfig eth2 up

[underscoredavid]

What if you just type
sudo ifconfig eth2 up


eth2 doesn't exist.
the exact error is "eth2: ERROR while getting interface flags: No such device"

interesting thing though - i disabled one of the mini-pci e slots completely in the bios (the one that was working flawlessly) and the other card came up immediately, except in the system it had it as "eth3" , there was no eth1 or eth2. worked and everything.

if i could get the second card assigned a logical name, while the first card was working, i'd be able to troubleshoot if from there. i'm wondering if this is some sort of bug with 2 cards using the same driver, you wouldn't think so, but i'm not familiar enough with the way hardware interfaces with drives under linux.

[kevdog]

Thats why I wanted you to use ndiswrapper -- only for testing purposes. Im not sure if you can use the same driver twice, however it would seem logical that if one was using ndiswrapper and the other ipw and for some reason both network cards worked in this scenario, that it would tell me that it was most likely a driver or configuration problem rather than a hardware problem. Again Im not exactly sure how the kernel interacts and assigns drivers (or duplicate copies of a driver). Im just trying to rule some things out.

[SeanBlader]

Kevdog, wanted to let you know this worked for me in Gutsy using NDISWrapper 1.47 with a Broadcom 43xx on a Dell Inspiron 8500. So it looks like it's an issue with Gutsy's Network manager or something. I was also glad to see someone mention the change to iftab for Gutsy, I did see that previously as well. Any idea if Network Manager can be backdated to Feisty's or if there's a configuration fix for it somewhere? If not, at least I know it CAN work, nice job.

[tonafernandez]

Hello, i have been looking around
i have a dv2000 hp laptop with an AMD and the 64bit version of Gutsy
My wireless network has WPA it works
After i go thru a lot of hoops
boot up, change the settings on my wireless ssid and password, click ok (they are already stored)
change them back
and the network manager does it thing and activates the connection

i dont know why i dont get an IP at the moment of boot up, if i go to wired connection everything works as supposed
i have a broadcom 43xx driver

any ideas?... all i can think of is that unfortunatly my card is not trying to fetch an IP from the router

i have tried static ip as well and it doesnt work

pls help!

[kevdog]

You got to give me more details like how you are setting up your wpa connection. This post is really only concerned with setting up manual connections, and not with problems with network manager. I know a lot about network manager, but to delve into it here in this particular post would be a little off topic.

[d_thrasher]

Kevdog, I am hoping you are still around and can help me with this:

My wifi card has the logical address of wifi0, but the iwlist scan is performed by ath0? Is this why I'm not getting any connection? And what about the wifi0: unknown hardware address type 801 error in the dhclient command?

Please help me sever the cable!

devo@devo-desktop:~$ lshw -C network
WARNING: you should run this program as super-user.
*-network:0
description: Ethernet interface
product: SiS900 PCI Fast Ethernet
vendor: Silicon Integrated Systems [SiS]
physical id: 4
bus info: pci@0000:00:04.0
logical name: eth0
version: 90
serial: 00:14:85:14:9f:fc
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=sis900 driverversion=v1.08.10 Apr. 2 2006 ip=192.168.1.44 latency=64 maxlatency=11 mingnt=52 module=sis900 multicast=yes
*-network:1
description: Wireless interface
product: AR5212/AR5213 Multiprotocol MAC/baseband processor
vendor: Atheros Communications, Inc.
physical id: c
bus info: pci@0000:00:0c.0
logical name: wifi0
version: 01
serial: 00:18:e7:2e:60:50
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=ath_pci latency=168 maxlatency=28 mingnt=10 module=ath_pci multicast=yes wireless=IEEE 802.11g

devo@devo-desktop:~$ sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wifi0 Interface doesn't support scanning.

ath0 Scan completed :
Cell 01 - Address: 00:E0:98:CC:54:D7
ESSID:"ThrasherNet"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=17/70 Signal level=-78 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=200
Cell 02 - Address: 00:09:5B:ED:5D:B2
ESSID:"NETGEAR"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=6/70 Signal level=-89 dBm Noise level=-95 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:ath_ie=dd0900037f01010006ff7f
Cell 03 - Address: 00:18:39:3F:17:5F
ESSID:"linksys"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=19/70 Signal level=-76 dBm Noise level=-95 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Cell 04 - Address: 00:12:0E:40:DC:B6
ESSID:"06B408648877"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=158/70 Signal level=-193 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=200

devo@devo-desktop:~$ sudo dhclient ath0
There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:18:e7:2e:60:50
Sending on LPF/ath0/00:18:e7:2e:60:50
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

[kevdog]

Your using the madwifi drivers. According to the madwifi specs it creates a virtual interface for each device. The device is wifi0, the virtual interface is ath0. All command line is directed toward the virtual interface, not the physical device itself. You need to probably specifiy a specific essid on the command line before the dhclient command. All though you mentioned the error with wifi0, where is the output that showed this error?

[d_thrasher]

where would I put the essid in the command? wifi0 error listed below.

devo@devo-desktop:~$ sudo dhclient ath0
There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:18:e7:2e:60:50
Sending on LPF/ath0/00:18:e7:2e:60:50
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

[kevdog]

Look at the original post (first page). It will tell you where to put the essid. If that error persists, it could be a problem.

Post
lshw -C network

[d_thrasher]

I just ran trough the entire exercise again. Output below. I'm sure it has something to do with the unknown hardware 801 error after sudo dhclient -r ath1, but I don't know what to do about it. Is there a way I can start from scratch? maybe something wonky in a configuration file?

devo@devo-desktop:~$ lshw -C network
WARNING: you should run this program as super-user.
*-network:0
description: Ethernet interface
product: SiS900 PCI Fast Ethernet
vendor: Silicon Integrated Systems [SiS]
physical id: 4
bus info: pci@0000:00:04.0
logical name: eth0
version: 90
serial: 00:14:85:14:9f:fc
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=sis900 driverversion=v1.08.10 Apr. 2 2006 ip=192.168.1.44 latency=64 maxlatency=11 mingnt=52 module=sis900 multicast=yes
*-network:1
description: Wireless interface
product: AR5212/AR5213 Multiprotocol MAC/baseband processor
vendor: Atheros Communications, Inc.
physical id: c
bus info: pci@0000:00:0c.0
logical name: wifi0
version: 01
serial: 00:18:e7:2e:60:50
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=ath_pci latency=168 maxlatency=28 mingnt=10 module=ath_pci multicast=yes wireless=IEEE 802.11g
devo@devo-desktop:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wifi0 Interface doesn't support scanning.

ath1 Scan completed :
Cell 01 - Address: 00:E0:98:CC:54:D7
ESSID:"ThrasherNet"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=13/70 Signal level=-82 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=200
Cell 02 - Address: 00:09:5B:ED:5D:B2
ESSID:"NETGEAR"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=209/70 Signal level=-142 dBm Noise level=-95 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:ath_ie=dd0900037f01010006ff7f
Cell 03 - Address: 00:18:39:3F:17:5F
ESSID:"linksys"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=0/70 Signal level=-95 dBm Noise level=-95 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100

devo@devo-desktop:~$ sudo ifconfig eth0 down
devo@devo-desktop:~$ sudo ifconfig ath1 down
devo@devo-desktop:~$ sudo dhclient -r ath1
There is already a pid file /var/run/dhclient.pid with pid 7271
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath1/00:18:e7:2e:60:50
Sending on LPF/ath1/00:18:e7:2e:60:50
Sending on Socket/fallback
devo@devo-desktop:~$ sudo ifconfig ath1 up
devo@devo-desktop:~$ sudo iwconfig ath1 essid "ThrasherNet"
devo@devo-desktop:~$ sudo iwconfig ath1 key 526d2c6b426a42646f3f382058
devo@devo-desktop:~$ sudo iwconfig ath1 mode managed
devo@devo-desktop:~$ sudo dhclient ath1
There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath1/00:18:e7:2e:60:50
Sending on LPF/ath1/00:18:e7:2e:60:50
Sending on Socket/fallback
DHCPDISCOVER on ath1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on ath1 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on ath1 to 255.255.255.255 port 67 interval 15
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

[kevdog]

Check your system logs (there is a reference in the reference section in the original post) to see if you find anything

dmesg | more

[d_thrasher]

Well, there is this:
[ 39.235637] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 39.319034] ath_hal: module license 'Proprietary' taints kernel.
[ 39.319859] ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
[ 39.547523] wlan: 0.8.4.2 (0.9.3.2)
[ 39.567685] ath_pci: 0.9.4.5 (0.9.3.2)
[ 39.567748] ACPI: PCI Interrupt 0000:00:0c.0[A] -> GSI 16 (level, low) -> IRQ 21
[ 40.236346] ath_rate_sample: 1.2 (0.9.3.2)
[ 40.236900] wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
[ 40.236906] wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
[ 40.236916] wifi0: turboG rates: 6Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
[ 40.236923] wifi0: H/W encryption support: WEP AES AES_CCM TKIP
[ 40.236927] wifi0: mac 7.9 phy 4.5 radio 5.6
[ 40.236933] wifi0: Use hw queue 1 for WME_AC_BE traffic
[ 40.236935] wifi0: Use hw queue 0 for WME_AC_BK traffic
[ 40.236937] wifi0: Use hw queue 2 for WME_AC_VI traffic
[ 40.236939] wifi0: Use hw queue 3 for WME_AC_VO traffic
[ 40.236941] wifi0: Use hw queue 8 for CAB traffic
[ 40.236943] wifi0: Use hw queue 9 for beacons
[ 40.306535] wifi0: Atheros 5212: mem=0xe8000000, irq=21


Then a lot of stuff like this:

[ 1683.492931] Unknown OutputIN= OUT=ath1 SRC=169.254.5.129 DST=192.168.1.1 LEN=80 TOS=0x00 PREC=0x00 TTL=64 ID=13146 DF PROTO=UDP SPT=32780 DPT=53
LEN=60
[ 1689.336286] Unknown OutputIN= OUT=ath1 SRC=192.168.1.44 DST=205.188.9.53 LEN=112 TOS=0x00 PREC=0x00 TTL=64 ID=9813 DF PROTO=TCP SPT=56667 DPT=519
0 WINDOW=29957 RES=0x00 ACK PSH URGP=0
[ 1712.238621] eth0: Media Link On 100mbps full-duplex
[ 1719.782730] eth0: no IPv6 routers present
[ 1820.302925] Inbound IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:12:f0:a3:29:4a:08:00 SRC=192.168.1.47 DST=192.168.1.255 LEN=237 TOS=0x00 PREC=0x00 TTL=
128 ID=541 PROTO=UDP SPT=138 DPT=138 LEN=217
[ 1826.247646] ath1: no IPv6 routers present
[ 2085.655551] ath1: no IPv6 routers present
[ 2225.572919] Unknown OutputIN= OUT=ath1 SRC=192.168.1.44 DST=207.46.106.20 LEN=70 TOS=0x00 PREC=0x00 TTL=64 ID=41815 DF PROTO=TCP SPT=32997 DPT=18
63 WINDOW=13936 RES=0x00 ACK PSH URGP=0
[ 2231.415242] Unknown OutputIN= OUT=ath1 SRC=169.254.5.129 DST=192.168.1.1 LEN=63 TOS=0x00 PREC=0x00 TTL=64 ID=19331 DF PROTO=UDP SPT=32780 DPT=53
LEN=43

Any of that say anything to you?

[kevdog]

Are you running wired and wireless at the same time??

Can you post
ifconfig

[d_thrasher]

devo@devo-desktop:~$ ifconfig
ath1 Link encap:Ethernet HWaddr 00:18:E7:2E:60:50
inet6 addr: fe80::218:e7ff:fe2e:6050/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth0 Link encap:Ethernet HWaddr 00:14:85:14:9F:FC
inet addr:192.168.1.44 Bcast:255.255.255.255 Mask:255.255.255.0
inet6 addr: fe80::214:85ff:fe14:9ffc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22085 errors:0 dropped:0 overruns:0 frame:0
TX packets:21338 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14910385 (14.2 MB) TX bytes:3101423 (2.9 MB)
Interrupt:20 Base address:0xc800

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:66 errors:0 dropped:0 overruns:0 frame:0
TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5176 (5.0 KB) TX bytes:5176 (5.0 KB)

wifi0 Link encap:UNSPEC HWaddr 00-18-E7-2E-60-50-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:65942 errors:0 dropped:0 overruns:0 frame:62139
TX packets:3557 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:5605636 (5.3 MB) TX bytes:180947 (176.7 KB)
Interrupt:21

[kevdog]

Did you bring the wired interface down prior to trying to bring up the wireless interface?

sudo ifconfig eth0 down
sudo ifconfig ath1 up

[d_thrasher]

yep

[Griff]

This is a great guide. Very nice work. I'll definitely be using this later to figure out a few issues of my own.

[Griff]

Kevdog. Thank you. This was so much easier than trying to find the right gui that worked. The last time I installed a *buntu on my laptop I struggled for a couple days trying to figure out why I couldn't connect to wireless networks and it ended up being a gui problem. Nice guide.=D>

[kevdog]

If you can do it from the command line, you dont ever have to worry what happens if suddenly network manager acts up (which it does), or if you take your laptop elsewhere and it cant connect through the GUI -- but it did at home. Again, the command line gives you the basic knowledge to get a connection when other methods are failing -- its a very reliable if not the ultimate fallback!!

[Griff]

I have no issues with establishing/maintaining connection on unprotected networks (like at school), but WEP just isn't working. The last step yields the following message, "No DHCPOFFERS received. No working leases in persistent database - sleeping."

Now I know the network is up because I can scan for it and see it with the pre installed gui. Any idea what's going on?

Thanks,
Griff

[kevdog]

64 or 128 bit wep?? Are you using hexidecimal or ascii? If hexidecimal did you set the key index correctly?? (man iwconfig gives examples how to do this)

[Griff]

It's 128 hex and I believe I did it correctly. I'll double check.

[Griff]

If hexidecimal did you set the key index correctly??
I'm not sure what you mean by index, but according to the man page all I should need to do is:

sudo iwconfig eth0 key 11111111111111111111111111
right?

edit: I saw the entry about index but from what it says I don't think it applies to me

[kevdog]

yes thats the right formati, you need to make sure then that key is 25 (24??) characters is in length and that its key index 1 on the router.

[solaris_wiz]

I went through the steps, but I'm still unable to pull an IP. Any help would be appreciated.

Here's what I end up getting:


$ sudo dhclient eth1
There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:12:17:9d:8a:ee
Sending on LPF/eth1/00:12:17:9d:8a:ee
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

[Griff]

All right, it was key 1 on the router and I enforced the key to index [1] on my card, but the outcome is the same as before.

[solaris_wiz]

All right, it was key 1 on the router and I enforced the key to index [1] on my card, but the outcome is the same as before.

looks like we're in the same boat right now, Griff.

did you bring your ether connection down before you tried enabling your wifi connection?
Just a thought, perhaps that could be holding you back, as I read it in a previous page.

[HUIG]

Now, does it matter if the ESSID contains spaces? Does it matter if the WPA is a passphrase? (both within the quotation marks tho)

Now, this is what I'm (also) getting

Listening on LPF/eth1/00:19:7e:b3:2c:89
Sending on LPF/eth1/00:19:7e:b3:2c:89
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

using ndiswrapper-1.47 installed on a clean gusty as detailed in
http://ubuntuforums.org/showthread.php?t=297092&highlight=bcm43xx

network name was found after this installation but i never got connected to it. also switching back to wired connection never works immediately, it might just take some time but usually i switch it on and off a couple of times from Administration/Network before anything happens

now did I use this command correctly?
sudo wpa_supplicant -w -Dwext -ieth1 -c/etc/wpa_supplicant.conf

it does not result in anything, I had to terminate

And here's some more info
*-network DISABLED
description: Wireless interface
product: BCM94311MCG wlan mini-PCI
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:0b:00.0
logical name: eth1
version: 01
serial: 00:19:7e:b3:2c:89
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.47+Broadcom,10/12/2006, 4.100. latency=0 module=ndiswrapper multicast=yes wireless=IEEE 802.11g


Thanks, this is wrecking my head, being a beginner doesn't help!

[kevdog]

Here is your problem:

*-network DISABLED

So if you have a wired connection, bring down the wired interface, and then bring up the wireless interface:

sudo ifconfig eth0 down
sudo ifconfig eth1 up

Recheck lshw -C network to confirm you do not have a disabled statement.

No spaces in essid --- spaces = BIG PROBLEMS!

Try an unencrypted connection before using wpa.

[HUIG]

Here is your problem:

*-network DISABLED

So if you have a wired connection, bring down the wired interface, and then bring up the wireless interface:

sudo ifconfig eth0 down
sudo ifconfig eth1 up

Recheck lshw -C network to confirm you do not have a disabled statement.

No spaces in essid --- spaces = BIG PROBLEMS!

Try an unencrypted connection before using wpa.

ah yeah well that was only disabled when I copied that report, thats not the problem here

but apparently "get your own broadband, ****!"-essid has to be changed, bah. been having problems logging into the router and its a common one to our house so just wanted to try and get it working without service disrupts but thats an another story altogether and will have to have a look at it now then...

thanks!

[Ubuntiac]

I'm having the *exact* same problem as d_thrasher, right down to the outputs above, error messages and logical names, and yes I've checked that my wired is down and there's no NETWORK DISABLED on my ath0/wifi0 device.

[kevdog]

Ubuntiac

Can you post the results of lshw -C network and iwlist scan?

[Ubuntiac]

Can you post the results of lshw -C network and iwlist scan?

lshw -C network:

*-network DISABLED
description: Ethernet interface
product: 82566DC Gigabit Network Connection
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: eth0
version: 02
serial: 00:19:d1:88:59:b4
capacity: 1GB/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000 driverversion=7.3.20-k2-NAPI firmware=1.1-0 latency=0 link=no module=e1000 multicast=yes port=twisted pair
*-network
description: Wireless interface
product: AR5212/AR5213 Multiprotocol MAC/baseband processor
vendor: Atheros Communications, Inc.
physical id: 0
bus info: pci@0000:07:00.0
logical name: wifi0
version: 01
serial: 00:18:e7:27:12:5f
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=ath_pci driverversion=0.9.4.5 (0.9.3.2) latency=168 maxlatency=28 mingnt=10 module=ath_pci multicast=yes wireless=IEEE 802.11g



iwlist scan:

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wifi0 Interface doesn't support scanning.



and just for good measure, lspci:


00:00.0 Host bridge: Intel Corporation 82P965/G965 Memory Controller Hub (rev 02)
00:01.0 PCI bridge: Intel Corporation 82P965/G965 PCI Express Root Port (rev 02)
00:03.0 Communication controller: Intel Corporation 82P965/G965 HECI Controller (rev 02)
00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network Connection (rev 02)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Contoller #4 (rev 02)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 02)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 02)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev f2)
00:1f.0 ISA bridge: Intel Corporation 82801HB/HR (ICH8/R) LPC Interface Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801H (ICH8 Family) 4 port SATA IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 02)
00:1f.5 IDE interface: Intel Corporation 82801H (ICH8 Family) 2 port SATA IDE Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation GeForce 8600 GT (rev a1)
03:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6101 single-port PATA133 interface (rev b1)
07:00.0 Ethernet controller: Atheros Communications, Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01)
07:01.0 RAID bus controller: Silicon Image, Inc. PCI0680 Ultra ATA-133 Host Controller (rev 02)
07:03.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)


Strange thing is that it seemed to work fine before the recent network-manager update, and now it still seems to work *sometimes*. If I don't use it for a few hours though it just seems to drop out and not even a computer restart gets it back. Oh, and for the record, my Atheros card usually supports scanning, just fine!

Thanks in advance for any ideas!

[kevdog]

You are using the madwifi drivers which usually are very reliable. B/c of the way madwifi works, it creates virutal interfaces (usually ath0) for your physical card located at wifi0.

I used to have a problem with my broadcom card doing something similar to what you describe. Short of rebooting, the only thing I found would work was to create a script that would bring down the interface, unload the driver module, reload the driver module, and then bring up the interface. Although definitely not an ideal solution it would at least save me a reboot.

Since you state that sometimes your atheros card work, see if it scan (iwlist scan) using ath0. I dont think wif0 is truly the interface to work through.

[tonycollinet]

Thanks for this process - wirless now works if I type in these commands.

Now - sorry for a total noob question (I am one - a noob that is)

How do I set things up so I don't have to type the command sequence everytime I start my PC? I assume I can put them into some sort of script file and have it auto run at start up? What if I want to make it flexible for different networks?

Or is there anything I can do to make the GUI work (It detects the SSID from the wirless, but repeatedly asks me to put in the WEP Key, and gets no further, although it did work once.)

[Ubuntiac]

I know in Kubuntu (or any KDE distro) you just put the script in a text file in ~/.kde/autostart, make sure the file name ends in .sh, rick click on it and check "executable" under the permissions tab. I'm sure there's something similar in gnome.

[kevdog]

If the manual commands are working for you on the command line, then Im not sure why network manager is not working.

A couple of things
WICD is an alternative to network manager. You might try this. I know that at its heart it works similar to the command line, but is very fancy and provides a GUI, tray icon, etc.

You can always write a script file that you either launch manually or when you log in. You could get really fancy with the script file, or keep it rather basic. Seems in my situation the more I jazz up the script file, I decrease the chances it will actually work. Usually I just scan for available networks with iwlist scan, and then wrote a script and call it with:
network_connect NETWORK_NAME

NETWORK_NAME in the script is variable $1, so everything pretty much connects. Simple but it works.

[bliffle]

"wicd" gave me a headache last week. the install unloaded NetworkManager then failed to complete. I couldn't successfully reload NM after that, so I was forced to upgrade from Feisty to Gutsy before I planned.

[Ubuntiac]

Thanks for your help Kevdog,

I guess I'm interested in getting my wireless to work via commandline not only so I can have it working (I have a working laptop with an Intel card :)), but also so I can find out what was wrong and let the good folks maintaining network-manager fix it for everyone, so I think I'll skip WICD. Thanks for th suggestion, though. Now to try and figure out what's actually going on here...

[bliffle]

If a guy had ONE cli command that would spell out what the pertinent values are for a wireless connection, then a guy could record that info when the connection is running correctly and go about re-instating those values when he has a problem.

The first step to solving most bugs is to insrument the system.

[bliffle]

Is there a monitor program of some kind that will dynamically display the current upload and download speeds?

[kevdog]

Check out conky. I really like it, however it might not be what you are looking for. Its a system monitor tool. There is a HOW-TO in the Tutorials&Tips section.

[Chazall1]

I need assistance Please

I have Gutsy on a Dell Dimension B110 Desktop using a Linksys Router with WEP. I can not conect to my WEP. However I was connecting to the Internet using other Linksys networks in the neighborhood. This however has stoped working, I do not have ndiswrapper installed, would this make a difference???
Here are my outputs if I use wmaster0 as my interface:

ace@ace-desktop:~$ lshw -C network
WARNING: you should run this program as super-user.
*-network:0
description: Wireless interface
product: RT2500 802.11g Cardbus/mini-PCI
vendor: RaLink
physical id: 0
bus info: pci@0000:01:00.0
logical name: wmaster0
version: 01
serial: 00:12:17:8c:99:3c
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=rt2500pci latency=64 module=rt2500pci multicast=yes wireless=IEEE 802.11g
*-network:1
description: Ethernet interface
product: 82562EZ 10/100 Ethernet Controller
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:01:08.0
logical name: eth0
version: 02
serial: 00:13:20:d4:8e:45
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=e100 driverversion=3.5.17-k4-NAPI firmware=N/A latency=64 maxlatency=56 mingnt=8 module=e100 multicast=yes

If I use wmaster0 in <interface>
ace@ace-desktop:~$ sudo ifconfig wmaster0 down
[sudo] password for ace:
ace@ace-desktop:~$ sudo dhclient -r wmaster0
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wmaster0/
Sending on LPF/wmaster0/
Sending on Socket/fallback
ace@ace-desktop:~$ sudo ifconfig wmaster0 up
ace@ace-desktop:~$ sudo iwconfig wmaster0 essid "lish1"
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device wmaster0 ; Operation not supported.
ace@ace-desktop:~$ sudo iwconfig wmaster0 key 6063547000
Error for wireless request "Set Encode" (8B2A) :
SET failed on device wmaster0 ; Operation not supported.
ace@ace-desktop:~$ sudo iwconfig wmaster0 mode Managed
Error for wireless request "Set Mode" (8B06) :
SET failed on device wmaster0 ; Operation not supported.
ace@ace-desktop:~$ sudo dhclient wmaster0
There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wmaster0/
Sending on LPF/wmaster0/
Sending on Socket/fallback
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

If I run wlan0, here is the output:

ace@ace-desktop:~$ sudo ifconfig wlan0 down
[sudo] password for ace:
ace@ace-desktop:~$ sudo dhclient -r wlan0
There is already a pid file /var/run/dhclient.pid with pid 6040
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:12:17:8c:99:3c
Sending on LPF/wlan0/00:12:17:8c:99:3c
Sending on Socket/fallback
ace@ace-desktop:~$ sudo ifconfig wlan0 up
ace@ace-desktop:~$ sudo iwconfig wlan0 essid "lish1"
ace@ace-desktop:~$ sudo iwconfig wlan0 key 6063547000
ace@ace-desktop:~$ sudo iwconfig wlan0 mode Managed
ace@ace-desktop:~$ sudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:12:17:8c:99:3c
Sending on LPF/wlan0/00:12:17:8c:99:3c
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Can anyone assist me, I have no WIRELESS at this time

Thanks

[kevdog]

Can you post the results of

iwlist scan

[oraste]

Great, my main broplem was that set configuration from X to WPA and the whole system freezes. With this info I got it back default by

gksudo gedit /etc/network/interfaces

saved the old file and made orginal as black. restart and voila :)

[Chazall1]

NM Showing no Wireless

ace@ace-desktop:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

I added ndiswrapper and followed the How Too RT2500, etc wireless cards Gutsy in the forums.
When I add the drivers to the 'Blacklist in etc/modprobs, everything seems fine untill
I run ndiswrapper -l, my output is this,
ace@ace-desktop:~$ ndiswrapper -l
rt2500 : invalid driver!
rt2500pci : invalid driver!
ace@ace-desktop:~$
I have no Internet now, The NM does not give me an option for wireless!!
Here is my network interface file info as well

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 intel dhcp

[kevdog]

Chazall

You have two different options for your rt2500 card

#1. Compile and use serial monkey rt2500 driver
#2. Use ndiswrapper with windows driver (xp) for the rt2500

In both cases the rt2500pci driver shipped in gutsy needs to be blacklisted (since this third option -- using the built-in driver -- is very unstable in most cases -- hence resorting to options #1 or #2). Which option above are you trying to use??

[Chazall1]

#2. Use ndiswrapper with windows driver (xp) for the rt2500
I have installed ndiswrapper and have followed the instructions here, http://ubuntuforums.org/showthread.php?t=563547

I have Blacklisted the rt2500 and the rt2500pci drivers. However now when I boot up My Network fails to load, along with the modules, I see this briefly in the Usplash script that indicates the status of the loading process.
Some additional outputs

I am having NO luck on getting my Wireless to Function any more, Before I added ndiswrapper, I had some functionality with picking up other non WEP Linksys connections, Now I do not even have a choice for any Wireless functions, Dell Dimension B110, Here are some outputs

ace@ace-desktop:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

I added ndiswrapper and followed the How Too RT2500, etc wireless cards Gutsy in the forums.
When I add the drivers to the 'Blacklist in etc/modprobs, everything seems fine untill
I run ndiswrapper -l, my output is this,
ace@ace-desktop:~$ ndiswrapper -l
rt2500 : invalid driver!
rt2500pci : invalid driver!
ace@ace-desktop:~$
I have no Internet now, The NM does not give me an option for wireless!!
Here is my network interface file info as well

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 intel dhcp

Before ndiswrapper
Output I have Gutsy on a Dell Dimension B110 Desktop using a Linksys Router with WEP. I can not conect to my WEP. However I was connecting to the Internet using other Linksys networks in the neighborhood. This however has stoped working, I do not have ndiswrapper installed, would this make a difference???
Here are my outputs if I use wmaster0 as my interface:

ace@ace-desktop:~$ lshw -C network
WARNING: you should run this program as super-user.
*-network:0
description: Wireless interface
product: RT2500 802.11g Cardbus/mini-PCI
vendor: RaLink
physical id: 0
bus info: pci@0000:01:00.0
logical name: wmaster0
version: 01
serial: 00:12:17:8c:99:3c
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=rt2500pci latency=64 module=rt2500pci multicast=yes wireless=IEEE 802.11g
*-network:1
description: Ethernet interface
product: 82562EZ 10/100 Ethernet Controller
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:01:08.0
logical name: eth0
version: 02
serial: 00:13:20:d4:8e:45
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=e100 driverversion=3.5.17-k4-NAPI firmware=N/A latency=64 maxlatency=56 mingnt=8 module=e100 multicast=yes

If I use wmaster0 in <interface>
ace@ace-desktop:~$ sudo ifconfig wmaster0 down
[sudo] password for ace:
ace@ace-desktop:~$ sudo dhclient -r wmaster0
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wmaster0/
Sending on LPF/wmaster0/
Sending on Socket/fallback
ace@ace-desktop:~$ sudo ifconfig wmaster0 up
ace@ace-desktop:~$ sudo iwconfig wmaster0 essid "lish1"
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device wmaster0 ; Operation not supported.
ace@ace-desktop:~$ sudo iwconfig wmaster0 key 6063547000
Error for wireless request "Set Encode" (8B2A) :
SET failed on device wmaster0 ; Operation not supported.
ace@ace-desktop:~$ sudo iwconfig wmaster0 mode Managed
Error for wireless request "Set Mode" (8B06) :
SET failed on device wmaster0 ; Operation not supported.
ace@ace-desktop:~$ sudo dhclient wmaster0
There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wmaster0/
Sending on LPF/wmaster0/
Sending on Socket/fallback
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

If I run wlan0, here is the output:

ace@ace-desktop:~$ sudo ifconfig wlan0 down
[sudo] password for ace:
ace@ace-desktop:~$ sudo dhclient -r wlan0
There is already a pid file /var/run/dhclient.pid with pid 6040
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:12:17:8c:99:3c
Sending on LPF/wlan0/00:12:17:8c:99:3c
Sending on Socket/fallback
ace@ace-desktop:~$ sudo ifconfig wlan0 up
ace@ace-desktop:~$ sudo iwconfig wlan0 essid "lish1"
ace@ace-desktop:~$ sudo iwconfig wlan0 key 6063547000
ace@ace-desktop:~$ sudo iwconfig wlan0 mode Managed
ace@ace-desktop:~$ sudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:12:17:8c:99:3c
Sending on LPF/wlan0/00:12:17:8c:99:3c
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
Maybe I should Re-Install, My internet was working for a couple of weeks, without my WEP

[Chazall1]

Sorry, I forgot I gave you this Info already !!!

[NothingtoGein]

I followed all your steps and still can't get on. I get the same line everyone else is getting "No DHCPOFFERS received. No working leases persisting databases - sleeping."

Have you or anyone figured out why everyone keeps getting these messages?

[kevdog]

I read your previous post however Im just trying to grasp your knowledge of what you are trying to accomplish since your setup is kind of messed up.

configuration: broadcast=yes driver=rt2500pci

This line tells me your system is trying to use the builtin rt2500pci driver for your wireless card. So if you dont want to use this driver you need to do the following:

sudo modprobe -r rt2500pci
Place a line in the /etc/modprobe.d/blacklist file that states
blacklist rt2500pci

This prevents the drivers from loading at startup

With ndiswrapper- where are your .sys and .inf files located (these are the windows drivers)? You cant try to load multiple drivers with ndiswrapper, so to basically start over and wipe the slate clean, you

sudo rm -rf /etc/ndiswrapper/*

Then you load the windows drivers into ndiswrapper with:
sudo ndiswrapper -i ****.inf
And then load the ndiswrapper module into the kernel with:
sudo modprobe ndiswrapper

To make sure the ndiswrapper custom module is loaded at boot, place a line in the /etc/modules files that states:
ndiswrapper

Please also post iwlist scan.

[NothingtoGein]

Actually I just figured out the problem. It wasn't any of the above. I needed a static IP address instead of a DHCP.

Just input something like

DEVICE=eth0
BOOTPROTO=static
IPADDR=192.168.1.2
NETMASK=255.255.255.0
NETWORK=192.168.1.0
BROADCAST=192.168.1.255
ONBOOT=yes

Gives you a static IP - no more "No DHCPOFFERS received messages".

Google static IP ubuntu for people suffering the same problem I had - which just looking at this thread...ALOT.

[kevdog]

NothingtoGein

Where do you put or type this information??

[Chazall1]

Well I, # out what ndiswrapper configured in /etc/modules, and /etc/modprobe.d/blacklist. I set /etc/network/interfaces to

auto lo
iface lo inet loopback

I have Wireless back, I have been using the internet for the past 3 hrs, on another router, not mine. I disabled my WEP about an hour ago, and the NM still showes a security key in the NM Wireless networks. I will watch and see what happens!!!!!

[Ubuntiac]

I can't believe I missed this but...

sudo ifconfig ath0 up
sudo dhclient ath0 essid myessid
<ignore error messages>
<open webbrowser and...>

Internet all works! I think my problem before was that when I saw errors in the command line and NM still showed unconnected, I nievely thought that it mustn't have worked, yet when I actually use a browser / instant messenger / adept it all just works. Almost instantly NM then notices and shows connected.

Happy d'oh!

Thanks Kevdog, you are a legend amongst men for supporting this thread (and you have the coolest avatar ever!).

Praise be to Kevdog, awooooooooooooo!

[kevdog]

I definitely no legend, legend in your mine but not mine.

[madsmaddad]

The commands are the same, however Im not sure if this will work. Its something about the drivers and Linux. So basically Im saying is that Im not certain ubuntu can connect to any router with hidden ssid broadcast.

It does. Kubuntu Feisty and Gutsy both connected fine to my router. I am using a 3COM 3CRUSB100075 usb stick.

This is without encryption. I am still trying to get WPA working. :(

Madsmaddad

[kevdog]

Thanks for the tip about connecting to a hidden SSID.

How are you trying to get WPA working?

[madsmaddad]

Tried via the Gui programs: is it kwifimanager? But it didn't work, then tried installing wpa_supplicant, and it didn't work either, But thanks to your post about the wkihelps, I have learned that supplicant does not support ZD1211 chipset, so am thinking that I am back to square 1.

Still have encryption enabled on my router, so am doing this from XP, which means I can't get at all the info about what I have done.

Any pointers appreciated. :(

Peter M.

[kevdog]

Where did you find the info that the wpasupplicant package does not support your chipset??? Im only curious since Ive never seen this before.

[madsmaddad]

http://hostap.epitest.fi/wpa_supplicant/

does not show the Zydas ZD1211 chipset as being supported.

I note that page was last updated 2/12/07, so guess that the information is current.

[ender8282]

I started another thread but this thread already seems to be dealing with my issues. My problem is that I can connect to secured networks (at least 2 different networks) but I cannot connect to any unsecured networks. To connect to my secured network I am using:


sudo ifconfig eth1 down
sudo iwconfig eth1 essid 'MY_NETWORKS_ESSID' key MY_KEY mode Managed
sudo ifconfig eth1 up
sudo dhclient eth1

It works and I have a connection.
When I try to connect to an unsecured network with:


sudo ifconfig eth1 down
sudo iwconfig eth1 mode Managed essid 'NETGEAR'
sudo ifconfig eth1 up
sudo dhclient eth1

I get the error:


There is already a pid file /var/run/dhclient.pid with pid 7188
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:16:cf:8f:80:98
Sending on LPF/eth1/00:16:cf:8f:80:98
Sending on Socket/fallback
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
Trying recorded lease 192.168.1.103
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

--- 192.168.1.1 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

No working leases in persistent database - sleeping.

I can connect to this network under XP so I know that there is no MAC filtering going on or anything like that.
Thanks in advance for any advice.

[kevdog]

For your zydas card, what driver are you using??


----


For your unencrypted network, can you post
iwlist scan

Try to connect from the command line leaving out the mode Managed part.

[dendy7h]

Maybe this can help someone. My WEP key has some special characters in it. This is the error message I was getting.

$ sudo iwconfig eth0 key s:KG"hSRaS{G!#[
sudo iwconfig eth0 key s:KG"hSRaS{Gsudo iwconfig eth0 key s:KG"hSRaS{G[

.....

$sudo dhclient eth0
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


I escape the special characters with a \ and it works


$sudo iwconfig eth0 key s:KG\"hSRaS\{G\!\#\[


Maybe this can help some people who can't get their connections working.

Thanks Kevdog for posting this :guitar:!!!!!

Dendy

[kevdog]

Thanks for the tip -- I thought special characters were out of the question -- I guess they are not!

[ender8282]

For your zydas card, what driver are you using??


----


For your unencrypted network, can you post
iwlist scan

Try to connect from the command line leaving out the mode Managed part.

I don't know about zydas but I am have a Broadcom 1390 wireless chipset. I am using the windows driver with ndiswrapper. I followed this (how to (http://ubuntuforums.org/showthread.php?t=297092)) to get everything set up.

At the moment I can't see the unencrypted wireless network but I will try to connect to it without the mode field tomorrow and I will get the iwlist scan as well.
Thanks

[ender8282]

The network signal is a little week this morning but when I scan I see it as:


Cell 02 - Address: 00:0F:B5:67:F0:22
ESSID:"NETGEAR"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:14/100 Signal level:-87 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0

Normally the quality is minimum of 30.
I also tried connecting without specifying mode and I get the same 'no dhcp offers' error msg.

[kevdog]

Can you do anything to get the signal stronger such as move closer to the router?

[AJWhitewolf]

I am having a very similar problem to this... I have no problems connecting to a secured wireless network, but when I attempt to connect to an unsecured network, I receive no DHCPOFFER.

I have a D-Link card and the driver I am using is ath_pci

I just got rid of Network Manager and started doing everything from the command line, following the guide outlined at the beginning of this thread, and I am receiving this same message:

DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

The network does show up in iwlist (would post it, but my comp. has no internet, so I'm posting this at work), and I have used a variety of settings for iwconfig to try and make this work, including:
iwconfig ath0 mode managed
iwconfig ath0 key off
iwconfig ath0 enc off

And also, of course, setting the essid.

The wireless network I am trying to connect to is the free wireless internet that my apartment complex provides, so I do not have access to their router to change any settings. However, I have a wireless router at my house, and when I turn on security, I am able to connect to it without problem, but when I make the network unsecured, I receive the errors listed above, so I am positive that it is a common cause that only affects my ability to connect to unsecured networks.

Any help would definitely be appreciated!

[kevdog]

Please type of list the commands you are using attempting to connect to your unencrypted wireless network.

[AJWhitewolf]

sudo ifconfig ath0 down
sudo dhclient -r ath0
sudo ifconfig ath0 up
sudo iwconfig ath0 essid "Pardeeville"
sudo iwconfig ath0 mode managed
sudo dhclient ath0

I have also tried adding:
sudo iwconfig ath0 key off
sudo iwconfig ath0 enc off

I have also manually set the channel and frequency to match that of the network I am trying to connect to, but it makes no difference.

If you need any further information, just ask!

[malc_adams]

kevdog, it took about 3 days of searching and trying other solutions, none of which worked, but I finally found your definitive answer and got my ra61 wireless card working in about 15 minutes. You have my grateful thanks.

[Thiago Cesar Vieira]

Yes, I agree with malc_adams: your post is very helpful and I follow a lot of tricks listed there.

After 1 week using wireless in Ubuntu, suddenly my connection gets bad. Sometimes I can use normally, other losing some packages and almost all time with no wireless.

I use wireless normally in Windows, so my adapter and the router is working fine. My problem is in Ubuntu configuration. I use dhcp in a D-Link router with WEP 128 bits.

As I said, I follow your procedure to fix bugs in wireless, and I listed above the results. Does anyone have already seen it before or knows the procedure to fix my problem?

$ lspci
...
05:06.0 Network controller: Texas Instruments ACX 111 54Mbps Wireless Interface
...

$ iwlist wlan0 scanning
wlan0 Scan completed :
Cell 01 - Address: 00:1B:11:FE:48:6E
ESSID:"[MY_ESSID]"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=44/100 Signal level=21/100 Noise level=0/100
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s

$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface wlan0 inet dhcp
wireless-key s:[MY-KEY]
wireless-essid [MY_ESSID]

auto wlan0

$ ifconfig -a
eth0 ...
lo ...

wlan0 Link encap:Ethernet HWaddr 00:13:46:34:D3:85
inet addr:192.168.0.151 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::213:46ff:fe34:d385/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3092 errors:17 dropped:0 overruns:0 frame:0
TX packets:2802 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3025914 (2.8 MB) TX bytes:561166 (548.0 KB)
Interrupt:16 Base address:0x8000

$ iwconfig wlan0
wlan0 IEEE 802.11b+/g+ ESSID:"[MY_ESSID]" Nickname:"acx v0.3.36"
Mode:Managed Frequency:2.437 GHz Access Point: 00:1B:11:FE:48:6E
Bit Rate:54 Mb/s Tx-Power=15 dBm Sensitivity=1/3
Retry min limit:7 RTS thr:off
Power Management:off
Link Quality=39/100 Signal level=14/100 Noise level=0/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


$ lshw -C network
*-network:0
description: Wireless interface
product: ACX 111 54Mbps Wireless Interface
vendor: Texas Instruments
physical id: 6
bus info: pci@0000:05:06.0
logical name: wlan0
version: 00
serial: 00:13:46:34:d3:85
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=acx_pci ip=192.168.0.151 latency=32 module=acx multicast=yes wireless=IEEE 802.11b+/g+
*-network:1
...


$ sudo dhclient wlan0
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:13:46:34:d3:85
Sending on LPF/wlan0/00:13:46:34:d3:85
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPOFFER from 192.168.0.1
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1
bound to 192.168.0.151 -- renewal in 579250 seconds.


After some minutes it starts to lose packages when I ping in router (192.168.0.1)... rate of successful packages 100% goes to 80%, 60%, 40%...

My log files listed bellow start logging problems...
/var/log/kern.log
/var/log/messages
/var/log/syslog

Dec 9 11:51:52 kernel: [ 1035.974387] acx: got IV_ICV_Failure (crypto) IRQ(s)
Dec 9 11:52:21 kernel: [ 1064.191699] wlan0: tx error 0x10, buf 05! (MSDU lifetime timeout? - try changing 'iwconfig retry lifetime XXX')
Dec 9 12:00:52 kernel: [ 1575.379976] NETDEV WATCHDOG: wlan0: transmit timed out
Dec 9 12:00:52 kernel: [ 1575.379984] wlan0: FAILED to free any of the many full tx buffers. Switching to emergency freeing. Please report!
Dec 9 12:00:52 kernel: [ 1575.380015] wlan0: tx timeout!
Dec 9 12:00:52 kernel: [ 1575.380118] wlan0: recalibrating radio
...
Dec 9 12:05:52 kernel: [ 1875.164877] wlan0: got disassoc frame with reason 4 (due to inactivity)
A cada 2segundos printa essa mensagem:
Dec 9 12:06:29 kernel: [ 1912.366504] acx: BUG: no free txdesc left


$ iwconfig wlan0
wlan0 IEEE 802.11b+/g+ ESSID:"[MY_ESSID]" Nickname:"acx v0.3.36"
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
Bit Rate:1 Mb/s Tx-Power=15 dBm Sensitivity=1/3
Retry min limit:7 RTS thr:off
Power Management:off
Link Quality=43/100 Signal level=20/100 Noise level=0/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:2 Missed beacon:0


$ sudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 5944
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:13:46:34:d3:85
Sending on LPF/wlan0/00:13:46:34:d3:85
Sending on Socket/fallback
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
No DHCPOFFERS received.
Trying recorded lease 192.168.0.151
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.

--- 192.168.0.1 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

No working leases in persistent database - sleeping.


$ sudo ifconfig wlan0 down
Stops to log errors.

$ sudo dhclient -r wlan0
There is already a pid file /var/run/dhclient.pid with pid 6505
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:13:46:34:d3:85
Sending on LPF/wlan0/00:13:46:34:d3:85
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.0.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.


$sudo ifconfig wlan0 up
Starts to log again:
Dec 9 12:18:33 kernel: [ 2635.423531] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec 9 12:19:10 kernel: [ 2672.586353] acx: BUG: no free txdesc left

$ sudo iwconfig wlan0 essid "[MY_ESSID]"
$ sudo iwconfig wlan0 key s:[MY_KEY]
$ sudo iwconfig wlan0 mode Managed
$ sudo dhclient wlan0

After last command
There is already a pid file /var/run/dhclient.pid with pid 0
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:13:46:34:d3:85
Sending on LPF/wlan0/00:13:46:34:d3:85
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


My /var/log/syslog prints
Dec 9 12:33:22 dhclient: No DHCPOFFERS received.
Dec 9 12:33:22 dhclient: No working leases in persistent database - sleeping.
Dec 9 12:33:22 avahi-autoipd(wlan0)[6945]: Found user 'avahi-autoipd' (UID 105) and group 'avahi-autoipd' (GID 113).
Dec 9 12:33:22 avahi-autoipd(wlan0)[6945]: Successfully called chroot().
Dec 9 12:33:22 avahi-autoipd(wlan0)[6945]: Successfully dropped root privileges.
Dec 9 12:33:22 avahi-autoipd(wlan0)[6945]: Starting with address 169.254.7.33
Dec 9 12:33:23 kernel: [ 3524.796812] acx: BUG: no free txdesc left
Dec 9 12:33:26 kernel: [ 3527.294933] acx: BUG: no free txdesc left
Dec 9 12:33:27 avahi-autoipd(wlan0)[6945]: Callout BIND, address 169.254.7.33 on interface wlan0
Dec 9 12:33:27 avahi-daemon[5278]: Joining mDNS multicast group on interface wlan0.IPv4 with address 169.254.7.33.
Dec 9 12:33:27 avahi-daemon[5278]: New relevant interface wlan0.IPv4 for mDNS.
Dec 9 12:33:27 avahi-daemon[5278]: Registering new address record for 169.254.7.33 on wlan0.IPv4.
Dec 9 12:33:30 kernel: [ 3531.841374] acx: BUG: no free txdesc left
Dec 9 12:33:31 avahi-autoipd(wlan0)[6945]: Successfully claimed IP address 169.254.7.33
Dec 9 12:33:32 kernel: [ 3533.338381] acx: BUG: no free txdesc left
Dec 9 12:33:34 kernel: [ 3535.836501] acx: BUG: no free txdesc left
Dec 9 12:33:37 kernel: [ 3538.334619] acx: BUG: no free txdesc left
Dec 9 12:33:39 kernel: [ 3540.832737] acx: BUG: no free txdesc left
Dec 9 12:33:41 avahi-autoipd(wlan0)[6945]: SIOCSIFFLAGS failed: Permission denied
Dec 9 12:33:41 avahi-autoipd(wlan0)[6945]: Callout STOP, address 169.254.7.33 on interface wlan0
Dec 9 12:33:41 avahi-daemon[5278]: Interface wlan0.IPv4 no longer relevant for mDNS.
Dec 9 12:33:41 avahi-daemon[5278]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 169.254.7.33.
Dec 9 12:33:41 avahi-daemon[5278]: Withdrawing address record for 169.254.7.33 on wlan0.
Dec 9 12:33:41 avahi-daemon[5278]: Joining mDNS multicast group on interface wlan0.IPv4 with address 169.254.7.33.
Dec 9 12:33:41 dhclient: receive_packet failed on wlan0: Network is down
Dec 9 12:33:41 avahi-daemon[5278]: New relevant interface wlan0.IPv4 for mDNS.
Dec 9 12:33:41 avahi-daemon[5278]: Registering new address record for 169.254.7.33 on wlan0.IPv4.
Dec 9 12:33:41 dhclient: receive_packet failed on wlan0: Network is down
Dec 9 12:33:41 avahi-daemon[5278]: Withdrawing address record for 169.254.7.33 on wlan0.
Dec 9 12:33:41 avahi-daemon[5278]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 169.254.7.33.
Dec 9 12:33:41 avahi-daemon[5278]: Interface wlan0.IPv4 no longer relevant for mDNS.


After I restart my machine...
Dec 9 12:44:55 NetworkManager: <info> Updating allowed wireless network lists.
Dec 9 12:44:55 NetworkManager: <WARN> nm_dbus_get_networks_cb(): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - There are no wireless networks stored..

Dec 9 12:50:16 kernel: [ 420.557064] wlan0: rx: 8 DUPs in 21 packets received in 10 secs
Dec 9 12:50:35 kernel: [ 439.245000] wlan0: tx error 0x20, buf 02! (excessive Tx retries due to either distance too high or unable to Tx or Tx frame error - try changing 'iwconfig txpower XXX' or 'sens'itivity or 'retry')
Dec 9 12:50:35 kernel: [ 439.245012] wlan0: tx error 0x20, buf 03! (excessive Tx retries due to either distance too high or unable to Tx or Tx frame error - try changing 'iwconfig txpower XXX' or 'sens'itivity or 'retry')
Dec 9 12:50:35 kernel: [ 439.245023] wlan0: tx error 0x20, buf 04! (excessive Tx retries due to either distance too high or unable to Tx or Tx frame error - try changing 'iwconfig txpower XXX' or 'sens'itivity or 'retry')
Dec 9 12:50:39 kernel: [ 443.182437] wlan0: several excessive Tx retry errors occurred, attempting to recalibrate radio. Radio drift might be caused by increasing card temperature, please check the card before it's too late!
Dec 9 12:50:39 kernel: [ 443.182450] wlan0: tx error 0x20, buf 05! (excessive Tx retries due to either distance too high or unable to Tx or Tx frame error - try changing 'iwconfig txpower XXX' or 'sens'itivity or 'retry')
Dec 9 12:50:39 kernel: [ 443.182458] wlan0: tx error 0x20, buf 06! (excessive Tx retries due to either distance too high or unable to Tx or Tx frame error - try changing 'iwconfig txpower XXX' or 'sens'itivity or 'retry')
Dec 9 12:50:39 kernel: [ 443.182468] wlan0: tx error 0x20, buf 07! (excessive Tx retries due to either distance too high or unable to Tx or Tx frame error - try changing 'iwconfig txpower XXX' or 'sens'itivity or 'retry')
Dec 9 12:50:39 kernel: [ 443.182489] wlan0: recalibrating radio
Dec 9 12:50:39 kernel: [ 443.229739] wlan0: successfully recalibrated radio



If you you have some advice, I'd like to "hear". Any words for you is much for me to understand Ubuntu better.

[madsmaddad]

For your zydas card, what driver are you using??


----


For your unencrypted network, can you post
iwlist scan

Try to connect from the command line leaving out the mode Managed part.

took awhile, But I have it. XP works with not encryption so I have to keep booting back to post. I have tried 'unsetting' everything to get back to Unencrypted operation in Kubuntu, but it's not happy. Here's the gen:
peterm@peterm-Kdesktop:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:15:58:4B:C3:23
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:16 Base address:0xe400

eth1 Link encap:Ethernet HWaddr 00:14:7C:66:B7:97
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:462 (462.0 b)

eth1:avah Link encap:Ethernet HWaddr 00:14:7C:66:B7:97
inet addr:169.254.8.14 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:352 (352.0 b) TX bytes:352 (352.0 b)

peterm@peterm-Kdesktop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11b/g ESSID:off/any Nickname:"zd1211"
Mode:Managed Frequency:2.462 GHz Access Point: Invalid
Bit Rate=1 Mb/s
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

peterm@peterm-Kdesktop:~$

peterm@peterm-Kdesktop:~$
from dmesg:
[ 41.677158] zd1211rw 4-3:1.0: firmware version 4605
[ 41.719113] zd1211rw 4-3:1.0: zd1211 chip 6891:a727 v4721 high 00-14-7c RF295
9_RF pa0 g----
[ 41.721657] zd1211rw 4-3:1.0: eth1
[ 41.721682] usbcore: registered new interface driver zd1211rw
....
[ 86.446150] NET: Registered protocol family 10
[ 86.449854] lo: Disabled Privacy Extensions
[ 86.451412] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 86.451468] ADDRCONF(NETDEV_UP): eth1: link is not ready ??not noticed this before..


peterm@peterm-Kdesktop:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:18:6E:CA:89:2C
ESSID:"bmth_wireless"
Protocol:IEEE 802.11b
Mode:Master
Channel:11
Frequency:2.462 GHz (Channel 11)
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Quality=100/100 Signal level=94/100
Extra: Last beacon: 80ms ago


peterm@peterm-Kdesktop://etc/network$ cat interfaces
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0


iface eth0 inet static
address 192.168.1.12
netmask 255.255.255.0
gateway 192.168.0.1

auto eth1
iface eth1 inet dhcp


Thanks for any help. I'll keep playing to try and get it working 'open'. Would it help to uninstall wpa_supplicant, even though it is not configured?

Peter

[kevdog]

Im not sure what to make about this line:

[ 86.451468] ADDRCONF(NETDEV_UP): eth1: link is not ready ??not noticed this before..

Try connecting from the command line for eth1. The instructions are in my signature. Try just a regular unencrypted connection first.

[caricc]

Kevdog - you helped me out a while back on a wireless connection problem. I was hoping you could do teh same again. I am now setting up a Dell Latitude 600 with Ubuntu 7.10. Hard drive was empty do it's a fresh install. i have a listing of the following:
lshw -C network
route
ifconfig
iwlist scan.

posting list:
*-network:0
description: Ethernet interface
product: NetXtreme BCM5705M Gigabit Ethernet
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 01
serial: 00:0f:1f:c9:0f:c2
width: 64 bits
clock: 66MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=tg3 driverversion=3.77 firmware=5705-v3.16 ip=192.168.1.64 latency=32 mingnt=64 module=tg3 multicast=yes
*-network:1
description: Wireless interface
product: PRO/Wireless LAN 2100 3B Mini PCI Adapter
vendor: Intel Corporation
physical id: 3
bus info: pci@0000:02:03.0
logical name: eth1
version: 04
serial: 00:0c:f1:4e:fd:4e
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ipw2100 driverversion=git-1.2.2 firmware=712.0.3:3:00000001 latency=32 maxlatency=34 mingnt=2 module=ipw2100 multicast=yes wireless=unassociated

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 0 0 0 eth1
link-local * 255.255.0.0 U 1000 0 0 eth0
default home 0.0.0.0 UG 100 0 0 eth0
default * 0.0.0.0 U 1000 0 0 eth1

eth0 Link encap:Ethernet HWaddr 00:0F:1F:C9:0F:C2
inet addr:192.168.1.64 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20f:1fff:fec9:fc2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5262 errors:0 dropped:0 overruns:0 frame:0
TX packets:2419 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2822985 (2.6 MB) TX bytes:294129 (287.2 KB)
Interrupt:11

eth1 Link encap:Ethernet HWaddr 00:0C:F1:4E:FD:4E
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:3 errors:1 dropped:1 overruns:0 frame:0
TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:395 (395.0 b) TX bytes:4500 (4.3 KB)
Interrupt:5 Base address:0x6000 Memory:fafef000-fafeffff

eth1:avah Link encap:Ethernet HWaddr 00:0C:F1:4E:FD:4E
inet addr:169.254.8.83 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:5 Base address:0x6000 Memory:fafef000-fafeffff

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 olo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:1A:04:F6:68:91
ESSID:"CARICK"
Protocol:IEEE 802.11b
Mode:Master
Channel:11
Frequency:2.462 GHz (Channel 11)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Quality:93 Signal level:0 Noise level:0
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
Extra: Last beacon: 28ms ago
Cell 02 - Address: 00:19:E4:14:63:41
ESSID:"2WIRE569"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Frequency:2.462 GHz (Channel 11)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality:35 Signal level:0 Noise level:0
Extra: Last beacon: 24ms ago
verruns:0 carrier:0

I am trying to use WICD as the network manager. I am not happhappy with nm that came with ubuntu. thanks in advance.


collisions:0 txqueuelen:0
RX bytes:280 (280.0 b) TX bytes:280 (280.0 b)

[kevdog]

What commands have you typed at the command line to attempt to connect?

[caricc]

I have followed your instructions in the help file you have posted here. Still will not connect.

[caricc]

I have an update: I was able to use a static ip address and now able to get online. But I would still like to have dhcp working and not have to use a static ip. Any suggestions?
I am using wicd as my network manager.
DHCP would allow me to have this laptop to move on to other networks.

any help. thanks in advance.

[madsmaddad]

Im not sure what to make about this line:

[ 86.451468] ADDRCONF(NETDEV_UP): eth1: link is not ready ??not noticed this before..

Try connecting from the command line for eth1. The instructions are in my signature. Try just a regular unencrypted connection first.

Once I uninstalled wpa_supplicant, the unencrypted connection worked. This is coming over an unencrypted wireless link.

config details as so:

eth1 Link encap:Ethernet HWaddr 00:14:7C:66:B7:97
inet addr:192.168.1.5 Bcast:192.168.1.7 Mask:255.255.255.248
inet6 addr: fe80::214:7cff:fe66:b797/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7552 errors:184 dropped:455 overruns:0 frame:175
TX packets:7674 errors:51 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7780642 (7.4 MB) TX bytes:1334843 (1.2 MB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

peterm@peterm-Kdesktop:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:18:6E:CA:89:2C
ESSID:"bmth_wireless"
Protocol:IEEE 802.11b
Mode:Master
Channel:11
Frequency:2.462 GHz (Channel 11)
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Quality=100/100 Signal level=47/100
Extra: Last beacon: 80ms ago


Note I have restricted speed to 802.11b as it gives better range through walls than g, and with a 512Kb/s broadband I don't need faster Wireless. Also Channel 11 to be aways from others in neighborhood.

Almost tempted to re-install wpa_supplicant and the kwlan gui manager for it, and see if that works. I didn't use kwlan last time.

[aldo_m]

ok i need help kevdog . man after the last update it was somthing todo with the kernal. but after restarting i lost my wg511t card i only have one light flashing. soi use the command in the beging of this thread and i came up with somthing i didnt find with anyone withthe same problem.

root@Nsa:~# iwconfig
lo no wireless extensions.

eth1 no wireless extensions.

eth0 IEEE 802.11b/g ESSID:"denise" Nickname:"Broadcom 4306"
Mode:Managed Frequency=2.437 GHz Access Point: 00:18:39:42:6F:3F
Bit Rate=24 Mb/s Tx-Power=15 dBm
RTS thr:off Fragment thr:off
Encryption key:off
Link Quality=65/100 Signal level=-66 dBm Noise level=-73 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

root@Nsa:~# lshw -C network
*-network:0
description: Wireless interface
product: BCM4306 802.11b/g Wireless LAN Controller
vendor: Broadcom Corporation
physical id: 2
bus info: pci@0000:02:02.0
logical name: eth0
version: 03
serial: 00:90:4b:44:53:c7
width: 32 bits
clock: 33MHz
capabilities: bus_master ethernet physical wireless
configuration: broadcast=yes driver=bcm43xx driverversion=2.6.22-14-generic ip=192.168.1.109 latency=64 link=yes module=bcm43xx multicast=yes wireless=IEEE 802.11b/g
*-network:1
description: Ethernet interface
product: RTL-8139/8139C/8139C+
vendor: Realtek Semiconductor Co., Ltd.
physical id: 3
bus info: pci@0000:02:03.0
logical name: eth1
version: 10
serial: 00:02:3f:69:80:34
size: 10MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=8139too driverversion=0.9.28 duplex=half latency=128 link=no maxlatency=64 mingnt=32 module=8139too multicast=yes port=MII speed=10MB/s
*-network UNCLAIMED
description: Ethernet controller
product: AR5212/AR5213 Multiprotocol MAC/baseband processor
vendor: Atheros Communications, Inc.
physical id: 1
bus info: pci@0000:03:00.0
version: 01
width: 32 bits
clock: 33MHz
capabilities: pm cap_list
configuration: latency=0 maxlatency=28 mingnt=10

its showing my network card *-network UNCLAIMED. please helpme i need to finsh cracking this wep.
i will give you the biggest hug ever kev and lick your toe jam.:lolflag:

[PhrozenPhoenix]

I think Madsmaddad found a way to do this already, but for anyone getting the "No DHCP Offers" message try:

sudo iwconfig [interface] key open

I found that when looking up the parameters of iwconfig on google.. it led me to: http://gd4.tuwien.ac.at/.vhost/linuxcommand.org/man_pages/iwconfig8.html


This is only my second day as a linx user (running Xubunto wirelessly atm), so I dont know if that helps any.. but I'm thinking the reason so many people are getting that error message is because their WEP settings on their router dont have "shared keys" but "open keys," if that makes any sense.. hope this helps.

Oh, and thanks a lot for the tutorial Kevdog... i've been going through a lot of troubles installing Xubuntu (install cd not burning, updates not working, loose video card making my system freeze, etc.) but its nice to finally have a working wireless system to play around with!

[kevdog]

PhrozenPhoenix

Updated the thread instructions with your suggestion. I dont really use WEP a whole bunch. The iwconfig documentation gives a poor explanation of when to use or not use the open command. Hopefully people will try this command if they are receiving problems when trying to make a WEP connection

[Tombo5150]

Allrighty! First off, Kevdog, awesome tutorial man as you know it is greatly appreciated. First, I had problems with the Hex key (WEP encryption). After following your advice and reading the man iwconfig, I saw that they put the key in XXXX-XXXX-XXXX-XXXX and since my key is a ten character key i thought to put it in as XXXX-XXXX-XX and it worked! So now I know how to get the wireless to work.......however, is all of this just a temporary fix untill you reboot your computer? The problem, is that this is my parents computer and I just installed Gutsy only a few days ago on it. I'm showing them an alternative to windows which has been giving them problems. These steps would be easy for me and I would certainly not have a problem entering them everytime I needed wireless, but it would be much easier if it would just stay after I got the wireless to work. Is there someway of making this permanent?

[kevdog]

Again as stated in the tutorial, this method isnt really for everyday use, rather than troubleshooting or just testing to see if the wireless network card works. As far as everyday use, are you planning on using network manager?? Also is this with a laptop or a desktop you are working with -- what Im getting at here is there any situation with this computer that you might need network roaming? If you do not need roaming then within the /etc/network/interfaces file you would put (for WEP)

auto <inteface>
iface <interface> inet dhcp
wireless-essid <essid>
wireless-key <key>
wireless-mode Managed

Thats about it. You probably have to do a
sudo /etc/init.d/networking restart

This should (cross your fingers) bring the network connection up on boot.

[Tombo5150]

Bring the connection up in the network manager? Because it hasn't even been giving me an option for wireless. It's for my parents desktop, so it won't need to roam. I'll try what you told me then i'll get back to you. Thanks again!

[Kadou]

Hey, I've been having some trouble with connecting with this method. After I set up everything (hex WEP key included) I'm still getting that same error at the last command:



No DHCPOFFERS received.
No working leases in persistent database - sleeping.

I'm grateful that I can at least see what the problem is, but I still have no idea how to solve it. Help would be appreciated!

[kevdog]

I cant help you with this -- it could be a configuration issue, a reception issue, or something else. Try first with unencryption to verify that everything is setup properly (minus the WEP line).

[Tombo5150]

Again as stated in the tutorial, this method isnt really for everyday use, rather than troubleshooting or just testing to see if the wireless network card works. As far as everyday use, are you planning on using network manager?? Also is this with a laptop or a desktop you are working with -- what Im getting at here is there any situation with this computer that you might need network roaming? If you do not need roaming then within the /etc/network/interfaces file you would put (for WEP)

auto <inteface>
iface <interface> inet dhcp
wireless-essid <essid>
wireless-key <key>
wireless-mode Managed

Thats about it. You probably have to do a
sudo /etc/init.d/networking restart

This should (cross your fingers) bring the network connection up on boot.


I did this but it won't let me save the file. It says that the file is read only. I opened it in gedit, is there some way I should do this?

[rustybronco]

I did this but it won't let me save the file. It says that the file is read only. I opened it in gedit, is there some way I should do this?sudo gedit...

[madsmaddad]

from message 117.

Have re-installed wpa_supplicant and kwlan.

set my router to wpa2/TKIP.

Having worked through a bunch of configuration stuff, I am confused.

Do I edit /etc/network/interfaces with the WPA config stuff,

or

/etc/wpa_supplicant.conf?

And how do I know which wpa driver is appropriate for my wireless hardware? Is there a table anywhere?

Kwlan seems to pick up the profile if there isa wpa_supplicant.conf file, but will not allow me to edit the encryption parameters to set them up. Note I started kwlan from the terminal as 'sudo kwlan'.

Am I just confusing myself?

Thanks for any guidance (again).

[...Max...]

Trying on this thread in hopes it'll get noticed sooner. I won't copy the bulk of the previos message from http://ubuntuforums.org/showthread.php?p=4064688#post4064688

In short, what can I look for when dhclient simply fails to get any offers and quits? No other relevant error messages anywhere in the log. I've tested this with the driver that does work properly in dual booted XP so it's gotta be a problem somewhere in the wireless stack/config rather than in the driver/hardware/access point. Is there any way to enable verbose logging from the wireless stack (whatever it consists of)? Note that all iw* commands SEEM to work -- as in no error messages and iwlist/iwconfig reflect the changes. Except, the essid is never set to what I specified -- iwconfig always shows it as "off/any".

[kevdog]

Can you post an example?

[...Max...]

Could you be more specific? The lspci listing is in the linked post. What would help -- protocol from the terminal window? Log excerpts? There's precious little infornation in either :( Something else? I need some ideas in which direction to dig...

[hulleye]

To those having the "No DHCP Offers Received" problem. I was getting this message repeatedly no matter what I tried. I just randomly decided to experiment with the settings on my router and discovered that just switching from a pure 802.11g network to a mixed 802.11b/g network solved my issues instantly. Felt quite silly in that instant

Am using the Orinoco driver for my wireless card. Might be worth a try to play around with your router settings.

Btw KevDog, hidden SSID seems to work fine for me.

[kevdog]

Hidden ESSID is very sporadic, it works for some but not for others. Not sure why -- likely related to whatever driver you are using. Maybe someone should come up with a poll in a new thread to find what drivers work with hidden ESSID and what drivers do not? Could also by a router specific issue -- but I dont that!

[madsmaddad]

Still having problems, but making progress. And yes, I am using a hidden ESSID, WPA2 and TKIP on a 3COM USB stick.

Have configured wpa_supplicant.conf for my setup by thinking about comments earlier in this thread.

file wpa_supplicant.conf:

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="bmth_wireless"
psk=13953c483e5d42339779f01317e83931b12e530f6ee541 6144da6185a89b499e
key_mgmt=WPA-PSK
proto=RSN
pairwise=TKIP
}

When I run through the list of commands this is what I get:
peterm@peterm-Kdesktop:~$ sudo ifconfig eth1 down
[sudo] password for peterm:
peterm@peterm-Kdesktop:~$ sudo dhclient -r eth1
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:14:7c:66:b7:97
Sending on LPF/eth1/00:14:7c:66:b7:97
Sending on Socket/fallback
peterm@peterm-Kdesktop:~$ sudo wpa_supplicant -w -Dwext -ieth1 -c/etc/wpa_supplicant.conf
Trying to associate with 00:18:6e:ca:89:2c (SSID='bmth_wireless' freq=2462 MHz)
ioctl[SIOCSIWFREQ]: Operation not permitted
Association request to the driver failed
Associated with 00:18:6e:ca:89:2c
WPA: Key negotiation completed with 00:18:6e:ca:89:2c [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:18:6e:ca:89:2c completed (auth) [id=0 id _str=]

Hung here so CTRL-C

CTRL-EVENT-TERMINATING - signal 2 received

The MAC address 3 lines back is the router, So that's what I mean by progress.

Any Ideas why it hangs at this point? Initially the association attempt fails, but then it happens.

When I put the Group parameter in the .conf file, the system did not like that.

I am wondering if for some reason it is having trouble at this point getting an IP address, as I am using DHCP. :confused:

[kevdog]

broadcast the essid.

[Mboo]

I was able to connect to my wirless using the instruciton below, but how do I get those setting to hold? After a restart, I have to do it all over again.

sudo ifconfig <interface> down
sudo dhclient -r <interface>
sudo ifconfig <interface> up
sudo iwconfig <interface> essid "ESSID_IN_QUOTES"
sudo iwconfig <interface> key HEX_KEY <<<-------- If using ASCII Equivalent, this is s:ASCII_KEY (please make note of the prefix s:)
****Additional Comand that may be needed -- sudo iwconfig <interface> key open <<<----See note below
sudo iwconfig <interface> mode Managed
sudo dhclient <interface>

[madsmaddad]

broadcast the essid.

When I checked, I was.

So, I don't know for how long I have been, but I am broadcasting. I am trying to keep reasonable documentation on what am doing, but I missed that.

Looks like you are trying to help multiple people on the same thread - Gets confusing? But I am also interested in the next guys solution.

Peter M.:confused:

[kevdog]

You just put the commands in a shell script -- make the file executable, and then add the file to your list of startup programs at boot.

[mabovo]

Hello ! May I ask permission to enter in this thread ?

I have a MacBook 2,1 with artheros AR5418 wireless card.
With today updates I finally got this wireless card working but only with Security disable.

My router is a DI-624 and is possible to configure security from WEP-WPA-WPA2-WPA-AUTO

The problem is : I am newbee in wireless networking and don't know how to configure security in my home network. Can You help me ?

Thanks.

[Mboo]

You just put the commands in a shell script -- make the file executable, and then add the file to your list of startup programs at boot.

I'm still pretty new to Linux. I don't know how to make a shell script, make is executable or make it load on startup.

[mabovo]

I have this result from:

mabovo@macbook:~$ sudo wpa_supplicant -w -D wext -i ath0 -c/ etc/wpa_supplicant.conf -dd
Initializing interface 'ath0' conf '/' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/' -> '/'
Reading configuration file '/'
Initializing interface (2) 'ath0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=22 WE(source)=18 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1b:63:05:81:11
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Added interface ath0
RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
Wireless event: cmd=0x8b06 len=12
Ignore event for foreign ifindex 3
RTM_NEWLINK: operstate=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 231 bytes of scan results (1 BSSes)
Scan results: 1
No suitable AP found.
Setting scan request: 0 sec 0 usec
No enabled networks - do not scan
State: SCANNING -> INACTIVE

P.S. Have no idea what it means. :-)

[mabovo]

Second try:


mabovo@macbook:~$ sudo su
root@macbook:/home/mabovo# ifconfig ath0 down
root@macbook:/home/mabovo# ifconfig wifi0 down
root@macbook:/home/mabovo# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wifi0 no wireless extensions.

ath0 IEEE 802.11a ESSID:"" Nickname:""
Mode:Managed Channel:0 Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:11 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=0/70 Signal level=-96 dBm Noise level=-96 dBm
Rx invalid nwid:2 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

root@macbook:/home/mabovo# ifconfig ath0 up
root@macbook:/home/mabovo# modprobe wlan_scan_sta
root@macbook:/home/mabovo# wlanconfig ath0 list scan
SSID BSSID CHAN RATE S:N INT CAPS
bovo 00:15:e9:79:52:9e 11 54M 26:0 100 EPSs WPA
root@macbook:/home/mabovo# iwlist ath0 scan
ath0 Scan completed :
Cell 01 - Address: 00:15:E9:79:52:9E
ESSID:"bovo"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=25/70 Signal level=-70 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

root@macbook:/home/mabovo# iwlist ath0 key tchecoslovaquia148
iwlist: command `keys' needs fewer arguments (max 0)
root@macbook:/home/mabovo# iwlist ath0 key <tchecoslovaquia148>
bash: erro de sintaxe próximo a símbolo inesperado `newline'
root@macbook:/home/mabovo# ifconfig ath0 down
root@macbook:/home/mabovo# dhclient -r ath0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:1b:63:05:81:11
Sending on LPF/ath0/00:1b:63:05:81:11
Sending on Socket/fallback
root@macbook:/home/mabovo# ifconfig ath0 up
root@macbook:/home/mabovo# iwconfig ath0 essid "bovo"
root@macbook:/home/mabovo# iwconfig ath0 key open "tchecoslovaquia148"
Error for wireless request "Set Encode" (8B2A) :
SET failed on device ath0 ; Invalid argument.
root@macbook:/home/mabovo# iwconfig ath0 key open <tchecoslovaquia148>
bash: erro de sintaxe próximo a símbolo inesperado `newline'
root@macbook:/home/mabovo# iwconfig ath0 key open tchecoslovaquia148
Error for wireless request "Set Encode" (8B2A) :
SET failed on device ath0 ; Invalid argument.
root@macbook:/home/mabovo# iwconfig ath0 key tchecoslovaquia148
Error for wireless request "Set Encode" (8B2A) :
invalid argument "tchecoslovaquia148".
root@macbook:/home/mabovo# iwconfig ath0 key "tchecoslovaquia148"
Error for wireless request "Set Encode" (8B2A) :
invalid argument "tchecoslovaquia148".
root@macbook:/home/mabovo# iwconfig ath0 key ASCII_KEY "tchecoslovaquia148"
Error for wireless request "Set Encode" (8B2A) :
invalid argument "ASCII_KEY".
root@macbook:/home/mabovo# iwconfig ath0 key s:ASCII_KEY "tchecoslovaquia148"
iwconfig: unknown command "tchecoslovaquia148"
root@macbook:/home/mabovo# iwconfig ath0 key s:ASCII_KEY tchecoslovaquia148
iwconfig: unknown command "tchecoslovaquia148"
root@macbook:/home/mabovo# iwconfig ath0 key s:ASCII_KEY <tchecoslovaquia148>
bash: erro de sintaxe próximo a símbolo inesperado `newline'
root@macbook:/home/mabovo#

[mabovo]

From Madwifi HowTo I got this:



mabovo@macbook:~$ iwconfig ath0 ap any
Error for wireless request "Set AP Address" (8B14) :
SET failed on device ath0 ; Operation not permitted.
mabovo@macbook:~$ iwconfig ath0 ap auto
Error for wireless request "Set AP Address" (8B14) :
SET failed on device ath0 ; Operation not permitted.
mabovo@macbook:~$ sudo iwconfig ath0 ap auto
[sudo] password for mabovo:
mabovo@macbook:~$ sudo dhclient ath0
There is already a pid file /var/run/dhclient.pid with pid 0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:1b:63:05:81:11
Sending on LPF/ath0/00:1b:63:05:81:11
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 11
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
mabovo@macbook:~$ sudo dhcpcd ath0
sudo: dhcpcd: command not found
mabovo@macbook:~$ ifconfig ath0 192.168.0.187 netmask 255.255.255.0 up
SIOCSIFADDR: Permissão negada
SIOCSIFFLAGS: Permissão negada
SIOCSIFNETMASK: Permissão negada
SIOCSIFFLAGS: Permissão negada
mabovo@macbook:~$ sudo ifconfig ath0 192.168.0.187 netmask 255.255.255.0 up
mabovo@macbook:~$ ping bbc.co.uk
PING bbc.co.uk (212.58.224.131) 56(84) bytes of data.
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=1 ttl=118 time=250 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=2 ttl=118 time=223 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=3 ttl=118 time=196 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=4 ttl=118 time=215 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=5 ttl=118 time=209 ms
64 bytes from rdirwww-vip.thdo.bbc.co.uk (212.58.224.131): icmp_seq=6 ttl=118 time=225 ms

--- bbc.co.uk ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5010ms
rtt min/avg/max/mdev = 196.348/220.030/250.027/16.463 ms
mabovo@macbook:~$

[kevdog]

Those commands need sudo in front of them

sudo iwconfig etc.

[peevee07]

I have found this "how to" most helpful in the past. I have just replaced my wireless router and now I find that the command line statements don't get me through to connection. I'm using 7.04 and I end up with No DHCPOFFERS. I can't get beyond that. Kwifimanager and wifi assistant don't help. So I'm looking for help.

[madsmaddad]

On mine, I have just run through the commands and the output of wpa_suuplicant with the -dd (extensive debug) parameter gives the following as the last few lines:

WPA: Key negotiation completed with 00:18:6e:ca:89:2c [PTK=TKIP GTK=TKIP]
Cancelling authentication timeout
State: GROUP_HANDSHAKE -> COMPLETED
CTRL-EVENT-CONNECTED - Connection to 00:18:6e:ca:89:2c completed (auth) [id=0 id_str=]
wpa_driver_wext_set_operstate: operstate 0->1 (UP)
WEXT: Operstate: linkmode=-1, operstate=6
EAPOL: External notification - portValid=1
EAPOL: External notification - EAP success=1
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state SUCCESS
EAP: EAP entering state DISABLED
EAPOL: SUPP_PAE entering state AUTHENTICATED
EAPOL: SUPP_BE entering state IDLE
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
EAPOL: startWhen --> 0

At this point nothing happens. It doesn't complete.

Any idea what EAPOL is looking for?

Thanks for any guidance.
:confused:

[kevdog]

When you run it with the -dd command and it seems to stop -- pop open another terminal window, and then continue typing the next series of commands. See if that works for you -- again this is only for testing purposes.

[MyrddinWyllt]

Hello, I am trying to get my wireless working on a computer running ubuntu 7.10 server. I have a Linksys WMP54GS wireless card, which uses a broadcom 4306 chipset. I opened a thread about it on the beginner forum, and they recommended that I ask here.

The original thread is here:
http://ubuntuforums.org/showthread.php?t=662363

Hopefully you guys can help, I'm about out of ideas..

[kevdog]

MyrddinWyllt

See following thread:

http://ubuntuforums.org/showthread.php?t=475963

[MyrddinWyllt]

MyrddinWyllt

See following thread:

http://ubuntuforums.org/showthread.php?t=475963

Another vote for NDISWrapper, then, I guess my current approach is totally wrong :)

Thanks!

[Mike1949]

Thanks for the post. I was able to get my wifi working, only now I don't know how to make the fix permanent. When I reboot, I have to run the commands again. I could always create a script and put it in rc.local, but I expect there's a better way. What do you recommend?

[kevdog]

Either script or wicd.

[Maricaibo]

I cannot get network settings to hold after reboot. I put the following script in my /etc/init.d folder:

sudo ifconfig ra0 down
sudo dhclient -r ra0
sudo iwconfig ra0 essid 2WIRE596
sudo iwconfig ra0 key 1234567890
sudo iwconfig ra0 mode Managed
sudo ifconfig ra0 up
sudo dhclient ra0

But I must still run these commands manuallt to get my wireless working.

The script is owned by root and I CHMOD +x on the script.

What in blazes is happening? the Wired connection camoes back up at reboot just fine...:confused:

[kevdog]

Does the script actually run?? Can you check the boot log or dmesg (system log) to see if the script ran and is it giving any errors? Is it supposed to go in rc.local instead? Also disable the wired connection at boot adding to your script

sudo ifconfig eth0 down

[Maricaibo]

SOLVED!

I'd read an earlier post on putting a startup shell script in the init.d folder.

When the commands are in the etc/rc.local file (set as an executable) viola!

THANKS!!!!!!!

Getting wireless working is a...challenge.

[kevdog]

Can you post your /etc/rc.local file?

I shall add this to the guide!

[kilometers]

kevdog,

Thanks for this thread it is of much help. I am setting up my roommate's laptop with ubuntu 7.10 an trying to get his wireless card working. It is a D-Link DWL-650 RevP with a Prosm 3.0 chipset. Using Synaptic I installed some drivers that recognize the card.

The iwconfig displays two wireless devices; wifi0 and wlan0, but ifconfig only shows the ethernet and lo.

I started with your manual configuration and all went smoothly until the essid command

'sudo iwconfig wlan0 essid "mynetwork"
Error for wireless request "Set ESSID" (8B1A):
SET failed on device wlan0 ; Invalid argument.'

Any ideas of what to do? I have a hunch that I need to edit some network configuration files.

thnx again,

kilometers

[kevdog]

Can you post the results of

lshw -C network
iwlist scan
ifconfig

Thanks

[Jay Jay]

Kevdog,

Just wanted to say thanks, your guide has worked brilliantly for me. Before I read your post I had to boot into Windows at times because Network Manager & Wireless Assistant could see the router I wanted to use, but could not connect to it. This would annoy me to no end... The same problem often occurred under Kubuntu 7.04 too and my workaround for that was to save my preferred ESSID within the interfaces file.

On a side note, does this mean there is a bug in the GUI connectivity software seeing as there are no issues when going through the Command Line?

Thanks again,

Jay

[kevdog]

Jay Jay

I dont know why the GUI managers do not work all the time. The closest one Ive found to emulate the command line is WICD. I dont know how NM works.

Do you have a bigger picture of your avatar?? I cant make it out!

[Jay Jay]

lol how's this?

http://starwars.wikia.com/wiki/Image:Cody%3B_Order_66.jpg

:)

[kevdog]

Ahhhh, that's a lot better!

[madsmaddad]

Me back again: Trying to get this 3CRUSB10075 working with WPA2.

Following on from what you have done so far with me, and from some thing I found on a fedoa forum about getting it working: I changed my wpa_supplicant.conf file to read:

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="bmth_wireless"
psk=13953c483e5d42339779f01317e83931b12e530f6ee541 6144da6185a89b499e
key_mgmt=WPA-PSK
proto= WPA RSN
pairwise=TKIP CCMP
}

and ran through the list of commands. As you suggested when the first terminal session seemed to hang after processing the wpa_supplicant command,I opened another window and did the rest of the commands, and here I am updating this online from Kubuntu 7.10. It seemed to need the WPA and CCMP parameters adding.

Now I need to fix it so it works every time:)

Peter M.

[kevdog]

Can you post the exact line you enter with the wpa_supplicant command??

I see the wpa_supplicant.conf file, I just want you to post the command

[kilometers]

kevdog,

sorry for the long reply time. here is the output for the commands you requested me to run.

lshw -C network
*-network
description: DWL-650 Wireless PC Card RevP
product: ISL37101P-10
vendor: D-Link
physical id: 0
version: A3
slot: Socket 0
resources: irq:3
*-network
description: Ethernet interface
product: 82801DB PRO/100 VE (MOB) Ethernet Controller
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:02:08.0
logical name: eth0
version: 83
serial: 00:e0:b8:57:79:a1
size: 10MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.17-k4-NAPI duplex=half firmware=N/A latency=66 link=no maxlatency=56 mingnt=8 module=e100 multicast=yes port=MII speed=10MB/s
*-network DISABLED
description: Wireless interface
physical id: 1
logical name: wlan0
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=hostap driverversion=0.4.4-kernel firmware=0.0.0 multicast=yes wireless=IEEE 802.11-DS

iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wifi0 Interface doesn't support scanning : Network is down

wlan0 Interface doesn't support scanning : Network is down

ifconfig
eth0 Link encap:Ethernet HWaddr 00:E0:B8:57:79:A1
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Thanks for the help.

-kilometers

[madsmaddad]

The exact commands were:

sudo ifconfig eth1 down
sudo dhclient -r eth1
sudo wpa_supplicant -w -Dwext -ieth1 -c/etc/wpa_supplicant.conf

then to new terminal session:

sudo ifconfig eth1 up
sudo iwconfig eth1 mode managed
sudo dhclient eth1

I gave you the wpa_supplicant.conf file in a previous post.

I am now trying to figure out what to put in the Interfaces file to get it to work automatically on boot.

Peter M.

[kevdog]

so what happens if you bring the interface up

sudo ifconfig wlan0 up

and then do a
iwlist scan

[kilometers]

kevdog,

sudo ifconfig wlan0 up

followed by

iwlist scan

gave the same out put as above

a dmesg command gave the following output:
[ 9121.948000] pccard: PCMCIA card inserted into slot 0
[ 9121.948000] pcmcia: registering new device pcmcia0.0
[ 9121.948000] hostap_cs: setting Vcc=33 (constant)
[ 9121.948000] Checking CFTABLE_ENTRY 0x01 (default 0x01)
[ 9121.948000] IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
[ 9121.948000] io->flags = 0x0047, io.base=0x0000, len=128
[ 9121.948000] hostap_cs: Registered netdevice wifi0
[ 9121.988000] hostap_cs: index 0x01: , irq 3, io 0x3080-0x30ff
[ 9122.488000] hostap_cs: assuming no Primary image in flash - card initialization not completed
[ 9122.488000] wifi0: test Genesis mode with HCR 0x1f
[ 9122.488000] prism2_pccard_cor_sreset: original COR 41
[ 9122.492000] prism2_pccard_genesis_sreset: original COR 41
[ 9122.520000] Readback test failed, HCR 0x1f write 00 e1 a1 ff read 00 ce a1 ce
[ 9122.520000] wifi0: test Genesis mode with HCR 0x0f
[ 9122.520000] prism2_pccard_cor_sreset: original COR 41
[ 9122.524000] prism2_pccard_genesis_sreset: original COR 41
[ 9122.556000] Readback test succeeded, HCR 0x0f
[ 9122.556000] prism2_pccard_genesis_sreset: original COR 41
[ 9122.584000] wifi0: registered netdevice wlan0
[ 9122.724000] wlan0: cannot get RID fdc6 (len=12) - no PRI f/w
[ 9122.724000] wlan0: could not set interface UP - no PRI f/w

does that shed any light on the problem?

-kilometers

[kevdog]

madsmaddad

Substitute the following command

sudo wpa_supplicant -Bw -Dwext -ieth1 -c/etc/wpa_supplicant.conf

Notice the B flag starts the wpa_supplicant daemon in the background. You can confirm this if you do a

sudo ps -ef | grep wpa

Does the process show up as running?

You dont put this in the /etc/network/interfaces file to get it to load at boot, you add it to

/etc/rc.local

See about 10-20 post back -- this was addressed and solved by another user!

[kevdog]

kilo

I see in your dmesg log:

[ 9122.724000] wlan0: cannot get RID fdc6 (len=12) - no PRI f/w
[ 9122.724000] wlan0: could not set interface UP - no PRI f/w

I have no idea what that means. I dont have really any experience with the hostap driver either. I think its more than likely a bad or incorrect driver you have. You may want to search the forums for your particular card or use the term hostap. Sometimes those cards are difficult to configure correctly -- meaning the driver setup is sometimes a pain.

[Maricaibo]

Here's how I got my wireless card to startup at boot time.

After ensuring your wireless card is working (device is up and can get an IP address from your router), add the following text to your /etc/rc.local file using your equipment names inside the brackets. I used this command in a Terminal (shell) window:

sudo gedit /etc/rc.local

This opens up the file in the gedit utility and allows you to make changes and save the file

ifconfig <wired network connection device> down
ifconfig <wireless network connection device> down
dhclient -r <wireless device>
iwconfig <wireless device> essid <router name>
iwconfig <wireless device> key <WEP key in ascii>
iwconfig <wireless device> mode Managed
ifconfig <wireless device> up
dhclient <wireless device>

Be sure this text goes into the /etc/rc.local file BEFORE the line reading "exit 0".

Save and close the /etc/rc.local file.

Open up a Terminal window (the shell) and type in:

sudo CHMOD +x /etc/rc.local

This command turns the rc.local file into an executable that will run at startup. Here's what my /etc/rc.local file now looks like. Your device names will be different:

#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

ifconfig eth0 down
ifconfig ra0 down
dhclient -r ra0
iwconfig ra0 essid 2WIRE596
iwconfig ra0 key 1234567890
iwconfig ra0 mode Managed
ifconfig ra0 up
dhclient ra0

exit 0


NOTE: The first line in the rc.local file downs your wired connection, so if for some reason you need the wired connection back just open up a Terminal window (shell) and type:

sudo <wired connection> up
sudo dhclient <wired connection>

NOTE! kevdog correctly pointed out the use of 'sudo' in the rc.local file was redundant, as the file is owned and executed by ROOT at bootup anyway- thanks!
Many thanks to all here who posted helpful tips, hints and suggestions. I could NOT have done this otherwise. Good luck!

[kilometers]

Thanks for the help kevdog. I know this thread will be useful when I get the drivers configured correctly.

[Kenniej]

Thank you SO MUCH for this tutorial , i've been working all day to get a EDIMAX old usb adapter to get to work.

Kudo's to you !!

Grtz,
Kenniej

[dub_u]

Thanks for the tip -- I thought special characters were out of the question -- I guess they are not!

First, thanks for this "Howto", I finally managed to get my wireless connection to work with WEP on my Ubuntu machine (worked on two windows though...and worked non-secure on Ubuntu).
Just wanted to add that my key includes only one special character (a "&" at the end) and that works as long as I write
sudo ifconfig wlan0 key s:"ABCDEFG1234&" but not s:ABCDEFG1234&

[Pointswest]

I would like to thank you so much for your tutorials on wireless networking. I have been trying to get this to work for months. Yours is the only instructions that seem to work. I have installed ndiswrapper from my 7.10 cd and followed your instructions for installation. I can see that ndis 1.45 is installed from the lshw -C network command. By using the network manager and manual config I can see my signal and if roaming is unchecked the bar graph comes up with a signal strength, but I am unable to connect to the internet.

My router is using wep encryption. I have tried to use the commands in this post to add the WEP but when I type "ifconfig wlan0 down" I receive an error about permission denied. Can you tell me where I have gone wrong? Have also tried same command using "sudo iconfig wlan0 down" with no results.

Thanks again for the useful tips. this issue of wireless connection is getting so many posts it's becoming hard to sort it all out.

Pointswest

[kevdog]

Good to see another guy from Colorado using Ubuntu

You need to preface the commands with sudo
You also need to make sure your wireless interface is referred to as wlan0 rather than eth1 or some other name. The best way to tell this in most cases is by looking at the results of lshw -C network, however in some cases this could be misleading (for example when using the madwifi drivers).

[Mor Hedroom]

Hi, kevdog -

Thanks so much for the tie and patience you put into your work in this forum! I've got an interesting/irritating problem, and I'm wondering if you have any suggestions.

First off, I've been successfully using my current setup, with the ability to switch freely between wired/wireless. Some time in the last couple days, I've lost the ability to connect wirelessly to my router. To my knowledge, the only changes made to my system were Ubuntu updates. The system is always under my direct supervision, and is not likely the victim of tampering.

My setup:
Computer: HP ze4420us
OS: Ubuntu (Gutsy) 7.10
Wireless: Airlink101 Cardbus - Ralink chipset
Driver: rt61pci
Interface name: wmaster0

It turns out that the reason I turned to your guide is I can see access points, including my own, but I cannot connect to them. Thinking it might be something going on with Network Manager, I tried the steps you outline in the beginning of this thread:
from lshw -C network:

*-network
description: Ethernet interface
product: DP83815 (MacPhyter) Ethernet Controller
vendor: National Semiconductor Corporation
physical id: 12
bus info: pci@0000:00:12.0
logical name: eth0
version: 00
serial: 00:0b:cd:a4:e2:f4
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=natsemi driverversion=2.1 ip=192.168.2.3 latency=90 maxlatency=52 mingnt=11 module=natsemi multicast=yes
*-network
description: Wireless interface
product: RT2600 802.11 MIMO
vendor: RaLink
physical id: 0
bus info: pci@0000:02:00.0
logical name: wmaster0
version: 00
serial: 00:14:a5:87:69:86
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=rt61pci latency=64 module=rt61pci multicast=yes wireless=IEEE 802.11g


I think this shows that my driver is actually installed, and the wireless card is in fact detected. The interface name is wmaster0 and the driver is rt61pci.

I then proceed with your instructions for WEP connections:


sudo ifconfig wmaster0 down


where I am asked for my sudo password, and I give it, and am returned to the prompt. Assumably, the command has been executed.

Then:

sudo dhclient -r wmaster0
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wmaster0/
Sending on LPF/wmaster0/
Sending on Socket/fallback


Strange, but I thought, "OK, I'll go ahead."


sudo ifconfig wmaster0 up
SIOCSIFFLAGS: Operation not supported

After which point I'm not sure whether it makes sense to proceed, but I try:


sudo iwconfig wmaster0 essid "BioBoy"
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device wmaster0 ; Operation not supported.

While I'm certainly new at Ubuntu, I'm pretty certain that continuing with your supplied commands will not produce meaningful results at this point. Do you have any suggestions as to how I may proceed to get my wireless back?

Thanks in advance.
-Mor Hedroom

[Pointswest]

I am still stuck with this command "ifconfig wlan 0 down". If I type the command as shown it says permission denied. If I add sudo the computer just blinks and goes back to the desktop prompt line. I didn't know if the brackets around wlan0 were part of the command or not. Tried both ways, neither worked.

Using the lshw -C network command, it shows my adapter on wlan0. I noticed using the dmesg command that one line in the scan said "Failure registering capabilities with primary security module". Also the ndiswrapper -l command shows "network disabled". The command d gksu gedit /etc/network/interfaces only shows: auto lo and iface lo net, no menion of wlan0. I have included a screenshot with the results of some of these commands for reference.

Any help with this is appreciated, I have been trying this for a long time without success. Last night was the first time I got the adapter to even turn on. Thanks

Pointswest

[kevdog]

Mor

can you post ifconfig?

[kevdog]

points


Howcome you have two entries for ndiswrapper? this cant be right

[Pointswest]

kevdog

I have been trying for many months to get this wireless working and have read many posts and typed lots of commands trying to get this to work. I wouldn't be suprised if I somehow I got this on the machine twice. At one point last week I managed to get a ndiswrapper 1.49 to the desktop but didn't know to use the commands to install it from there. I finally gave up trying to install this and followed your instructions to install ndis. from the 7.10CD. A few of the commands in your tutorial gave me messages that said already installed so I just went to the next step. The version I thought I installed with the CD was 1.45 and is the version shown in the wireless interface section. The version 1.49 was not installed unless it happened by accident because it was on the desktop.

One thing I noticed with the ifconfig command was that I not only have a wlan0 but a wlano.ava. No clue about this. I am just trying to teach myself to use Linux so all I can do at this point is copy commands from the forum, not knowing why or how to use them. I thought I was so close last night when the bar graph showed up after clicking the monitor icon but then I was not able to connect to any web sites.

I thought this might be because I didn't use the command lines to set the WEP. I only used the network manager to set the hex key. As you can tell I am really new at this and don't know if I can even explain the problems correctly.

Thanks

Pointswest

[kevdog]

For one, just try reloading the ndiswrapper driver:

sudo modprobe -r ndiswrapper
sudo rm -R /etc/ndiswrapper/*

Reload the driver into ndiswrapper (I dont know where the driver is so you are going to have to change to the directory where the driver is located:

sudo ndiswrapper -i <driver.inf file>
sudo modprobe ndiswrapper

Check your work with:

ndiswrapper -l
dmesg | more

To see if the driver is correct

[Pointswest]

Kevdog

I have run the commands "sudo modprobe -r ndiswrapper" and" sudo rm -R/etc/ndiswrapper/*. I dont think anything has happened from these commands. I have included screenshots from these commands.

The ndiswrapper -l shows my driver rtl8187b (Airlink 101 w/realtek 8187b chipset) as loaded with ndiswrapper 1.45 which was on the 7.10CD.

Just a new note to add to this. I followed your instructions for setting wep and they worked this time. Now I can connect wirelessly. I am thrilled about this. Although I set my hex key with the command line, when I surf, a window tells me I am using an unencrypted connection. Have I missed something here? I cant thank you enough for your patience with me, I was beginning to think you were the only one in North America using Ubuntu wirelessly.

Pointswest

[kevdog]

Your screenshot tells me nothing other than you are using ndiswrapper. What screen tells you that you are using an unencrypted connection? When connecting via command line, there shouldnt be a popup, gui, or other desktop method like an icon that is going to tell you anything (that is definitely a negative with using the command line since there isnt a good feedback system).

Sometimes
iwlist scan will show you the encryption type.

Are you trying to use network manager or a GUI?

[Pointswest]

Kevdog

As the old song goes "The Thrill is Gone". After connecting last night for a short while,when the computer shut down it would not reconnect on reboot.

When it started working I had just finished running the commands for the WEP encriptions. I also used the monitor icon on the toolbar to set my hex key as well as going to network manager and unchecking roaming, entering my ESSID and hex key, and setting configuration to dhcp, then rechecking enable roaming mode.

I think the message screens showed up when going from one ebay site to another. I dont see how my computer could connect through my router if it was not encr ypted the same as the router . iwlist scan shows my ESSID "pointswest. also says the encryption key is on.

After loosing the connection I tried modifing the network interface files. The only entries were: auto lo and iface lo inet loopback. I added auto eth0,iface eth0 inet dhcp.auto wlan0, and iface wlan0 inet dhcp to the list. I haven't modified the etc/iftab file as shown on the tutorial because my interface is wlan0.

Today when I look at ifconfig there is no wlan0 listed, yesterday the same command showed wlan0 and wlan0.ava
Thanks again

Pointswest

[kevdog]

I dont use network manager -- well I do on one computer -- but the whole purpose of this guide was not to use network manager b/c its oftentimes just plain buggy. If you can see your network with iwlist, then the driver is likely set up appropriately.

You need to complete your connection by using the commands on the command line as stated on page 1 of the tutorial -- forget network manager or any gui for now. And if things are not working initially, turn off WEP temporarily. Boil it down to the simplest common denominator, and then increase complexity with encryption.

[madsmaddad]

Kevdog, Thanks for all your help.

As You know, Gutsy picked up this device on install. It uses the ZD1211 chipset.

I now have it working with WPA2, and ESSID Broadcast. The rc.local file and the wpa_supplicant.conf file are listed here:

/etc$ cat rc.local

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

sudo ifconfig eth1 down
sudo dhclient -r eth1
sudo wpa_supplicant -Bw -Dwext -ieth1 -c/etc/wpa_supplicant.conf
sudo ifconfig eth1 up
sudo iwconfig eth1 mode managed
sudo dhclient eth1

exit 0

/etc$ cat wpa_supplicant.conf

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="bmth_wireless"
psk=13953c483e5d42339779f01317e83931b12e530f6ee541 6144da6185a89b499e
key_mgmt=WPA-PSK
proto= WPA RSN
pairwise=TKIP CCMP
}

As noted on another users comments, I am using an 8 character encryption key.

I did try turning off ESSID Broadcast on my router, but then couldn't connect.. There is a parameter mentioned in the How-to by Weiman01 (thread 318539) to set this capability.

Not sure if I needed to put all the 'sudo's in the rc.local file, but did it anyway.

Overall, though we have to admit that this is a workaround. I would still like to see a solution as per message 126 in this thread and the weiman01 thread where the parameters are placed in the Interfaces file.

One thing that I have not determined is where the GUI configuration applications look/store the data.

Thanks again.

[kevdog]

A lot of chipsets within linux can not or have problems connecting to access points with hidden essids. This is a known problem and unfortunately I cant do anything about it.

As far as the settings in the /etc/network/interfaces file, that is for network manager and other programs and have nothing to do with this method. This method is a simpler alternative. Although definitely not as sexy, this method seems to default the ultimate fallback method. I would suggest making another post asking for help with network manager or settings within the interfaces file. You are not the only one to have problem with the other approach.


Yes the sudo statements within the rc.local file are redundant -- you dont need the sudo statement.

[yknivag]

Firstly, kevdog, thank you for such an excellent guide. I've now got my wireless working perfectly at home.

However, using the access point at work is a different story. there are a couple of differences. My home WIFI is WPA protected with a PSK and TKIP encryption and uses static IPs. The one at work is WEP and supports DHCP. I know that the work one is functioning and that DHCP is working as my colleagues can connect OK from their ******* machines.

Here is what I tried (following the OP as best I could) and the results.

ifconfig

gavin@knuckle:/etc/init.d$ sudo ifconfig
ath0 Link encap:Ethernet HWaddr 00:11:0A:81:19:46
inet6 addr: fe80::211:aff:fe81:1946/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:1028 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:164590 (160.7 KB)

ath0:avah Link encap:Ethernet HWaddr 00:11:0A:81:19:46
inet addr:169.254.3.*** Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0 Link encap:Ethernet HWaddr 00:08:02:E6:9D:02
inet addr:10.0.0.20 Bcast:10.255.255.255 Mask:255.0.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:247 errors:0 dropped:0 overruns:0 frame:0
TX packets:247 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:27578 (26.9 KB) TX bytes:27578 (26.9 KB)

wifi0 Link encap:UNSPEC HWaddr 00-11-0A-81-19-46-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:60496 errors:0 dropped:0 overruns:0 frame:18237
TX packets:1715 errors:1 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:5454899 (5.2 MB) TX bytes:225734 (220.4 KB)
Interrupt:11
iwconfig

gavin@knuckle:/etc/init.d$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wifi0 no wireless extensions.

ath0 IEEE 802.11g ESSID:"Livebox-****" Nickname:""
Mode:Managed Frequency:2.422 GHz Access Point: 00:14:A4:7D:**:**
Bit Rate:36 Mb/s Tx-Power:14 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=53/70 Signal level=-45 dBm Noise level=-98 dBm
Rx invalid nwid:2731 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

irda0 no wireless extensions.
iwlist scan

gavin@knuckle:/etc/init.d$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wifi0 Interface doesn't support scanning.

ath0 Scan completed :
Cell 02 - Address: 00:14:A4:7D:**:**
ESSID:"Livebox-****"
Mode:Master
Frequency:2.422 GHz (Channel 3)
Quality=52/70 Signal level=-43 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100

irda0 Interface doesn't support scanning.
lshw -C network

gavin@knuckle:/etc/init.d$ sudo lshw -C network
*-network:0
description: Wireless interface
product: AR5212/AR5213 Multiprotocol MAC/baseband processor
vendor: Atheros Communications, Inc.
physical id: 4
bus info: pci@0000:02:04.0
logical name: wifi0
version: 01
serial: 00:11:0a:81:19:46
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=ath_pci driverversion=0.9.4.5 (0.9.3.2) latency=168 maxlatency=28 mingnt=10 module=ath_pci multicast=yes wireless=IEEE 802.11g
*-network:1 DISABLED
description: Ethernet interface
product: NetXtreme BCM5705M_2 Gigabit Ethernet
vendor: Broadcom Corporation
physical id: e
bus info: pci@0000:02:0e.0
logical name: eth0
version: 03
serial: 00:08:02:e6:9d:02
capacity: 1GB/s
width: 64 bits
clock: 66MHz
capabilities: pm vpd msi bus_master cap_list ethernet physical mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=3.77 duplex=half firmware=5705-v3.14 ip=10.0.0.20 latency=64 link=no mingnt=64 module=tg3 multicast=yes port=twisted pair
Commands

gavin@knuckle:/etc/init.d$ sudo ifconfig ath0 down
gavin@knuckle:/etc/init.d$ sudo iwconfig ath0 essid "Livebox-****"
gavin@knuckle:/etc/init.d$ sudo iwconfig ath0 key "**************************"
gavin@knuckle:/etc/init.d$ sudo iwconfig ath0 key open (tried with and without this)
gavin@knuckle:/etc/init.d$ sudo ifconfig ath0 up
Result

gavin@knuckle:/etc/init.d$ sudo dhclient ath0
There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:11:0a:81:19:46
Sending on LPF/ath0/00:11:0a:81:19:46
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

I hope someone can shed some light on things. I just can't understand why it works at home and not at work.

[Ber P]

I finaly got my wifi to work with WEP. But I have to retype the key every time I log in :(.

Then I found this guide, and got it all to work from the command line, made the rc.local, and - it dosen't run when I boot!! I can execute it manualy, and then it works, so the file is apparently ok.
When executed manualy, however, I have to use administrator rights. So mayby it's a user rights issue? Isn't rc.local executed with administrator rights?

[kevdog]

I believe rc.local has administrator rights -- or at least it should.

You can check by doing the following:

ls -la /etc/rc.local

[Ber P]

:~$ ls -la /etc/rc.local
-rwxr-xr-x 1 root root 481 2008-01-22 21:21 /etc/rc.local


Should I uninstall NetworkManager? Is it because it forces other settings after rc.local is done?

[Pointswest]

After connecting a few nights ago, then losing the connection upon shutdown I found if I re-entered the start up commands at the console I can always connect with no problem. I have left this connection on for over 24 hours without the connection dropping.

I have changed the rc.local file as noted above to try to get the adapter to turn on at boot, but still get no connection. I do not have network manager installed so I don't think this is the problem. I am using WEP encryption.

After closer inspection of my rc.local file I found I had made a keystroke error when entering the start-up commands, upon correction the wireless adapter now starts every time at boot without the addition of of the sleep 40 command. For those of you who are new at using the terminal like me, make sure the commands are written as posted to avoid problems.

Thanks

Pointswest

[kevdog]

You may want to put a sleep 40 statement at the top of the rc.local file (or at least the networking section) to give time for other services to start. Im not sure why it doesnt work for you since others have reported success with this method. I guess you could always fall back on a script that you could run either from command line, or put an icon on the desktop that would link to the executable.

[Ber P]

I do use a script in the moment, but would realy like to have it working automaticly, since the computer is used by my kids and wife too.

I'll try the sleep command when i come home. Might just work, because yesterday it actually connected by itself one time (out of ~20)??!?!?

[LPA]

Thanks, but ...
This is all well and good if you are a real Linux techie and understand command-line lingo, but I'm not. I want my Ubuntu to work simply, and from the GUI - for real dummies. Any good idea?

Richard

[kevdog]

LPA

Please see another post. I think the title of this post was explicitly clear -- Connecting from the Command Line. Your complaint was kind of like going to a post explaining how to make mp3's, and then complaining that you wanted to make ogg files.

[walterhisownself]

kevdog,

I attempted the commands you suggest at the beginning of this thread and here are my results. I am using an Atheros wireless card AR5212 and running (newly installed) Gutsy 7.10 and my wireless router has security turned off.
The wireless router is working properly because I am able to connect to it with another laptop which was upgraded to Gutsy from 7.04 and does not use an Atheros wireless card, but a Cisco Aironet.

Here's my terminal session with the commands you suggested:

lshw -C network
WARNING: you should run this program as super-user.
*-network:0
description: Ethernet interface
product: 82540EP Gigabit Ethernet Controller (Mobile)
vendor: Intel Corporation
physical id: 1
bus info: pci@0000:02:01.0
logical name: eth0
version: 03
serial: 00:11:25:45:31:3b
width: 32 bits
clock: 66MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=e1000 driverversion=7.3.20-k2-NAPI firmware=N/A latency=64 mingnt=255 module=e1000 multicast=yes
*-network:1
description: Wireless interface
product: AR5212 802.11abg NIC
vendor: Atheros Communications, Inc.
physical id: 2
bus info: pci@0000:02:02.0
logical name: wifi0
version: 01
serial: 00:05:4e:4d:a7:7b
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=ath_pci latency=168 maxlatency=28 mingnt=10 module=ath_pci multicast=yes wireless=IEEE 802.11g

sudo ifconfig wifi0 down
sudo dhclient -r wifi0
There is already a pid file /var/run/dhclient.pid with pid 5623
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/wifi0/
Sending on LPF/wifi0/
Sending on Socket/fallback

sudo ifconfig wifi0 up
sudo iwconfig wifi0 essid "collards"
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device wifi0 ; Invalid argument.

sudo iwconfig wifi0 mode Managed
Error for wireless request "Set Mode" (8B06) :
SET failed on device wifi0 ; Invalid argument.

sudo dhclient wifi0
There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/wifi0/
Sending on LPF/wifi0/
Sending on Socket/fallback
DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 10
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Any thoughts?

iwconfig gives the following results:

iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wifi0 no wireless extensions.

ath0 IEEE 802.11g ESSID:"collards" Nickname:""
Mode:Managed Channel:0 Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:14 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=0/70 Signal level=-83 dBm Noise level=-83 dBm
Rx invalid nwid:195831 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Thanks for any help you can provide.

[kevdog]

For atheros based cards with the madwifi driver, you need to use the interface name ath0 rather than wifi0 since the madwifi driver creates virtual interface points to connect to the actual driver.

[walterhisownself]

kevdog,

Thanks for your prompt reply. I'll give those commands a try with "ath0" rather than "wifi0" and let you know what happens.

[walterhisownself]

kevdog,

Here's what I get when using "ath0" for my atheros wireless card with the madwifi driver:

sudo ifconfig ath0 down
sudo dhclient -r ath0
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:05:4e:4d:a7:7b
Sending on LPF/ath0/00:05:4e:4d:a7:7b
Sending on Socket/fallback
DHCPRELEASE on ath0 to 192.168.1.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
walaka@afagddu:~$ sudo ifconfig ath0 up
walaka@afagddu:~$ sudo iwconfig ath0 essid "collards"
walaka@afagddu:~$ sudo iwconfig ath0 mode Managed
walaka@afagddu:~$ sudo dhclient ath0
There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:05:4e:4d:a7:7b
Sending on LPF/ath0/00:05:4e:4d:a7:7b
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Any thoughts on this? It almost seems that it times out before being issued a DHCP address. I say this because when I boot up with an ethernet cable unplugged, and successfully logon, the small icon for Network Manager attempts to join any unsecured wireless network (because I have it set to roaming mode). One of the two "balls" representing the wireless network connection with Network Manager as it attempts to connect turns green. The other stays dark blue and the connection never successfully connects. This is the reason I am attempting to connect via the command line using the commands you suggest in this thread.

I'm not sure where to go from here. At times it will connect with Network Manager, but it's really sporatic.

Thanks in advance for any pointers you can provide.

[kevdog]

Can you see your network at least with

iwlist scan

and what is the reported signal strength?

[walterhisownself]

I can see my network with "iwlist scan" or "iwlist ath0 scanning"


Here's the output:


Cell 02 - Address: 02:19:5B:C7:8F:97
ESSID:"collards"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=46/70 Signal level=-49 dBm Noise level=-95 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s

I can see other networks and actually the laptop connected automatically when I unplugged it from ethernet to another unsecured network because I have it in roaming mode. I saw the Network Manager icon in the upper right panel attempt to connect to any unsecured network and it was successful in joining that network.

[kevdog]

So it sounds like the problem is solved?

[akhyarsi]

Dear all,

I have problem with my WLI-U2-KG54-AI wireless LAN USB adapter.
Gutsy uses rt2500usb driver for the device. I can see network signals, its strength after login, but the internet is not working.

I do not know what to do.
Is the rt2500usb really compatible with my device? why the driver does not appear when I type "lshw -C network" in the terminal?

I attach my screenshot below.

Any idea? thanks in advance.

[sofamensch]

Weird thing happening here when trying the static IP address. I really need it :-(

Ok so whats happening? Assume i already did all the commands for iwconfig (WEP Network), it works to get me connected, but not the part with the static ip.



sudo dhclient ath0 -r
sudo ifconfig ath0 192.168.0.254 netmask 255.255.255.0 up
sudo route add default gw 192.168.0.1
sudo dhclient ath0
>There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:0f:b5:8a:ce:8e
Sending on LPF/ath0/00:0f:b5:8a:ce:8e
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 14
DHCPOFFER from 192.168.0.1
DHCPREQUEST on ath0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1
bound to 192.168.0.155 -- renewal in 244411 seconds.
alex@desktop:~$


Shortly said, i tell him the wanted IP Address, but he still acquires an IP vom the DHCP server. Any idea? I already tried to rm dhclient.pid but no difference.

[Hillwalker]

Kevdog

I didn't post a query - all my problems were already well documented by others. I followed the advice you gave them and this is my first on-line posting with my first Ubuntu- driven machine. Many thanks for originating and sustaining the thread. Thanks too to Maricaibo for his boot script - that worked first time. For the record my card is Belkin F5D7000de with an RTL8185 chipset. I had trouble with the NDIS wrapper on the 7.10 installation disk and upgraded to the latest version (your how to came in pretty handy there too). I used the WIN98 driver set downloaded from the RealTek website. And despite having an installed and fully operational card, lspci still shows it as an unknown device. Wierd!

One bit of advice I followed was to switch to a fixed IP. That seems to have helped me along the way. However, the recipes (several of them) directed me to ~/etc/resolv.conf to remove old dhcp server assignments. Resolve.conf doesn't seem to exist in 7.10 although. When I ran dhclient this induced a couple of error messages which, I found to my great pleasure can be ignored.

Thanks again and good wishes to all other followers of the path of wisdom and truth mapped out in all that has gone before

HW

[walterhisownself]

So it sounds like the problem is solved?

Well, not actually. I'm still not able to connect to my wireless access point. It's as if it tries and then times out after a few attempts. This is via the command line. Also, via Network Manager, it seems to do the same thing. The funny thing is that I can connect to another unsecured wireless network with no problems - via Network Manager icon. I much prefer to connect to my wireless network via Network Manager, but was having problems doing it that way, that I decided to try it via the command line as instructed with this thread. But it doesn't work either way for me.
Could it be that my D-Link wireless router and the Atheros wireless card are incompatible? Thoughts from anyone...

Best,
Walter

[kevdog]

You've got me on that one. Id make sure your router was not doing any MAC filtering or have any other restrictive protocols in place. Ive only read of a few others reporting chipset/router combination problems, and I've wondered if its actually true.

[defenestratos]

I tried to establish an unencripted connection but failed on the third command. The read out is below.
What is going on? It's all greek to me.


hugo@hugo-laptop:~$ sudo dhclient -r wmaster0
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wmaster0/
Sending on LPF/wmaster0/
Sending on Socket/fallback
hugo@hugo-laptop:~$ sudo ifconfig wmaster0 up
SIOCSIFFLAGS: Operation not supported
hugo@hugo-laptop:~$ sudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
wlan0: ERROR while getting interface flags: No such device
wmaster0: unknown hardware address type 801
Bind socket to interface: No such device
hugo@hugo-laptop:~$

[kevdog]

Can you list ifconfig? Your interface name is not wmaster.

[defenestratos]

Can you list ifconfig? Your interface name is not wmaster.

Here is the output of lshw. I don't know how to list ifconfig.

hugo@hugo-laptop:~$ lshw -C network
WARNING: you should run this program as super-user.
*-network:0 DISABLED
description: Wireless interface
product: RT2500 802.11g Cardbus/mini-PCI
vendor: RaLink
physical id: a
bus info: pci@00:0a.0
logical name: wmaster0
version: 01
serial: 00:10:60:65:a5:8f
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=rt2500pci latency=128 multicast=yes wireless=IEEE 802.11g
resources: iomemory:f0000000-f0001fff irq:20
*-network:1
description: Ethernet interface
product: VT6102 [Rhine-II]
vendor: VIA Technologies, Inc.
physical id: 12
bus info: pci@00:12.0
logical name: eth0
version: 74
serial: 00:40:d0:97:93:c7
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=via-rhine driverversion=1.4.3 ip=192.168.2.20 latency=128 maxlatency=8 mingnt=3 multicast=yes
resources: ioport:e200-e2ff iomemory:f0002100-f00021ff irq:19

[kevdog]

This is your wireless driver:
driver=rt2500pci

The built-in rt2500pci driver in gutsy is sketchy. Id recommend a different driver. You have 3 options:

1. The serial monkey rt2500 cvs driver: http://ubuntuforums.org/showthread.php?t=584657&highlight=rt2500
2. Ndiswrapper + windowsxp driver: http://ubuntuforums.org/showthread.php?t=574501&highlight=ndiswrapper
3. Upgrade to Hardy's developing kernel and use the rt2x00 driver: http://ubuntuforums.org/showthread.php?t=646755

The first option is probably the easiest, but they all work.

[ounas]

Thanks Kevdog, good hints here

:popcorn:

[walterhisownself]

You've got me on that one. Id make sure your router was not doing any MAC filtering or have any other restrictive protocols in place. Ive only read of a few others reporting chipset/router combination problems, and I've wondered if its actually true.

I'm looking through my router settings. It's funny that another laptop running Ubuntu (with a different wireless device chipset) is able to easily connect. Additionally, I have one other laptop with exactly the same wireless device chipset running Winders and it is unable to connect to the access point too.

[dee_kay]

I can see my network with "iwlist scan" or "iwlist ath0 scanning"


Here's the output:


Cell 02 - Address: 02:19:5B:C7:8F:97
ESSID:"collards"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=46/70 Signal level=-49 dBm Noise level=-95 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s

I can see other networks and actually the laptop connected automatically when I unplugged it from ethernet to another unsecured network because I have it in roaming mode. I saw the Network Manager icon in the upper right panel attempt to connect to any unsecured network and it was successful in joining that network.

Apologies for parachuting in like this. I've been haunting this thread for a while trying to solve an issue hugely similar to the above. Same symptoms, different hardware. The PCI card is an Encore ENPWI-G2 card with a Realtek 8185 chipset.

I've ndiswrapper'd the driver from the factory CD and loaded it.


ndiswrapper -l
net8185 : driver installed

lsmod
Module Size Used by
ndiswrapper 185240 0

ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:66 errors: 0 dropped: 0 overruns: 0 frame: 0
TX packets:66 errors: 0 dropped: 0 overruns: 0 carrier: 0
collisions: 0 txqueuelen: 0
RX bytes:5104 (4.9 KB) TX bytes:5104 (4.9 KB)

wlan0 Link encap:Ethernet HWaddr 00:08:54:AF:4B:C8
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets: 0 errors: 0 dropped: 0 overruns: 0 frame: 0
TX packets:1 errors: 0 dropped: 0 overruns: 0 carrier: 0
collisions: 0 txqueuelen:1000
RX bytes: 0 (0.0 b) TX bytes: 0 (0.0 b)
Interrupt:11 Memory:34000000-34000025

iwconfig
lo no wireless extensions.

wlan0 IEEE 802.11g ESSID:off/any
Mode:Auto Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:-2147483648 dBm Sensitivity=0/3
RTS thr:off Fragment thr:off
Power Management:off
Link Quality: 0 Signal level: 0 Noise level:0
Rx invalid nwid: 0 Rx invalid crypt: 0 Rx invalid frag: 0
Tx excessive retries: 0 Invalid misc: 0 Missed beacon: 0

sudo lshw -C network

*-network
description: Wireless interface
product: RTL-8185 IEEE 802.11a/b/g Wireless LAN Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 1
bus info: pci@0000: 02: 00.0
logical name: wlan0
version: 20
serial: 00: 08:54:af:4b:c8
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+net8185 driverversion=1.45+Realtek,02/08/2006,5.105.0. latency=64 link=no maxlatency=64 mingnt=32 module=ndiswrapper multicast=yes wireless=IEEE 802.11g

sudo iwlist wlan0 scan
wlan0 Scan completed :
Cell 01 - Address: 00: 0F:CC:AB:9F:F4
ESSID:"KennyNET"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.442 GHz (Channel 7)
Quality:79/100 Signal level:-45 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
Extra:bcn_int=100
Extra:atim=0

sudo ifconfig wlan0 down

sudo dhclient -r

Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:08:54:af:4b:c8
Sending on LPF/wlan0/00:08:54:af:4b:c8
Sending on Socket/fallback

sudo iwconfig wlan0 essid "KennyNET" key restricted s:************************** mode Managed

sudo dhclient wlan0

There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00: 08:54:af:4b:c8
Sending on LPF/wlan0/00: 08:54:af:4b:c8
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

iwconfig
lo no wireless extensions.

wlan0 IEEE 802.11g ESSID:off/any
Mode:Auto Frequency:2.442 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:-2147483648 dBm Sensitivity=0/3
RTS thr:off Fragment thr:off
Power Management:off
Link Quality: 0 Signal level: 0 Noise level:0
Rx invalid nwid: 0 Rx invalid crypt: 0 Rx invalid frag: 0
Tx excessive retries: 0 Invalid misc: 0 Missed beacon: 0

ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:66 errors: 0 dropped: 0 overruns: 0 frame: 0
TX packets:66 errors: 0 dropped: 0 overruns: 0 carrier: 0
collisions: 0 txqueuelen: 0
RX bytes:5104 (4.9 KB) TX bytes:5104 (4.9 KB)

wlan0 Link encap:Ethernet HWaddr 00:08:54:AF:4B:C8
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets: 0 errors: 0 dropped: 0 overruns: 0 frame: 0
TX packets:1 errors: 0 dropped: 0 overruns: 0 carrier: 0
collisions: 0 txqueuelen:1000
RX bytes: 0 (0.0 b) TX bytes: 0 (0.0 b)
Interrupt:11 Memory:34000000-34000025

wlan0:ava Link encap:Ethernet HWaddr 00:08:54:AF:4B:C8
inet addr:169.254.7.210 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:11 Memory:34000000-34000025

That's about all the diagnostic I know how to run. I can ping the loopback device 127.0.0.1 but not the router 192.168.1.254. As far as I can see I don't have MAC address filtering enabled on the router and I'm broadcasting the SSID.

I've been slowly chipping away at this for a few weeks but I've finally plateau'd in terms of things to try.

Any new avenues to disappear down would be gratefully accepted.

Here's hoping',
dee_kay

[smooveg]

I'm not sure if anyone is having these same problems setting up wpa_supplicant manually per the tutorial here, but if someone could help diagnose my problem that would be great --

Attached is the terminal output from setting up wpa_supplicant and the relevant driver and config information.

Thanks in advance!


scott@scott-laptop:~$ sudo ifconfig wifi0 down

scott@scott-laptop:~$ sudo dhclient -r wifi0
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/wifi0/
Sending on LPF/wifi0/
Sending on Socket/fallback

scott@scott-laptop:~$ sudo wpa_supplicant -w -Dmadwifi -iwifi0 -c/etc/wpa_supplicant.conf
ioctl[SIOCSIWPMKSA]: Invalid argument
ioctl[SIOCSIWMODE]: Invalid argument
Could not configure driver to use managed mode
ioctl[SIOCGIWRANGE]: Invalid argument
ioctl[IEEE80211_IOCTL_SETPARAM]: Invalid argument
ioctl[SIOCSIWAP]: Invalid argument
Failed to initialize driver interface

scott@scott-laptop:~$ sudo ifconfig ath0 down

scott@scott-laptop:~$ sudo wpa_supplicant -w -Dmadwifi -iath0 -c/etc/wpa_supplicant.conf
Trying to associate with 00:1d:7e:3a:cb:6e (SSID='Linksys54G' freq=2452 MHz)
Associated with 00:1d:7e:3a:cb:6e
WPA: 4-Way Handshake failed - pre-shared key may be incorrect
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

.....when trying to run the wpa_supplicant.conf again, I get this message:

scott@scott-laptop:~$ sudo wpa_supplicant -w -Dmadwifi -iath0 -c/etc/wpa_supplicant.conf
ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/wpa_supplicant/ath0' manually if it is not used anymore
Failed to initialize control interface '/var/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.

__________________________________________________ ______________________________________

scott@scott-laptop:~$ lshw -C network
*-network
description: Ethernet interface
product: 88E8039 PCI-E Fast Ethernet Controller
vendor: Marvell Technology Group Ltd.
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 15
serial: 00:1a:80:24:d7:fa
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=sky2 driverversion=1.18 firmware=N/A latency=0 module=sky2 multicast=yes
*-network
description: Wireless interface
product: AR5006EG 802.11 b/g Wireless PCI Express Adapter
vendor: Atheros Communications, Inc.
physical id: 0
bus info: pci@0000:06:00.0
logical name: wifi0
version: 01
serial: 00:1d:d9:de:5b:a8
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=ath_pci latency=0 module=ath_pci multicast=yes wireless=IEEE 802.11g

scott@scott-laptop:~$ sudo ifconfig
ath0 Link encap:Ethernet HWaddr 00:1D: D 9: DE:5B:A8
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:19 errors:0 dropped:0 overruns:0 frame:0
TX packets:22 errors:5 dropped:5 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2147 (2.0 KB) TX bytes:2727 (2.6 KB)

eth0 Link encap:Ethernet HWaddr 00:1A:80:24: D7:FA
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wifi0 Link encap:UNSPEC HWaddr 00-1D-D9-DE-5B-A8-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3359 errors:0 dropped:0 overruns:0 frame:138
TX packets:517 errors:0 dropped:5 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:496502 (484.8 KB) TX bytes:27625 (26.9 KB)
Interrupt:18


scott@scott-laptop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wifi0 no wireless extensions.

ath0 IEEE 802.11g ESSID:"Linksys54G" Nickname:""
Mode:Managed Frequency:2.452 GHz Access Point: 00:1D:7E:3A:CB:6E
Bit Rate:54 Mb/s Tx-Power:15 dBm Sensitivity=1/1
Retry: off RTS thr: off Fragment thr: off
Power Management: off
Link Quality=21/70 Signal level=-69 dBm Noise level=-90 dBm
Rx invalid nwid:5989 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

scott@scott-laptop:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wifi0 Interface doesn't support scanning.

ath0 Scan completed :

Cell 02 - Address: 00:1D:7E:3A:CB:6E
ESSID:"Linksys54G"
Mode:Master
Frequency:2.452 GHz (Channel 9)
Quality=16/70 Signal level=-79 dBm Noise level=-95 dBm
Encryption key: on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK

[kevdog]

scott@scott-laptop:~$ sudo wpa_supplicant -w -Dmadwifi -iath0 -c/etc/wpa_supplicant.conf
Trying to associate with 00:1d:7e:3a:cb:6e (SSID='Linksys54G' freq=2452 MHz)
Associated with 00:1d:7e:3a:cb:6e
WPA: 4-Way Handshake failed - pre-shared key may be incorrect
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

The command line seems to be correct. Can you attempt to start the process including a -dd flag -- it should list more output that might help.

[jackwhite]

Hi folks,

I'm having a hard time connecting to my wireless network

I have a RT2500 (Ralink) card. If I follow the instructions set out on this thread: http://ubuntuforums.org/showthread.php?t=571188 (the "WPA with Ra Based Chipsets" bit) it looks like I'm connected to the network (i.e. the network icon on the top right of the screen shows as being connected). However even though I can connect to my router I cannot connect to the wider internet.

Doesn't make any sense to me... but I'd love any help anyone could offer.

(I'm on Ubuntu 7.04, would 7.10 be a better bet?)

[kevdog]

Ok lets just test a few things since its either a route or gateway problem.


Can you ping the router by IP address or google by IP address
64.233.187.99? If you get a response its a DNS problem

Can you also post route -n

[jackwhite]

Ok lets just test a few things since its either a route or gateway problem.


Can you ping the router by IP address or google by IP address
64.233.187.99? If you get a response its a DNS problem

Hi Kevdog - thanks for getting back to me so quickly.
I can ping the router and wireless but not google. Here's the output from route -n.

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 ra0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 ra0
0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 eth0

[flyer415]

Installed easy enough. had networking issues. This sticky solved them immediately. Using a laptop and wireless and thought I was in trouble until I followed your directions.

thanks

[lestat]

Thanks for the great advice and info. But could you shed more light on what you can do when network manager crashes or how to disable it in such a way that you can manually configure the network.
If I kill the network manager process, i cannot bring any interfaces up again. And if i try to override nm while it is searching for networks (indefinitely), my wireless card stays unassociated.
It would be great if you could indicate a simple and effective way to recover from a nm crash and manually reset the network.

Thanks

Lestat

[kevdog]

is the routing table correct?

192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 ra0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 ra0
0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 eth0

Are you using your wireless card ra0 rather than the wired ethernet connection?

Is the IP address of your card 192.168.0.0?
The router IP address 192.168.0.1?


Something seems strange with the first line!

[kevdog]

To restart networking services its simple

sudo /etc/init.d/networking restart

[dee_kay]

. . . bump!

Has anyone any ideas?

[dee_kay]

Apols. Re the "bump", I was referring to my previous post# 216.

Rgds,
Dave

[jw5801]

Well, in the post you posted on the previous page, you took down the interface, but never brought it back up again. "sudo ifup wlan0" might help in the middle there somewhere.

[randiroo76073]

Big thanks Kevdog, saved my bacon with wifes puter :D

[dee_kay]

Well, in the post you posted on the previous page, you took down the interface, but never brought it back up again. "sudo ifup wlan0" might help in the middle there somewhere.

Thanks JW5801!

I might have left that out somewhere in the post but then again . . . I'll start again. ifup wlan0 is the same as ifconfig wlan0 up isn't it?

Rgds,
Dave

[jw5801]

Thanks JW5801!

I might have left that out somewhere in the post but then again . . . I'll start again. ifup wlan0 is the same as ifconfig wlan0 up isn't it?

Rgds,
Dave

As far as I know, yes. Dunno whether ifup actually calls ifconfig or vice versa or if they're independent, but they achieve the same end!

[kevdog]

Id stick with ifconfig rather than ifup. ifup calls ifconfig and also sets a route. ifup references the /etc/network/interfaces file and is capable of reading settings. ifconfig is more low level and does not. Again the purpose of this demonstration is to attempt to get wireless working using the lowest common denominator -- which is definitely not ifup but rather ifconfig <interface> up. If you route isn't set using this method (or the gateway), we can set this up later manually also.

[jackwhite]

is the routing table correct?

192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 ra0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 ra0
0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 eth0

Are you using your wireless card ra0 rather than the wired ethernet connection?

Is the IP address of your card 192.168.0.0?
The router IP address 192.168.0.1?


Something seems strange with the first line!


Hmmm, i think I might be having an issues with the router and modem using the same ip address. I'm going to be offline for a couple of days. i'll try to tackle this at the weekend and will prob post back then.

thanks for your help!

[mmbates]

G'day,
I'm having trouble
(1) establishing a wireless connection; and
(2) when one is established, getting something like a reasonable speed out of it (like I'm talking slower than a poor dial up connection)

Here is some output:
#######################################
$ lshw -C network
*-network
...stuff about ethernet interface eth0...
*-network
...stuff about ethernet interface eth1...
*-network
description: Wireless interface
product: BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller
vendor: Broadcom Corporation
physical id: 6
bus info: pci@0000:06:06.0
logical name: eth2
version: 02
serial: 00:1d:60:6f:00:fd
width: 32 bits
clock: 33MHz
capabilities: bus_master ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.45+Broadcom,10/12/2006, 4.100. latency=32 module=ndiswrapper multicast=yes wireless=IEEE 802.11g
$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 no wireless extensions.

eth2 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:32 dBm
RTS thr:2347 B Fragment thr:2346 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
$ sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Interface doesn't support scanning.

eth2 Scan completed :
Cell 01 -
.... someone else's wireless on Channel 10 ...
Cell 02 - Address: 00:14:A5:C5:30:F2
ESSID:"wantok"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.442 GHz (Channel 7)
Quality:96/100 Signal level:-34 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
#########################################

So, the driver seems to be working ok, but its not associated to anything. It does see the newtorks ok as well. Then using the rest of the howto with WEP enabled:
#########################################
$ sudo ifconfig eth2 down
$ sudo dhclient -r eth2
There is already a pid file /var/run/dhclient.pid with pid 0
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth2/00:1d:60:6f:00:fd
Sending on LPF/eth2/00:1d:60:6f:00:fd
Sending on Socket/fallback
DHCPRELEASE on eth2 to 192.168.0.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
$ sudo ifconfig eth2 up
$ sudo iwconfig eth2 essid "wantok"
$ sudo iwconfig eth2 key MY_KEY_HERE
$ sudo iwconfig eth2 key open
$ sudo iwconfig eth2 mode Managed
$ sudo dhclient eth2

There is already a pid file /var/run/dhclient.pid with pid 0
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth2/00:1d:60:6f:00:fd
Sending on LPF/eth2/00:1d:60:6f:00:fd
Sending on Socket/fallback
DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 9
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
$
###########################################

Also, if I use the address listed in iwlist, and
$sudo iwconfig eth2 ap 00:14:A5:C5:30:F2

it still doesn't want to connect.

I have managed to get it to connect a couple of times, by just doing the above a few times, then repeating it in some kind of random order (mainly the iwconfig commands). It seems as though it will sometimes randomly connect after a "sudo iwconfig eth2 key open" command, but this could be coincidence.

The times that I have got it connected, it then runs really, really slowly. To give you a measure of it, if I ping my router wired, the return time is typically less than or equal to 1.0ms, while if I do it wireless, it is typically between 4ms and 25ms, with most values in the region of 10-20ms.

Any help or advice would be much appreciated. If it is of any help, some of my hardware, including the wireless card details is listed in this post: http://ubuntuforums.org/showthread.php?p=4314537#post4314537

cheers,
Michael

[kevdog]

Im sorry that the topic of a poor connection is a very difficult topic to master. Possibly turn off IPV6.

[just4priya]

Hi,

Thanks for providing this info. It really helped in a way.
I tried the above steps and was able to receive an IP.
The network is an unencrypted n/w. Though it requires a username and passwd to be submiited from the web .

How do i automate such steps ..as in after login i directly get connected and there is no need for provoding auth details

Cheers,
just4priya

[kevdog]

At the bottom of the tutorial on page one there is a section entitled:
Setting the Wireless Interface to Connect at Boot ***Courtesy of Maricaibo

Is this what you are looking for?

[praddie]

Thanks kevdog's for the detailed articles.

[dee_kay]

Id stick with ifconfig rather than ifup. ifup calls ifconfig and also sets a route. ifup references the /etc/network/interfaces file and is capable of reading settings. ifconfig is more low level and does not. Again the purpose of this demonstration is to attempt to get wireless working using the lowest common denominator -- which is definitely not ifup but rather ifconfig <interface> up. If you route isn't set using this method (or the gateway), we can set this up later manually also.

KevDog,
Thanks! I haven't had a chance to get back to this yet but hopefully over the weekend. I'm a big fan of lowest common denominators and first principles.

Best regards,
Dave.

[jackwhite]

Hi Kevdog, all,

I've had another go at this and had some initially positive results.

I'm working off the part of your tutorial for Ra wireless cards. I input the following:



sudo ifconfig ra0 down
sudo dhclient -r ra0
sudo ifconfig ra0 up
sudo iwconfig ra0 essid "network.name"
sudo iwpriv ra0 set AuthMode=WPAPSK
sudo iwpriv ra0 set EncrypType=TKIP
sudo iwpriv ra0 set WPAPSK=password
sudo dhclient ra0


I then go to the network icon on the top bar and select 'Manual configuration'. Within this screen I go to the DNS section, I delete the two entries there and add 192.168.1.1 (this is the DNS value all other computers in the house use to access the wifi).

This connects me to the network and I'm actually typing this from my ubuntu box.

The only problem I have now is that i don't know how to store this in the system. [At the moment it drops after half an hour or so - the same period of time the terminal 'remembers' my sudo password it seems]. I know that you gave fairly clear instructions in your tutorial but I'm not so great at the adapting them bit. Could you walk me through it?



ifconfig eth0 down
ifconfig ra0 down
dhclient -r ra0
iwconfig ra0 essid <router name>*
iwconfig ra0 mode Managed
ifconfig ra0 up
dhclient ra0


* How do I get the router name?
** What lines do I have to add because the network is encrypted? Is it just

sudo iwpriv ra0 set AuthMode=WPAPSK
sudo iwpriv ra0 set EncrypType=TKIP
?

Is there anything I can do to permanently change the DNS entries?

I know that these are newbie questions but I really appriciate you help!

[kevdog]

Get the router name by doing a
iwlist scan

And look at the results -- the essid of your router should be shown.

DNS servers: Take a look at this thread:
http://ubuntuforums.org/showthread.php?t=282034
(I posted this link under the reference section -- I can see that this section was skipped).

If you want to save these commands, just put them all in a shell script file, make the file executable, and then you can run the set of commands anytime you want from the command line!

[mmbates]

G'day,
WRT to my previous post (http://ubuntuforums.org/showthread.php?p=4319813#post4319813) -- turning off IPV6 didn't work.

I am thinking that it could be a problem with the driver(s), as I am using a 64 bit OS.

I'm thinking that I will discard the present card and try to find a card that has good, stable, open 64 bit drivers -- unless someone rekons that it's just that I'm a a useless twit and not the card :)

cheers,
Michael

[walterhisownself]

You've got me on that one. Id make sure your router was not doing any MAC filtering or have any other restrictive protocols in place. Ive only read of a few others reporting chipset/router combination problems, and I've wondered if its actually true.

DOH! :oops:

"MAC filtering" Yes, I did set that up several months ago...

[Retrieves that memory from tape backup]

Thanks for your help, kevdog. I'm up and running now!

[0gl]

OK, first off, thank you KevDog for your guides, you are AWESOME.

I diligently entered all the input needed for the WEP enabled connection to work, but at the key entry, it goes wrong:


~$ sudo iwconfig wlan0 key 1957-1963-03
Error for wireless request "Set Encode" (8B2A) :
SET failed on device wlan0 ; Invalid argument.

The ifconfig gives no apparent problems:

eth0 Link encap:Ethernet HWaddr 00:01:6C:2A:90:8F
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17 Base address:0x2000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:107 errors:0 dropped:0 overruns:0 frame:0
TX packets:107 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10052 (9.8 KiB) TX bytes:10052 (9.8 KiB)

wlan0 Link encap:Ethernet HWaddr 00:0C:41:BC:5D:93
inet6 addr: fe80::20c:41ff:febc:5d93/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:1404 (1.3 KiB)
Interrupt:21 Memory:fa000000-fa000800

As does the "iwlist scan" (number 02 is the one I need to have):

$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:14:7F:76:4D:A9
// the neighbour's network - heaven know what kind of network he has, but all the options make his cell as long as the other 3 together
Cell 02 - Address: 00:0C:F6:02:FE:6C //the home network - this is what I have to connect with
ESSID:"Sitecom"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.457 GHz (Channel 10)
Quality:43/100 Signal level:-68 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 03 - Address: 00:18:4D:87:54:7E
ESSID:"Rovala"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:28/100 Signal level:-78 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 04 - Address: 00:0C:F6:2D:95:AE
ESSID:""
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:18/100 Signal level:-84 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Extra:bcn_int=100
Extra:atim=0I didn't know there were that many wireless networks around the house :)

And, while we're at it: lshw -C network
~$ lshw -C network
WARNING: you should run this program as super-user.
*-network:0
description: Wireless interface
product: WMP11v4 802.11b PCI card
vendor: Linksys, A Division of Cisco Systems
physical id: 1
bus info: pci@02:01.0
logical name: wlan0
version: 00
serial: 00:0c:41:bc:5d:93
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+lsipnds driverversion=1.48+Cisco-Linksys, LLC.,08/15/2 latency=32 maxlatency=32 mingnt=32 multicast=yes wireless=IEEE 802.11b
resources: iomemory:fa000000-fa0007ff irq:21
*-network:1
description: Ethernet interface
product: RTL-8139/8139C/8139C+
vendor: Realtek Semiconductor Co., Ltd.
physical id: 5
bus info: pci@02:05.0
logical name: eth0
version: 10
serial: 00:01:6c:2a:90:8f
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=8139too driverversion=0.9.28 latency=32 maxlatency=64 mingnt=32 multicast=yes
resources: ioport:9000-90ff iomemory:fa001000-fa0010ff irq:17

I tried every possible way the 64-bit key would work (that is: XXXXXXXXXX or XXXX-XXXX-XX or XX-XX-XX-XX-XX or XX:XX:XX:XX:XX, the latter two being products of my stupiditiness), and I installed all the permutations possible with the three .inf files from the driver using NDISwrapper...

So where did I go wrong?

Regards, Leo

[kevdog]

Leo

Can you connected to an unencrypted network without WEP?
Can you change the WEP key?

How about just doing this for testing purposes:
sudo ifconfig key s:ASCII_KEY

Im just trying to get something working for you to prove that you can connect, and then fine tune the process later.

[mahinda]

I am new to ubuntu/linux. I am trying to configure the network. I am using static IP, so as said in this thread I want to add/change codes. But where should I add/change them, which file??

please somebody let me know, sorry again, I am new to this, :confused:

[kevdog]

mahinda

Read the instructions again. There are no files involved in this method, except if you are using WPA for authentication -- in this case you need to create and add parameters to the wpa_supplicant.conf file. Again the majority of this method only uses commands typed at the command line.

[dee_kay]

Id stick with ifconfig rather than ifup. ifup calls ifconfig and also sets a route. ifup references the /etc/network/interfaces file and is capable of reading settings. ifconfig is more low level and does not. Again the purpose of this demonstration is to attempt to get wireless working using the lowest common denominator -- which is definitely not ifup but rather ifconfig <interface> up. If you route isn't set using this method (or the gateway), we can set this up later manually also.

Yup, as in "nope". I revisited this over the weekend and just again now. No joy. Card looks good but the router can't be found.


dkenny@ubuntu01:~$ sudo ifconfig wlan0 down
[sudo] password for dkenny:
dkenny@ubuntu01:~$ sudo dhclient -r
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:08:54:af:4b:c8
Sending on LPF/wlan0/00:08:54:af:4b:c8
Sending on Socket/fallback

dkenny@ubuntu01:~$ sudo ifconfig wlan0 up
dkenny@ubuntu01:~$ sudo iwconfig wlan0 essid "KennyNET"
dkenny@ubuntu01:~$ sudo iwconfig wlan0 key s:**************************
dkenny@ubuntu01:~$ sudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:08:54:af:4b:c8
Sending on LPF/wlan0/00:08:54:af:4b:c8
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
dkenny@ubuntu01:~$


I wonder if it's the key? I have an 8 character pass phrase that my router uses to generate a 26 character WEP key. At the mo' I'm feeding iwconfig the 26 ascii (I assume it's ascii) key. It's just a string of lowercase letters and digits.

The iwlist wlan0 scan still says the card isn't associated with the router.

Any ideas?

Rgds,
Dave

[jw5801]

If it's 26 characters it won't be ASCII, it'll be HEX. If it were ASCII it would be only 13 characters. That means you should leave off the s: and everything should work well!

[dee_kay]

Just as a follow up to the last post, I pulled this from a tail of the messages log. I thought the reference to a redhat directory was a bit off.


Feb 18 21:53:54 ubuntu01 kernel: [ 3962.884000] pccard: CardBus card inserted into slot 0
Feb 18 21:53:54 ubuntu01 kernel: [ 3962.884000] PCI: Enabling device 0000:02:00.0 (0000 -> 0003)
Feb 18 21:53:54 ubuntu01 kernel: [ 3962.884000] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
Feb 18 21:53:54 ubuntu01 kernel: [ 3962.884000] eth0: Xircom cardbus revision 3 at irq 11
Feb 18 21:53:54 ubuntu01 kernel: [ 3962.884000] PCI: Enabling device 0000:02:00.1 (0000 -> 0003)
Feb 18 21:53:54 ubuntu01 kernel: [ 3962.884000] ACPI: PCI Interrupt 0000:02:00.1[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
Feb 18 21:53:54 ubuntu01 kernel: [ 3962.988000] 0000:02:00.1: ttyS1 at I/O 0x1080 (irq = 11) is a 16550A
Feb 18 21:53:54 ubuntu01 kernel: [ 3963.164000] xircom cardbus adaptor found, registering as eth0, using irq 11
Feb 18 21:53:59 ubuntu01 kernel: [ 3967.744000] xircom_cb: Link is 100 mbit
Feb 18 21:54:30 ubuntu01 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Feb 18 21:54:30 ubuntu01 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.domain_name
Feb 18 21:54:30 ubuntu01 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Feb 18 21:54:30 ubuntu01 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers

or am I barking up the wrong tree?

Would you advise peeling things back and switching encryption off on my home network and trying again by the numbers?

Rgds,
Dave

[dee_kay]

If it's 26 characters it won't be ASCII, it'll be HEX. If it were ASCII it would be only 13 characters. That means you should leave off the s: and everything should work well!

Alas, no.


dkenny@ubuntu01:~$ sudo killall dhclient
dkenny@ubuntu01:~$ sudo ifconfig wlan0 down
dkenny@ubuntu01:~$ sudo ifconfig wlan0 up
dkenny@ubuntu01:~$ sudo iwconfig wlan0 essid "KennyNET" key ************************** mode Managed
dkenny@ubuntu01:~$ iwconfig
lo no wireless extensions.

wlan0 IEEE 802.11g ESSID:off/any
Mode:Auto Frequency:2.442 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:-2147483648 dBm Sensitivity=0/3
RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

dkenny@ubuntu01:~$ sudo dhclient
There is already a pid file /var/run/dhclient.pid with pid 6820
removed stale PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:08:54:af:4b:c8
Sending on LPF/wlan0/00:08:54:af:4b:c8
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Grr! :)

Right. Next move is to turn off WEP.

Rgds,
Dave.

[0gl]

Leo

Can you connected to an unencrypted network without WEP?
Can you change the WEP key?

How about just doing this for testing purposes:
sudo ifconfig key s:ASCII_KEY

Im just trying to get something working for you to prove that you can connect, and then fine tune the process later.

Ok I removed the WEP key from the network, and I got Internet. So this issue is probably due to a corrupt WEP key.

But what is wrong with 10 numbers?

I'll now try a ASCII key, and maybe that will work.

*edit*

ASCII (s:XXXXX) didn't work either. same error message appeared:
Error for wireless request "Set Encode" (8B2A):
SET failed on device wlan0: invalid argument.
*edit2*
I changed it back, and the whole network thing has not been changed.When I type "sudo dhclient -r wlan0" I receive the error:
There is already a pid file /var/run/dhclient.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:0c:41:bc:5d:93
Sending on LPF/wlan0/00:0c:41:bc:5d:93
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.57.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.

[kevdog]

Sounds definitely like a WEP authentication problem. dhclient -r simply releases the assigned IP address (if any back to the DHCP server). If this step fails or produces errors, its probably not a big deal. You are right in stating that a 64 bit wep key is 10 characters in length (the hex key). A 128 bit WEP key has a hex key 26 characters long. Make sure the router settings are correct and no MAC filtering is in place. Just to confirm however that running an open network, you are able to connect?

[rakusson]

i hope this will help.

[dee_kay]

Right. Next move is to turn off WEP.

Rgds,
Dave.

Ah! Excellent. I turned off WEP security and I got to my network. Using it now to post this.

Now . . . I don't really want to run the network wide open and I think we're happy that I've got a 26 char hex key to enter when I switch WEP back on.

I'll switch it back on and give it a whirl.

Rgds,
Dave

[dee_kay]

Ah! Excellent. I turned off WEP security and I got to my network. Using it now to post this.

Now . . . I don't really want to run the network wide open and I think we're happy that I've got a 26 char hex key to enter when I switch WEP back on.

I'll switch it back on and give it a whirl.

Rgds,
Dave

Woo, and indeed, hoo!!!!

Pherkling excellent.

I'm up. Before I switched security back on I changed from a 26char key to a 64bit 10char key and bizarrely I was able to connect using NetMgr. I know, I know. This is not good. The whole point of this is to do it using ifconfig and iwconfig but that didn't work so (very guiltily) I gave NetMgr a go. I tried again with the CLI but

sudo iwconfig wlan0 essid KennyNET key xx-xx-xx-xx-xx
sudo iwconfig wlan0 essid "KennyNET" key xx-xx-xx-xx-xx
sudo iwconfig wlan0 essid KennyNET key xxxxxxxxxxx

or

sudo iwconfig wlan0 essid "KennyNET" key xxxxxxxxxxx

didn't result in a connection.

I'd be more than happy to be able to do this from the command line.

In the meantime, thanks to you guys for all your help and forbearance.

Rgds,
Dave

[kevdog]

Are you using key index 1 or 2 or 3 or 4? Just wondering if you have to specify the key index. Also could you tell me if the WEP is using an open or shared system?? It should say this in the router!

[chocolatetoothpaste]

Thank you sooooooo much! I have been dying for a low level setup for my card, as I'm running an Openbox only system. I have an issue though, maybe someone can give me some insight. I don't have my wireless enable on boot up, but I put a little script together to enable it quickly. The problem is, if I start wlan0, and then just unplug eth0, the system semi-freezes. I can still start apps, but if I'm at the command prompt and type 'ls', it hangs. I can still close the console though. I have a samba share that I auto-mount on boot up, and if I unmount it, start wlan0, then remount it, it works. Anyway, not sure what the problem is really, just wondering if eth0 has to be down when wlan0 is up. Any suggestions appreciated. Again, thanks for a stellar guide!

[kevdog]

If you are planning on wlan0 taking the place of eth0, then yes, eth0 must be down on boot. Do you have an auth eth0 line in your /etc/network/interfaces file? If so, comment it out!

[chocolatetoothpaste]

I don't have 'auth eth0' but I have 'auto eth0'. Is that what you meant? There is also 'auto lo'. Will it cause any problems?

[kevdog]

Sorry, I meant auto eth0. This means the eth0 interface is automatically brought up with the network services daemon runs (which is at boot). Comment out the auto eth0 line, and this interface would have to be brought up manually instead of started automatically. lo refers to the loopback interface -- this shouldn't cause a problem.

[_Azrael_]

A *ton* of thanks to you kevdog! This is a very helpful and informative howto!

I'm interested in what ended up solving my final wireless problem.

I was unable to connect to my home AP using WPA. The debug report implied that the handshake couldn't be completed and just kept on trying in a loop. Unfortunately I did not archive the output.

After reading your guide I decided to switch off encryption just to test my device. It worked fine. Switched WPA back on and now it works like a charm.

Do you know what happened on that successful unencrypted handshake that resulted in the WPA connection working smoothly?

Thanks again!

[kevdog]

WPA is strange like that sometimes. I wouldn't be surprised if the problem reared its head in the future :)

[PGScooter]

Hi Kevdog,

thank you for your guide! I am still having trouble though..

dmesg seems to turn up some errors:


57.979763 wlan0: issue_cmd(): cmd_status is not SUCCESS: 14 (Invalid parameter). took 2ms of 49
573979769 wlan0: issue_cmd(cmd:0X0008) FAILED


I did some searching and found a post with a similar error. The poster said that there was an IRQ conflict, and to see if you have one, to do the command lspci -vv, but I do not know how to read this output for an error.

the command lshw -C network returns 2 entries:
"Ethernet interface" (which I don't think is important, right?)
and
"Wireless interface"
product ACX 111 54 wps Wireless Interface
driver=acx_pci

in case it is helpful, I posted output from the following commands
iwlist scanning
sudo ifdown wlan0
sudo ifup wlan0
iwconfig
on this thread
http://ubuntuforums.org/showthread.php?t=706827 (I do not want to further clutter this thread)

thanks!

[ukstar]

Hi there my name is riaz i am new to ubunto but geek of windows my email adress is ukstar34@hotmail.com

I want serious help i live in Pakistan and i feel ubuntu/ linux is real need i am very pleased to see ubuntu 7 i want to use internet through network
my internet service is working on XP through Lan network but recently
network administrator have given me static ip and subnet address
now and have installed a batch file on my desktop if i click them my internet works (file is having ARP comand which locks my IP) and MAC address comand line is like this
arp -d
arp -s 172.16.0.1 00.bhhhbb(mac adress)
when i click it goes in dos mode and then gone then i click browsers and they work in xp
I NEED SOME ONE TO HELP ME SO I CAN RUN internet ON UBUNTU
PLZZZZZ i need your help and i will be very greatfull cuz my admin says
linux is just trash keep using windows .

i hope to hear soon from someone ........RIAZ

[Prefix100]

Hey,

I have an issue that is driving me crazy.

My wireless device is the usb belkin F5D7050.
I once got my wireless device working using the rt73usb drivers.

Then when i restarted my computer the device stopped working.

I tried using the same commands as i used before to get it working, but when i type

sudo ifconfig wlan0 up

it returns the error

SIOCSIFFLAGS: No buffer space available

The device is showed as disabled when I check my network.

Any advice on this issue would be greatly appreciated, I really need this to work because I have some work that really needs done.

[kevdog]

Check if the rt73 drivers are loaded into the kernel with the lsmod statement.

[SunnyRabbiera]

alright I think I have an issue with lshw -C network, it gives me no output when I type in the command...

help?

[Crash90]

First off - Awesome how-to! Simple and easy to follow. Not super dense like some How-To's out there!!

Unfortunately, I have run into a few small problems!

My setup:

Logical: Eth1
Driver: IPW
CARD: Broadcom 440x


Wow. I am a huge retard. I just spent the past 3 hours trying to get access a WPA network when the whole time the network is WEP.

The problem? My pass key (in windows) for the network is Alphanumeric - How do I convert it into a Hex or ASCII format??

I tried using the WPA_passkey to convert and used the key it puts out, but I get no DHCP offers.

[kevdog]

You can use either ASCII or HEX for your WPA passphrase, depending on the configuration within the wpa_supplicant file

For ASCII (snippet below):
psk="ASCII PSK Password in Quotes"

To convert to HEX:
At the command line type the following:
wpa_passphrase <your_essid> <your_ascii_key>

Resulting in an output like...
Quote:
network={
ssid="test"
#psk="12345678"
psk=fe727aa8b64ac9b3f54c72432da14faed933ea511ecab1 5bbc6c52e7522f709a
}

The psk is your HEX key, so in the wpa_supplicant.conf file you would put the following line:

psk=<HEX_KEY>

Notice the hex key is not in quotes


-----

If lshw -C network is not working, check dmesg for errors, since this implies that the OS is not recognizing your card. If you have a USB device (since you never stated), try lsusb -v

[CodeAlias]

Hi,

This is a useful article that describes how to setup EAP-TLS authentication with wpa_supplicant. I could not find equivalent howto on ubuntuforums.org, so I though I'd share the link : Wireless security with EAP-TLS : Linux client setup (http://www.codealias.info/technotes/wpa2_eap-tls_authentication_linux_client_setup)

[kevdog]

Nice link -- most steps are applicable to ubuntu -- Have you tried these steps and verified that they work? I could add a section in the howto (with credit to you or course) if you could demonstrate to me if these steps work.

[SunnyRabbiera]

I still have an issue, what does it mean if nothing comes up with lshw????

[kevdog]

Do you have a usb device? If you have a pci device and nothing comes up with lshw - check dmesg. If no errors are listed you have a hardware problem.

[SunnyRabbiera]

yeh its a usb device...

do I have to have something else?
I hope not as I need this adapter to work, is there another command I have to use?

[kevdog]

lsusb -v

[SunnyRabbiera]

alright I will give it a shot

[dee_kay]

Are you using key index 1 or 2 or 3 or 4? Just wondering if you have to specify the key index. Also could you tell me if the WEP is using an open or shared system?? It should say this in the router!

I'm using index key 1, which is 64 bit. Keys 2-4 are 128 bit and "Enable Closed System Mode" is unchecked.

Sorry about the delay in replying . . .

Rgds,
Dave

[SunnyRabbiera]

alright I have some output from lsusb:
Bus 002 Device 002: ID 13b1:000b Linksys WUSB11 v4.0 802.11b Adapter
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 8
idVendor 0x13b1 Linksys
idProduct 0x000b WUSB11 v4.0 802.11b Adapter
bcdDevice 0.01
iManufacturer 1 ALinx Corp
iProduct 2 USB Device
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 200mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 1
Device Status: 0x0000
(Bus Powered)


so how do I get this thing cooking?

[kevdog]

What kind of router are you using -- Ive never seen mixed 64 and 128 bit keys.

[SunnyRabbiera]

What kind of router are you using -- Ive never seen mixed 64 and 128 bit keys.

is that toward me or someone else?

[kevdog]

Sunny

Bus 002 Device 002: ID 13b1:000b Linksys WUSB11 v4.0 802.11b Adapter

Thats your device - it is being recognized. Do you happen to know the chipset of the device. I'm guessing its rt2500 but I could be wrong. You may have to google to find out the chipset. Do you have drivers (windows for the device)?

[SunnyRabbiera]

Sunny

Bus 002 Device 002: ID 13b1:000b Linksys WUSB11 v4.0 802.11b Adapter

Thats your device - it is being recognized. Do you happen to know the chipset of the device. I'm guessing its rt2500 but I could be wrong. You may have to google to find out the chipset. Do you have drivers (windows for the device)?

yeh I installed the drivers with ndiswrapper, they appeared to install fine with it.
as for the chipset...
its a prism2 from what i read, though someone else said its a ALi M4301

how much does that help?

[CodeAlias]

Nice link -- most steps are applicable to ubuntu -- Have you tried these steps and verified that they work? I could add a section in the howto (with credit to you or course) if you could demonstrate to me if these steps work.

I have tried the procedure and it worked like a charm :)

[kevdog]

Sunny

With lsmod | grep ndis

Is the ndiswrapper module shown?

CodeAlias
Could you write up the exact steps you did so I can add it to the guide?

[SunnyRabbiera]

Sunny

With lsmod | grep ndis

Is the ndiswrapper module shown?


no
what now?

[kevdog]

Post the following:

ndiswrapper -l

sudo modprobe ndiswrapper

lsmod | grep ndis

[Crash90]

I have been trying to configure my wireless using the guide provided in this forum. I am using WEP 128 bit w/ passphrase on an open connection. Here is what I have done so far:

sudo ifconfig eth1 down (works fine)

sudo dhclient -r eth1
sudo ifconfig eth1 up
sudo iwconfig <interface> essid "JLWIRELESS"
sudo iwconfig <interface> key 4d6f6e616432393031666f786d
sudo iwconfig <interface> mode Managed




my problems come @
sudo dhclient eth1

returns:

Code:

NO DHCP Offers received


I know that this is not an encryption problem. I have entered both the Essid correctly and my passphrase converted to Hex correctly.

Should I go for a static IP address? Am I missing something simple.

What I am using:

Logical drive: eth1

Driver: IPW2200

Open WEP style 128 Bit encryption

Passphrase = Monad2901foxm

Hex conversion = 4d6f6e616432393031666f786d

ESSID = JLWIRELESS

[dee_kay]

What kind of router are you using -- Ive never seen mixed 64 and 128 bit keys.

I thought it was a bit weird all right. When I changed the pass key from 128 bit to 64 bit I thought it would reset all the keys but it only reset key 1 (to 64 bit) and left the rest of them at 128 bit.

The router is my ISP's standard issue, a Netopia 2247.

Rgds,
Dave

[kevdog]

Crash90:

Lines like this in your situation:
sudo iwconfig <interface> essid "JLWIRELESS"

should be:

sudo iwconfig eth1 essid "JLWIRELESS"

[kevdog]

deekay

Not sure what to say, have you tried someone else's network or a different router. Im not even sure its a router problem, however it just seems funny. You said you can connect when WEP is turned off, so it seems to be an authentication problem.

[SunnyRabbiera]

here is what I got:
ndiswrapper -l
lspmusb : driver installed
device (13B1:000B) present
netusb : driver installed
device (13B1:000B) present
wusb11v4 : driver installed
device (13B1:000B) present

lsmod | grep ndis
ndiswrapper 185240 0
usbcore 138632 6 ndiswrapper,cdc_ether,usbnet,usbhid,uhci_hcd

however I got nothing with sudo modprobe ndiswrapper

[Crash90]

Crash90:

Lines like this in your situation:
sudo iwconfig <interface> essid "JLWIRELESS"

should be:

sudo iwconfig eth1 essid "JLWIRELESS"

whoops - I just copy pasted your instructions for this post. I am using the eth1 when doing in CL - no change.

[rustybronco]

device (13B1:000B) present

https://help.ubuntu.com/community/WifiDocs/Device/Linksys_WUSB11v4_(ndiswrapper)

Version 4 of the WUSB11 uses the former Acer Labs now ALi M4301 wireless chipset. There are no Linux native drivers available for this chipset at present and I assume that there will not be any forth coming.

[SunnyRabbiera]

https://help.ubuntu.com/community/WifiDocs/Device/Linksys_WUSB11v4_(ndiswrapper)

so I guess it wont work no matter what?
But how come I read others having success with this adapter????

[rustybronco]

so I guess it wont work no matter what?
But how come I read others having success with this adapter????Sonny, it was done for verification of the chipset used in your device. that reason only.
it was something that kevdog asked about.

nothing to do with it working or not.

[jw5801]

here is what I got:
ndiswrapper -l
lspmusb : driver installed
device (13B1:000B) present
netusb : driver installed
device (13B1:000B) present
wusb11v4 : driver installed
device (13B1:000B) present

lsmod | grep ndis
ndiswrapper 185240 0
usbcore 138632 6 ndiswrapper,cdc_ether,usbnet,usbhid,uhci_hcd

however I got nothing with sudo modprobe ndiswrapper

"sudo modprobe ndiswrapper" is a command to insert the ndiswrapper module (driver) into the kernel, it won't output anything unless it's broken. The reason your wireless is probably not working is because you have three different drivers installed for the same device. The thread kevdog linked you to should be able to tell you which one you need for your card, so you'll need to install the correct ndiswrapper driver. You can use the following commands to remove the three you have now:

sudo ndiswrapper -e lspmusb
sudo ndiswrapper -e netusb
sudo ndiswrapper -e wusb11v4

[SunnyRabbiera]

its probably the others listed, lspmusb and netusb.
it would seem logical

[rustybronco]

in https://help.ubuntu.com/community/WifiDocs/Device/Linksys_WUSB11v4_(ndiswrapper)


We can also look inside the directory where the drivers get stored by ndiswrapper:

user@ubuntu:~/wusb11/WUSB11v4_08272004/Drivers$ ls /etc/ndiswrapper/
wusb11v4

And the contents are:

user@ubuntu:~/WUSB11v4_08272004/Drivers$ ls /etc/ndiswrapper/wusb11v4/
13B1:000B.F.conf m4301a.sys mdusb.out wusb11v4.inf

from http://www.knoppix.net/forum/viewtopic.php?p=96217

i got the linksys CD and in a file called drivers i found the following files

LSPMUSB.inf
M4301A.sys
NETUSBXP.SYS
VNETUSBA.SYS
m4301a.cat
vnet581.sys
vnetusbl.sys
LSPMUSB.inf
NETUSB.SYS
PRISM9x.SYS
mdusb.out
vnet581x.sys
vnetusbxp.sys
LSPMUSB.sys
NETUSB.inf
PRISMXP.SYS
WUSB11v4.inf
netrfm2k.cat
vnetu9x1.sys
would you not need the proper.sys and .inf files?

[SunnyRabbiera]

well I did get them in yes, someone suggested that packing it all together could get this working

[kevdog]

Sunny -

So it seems you dont have the correct windows drivers?

[SunnyRabbiera]

Sunny -

So it seems you dont have the correct windows drivers?

huh?
I thought the wireless drivers are the correct ones?
the wusb11v4.inf file should cover that right?
I got like 3 .inf files to work with, how can I tell what was the right one?
lspmusb.inf
netusb.inf
wusb11v4.inf
this is confusing

[kevdog]

Where did you get all of those inf files -- did they come on a CD or from the manufacturers website? Usually one sys and one inf file.

[SunnyRabbiera]

it came from the windows.exe file and the CD.
I tested them both, I have an installer CD and the .exe from the linksys website, all have three .inf files.

[wieman01]

it came from the windows.exe file and the CD.
I tested them both, I have an installer CD and the .exe from the linksys website, all have three .inf files.

wusb11v4.inf
That should be the right file. Any other files that came with it? .CAT or .SYS? You probably need to have these in the same directory while you deploy the driver.

Or are you on 64-bit Ubuntu by chance?

Sorry for hijacking this thread... I'll shut up after this one. Wanted to make myself useful.

[SunnyRabbiera]

That should be the right file. Any other files that came with it? .CAT or .SYS? You probably need to have these in the same directory while you deploy the driver.

Or are you on 64-bit Ubuntu by chance?

Sorry for hijacking this thread... I'll shut up after this one. Wanted to make myself useful.

no 32 bit, as the other computer I am trying to get wireless on has the same chip I have a pentium 4.
and yeh I put all the .cat and .sys files in the directory where the driver has installed.

[wieman01]

no 32 bit, as the other computer I am trying to get wireless on has the same chip I have a pentium 4.
and yeh I put all the .cat and .sys files in the directory where the driver has installed.
And 'ndiswrapper -l' says that the driver is installed, right? I saw your previous post and it listed 3 different drivers. Now that's definitely incorrect and each of them will try to interfere with your card and prevent it from working correctly. You need to remove all of them and install the right driver once again. Could you do that?

Once you have done it, please post:

sudo iwlist scan

sudo lshw -C network
'ndiswrapper -l' must list only 1 driver.

[dee_kay]

deekay
Not sure what to say, have you tried someone else's network or a different router. Im not even sure its a router problem, however it just seems funny. You said you can connect when WEP is turned off, so it seems to be an authentication problem.

Changing the key from 128 bit to 64 bit seemed to be the kick in the rear that was needed so I'll try reverting to 128 bit and see how that goes.

Rgds,
Dave

[SunnyRabbiera]

And 'ndiswrapper -l' says that the driver is installed, right? I saw your previous post and it listed 3 different drivers. Now that's definitely incorrect and each of them will try to interfere with your card and prevent it from working correctly. You need to remove all of them and install the right driver once again. Could you do that?

Once you have done it, please post:


'ndiswrapper -l' must list only 1 driver.

if you insist, I just got thrown off as there were 3 .inf files and I never did this before.
I guess I should re install the driver and put all the nonsense that comes along with it in the folder it is installed to except the other .inf files?

[kevdog]

You are going to have to try with each inf file individually, meaning remove two of them, try to install the driver, and then see if it works. If it does not, remove that driver, and then try with the second inf file and so on. All though this sounds painful it shouldn't take more than 10 minutes.

[SunnyRabbiera]

well I am more then sure its the wusb11v4.inf file as it did come up in ndisgtk as connected while the others did not.

[jw5801]

if you insist, I just got thrown off as there were 3 .inf files and I never did this before.
I guess I should re install the driver and put all the nonsense that comes along with it in the folder it is installed to except the other .inf files?

It doesn't matter what else is in the folder so long as wusb11v4.inf and wusb11v4.sys (and maybe wusb11v4.cat) are there. Anything else will be ignored when you run:

sudo ndiswrapper -i wusb11v4.inf

[SunnyRabbiera]

alright, I un installed the driver and re installed the drive, but I still get nothing when typing in lshw -C network.
I am more then sure the wusb11v4.inf file is the right one, so what does this tell you folks.
You know I am about to give this one up and tell the owner to either install XP or get another wireless adapter.

[kevdog]

I thought you were working at the command line. You've taken a look at my other tutorial about installation of ndiswrapper?
http://ubuntuforums.org/showthread.php?t=574501

[SunnyRabbiera]

yeh I am working from the command line, the ndisgtk is there for further confirmation and not installation. I only installed it as I know the person I am giving this to wont understand command line too well.
I am giving them lessons yes but I do have some gui front ends to some things just in case.
Now installing ndiswrapper is a non issue, I just have the version of ndiswrapper in the repos installed.
Now if I have to compile a newer version tell me, I know there is a more recent version of ndiswrapper out there but I am trying to avoid compiling due to the other computer not having many options connecting.

[rustybronco]

but I still get nothing when typing in lshw -C network.
I am more then sure the wusb11v4.inf file is the right one, so what does this tell you folks.
SonnyR are you doing ndisswrapper on linux mint or 7.10 ?, remember... lshw -class network on mint.
not to leave any stone unturned the l is a lower case "L".

now time for me to butt out.

[SunnyRabbiera]

SonnyR are you doing ndisswrapper on linux mint or 7.10 ?, remember... lshw -class network on mint.
not to leave any stone unturned the l is a lower case "L".

now time for me to but out.

no I got rid of mint on the other computer and put gutsy on it just in case the two have more differences

[wieman01]

For this device I doubt that you have to install the latest, latest version of ndiswrapper. I think the current should do as it works for other users with WUSB11 devices. Really odd.

What does a "ndiswrapper -l" yield right now?

[SunnyRabbiera]

For this device I doubt that you have to install the latest, latest version of ndiswrapper. I think the current should do as it works for other users with WUSB11 devices. Really odd.

What does a "ndiswrapper -l" yield right now?

almost the same as before:
wusb11v4 : driver installed
device (13B1:000B) present

the others i listed are gone now as I removed them and re installed the wusb11v4 driver.
I even did a restart...
so what now?

[wieman01]

Please do a scan for us:

sudo iwlist scan

sudo lshw -C network
Please post both. Let's see.

[kevdog]

Ok, do a

sudo modprobe ndiswrapper

Confirm with
lsmod | grep ndis

Then do a iwlist scan

If this doesnt work do a
sudo modprobe -r ndiswrapper
sudo rm -R /etc/ndiswrapper/*

Then reload a different driver into ndiswrapper
sudo ndiswrapper -i <different_driver>
sudo modprobe ndiswrapper

Just checking -- no errors with
sudo depmod -a

[SunnyRabbiera]

wieman01
alright, once more i get no output with lshw -C network
and this is what i get with iwlist scan:
lo interface doesnt support scanning

kevdog
alright, but all this is going in circles...

[wieman01]

Another thought... Do you have the right version of the driver? There is a version number on the back of the device.

Also, try another USB port. Is the LED lit when it's connected?

[SunnyRabbiera]

Another thought... Do you have the right version of the driver? There is a version number on the back of the device.

Also, try another USB port. Is the LED lit when it's connected?

yes its the right driver version, as the device a wusb11v4.
and yes the LED is lit no matter what port i put this in.
once again I am going in circles here.
now kevdog your guide on installing ndiswrapper suggested this command:
cd ~
mkdir driver
cd driver
I did not do this, all the files I installed are going to /etc/ndiswrapper
should I make the diver directory as you suggested or is that for when you compile ndiswrapper from source?

[kevdog]

I wouldnt worry about compiling ndiswrapper -- The guide was mentioned just for the end part.

Im not sure usb devices are going to show up with lshw -C network. After each ndiswrapper or modprobe statement have you checked dmesg for any errors??

I'm grasping the concept things are not working, but without any error messages or output to provide some help to me, we are getting stuck.

[wieman01]

When you plug in the device, what do the last 10 lines of...

dmseg
...yield?

And what about:

lsusb

[SunnyRabbiera]

I wouldnt worry about compiling ndiswrapper -- The guide was mentioned just for the end part.

Im not sure usb devices are going to show up with lshw -C network. After each ndiswrapper or modprobe statement have you checked dmesg for any errors??

I'm grasping the concept things are not working, but without any error messages or output to provide some help to me, we are getting stuck.

checked dmesg for errors, and here is what I got:
[3308.357270] ndiswrapper (load_wrap_driver: 118 ): couldnt load driver wusb11v4; check system log for messages from 'loadndisdrivers'

[kevdog]

Remove the driver, put all the drivers back in the folder and try again.

See what comes up with dmesg

[SunnyRabbiera]

alright I will do that as soon as possible...
this is giving me a bit of a headache though

[rustybronco]

Im not sure usb devices are going to show up with lshw -C network. I'm glad you said it, it was bugging me to no end.

[SunnyRabbiera]

alright I got no errors with dmesg when using the other two .inf files...
I am just going to stick with one of them I guess, but it still doesnt seem to want to do anything.
I think its time to throw in the towel with this thing though, maybe I should tell the owner of the other computer to invest in another wireless adapter.
luckily I can give them a list of stuff that will work with linux, I just wanted to see if I could get this one working before telling them to invest in another wireless adapter.

[wieman01]

alright I got no errors with dmesg when using the other two .inf files...
I am just going to stick with one of them I guess, but it still doesnt seem to want to do anything.
I think its time to throw in the towel with this thing though, maybe I should tell the owner of the other computer to invest in another wireless adapter.
luckily I can give them a list of stuff that will work with linux, I just wanted to see if I could get this one working before telling them to invest in another wireless adapter.
OK, I understand. It's probably a good thing to invest in another device for kernel 2.6.25 won't support "ndiswrapper" any longer. It some issue with the GPL and there has been a dispute going on between Torvald and the developers of "ndiswrapper" as far as I remember it correctly. So sooner or later, you will have to find another solution anyway.

EDIT:
You have seen this thead, haven't you?

https://help.ubuntu.com/community/WifiDocs/Device/Linksys_WUSB11v4_(ndiswrapper)

[wieman01]

Im not sure usb devices are going to show up with lshw -C network.
They do.

[rustybronco]

They do.Good to know I thought i was loosing my mind.
http://ubuntuforums.org/showpost.php?p=4436877&postcount=31

[wieman01]

Good to know I thought i was loosing my mind.
http://ubuntuforums.org/showpost.php?p=4436877&postcount=31
I'll confirm that once again when I sit in front of my personal computer.

[kevdog]

Im not ready to throw in the towel just yet!! If you want another crack at it lets try!!


Kernel not supporting ndiswrapper??? Seems like this was ever the case there would be a patch available to make sure ndiswrapper would work. ndiswrapper is a life saver for many. You've seen my poll about chipsets that dont work:
http://ubuntuforums.org/showthread.php?t=594857

Its amazing the ra chipsets top the list when these are supposed to be natively supported in the kernel. Broadcom is next -- no surprise -- Intel chipsets are 3rd, and again aren't many of these supposed to be supported by the kernel?? It would seem ludicrous to remove ndiswrapper support!!

[wieman01]

Im not ready to throw in the towel just yet!! If you want another crack at it lets try!!


Kernel not supporting ndiswrapper??? Seems like this was ever the case there would be a patch available to make sure ndiswrapper would work. ndiswrapper is a life saver for many. You've seen my poll about chipsets that dont work:
http://ubuntuforums.org/showthread.php?t=594857

Its amazing the ra chipsets top the list when these are supposed to be natively supported in the kernel. Broadcom is next -- no surprise -- Intel chipsets are 3rd, and again aren't many of these supposed to be supported by the kernel?? It would seem ludicrous to remove ndiswrapper support!!
Yeah, it's a life saver and I favor it as well, however, 2.6.24 will come with a long list of new wireless drivers/stacks so it will be less necessary. But I am with you, I am watching your poll.

See this for more:

http://kerneltrap.org/Linux/NDISwrapper_and_the_GPL

Linus T. is very unhappy with ndiswrapper's policy.

[kevdog]

Seems like Linus retracted his feeling about the abandonement of ndiswrapper:
http://lkml.org/lkml/2008/3/4/300

[wieman01]

Seems like Linus retracted his feeling about the abandonement of ndiswrapper:
http://lkml.org/lkml/2008/3/4/300
Ah, now that's interesting. Let's hope for the best, Linux cannot afford to lose an invaluable module like "ndiswrapper". It's my best friend too, it lets my Desktop breath fresh internet air, it could not survive without it.

[rustybronco]

Im not ready to throw in the towel just yet!! If you want another crack at it lets try!!

http://ubuntuforums.org/showpost.php?p=4435023&postcount=26
me too...
irq problem possibly?

[wieman01]

http://ubuntuforums.org/showpost.php?p=4435023&postcount=26
me too...
irq problem possibly?
But where should we continue? I am really running out of smart ideas, Rusty.

[rustybronco]

But where should we continue? I am really running out of smart ideas, Rusty.She's frustrated enough and i don't think we need to tax her just for answers, but I really would like to have that machine in front of me to find out what is causing it.
boot options irq=nopoll, bios settings. who knows where to start.

[SunnyRabbiera]

alright, I decided to compile ndiswrapper on the other computer and guess what?
the adapter works now.
However It will not connect when the system is booting, and the only way to get it working again is if I enter the terminal and connect it the hard way.
Is there any way to enable ndiswrapper to run by default.
I tried echo "ndiswrapper" | sudo tee -a /etc/moduels as another post suggested but no luck

[SunnyRabbiera]

I have another poser, how the @#$% do I get the WEP?
I know how to get my WEP key in windows but have no idea how to get it here.

[wieman01]

She's frustrated enough and i don't think we need to tax her just for answers, but I really would like to have that machine in front of me to find out what is causing it.
boot options irq=nopoll, bios settings. who knows where to start.
I am with you. :-)

[wieman01]

I have another poser, how the @#$% do I get the WEP?
I know how to get my WEP key in windows but have no idea how to get it here.
Have you used Network Manager before? I mean the networking applet that most of us use... the one that comes with Ubuntu. You know what I mean? It lets you enter a WEP key and connect to your network.

[SunnyRabbiera]

Have you used Network Manager before? I mean the networking applet that most of us use... the one that comes with Ubuntu. You know what I mean? It lets you enter a WEP key and connect to your network.

Yes I know about network manager, I am not that stupid you know.
I just never this bit before
but what would the WEP be listed under?

[wieman01]

Yes I know about network manager, I am not that stupid you know.
I just never this bit before
By no means am I implying you are stupid.

Would it do a better job perhaps? I would give it a go if I were you and test it.

[SunnyRabbiera]

well the confusing bit is that I dont know what I am looking for on here, I know my ISP stuff but finding out the WEP key is a different story, never did that bit before.
here is what I got with the terminal, once I know what I am doing here i will get it:
NM Path: /org/freedesktop/NetworkManager/Devices/eth0
Type: Wired
Driver: 8139too
Active: yes
HW Address:

Capabilities:
Supported: yes
Carrier Detect: yes
Speed: 100 Mb/s

Wired Settings
Hardware Link: yes

IP Settings:
IP Address:
Subnet Mask:
Broadcast:
Gateway:
Primary DNS:
Secondary DNS:
what one of these I would use as the WEP?
and I put the catagories in only as I want this stuff private

[wieman01]

Hang on... you don't KNOW your key, is that the issue? I think I cannot help you there, usually it is put here:

sudo cat /etc/network/interfaces
But I don't know where NM or WICD would store it.

[SunnyRabbiera]

Hang on... you don't KNOW your key, is that the issue? I think I cannot help you there, usually it is put here:

But I don't know where NM or WICD would store it.

Yeh I dont know the key, and no nothing to see in cat /etc/network/interfaces
no key, just this:
auto lo
iface lo inet loopback


I never got down the key as before the WEP key was automatically detected by the wireless devices and I never had to jot it down.
but now i do and I have no idea what it is.

[wieman01]

Then you must ask the admin of the network for the key. Sorry I cannot help you there.

[SunnyRabbiera]

Then you must ask the admin of the network for the key. Sorry I cannot help you there.

yeh but I AM the admin of the network, this is the primary comp that is connected to the net and yes it is mine.
do you suggest I call my cable company, after all I am using cable internet you think they would have it?

[wieman01]

yeh but I AM the admin of the network, this is the primary comp that is connected to the net and yes it is mine.
do you suggest I call my cable company, after all I am using cable internet you think they would have it?
Is it still the default password? Then yes, the cable company would know it. You could also connect to the router via Ethernet and check for the password?

[SunnyRabbiera]

Is it still the default password? Then yes, the cable company would know it. You could also connect to the router via Ethernet and check for the password?

well I am conntected to the router, as i said this computer is the primary.
I have a cable modem that goes into a router and that router goes into my computer.
this is the master computer on the network.
as for the password being changed, I am not sure.
I could check with my cable company though

[SunnyRabbiera]

okay so there is no WEP key...
looks like i dont have one with some recent information I got...
but this thing is still giving me a headache, one second this thing is working and the next its not...

oy

[kevdog]

Cable modem -> Router -> Primary Computer. Is the wireless access point contained on the Router or Cable Modem? Don't you own the router?

[SunnyRabbiera]

Cable modem -> Router -> Primary Computer. Is the wireless access point contained on the Router or Cable Modem? Don't you own the router?

I own the router yes, and i technically own the modem too as thats a part of the plan I have.
but if there is no WEP to worry about what about this part of the guide you guys linked me to:
Using gedit put the required record into /etc/network/interfaces file: (note that the Xs are your actual WEP key.)

user@ubuntu:~/wusb11/WUSB11v4_08272004/Drivers$ gksudo gedit /etc/network/interfaces

Create a record that looks like this: (Note normally we would use the keyword "wireless-key" but this device needs "wireless-key1".)

iface wlan0 inet dhcp
wireless-essid My_Essid
wireless-key1 XXXXXXXXXXXXXXXXXXXXXXXXXX
auto wlan0


for this should i just leave the wireless key blank if I have no WEP?

[kevdog]

If there is no WEP do not include the line.

I dont know what you mean about no WEP??

Why are you using WEP anyways -- you should really go for WPA2 if possible.

[SunnyRabbiera]

If there is no WEP do not include the line.

I dont know what you mean about no WEP??

Why are you using WEP anyways -- you should really go for WPA2 if possible.

I was going by the guide, I was working blind here as I never did this before.
it was this guide:
here (https://help.ubuntu.com/community/WifiDocs/Device/Linksys_WUSB11v4_(ndiswrapper))

i followed all the steps suggested in it, the WEP part threw me off

I never set up a WEP on this thing I guess, I know I was supposed to but I never knew how to do it in linux (much like any protocol) until now

[kevdog]

So are you good to go now?

[wieman01]

Could you do a scan please and post the reults:

sudo iwlist scan
Please highlight the wireless AP that belongs to you. Just to see if WEP is really turned on.

[SunnyRabbiera]

no not from what I saw, I will have to post the output a bit later.

[maartenlameris]

I have a problem with a wireless network using a wep encryption. and the ubuntu networmanager.
when i connect to a wep network the networkmanager asks for the key when i enter the key it asks a minute or so and asks for the key again.

when i input the key with # iwconfig eth1 key hexkey
after i input the key in the networkmanager i get a ip adress and the connection works!

is there a easyer fix for this problem?

Thx

[kevdog]

definitely sounds like a NWM issue. Do you always connect to the same ESSID or do you use roaming a lot?

[maartenlameris]

no, its alway's the same ESSID

[kevdog]

So if its always the same ESSID, why dont you try this addition to the /etc/network/interfaces file

auto <interface>
iface <interface> inet dhcp
wireless-ssid "ESSID"
wireless-key HEX_KEY_HERE

You need to fill in for <interface> ESSID and HEX_KEY_HERE

Save the file, and then reboot to be on the safe side (although you could probably restart the dbus, but lets just be on the safe side)!!

[Malikius]

from MSHOME to something different that I want to change? I looked at the forums and couldn't find it. Please guide me to a area or a step by step tutorial.

[jw5801]

from MSHOME to something different that I want to change? I looked at the forums and couldn't find it. Please guide me to a area or a step by step tutorial.

What does this have to do with the original how-to? Please start a new thread if you have a different issue.

[kevdog]

What does this have to do with the original how-to? Please start a new thread if you have a different issue.

+1 :)

[fretnoise]

Doesn't work for my WPA setup (Atheros chipset).

Here's the commands I've run and their outputs:

--> lshw -C network

*-network:0 DISABLED
description: Ethernet interface
product: 82801DB PRO/100 VE (LOM) Ethernet Controller
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:02:08.0
logical name: eth0
version: 81
serial: 00:07:e9:e9:96:f1
size: 10MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.17-k4-NAPI duplex=half firmware=N/A latency=64 link=no maxlatency=56 mingnt=8 module=e100 multicast=yes port=MII speed=10MB/s
*-network:1 DISABLED
description: Wireless interface
product: AR2413 802.11bg NIC
vendor: Atheros Communications, Inc.
physical id: c
bus info: pci@0000:02:0c.0
logical name: wifi0
version: 01
serial: 00:11:50:6f:a3:1e
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=ath_pci driverversion=0.9.4.5 (0.9.3.2) latency=168 maxlatency=28 mingnt=10 module=ath_pci multicast=yes wireless=IEEE 802.11g


so, from the how to, the logical interface is "wifi0".

next, I run:
--> ifconfig wifi0 down
--> dhclient -r wifi0

There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/wifi0/
Sending on LPF/wifi0/
Sending on Socket/fallback


Next, created file /etc/wpa_supplicant.conf

ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="Fretnoise"
proto=WPA
key_mgmt=WPA-PSK
psk="welcome"
pairwise=TKIP
group=TKIP
}


Next, I run
--> wpa_supplicant -w -Dmadwifi -iwifi0 -c/etc/wpa_supplicant.conf
using "-Dmadwifi" because I have the ath_pci driver, and "-iwifi0" because that's the logical
name...

But, the output is:

ioctl[SIOCSIWPMKSA]: Invalid argument
ioctl[SIOCSIWMODE]: Invalid argument
Could not configure driver to use managed mode
ioctl[SIOCGIWRANGE]: Invalid argument
ioctl[IEEE80211_IOCTL_SETPARAM]: Invalid argument
ioctl[SIOCSIWAP]: Invalid argument
Failed to initialize driver interface


Hm... so, instead, I try
--> wpa_supplicant -w -Dmadwifi -iath0 -c/etc/wpa_supplicant.conf

which gives:

ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument
Association request to the driver failed
Authentication with 00:00:00:00:00:00 timed out.
ioctl[SIOCSIWSCAN]: Network is down
Failed to initiate AP scan.


Because it complains that network is down, I run
--> ifconfig ath0 up

and then again
--> wpa_supplicant -w -Dmadwifi -iath0 -c/etc/wpa_supplicant.conf

which now shows

Trying to associate with 00:13:49:ee:7f:74 (SSID='Fretnoise' freq=2437 MHz)
ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument
Association request to the driver failed
Associated with 00:13:49:ee:7f:74
WPA: Key negotiation completed with 00:13:49:ee:7f:74 [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:13:49:ee:7f:74 completed (auth) [id=0 id_str=]


seems to look good, but the wpa_supplicant command doesn't stop, so I have to hit
Control-C.

Before I hit control C, so while wpa_supplicant was running, I run the following on another
terminal:

--> iwconfig

lo no wireless extensions.

eth0 no wireless extensions.

wifi0 no wireless extensions.

ath0 IEEE 802.11g ESSID:"Fretnoise" Nickname:""
Mode:Managed Frequency:2.437 GHz Access Point: 00:13:49:EE:7F:74
Bit Rate:1 Mb/s Tx-Power:9 dBm Sensitivity=1/1
Retry: off RTS thr: off Fragment thr: off
Encryption key:EF11-3FE9-DAA2-C8F1-AFD6-6A8C-C5CF-022E Security mode:restricted
Power Management: off
Link Quality=22/70 Signal level=-76 dBm Noise level=-98 dBm
Rx invalid nwid:10896 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


after I've hit Control-C to stop wpa_supplicant, I run iwconfig on another terminal again, and
now I get:

ath0 IEEE 802.11g ESSID:"Fretnoise" Nickname:""
Mode:Managed Channel:0 Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:9 dBm Sensitivity=1/1
Retry: off RTS thr: off Fragment thr: off
Encryption key: off
Power Management: off
Link Quality=0/70 Signal level=-99 dBm Noise level=-99 dBm
Rx invalid nwid:15241 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0



After this, I've followed with the other commands:
--> ifconfig wifi0 up
--> iwconfig wifi0 mode Managed
--> dhclient wifi0

For dhclient, the output was:

There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/wifi0/
Sending on LPF/wifi0/
Sending on Socket/fallback
DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 12
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


same result for using ath0 as interface, and while wpa_supplicant has associated
access point, but hasn't stopped yet.



Here's some facts:

(1) I was able to connect using WPA before using Network Manager, then wasn't. After about 20
tries, it worked again, but now it doesn't work anymore.

(2) The HOWTO instructed me to use the logical name "wifi0" for <interface> - but that did not
work for wpa_supplicant's -i argument

(3) wpa_supplicant doesn't quick after it's associated the access point

(4) when I run wpa_supplicant in the background, it associates AP, but running dhclient doesn't
get a DHCHOFFER...

(5) When I do a scan, the output is:

Cell 03 - Address: 00:13:49:EE:7F:74
ESSID:"Fretnoise"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=15/70 Signal level=-80 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK



(6) wifi0: unknown hardware address type 801 --> is this really bad??



What am I doing wrong?

Thank's a bunch

[kevdog]

For madwifi -- the actual hardware address is wifi0, however the way the driver is made it creates virtual interfaces to talk with the physical device. The first virtual interface made is ath0. You can only physically change the settings in the device by working through the ath0 interface and not wifi0. Please note this is special to the madwifi driver.

Next there is one thing you posted that troubles me:

*-network:1 DISABLED
description: Wireless interface
product: AR2413 802.11bg NIC
vendor: Atheros Communications, Inc.
physical id: c
bus info: pci@0000:02:0c.0
logical name: wifi0
version: 01
serial: 00:11:50:6f:a3:1e
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=ath_pci driverversion=0.9.4.5 (0.9.3.2) latency=168 maxlatency=28 mingnt=10 module=ath_pci multicast=yes wireless=IEEE 802.11g

It states disabled. Does it still say this if you put
sudo ifconfig ath0 up

Does it still come back as disabled?

[fretnoise]

It comes up as enabled when I run ifconfig ath0 up.

After I sent this post, I rebooted later, and nm_applet and
Network Manager have automatically succeeded in setting up
wireless. But, it sporadically worked before, so I thought I was
just lucky.... but, after 4 reboots, it still connects fine. And I did
not run anything manually... confused but pleasantly surprised.

So, I guess I'm good for now. Thank's for writing the HOWTO, even
though it's confusing when configuring for ath0 and wifi0, since
the same interface name cannot be used as stated in the HOWTO.
Maybe the HOWTO could reflect this?

Thank's

[kevdog]

Yea I probably should change the instructions however with madwifi drivers they are the exception. Always exceptions to the rules which stick when trying to write a "general"tutorial

[archman]

when i do sudo dhclient it says cannot read or parse file /etc/wpa_supplicant.conf...
How can i solve that?

[fretnoise]

Ok, starting today it's not working again. Today I booted, logged in, and nm_applet connected me. After some hours, networking wasn't working, although nm_applet showed me the "staircaise". Trying to reconnect with nm_applet did not work. Reboot did not work (tried it twice).

Since I could not get manual configuration working either, I'm out in the cold. Could you let me know what I did wrong when I tried to configure it manually? Should I post any syslog here? (I have logs for both successful and failed wireless networking).

Thank's

[kevdog]

when i do sudo dhclient it says cannot read or parse file /etc/wpa_supplicant.conf...
How can i solve that?


Can you post your wpa_supplicant.conf file?

[kevdog]

Ok, starting today it's not working again. Today I booted, logged in, and nm_applet connected me. After some hours, networking wasn't working, although nm_applet showed me the "staircaise". Trying to reconnect with nm_applet did not work. Reboot did not work (tried it twice).

Since I could not get manual configuration working either, I'm out in the cold. Could you let me know what I did wrong when I tried to configure it manually? Should I post any syslog here? (I have logs for both successful and failed wireless networking).

Thank's

Just an idea since I see that you like the gui network manager gives you (a lot of people do). Uninstall network manager and try WICD. This provides a GUI, and I bet you will find this much more reliable.

[archman]

Can you post your wpa_supplicant.conf file?

ap_scan=1
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=0
network={
key_mgmt=IEEE8021X
eap=TTLS
anonymous_identity="xxx@yyy.yy"
phase2="auth=PAP"
identitctrl_interface=/var/run/wpa_supplicant
ctrl_interfy="xxx@yyy.yy"
password="xxx"
}

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
network={
ssid="eduroam"
proto=WPA WPA2
key_mgmt=WPA-EAP
group=CCMP TKIP
eap=TTLS
anonymous_identity="xxx@yyy.yy"
phase2="auth=PAP"
identity="xxx@yyy.yy"
password="xxx"
}

[ribbonsandbows]

stumped in this, I got as far as:
sudo iwconfig <interface> essid "name"
to be told its not supported - which is very nice, the wireless is connecting but I am not able to use firefox, or any other form of internet useage.

will carry on searching but any suggestions would be gratefully recieved as I have 5 more of these waiting for the same treatment.
driver is a b44, 1.01

[kevdog]

sudo iwconfig <interface> essid "name"

name is the physical name of the access point?

This line should be something like:
sudo iwconfig wlan0 essid "RouterLan"

That's an example!!

[kevdog]

ap_scan=1
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=0
network={
key_mgmt=IEEE8021X
eap=TTLS
anonymous_identity="xxx@yyy.yy"
phase2="auth=PAP"
identitctrl_interface=/var/run/wpa_supplicant
ctrl_interfy="xxx@yyy.yy"
password="xxx"
}

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
network={
ssid="eduroam"
proto=WPA WPA2
key_mgmt=WPA-EAP
group=CCMP TKIP
eap=TTLS
anonymous_identity="xxx@yyy.yy"
phase2="auth=PAP"
identity="xxx@yyy.yy"
password="xxx"
}

Do you need to repeat the following information:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1

I don't have a lot of experience with TTLS, EAP.

[zoe-scutterbug]

hi kevdog

just had to send a whopping big thank you :)

sorry It had to be said
zo

[ante.wessels]

Hi,

Some time ago I reported I got wifi working on a Toshiba with rtl8187B, by using Xcuervo's modified driver and Kevdog's manual commands.

http://ubuntuforums.org/showthread.php?t=630791&page=2

Now I ran into something I didn't expect. Playing with logical interfaces in /etc/network/interfaces (not effecting wlan0), I stopped the NetworkManager with

sudo /etc/dbus-1/event.d/26NetworkManagerDispatcher stop
sudo /etc/dbus-1/event.d/25NetworkManager stop

That second command did not always work, then I added:
killall NetworkManager

I find that having killed NetworkManager this way, loading Xcuervo's driver does not result in bringing up wlan0 according to the ifconfig command. iwlist scan does not work either, it reports: wlan0 Failed to read scan data: Operation not permitted

If I start NetworkManager again, loading the modified driver does result in ifconfig showing wlan0.

So it seems the modified driver needs NetworkManager, even to use the manual commands.

[kevdog]

You might want to confirm that with cuervo, however its possible you have to load the driver by hand -- (if thats what the Network Manager Process is doing). I'd be surprised if operation of the driver is really dependent on NM as there are other GUIs available such as WICD, wifi radar.

That being said, Ive never had any personal experience with cuervo's driver or used it, so I can't say for certain.

[ante.wessels]

That being said, Ive never had any personal experience with cuervo's driver or used it, so I can't say for certain.

Oops, my stupidity ;-)

After loading the driver I have to bring it up first, of course, with ifconfig wlan0 up, before ifconfig can show it...

[imdano]

What commands are you using to load the cuervo driver manually? Reading his site it looks like it relys on commands getting executed in /etc/network/interfaces. NetworkManager makes use of that file to determine which interfaces to use, and what commands to run when bringing them up/down. Without NM running, those commands won't get executed unless you run them, which means the driver won't load correctly. I'm not an expert on the inner-workings of NM, but from what I've read of their source code they don't mess around with anything at the driver level. They just make use of what's already there.

[WadiJM]

Hi I followed the tutorial trying to conect to wpa2 but when I type



sudo wpa_supplicant -w -Dwext -ieth1 -c /etc/wpa_supplicant.conf


the terminal stops there with no output. When I open a terminal and type the next commands it can't obtain an ip. Any help would be appreciated.
Thanks in advance,
Wadi

[kevdog]

imdano

Isn't that what differentiates ifconfig <interface> up vs ifup <interface>?? Doesn't the latter command ifup read the network interfaces file when bringing up the interface and use this file as a configuration file to set the parameters?? This is what I always believed. So I guess if you needed to bring up the interface you would us ifup rather than ifconfig up.

Am I wrong in this assumption?

[kevdog]

wadijm

If you could run the following command:

sudo wpa_supplicant -w -Dwext -ieth1 -c /etc/wpa_supplicant.conf -dd

and also post your
/etc/wpa_supplicant.conf file, that would be great.

[imdano]

imdano

Isn't that what differentiates ifconfig <interface> up vs ifup <interface>?? Doesn't the latter command ifup read the network interfaces file when bringing up the interface and use this file as a configuration file to set the parameters?? This is what I always believed. So I guess if you needed to bring up the interface you would us ifup rather than ifconfig up.

Am I wrong in this assumption?Yes, that is the difference. Didn't think about that, but using ifup would probably work just as well.

[ante.wessels]

What commands are you using to load the cuervo driver manually? Reading his site it looks like it relys on commands getting executed in /etc/network/interfaces. NetworkManager makes use of that file to determine which interfaces to use, and what commands to run when bringing them up/down. Without NM running, those commands won't get executed unless you run them, which means the driver won't load correctly. I'm not an expert on the inner-workings of NM, but from what I've read of their source code they don't mess around with anything at the driver level. They just make use of what's already there.

The driver directory has a wlan0up script, so that is the one I use, manually. The /etc/network/interfaces file has no wlan0 entry on my machine, NM does not depend on it. If I disable the driver, start NM, NM does not show wlan0. If I then load the driver, NM shows wlan0. So NM spots the interfaces when they become available (without needing the /etc/network/interfaces file).

I guess we are going of topic ;-)

[kevdog]

Guess I'll have to redownload the driver and take a look at that script.

[WadiJM]

Firs of all thank you kevdog for your quick reply.
Today after reinstalling and changing 100 configuration files I get the following output


wadi@wadi-laptop:~$ sudo wpa_supplicant -w -Dwext -ieth1 -c /etc/wpa_supplicant.conf
l2_packet_receive - recvfrom: Network is down
ioctl[SIOCSIWSCAN]: No such device
Failed to initiate AP scan.
ioctl[SIOCGIWSCAN]: No such device
ioctl[SIOCSIWSCAN]: No such device
Failed to initiate AP scan.
CTRL-EVENT-TERMINATING - signal 2 received


This is my /etc/wpa_suplicant.conf file



ctrl_interface=/var/run/wpa_supplicant

network={
ssid="aco"
psk="pepe"
key_mgmt=WPA-PSK
proto=RSN
pairwise=CCMP
}



Regarding to the command sudo wpa_supplicant -w -Dwext -ieth1 -c /etc/wpa_supplicant.conf -dd the output is the following:



Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
Line: 3 - start of a new network block
ssid - hexdump_ascii(len=3):
61 63 6f aco
PSK (ASCII passphrase) - hexdump_ascii(len=9): [REMOVED]
key_mgmt: 0x2
proto: 0x2
pairwise: 0x10
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='aco'
Initializing interface (2) 'eth1'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=22 WE(source)=16 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1c:bf:13:b5:5b
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Added interface eth1
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=12
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 651 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:1b:11:d3:b8:89 ssid='aco' wpa_ie_len=24 rsn_ie_len=22 caps=0x11
skip RSN IE - PTK cipher mismatch
1: 00:02:72:55:9b:fb ssid='HectorWiFi' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:1b:11:d3:b8:89 ssid='aco' wpa_ie_len=24 rsn_ie_len=22 caps=0x11
skip - non-WPA network not allowed
1: 00:02:72:55:9b:fb ssid='HectorWiFi' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
No suitable AP found.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 980 bytes of scan results (3 BSSes)
Scan results: 3
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:1b:11:d3:b8:89 ssid='aco' wpa_ie_len=24 rsn_ie_len=22 caps=0x11
skip RSN IE - PTK cipher mismatch
1: 00:1a:70:5e:3a:4c ssid='elzefiro' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
2: 00:02:72:55:9b:fb ssid='HectorWiFi' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:1b:11:d3:b8:89 ssid='aco' wpa_ie_len=24 rsn_ie_len=22 caps=0x11
skip - non-WPA network not allowed
1: 00:1a:70:5e:3a:4c ssid='elzefiro' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
2: 00:02:72:55:9b:fb ssid='HectorWiFi' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 1273 bytes of scan results (4 BSSes)
Scan results: 4
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:1b:11:d3:b8:89 ssid='aco' wpa_ie_len=24 rsn_ie_len=22 caps=0x11
skip RSN IE - PTK cipher mismatch
1: 00:1a:70:5e:3a:4c ssid='elzefiro' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
2: 00:16:cf:56:d7:b1 ssid='Wi-Fi Arnet' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
3: 00:02:72:55:9b:fb ssid='HectorWiFi' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:1b:11:d3:b8:89 ssid='aco' wpa_ie_len=24 rsn_ie_len=22 caps=0x11
skip - non-WPA network not allowed
1: 00:1a:70:5e:3a:4c ssid='elzefiro' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
2: 00:16:cf:56:d7:b1 ssid='Wi-Fi Arnet' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
3: 00:02:72:55:9b:fb ssid='HectorWiFi' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 943 bytes of scan results (3 BSSes)
Scan results: 3
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:1b:11:d3:b8:89 ssid='aco' wpa_ie_len=24 rsn_ie_len=22 caps=0x11
skip RSN IE - PTK cipher mismatch
1: 00:16:cf:56:d7:b1 ssid='Wi-Fi Arnet' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
2: 00:02:72:55:9b:fb ssid='HectorWiFi' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:1b:11:d3:b8:89 ssid='aco' wpa_ie_len=24 rsn_ie_len=22 caps=0x11
skip - non-WPA network not allowed
1: 00:16:cf:56:d7:b1 ssid='Wi-Fi Arnet' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
2: 00:02:72:55:9b:fb ssid='HectorWiFi' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 651 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:1b:11:d3:b8:89 ssid='aco' wpa_ie_len=24 rsn_ie_len=22 caps=0x11
skip RSN IE - PTK cipher mismatch
1: 00:02:72:55:9b:fb ssid='HectorWiFi' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:1b:11:d3:b8:89 ssid='aco' wpa_ie_len=24 rsn_ie_len=22 caps=0x11
skip - non-WPA network not allowed
1: 00:02:72:55:9b:fb ssid='HectorWiFi' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 650 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:1b:11:d3:b8:89 ssid='aco' wpa_ie_len=24 rsn_ie_len=22 caps=0x11
skip RSN IE - PTK cipher mismatch
1: 00:02:72:55:9b:fb ssid='HectorWiFi' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:1b:11:d3:b8:89 ssid='aco' wpa_ie_len=24 rsn_ie_len=22 caps=0x11
skip - non-WPA network not allowed
1: 00:02:72:55:9b:fb ssid='HectorWiFi' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 651 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:1b:11:d3:b8:89 ssid='aco' wpa_ie_len=24 rsn_ie_len=22 caps=0x11
skip RSN IE - PTK cipher mismatch
1: 00:02:72:55:9b:fb ssid='HectorWiFi' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:1b:11:d3:b8:89 ssid='aco' wpa_ie_len=24 rsn_ie_len=22 caps=0x11
skip - non-WPA network not allowed
1: 00:02:72:55:9b:fb ssid='HectorWiFi' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
No suitable AP found.
Setting scan request: 5 sec 0 usec

Thanks in advance,
Regards,
Wadi

[archman]

ap_scan=1
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=0
network={
key_mgmt=IEEE8021X
eap=TTLS
anonymous_identity="xxx@yyy.yy"
phase2="auth=PAP"
identitctrl_interface=/var/run/wpa_supplicant
ctrl_interfy="xxx@yyy.yy"
password="xxx"
}

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
network={
ssid="eduroam"
proto=WPA WPA2
key_mgmt=WPA-EAP
group=CCMP TKIP
eap=TTLS
anonymous_identity="xxx@yyy.yy"
phase2="auth=PAP"
identity="xxx@yyy.yy"
password="xxx"
}

Do you need to repeat the following information:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1

I don't have a lot of experience with TTLS, EAP.

here's the output:
(attachment)

[kevdog]

Ok,

First post
lshw -C network
iwlist scan
ifconfig

And modify the wpa_supplicant.conf file to connect to only one AP for now. Lets just go with the basics. Can you connect to an unencrypted network?

[archman]

Ok,

First post
lshw -C network
iwlist scan
ifconfig

And modify the wpa_supplicant.conf file to connect to only one AP for now. Lets just go with the basics. Can you connect to an unencrypted network?

thank you for your help, but i solved it with: http://ubuntuforums.org/showthread.php?t=708148#post4410798

[fretnoise]

Just an idea since I see that you like the gui network manager gives you (a lot of people do). Uninstall network manager and try WICD. This provides a GUI, and I bet you will find this much more reliable.

Thank's kevdog. Wireless networking is playing with me... as soon
as I post that I have problems again, it starts working. It's been
working fine so far. If it fails again, I'll try WICD.

[Cain67]

hi, im using a macbook with madwifi, and am connecting to a WPA1 network..

connecting via network manager doesnt seem to work...
so i tried what you said...

and it was all going fine untill i entered this command:

sudo wpa_supplicant -w -D madwifi -i wifi0 -c/etc/wpa_supplicant.conf -dd

and then got this:::


Initializing interface 'wifi0' conf '/etc/wpa_supplicant.conf' driver 'madwifi' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ap_scan=1
ctrl_interface='/var/run/wpa_supplicant'
Line: 4 - start of a new network block
ssid - hexdump_ascii(len=3):
56 56 56 VVV
scan_ssid=0 (0x0)
proto: 0x1
key_mgmt: 0x2
PSK (ASCII passphrase) - hexdump_ascii(len=9): [REMOVED]
pairwise: 0x8
group: 0x8
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='VVV'
Initializing interface (2) 'wifi0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
ioctl[SIOCSIWMODE]: Operation not supported
Could not configure driver to use managed mode
ioctl[SIOCGIWRANGE]: Operation not supported
WEXT: Operstate: linkmode=1, operstate=5
ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
wpa_driver_madwifi_init: failed to set wpa_supplicant-based roaming
ioctl[SIOCSIWAP]: Operation not supported
WEXT: Operstate: linkmode=0, operstate=6
Failed to initialize driver interface
Failed to add interface wifi0
Cancelling scan request
Cancelling authentication timeout


any help would be great... as i am unable to connect via anything other than a cable.

[kevdog]

This line:
sudo wpa_supplicant -w -D madwifi -i wifi0 -c/etc/wpa_supplicant.conf -dd

is likely supposed to be:
sudo wpa_supplicant -w -D madwifi -i ath0 -c/etc/wpa_supplicant.conf -dd

[kingweee]

First of all, thank you to all those that have provided help in this thread.

Unfortunately, I have a problem with my manual configuration. Specifically, I cannot associate with an OPEN or WEP APs after first connecting to a WPA AP.

Process:

sudo dhclient -r ath0
sudo ifconfig ath0 down
sudo wpa_supplicant -Dwext -iath0 -c/etc/wpa_supplicant.conf -dd
sudo ifconfig ath0 up
sudo iwconfig ath0 mode Managed
sudo dhclient ath0

I have absolutely no problem associating with "Jamnet", my home AP. However when I close wpa_supplicant (ctrl_c) and:

sudo dhclient -r ath0
sudo ifconfig ath0 down
sudo ifconfig ath0 up
sudo iwconfig interface essid "freenet"
sudo iwconfig interface mode Managed
sudo dhclient ath0

I cannot associate with the AP 'freenet'. Iwconfig lists freenet under the essid, but nothing under "Access Point". Further, it lists the incorrect "Link Quality", showing the quality for Jamnet rather than the weaker signal of freenet. I have previously also had the problem with associating with WEP networks after using wpa_supplicant.

If I do want to associate with WEP or OPEN networks after running wpa_supplicant, I am forced to reboot my machine. Once I reboot, I can easily connect to the OPEN and WEP networks. However, if I connect to my WPA network, I cannot go back to OPEN or WEP networks.

wpa_supplicant.conf

//
ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="Jamnet"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk="testtest"
pairwise=TKIP
group=TKIP
}
//

lshw -C network

//
*-network
description: Wireless interface
product: AR5212/AR5213 Multiprotocol MAC/baseband processor
vendor: Atheros Communications, Inc.
physical id: 0
bus info: pci@0000:04:00.0
logical name: wifi0
version: 01
serial: 00:20:a6:60:c2:f4
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=ath_pci ip=192.168.1.225 latency=168 maxlatency=28 mingnt=10 module=ath_pci multicast=yes wireless=IEEE 802.11g
//

[kevdog]

Ok a couple of things I would try:

This particular line:
sudo wpa_supplicant -Dwext -iath0 -c/etc/wpa_supplicant.conf -dd

Since you know it works, you could probably drop the -dd option since you no longer need the debugging info, and instead fork it to the background with the -Bw option.

Also, you driver is ath_pci or madwifi, not wext in your case. So I would use this as follows:

sudo wpa_supplicant -Bw -Dmadwifi -iath0 -c/etc/wpa_supplicant.conf

Next, when you are done with wpa_supplicant (or done connecting with WPA), kill the wpa_supplicant handshake with:

sudo killall wpa_supplicant

This line would go right under the sudo dhclient -r ath0 line.

[kingweee]

Ok a couple of things I would try:

This particular line:
sudo wpa_supplicant -Dwext -iath0 -c/etc/wpa_supplicant.conf -dd

Since you know it works, you could probably drop the -dd option since you no longer need the debugging info, and instead fork it to the background with the -Bw option.

Also, you driver is ath_pci or madwifi, not wext in your case. So I would use this as follows:

sudo wpa_supplicant -Bw -Dmadwifi -iath0 -c/etc/wpa_supplicant.conf

Next, when you are done with wpa_supplicant (or done connecting with WPA), kill the wpa_supplicant handshake with:

sudo killall wpa_supplicant

This line would go right under the sudo dhclient -r ath0 line.


Thank you very much good sir, the problem has been solved.

You are a gentleman and a scholar.

[madscientist]

I feel a little left out in the cold, trying to use Ubuntu in a traditional Enterprise environment, but nevertheless I persevere!!

You m ight want to add a note to your guide that if you are working in an environment using NIS, and you are using Hardy, and you want to disable NetworkManager, then you also have to add this line to /etc/defaults/nis:


YPBINDARGS=-no-dbus

If you don't do that then ypbind will wait around forever for NetworkManager to report via dbus that the network is up, and it will never bind.

This new behavior of ypbind is confusing, and I don't think I like the requirement that NetworkManager seems to make, that all upper-layer applications who require networking services have to be modified to have special GNU/Linux-specific awareness (for dbus/NM) or they don't work correctly.

I haven't considered the problem completely but it just FEELS like, if your implementation requires this level of cooperation, you're doing something wrong and need to step back and reconsider from first principles.

[kevdog]

Sorry, but I have no experience with NIS or ypbind. You would have to elaborate on these two programs further. Thanks.

[steveo10078]

Hey, i'm pretty much a noob to ubuntu and linux on a whole really so please excuse my ignorance. When i got ubuntu, my wireless wouldnt work, so my friend took the windows drivers and installed them using ndiswrapper, and installed wifi radar, and thats the only way i can connect. The only problem with this is that i have to go into terminal and type in:
code: sudo modprobe ndiswrapper
every time i start my comp.

is there a way i can automate this, or would i do this the same way it was dome as shown above?

i would apreciate the help because so far thats one of the only problems i have with ubuntu so far :KS

[madscientist]

NIS, or Network Information Services, is the granddaddy of distributed information services: it was around long before, and serves the same type of niche as, Active Directory. Originally developed by Sun, it was called "Yellow Pages", or YP, until Sun was sued by AT&T (I suppose--I don't remember the details) over using "Yellow Pages" which they had trademarked or something. Anyway, they changed the name of the feature to NIS but the commands and config files that make it up all still refer to YP, so ypbind, ypwhich, yp.conf, etc.

Unlike AD which is LDAP-based, NIS is an extremely simple key/value pair database, like UNIX dbm, but network-distributed. It can store any type of information which can be expressed as a lookup key and a value. Each "database" is called an NIS "map". It is most often used to distribute username and group information via the "passwd" and "group" NIS maps. This is how this information was shared in a UNIX enterprise, much like AD is used to share user information in a Windows environment.

Other, less common but still widely used maps are automount maps and netgroup maps. It used to be that hosts were distributed that way as well, before it became easier to run your own DNS server. And some companies have created their own types of maps for special purposes. Commands like ypcat (show an entire map) and ypmatch (show a matching entry) are used to display maps.

NIS is a 3-tier protocol: at the top is the master server where the master copies of all the maps live. Then you can (optionally) have slave servers, and finally the clients themselves. Clients do not do any caching of data, so if you have a large network you need slave servers to distribute the load. In the old days, there would be one slave per LAN and the clients would broadcast for an NIS server. These days that's not very common and instead a specific server is configured. The configuration file that controls this is /etc/yp.conf.

Ypbind is the daemon that runs on a client system that "binds" to the NIS server, either by broadcasting and listening for a response or by connecting to the server specified in the config file. On Debian/Ubuntu it's started via /etc/init.d/nis. If you look through Launchpad bugs and these forums you'll find many reports that it wasn't working properly in Feisty and Gutsy, because of NetworkManager; when the system comes up, NetworkManager is invoked to try to configure the network interfaces. But, unlike "normal" UNIX startup, the interface is not actually up when the system initialization continues, and so when ypbind tries to come up it can't connect and the whole thing fails.

In Hardy, apparently ypbind has been enhanced to be able to listen on D-Bus for reports from NetworkManager about interfaces coming up, and when you start it by default it waits for those D-Bus messages before it continues on. If it doesn't receive that message, it will never actually try to bind.

That's good, I suppose, in that it works better with NetworkManager (although now we've just delayed the errors to the NEXT set of things: the things that depend on NIS, like automount, which now don't work right in Hardy... but that's another bug report). However, if NetworkManager is not running then ypbind waits forever because NetworkManager is not there.

So, if you disable NM you have to add a -no-dbus flag to the ypbind startup so it will go back to its old behavior. You do that by adding it to /etc/default/nis. If you install the NIS package you can read about it in the ypbind man pages.

HTH!

[kevdog]

steveo

Yes just type one type

echo ndiswrapper | sudo tee -a /etc/modules and the ndiswrapper kernel device driver will be loaded automatically at startup.

[fxjr]

Hi, kevdog!

As you said, I tried to setup a commandline manual connection with my ap and here is the output I got:



wpa_supplicant -w -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ap_scan=1
ctrl_interface='/var/run/wpa_supplicant'
Line: 5 - start of a new network block
ssid - hexdump_ascii(len=5):
74 65 73 74 65 teste
scan_ssid=0 (0x0)
proto: 0x1
key_mgmt: 0x2
PSK (ASCII passphrase) - hexdump_ascii(len=10): [REMOVED]
pairwise: 0x8
group: 0x8
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='teste'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:90:4b:17:8a:a9
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Added interface wlan0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=8
Received 386 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:17:9a:62:bb:e7 ssid='teste' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
selected based on WPA IE
selected WPA AP 00:17:9a:62:bb:e7 ssid='teste'
Try to find non-WPA AP
Trying to associate with 00:17:9a:62:bb:e7 (SSID='teste' freq=2447 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: DISCONNECTED -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=13
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c02 len=161
WEXT: Custom wireless event: 'ASSOCINFO(ReqIE2432043048606cdd160050f20101000050 f20201000050f20201000050f202 RespIE)'
Association info event
req_ies - hexdump(len=47): 00 05 74 65 73 74 65 01 08 02 04 0b 16 0c 12 18 24 32 04 30 48 60 6c dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
resp_ies - hexdump(len=16): 01 04 82 84 8b 96 32 08 0c 12 18 24 30 48 60 6c
WPA: set own WPA/RSN IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:17:9a:62:bb:e7
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:17:9a:62:bb:e7
No keys have been configured - skip key clearing
Associated with 00:17:9a:62:bb:e7
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
Added BSSID 00:17:9a:62:bb:e7 into blacklist
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
State: ASSOCIATED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 386 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:17:9a:62:bb:e7 ssid='teste' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
selected based on WPA IE
selected WPA AP 00:17:9a:62:bb:e7 ssid='teste'
Try to find non-WPA AP
Trying to associate with 00:17:9a:62:bb:e7 (SSID='teste' freq=2447 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=13
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c02 len=161
WEXT: Custom wireless event: 'ASSOCINFO(ReqIE2432043048606cdd160050f20101000050 f20201000050f20201000050f202 RespIE)'
Association info event
req_ies - hexdump(len=47): 00 05 74 65 73 74 65 01 08 02 04 0b 16 0c 12 18 24 32 04 30 48 60 6c dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
resp_ies - hexdump(len=16): 01 04 82 84 8b 96 32 08 0c 12 18 24 30 48 60 6c
WPA: set own WPA/RSN IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:17:9a:62:bb:e7
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:17:9a:62:bb:e7
No keys have been configured - skip key clearing
Associated with 00:17:9a:62:bb:e7
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
BSSID 00:17:9a:62:bb:e7 blacklist count incremented to 2
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
State: ASSOCIATED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface wlan0
State: SCANNING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Removed BSSID 00:17:9a:62:bb:e7 from blacklist (clear)
Cancelling scan request
Cancelling authentication timeout
WEXT: Operstate: linkmode=0, operstate=6




I don't know what can be going wrong, but I think it is the same problem networkmanager is having to be able to connect to my AP.

Here is the result of lshw -C network:



lshw -C network
*-network:0
description: Network controller
product: BCM4306 802.11b/g Wireless LAN Controller
vendor: Broadcom Corporation
physical id: 3
bus info: pci@0000:02:03.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration: driver=b43-pci-bridge latency=64 module=ssb
*-network:1
description: Ethernet interface
product: 82801DB PRO/100 VE (MOB) Ethernet Controller
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:02:08.0
logical name: eth0
version: 83
serial: 00:e0:b8:67:5f:90
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.23-k4-NAPI duplex=full firmware=N/A ip=192.168.0.156 latency=66 link=yes maxlatency=56 mingnt=8 module=e100 multicast=yes port=MII speed=100MB/s
*-network
description: Wireless interface
physical id: 1
logical name: wlan0
serial: 00:90:4b:17:8a:a9
capabilities: ethernet physical wireless
configuration: broadcast=yes multicast=yes wireless=IEEE 802.11g




If you can shed some light about that, I would thank you very much!

Thanks in advance.

[kevdog]

Something is wacky about your driver setup on your wireless card. Can you post iwlist scan. Do you have a bridge configured?

[fxjr]

Sure! here is iwlist scan:



iwlist scan
lo Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:0D:88:2F:EB:F9
ESSID:"minha"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=45/100 Signal level=-73 dBm Noise level=-69 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Extra:tsf=00000049c8ef7b26
Cell 02 - Address: 00:17:9A:62:BB:E7
ESSID:"teste"
Mode:Master
Channel:8
Frequency:2.447 GHz (Channel 8)
Quality=65/100 Signal level=-57 dBm Noise level=-69 dBm
Encryption key:on
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=0000000005f8863c

eth0 Interface doesn't support scanning.


My ap is teste. minha maybe a neighbor.

I don't know if I have a bridge as I didn't configure anything about that. I only installed the firmware as b43-legacy driver was showing on messages.

Thanks in advance.

[kevdog]

I dont know what this means:
No keys have been configured - skip key clearing

Can you post your wpa_supplicant.conf file along with telling me about your router setup.

[fxjr]

Yeap.

Here is my wpa_cupplicant.conf


ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="teste"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk=<removed>
pairwise=TKIP
group=TKIP
}


My ap is a dlink DI-524 wireless router with default configuration of wireless.

I konw it is ok because as I said in past, this same router, with this same notebook worked perfectly some days ago, but after some ubuntu updates it doesn't work. Indeed when it worked, it was the first time ever I could get wpa to work on it under gnu/linux. I even removed the network cable just to be sure it wasn't a networkmanager icon problem :)

I thought it could be a kernel update which made it work (2.6.24-14) we are now at -15. But when I booted back on -14, it also didn't work, so I think it may be some modification elsewhere. I saw in networkmanager changelog something about wpa which I thought could be the solution but it didn't work :(

So, as wpa_supplicant is also looping to get a connection, I think it is the same cause for networkmanager. That's why I'm here.

Maybe there is some configuration I can do. I also can try ndiswrapper but I'm not intended to because in past I had this same problem and it didn't fix by using ndiswrapper :(

Thanks in advance for any help.

[kevdog]

Just to save some time and frustration -- can you connect to your router if there is no encryption -- turn of WPA -- just want to confirm its not a network drivers issue or any other thing that would prevent even a nonencrypted connection and session!

What driver are you using?
lshw -C network

[bdstein]

Wow this was so cool yet it did not work for me. the last response from the sudo dhclient wlan0 command resulted in NODHCPOFFER.

I really believed it would work for me.

UPDATE EDIT:
My issue is resolved and was due to having an extra :s before my key in /etc/network/interfaces file.

[fxjr]

Just to save some time and frustration -- can you connect to your router if there is no encryption -- turn of WPA -- just want to confirm its not a network drivers issue or any other thing that would prevent even a nonencrypted connection and session!

What driver are you using?
lshw -C network


Hi, Kevdog.

Yes, it works without WPA.

My driver is b43-legacy.

Here is my lshw:



lshw -C network
*-network:0
description: Network controller
product: BCM4306 802.11b/g Wireless LAN Controller
vendor: Broadcom Corporation
physical id: 3
bus info: pci@0000:02:03.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration: driver=b43-pci-bridge latency=64 module=ssb
*-network:1
description: Ethernet interface
product: 82801DB PRO/100 VE (MOB) Ethernet Controller
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:02:08.0
logical name: eth0
version: 83
serial: 00:e0:b8:67:5f:90
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.23-k4-NAPI duplex=full firmware=N/A ip=192.168.0.156 latency=66 link=yes maxlatency=56 mingnt=8 module=e100 multicast=yes port=MII speed=100MB/s
*-network
description: Wireless interface
physical id: 1
logical name: wlan0
serial: 00:90:4b:17:8a:a9
capabilities: ethernet physical wireless
configuration: broadcast=yes multicast=yes wireless=IEEE 802.11g

Thanks in advance for any info.

Also, I'd like to add that this same notebook worked with wpa some days ago. I don't know what happend it isn't working anymore :(

[fxjr]

Well, I think you won't believe me but after last updates I did yesterday night, my wpa connection is working again!!!

But I couldn't track what package fixed it again. I know it wasn't networkmanager because the version installed is the same which worked before and later stopped work and now is working again.

Hmmmm, I just remember the histoy synaptics record telling what packages were updated... I will check it to see if I can find what package made my wifi work again...

I just hope it isn't any type of race condition between driver, hardware, OS or whatever which would make my wifi wpa works sometimes and others don't

Note that I didn't change anything to make it work again. Just the updates... Even in previous kernel it is working ok.

Anyway, thanks for your help. I will keep this thread updated if I find anything.

[nihiilist]

I had to post to thank you for this tutorial, I am new to Ubuntu and whenever I tried to set up the wireless connection with the GUI it would freeze up on me. I followed your steps for WEP and it works fine now.

Next thing is to move on to WPA cause WEP can be cracked in 5 minutes.

thanks again

[cmichaelt]

Hey there new to Ubuntu and Linux in general. I'm trying to get my wireless set up. The network manager doesn't work for me at all. i've done


aptitude remove network-manager network-manger-gnome

i'm able to connect no problem following this how-to and using the static ip part of the guide. my annoyance comes from having to type in the commands all the time i start the computer.

i followed the script instructions with a few modifications and this is what i have:

/etc/rc.local

#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

ifconfig lo down
ifconfig eth0 down
ifconfig wlan0 down
ifconfig wlan0 192.168.1.108 netmask 255.255.255.0
iwconfig wlan0 essid "bahay"
ifconfig wlan0 up
route add default gw 192.168.1.1

exit 0

when i first turn on the computer there are the results i get from each command:

sudo ifconfig

wlan0 Link encap:Ethernet HWaddr 00:16:B6:99:17:B9
inet addr:192.168.1.108 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15 errors:0 dropped:0 overruns:0 frame:0
TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4305 (4.2 KB) TX bytes:2396 (2.3 KB)

wmaster0 Link encap:UNSPEC HWaddr 00-16-B6-99-17-B9-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)


sudo iwconfig

lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"bahay"
Mode:Managed Frequency:2.412 GHz Access Point: 00:14:BF:CD:D0:01
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:off
Link Signal level=-50 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0



ping 192.168.1.1

PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

--- 192.168.1.1 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 3999ms


sudo route

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 wlan0
default 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0


there are my results after i manually enter each command and have a successful connection to both the router and world wide web:

sudo ifconfig

wlan0 Link encap:Ethernet HWaddr 00:16:B6:99:17:B9
inet addr:192.168.1.108 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:47 errors:0 dropped:0 overruns:0 frame:0
TX packets:54 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13111 (12.8 KB) TX bytes:4146 (4.0 KB)

wmaster0 Link encap:UNSPEC HWaddr 00-16-B6-99-17-B9-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)



sudo iwconfig

lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"bahay"
Mode:Managed Frequency:2.412 GHz Access Point: 00:14:BF:CD:D0:01
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:off
Link Signal level=-51 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0



ping 192.168.1.1

PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=11.3 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=3.14 ms

--- 192.168.1.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 3.147/7.230/11.313/4.083 ms


sudo route

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 wlan0
default 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0


i'm not sure of what could be wrong because i'm fairly certain i have followed all the necessary directions up to this point. Thanks for the great how-to btw! just need to pass this last hurdle for wireless.

[Virtual_Ron]

sorry. deleted. (i was stupid)

[kevdog]

cmichaelt

You do not need the lo interface mentioned in the script.

Here are some suggestion you may want to try, just be warned that I haven't actually tried any of these suggestions.

1. Put a sleep 20 statement at the top of the script -- see if something changes at boot.

2. What about changing or putting these changes in the /etc/network/interfaces script? In fact what are the contents of your /etc/network/interfaces file?

[cmichaelt]

contents of /etc/network/interfaces

auto lo
iface lo inet loopback


will test the second suggestion as i've already tried the first with sleep 40 and nothing came of it, will have to wait for a couple hours though. have class.

[cmichaelt]

tried adding the changes to /etc/network/interfaces and commented out the changes in /etc/rc.local but nothing happened at all this time.

when i use the /etc/rc.local script then login. i have to do these commands to get a wireless connection to the router:

sudo ifconfig wlan0 down
sudo iwconfig wlan0 essid "bahay"
sudo ifconfig wlan0 up

then this to get connected to the world wide web.

sudo route add default gw 192.168.1.1

[kevdog]

Can you post your new "interfaces" file? Thanks. Strange indeed!

[cmichaelt]

contents of /etc/network/interfaces


auto lo
iface lo inet loopback

ifconfig eth0 down
ifconfig wlan0 down
ifconfig wlan0 192.168.1.108 netmask 255.255.255.0
iwconfig wlan0 essid "bahay"
ifconfig wlan0 up
route add default gw 192.168.1.1

[kevdog]

Wouldn't it be more appropriate similar to this structure or syntax?

auto wlan0
iface wlan0 inet static
address 192.168.168.40
gateway 192.168.168.230
dns-nameservers 192.168.168.230
netmask 255.255.255.0

[cmichaelt]

Wouldn't it be more appropriate similar to this structure or syntax?

auto wlan0
iface wlan0 inet static
address 192.168.168.40
gateway 192.168.168.230
dns-nameservers 192.168.168.230
netmask 255.255.255.0

you sir are a genius, thank you for your help!\\:D/

[dmub82]

Just upgraded from Gutsy to Hardy. Using a Belkin F5D7050 v3002, the RT73 chipset. Under Gutsy, it didn't work out of the box, I was using the compiled Ralink driver and that worked, but wouldn't support WPA (though WPA worked under Windows). After I upgraded to Hardy (not a clean install), that RT73 driver is no longer listed under Restricted Drivers Manager like it was in Gutsy and "sudo modprobe -l |grep rt73" only returns the rt73usb.ko listing, so it looks like Hardy supports my adapter out of the box (awesome! is this correct?)

I still can't get WPA to work; I was hoping this would change if the built-in drivers are working under Hardy. I tried the simple way, entering my passkey under System-Administration-Network, but that won't connect. So I tried the instructions in this thread under "WPA with Ra Based chipsets" but on each of the "sudo iwpriv" commands, I get:
wlan0 no private ioctls Any ideas or are RT73s still out of luck when it comes to WPA? Thanks.

[ricochet1269]

Thank you for this, it worked perfectly for me!

[la3875]

Help! I'm using Hardy and I upgraded some packages this evening and a restart was required. On restart wireless and sounds are gone. Looking at another thread here's the output from terminal -

jeff@jeff-laptop:~$ sudo iwconfig
[sudo] password for jeff:
lo no wireless extensions.

eth0 no wireless extensions.

jeff@jeff-laptop:~$ sudo iwconfig eth1
eth1 No such device

jeff@jeff-laptop:~$ lshw -C network
WARNING: you should run this program as super-user.
*-network:0
description: Ethernet interface
product: BCM4401-B0 100Base-TX
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 02
serial: 00:11:43:4c:b6:15
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=b44 driverversion=2.0 ip=10.xx.xx.xx latency=32 module=ssb multicast=yes
*-network:1 UNCLAIMED
description: Network controller
product: PRO/Wireless 2915ABG Network Connection
vendor: Intel Corporation
physical id: 3
bus info: pci@0000:02:03.0
version: 05
width: 32 bits
clock: 33MHz
capabilities: cap_list
configuration: latency=32 maxlatency=24 mingnt=3

I gotta get to bed. Any advice?

[Taxi]

I'm having a problem where my system (Xubuntu Gutsy) doesn't seem to be recognizing my wireless device as a network device at all. It uses the zd1211b chipset that should be supported by the zd1211rw module, but even with the module manually loaded it sees the device in "lsusb" but doesn't acknowledge it as a network device ("lshw -C network" doesn't give any results at all and "iwconfig" doesn't mention it either). I'd appreciate any help anyone can offer. I've got more information in my original post (and it would probably be better for any future searchers if responses could be posted there instead, if you don't mind): http://ubuntuforums.org/showthread.php?p=4770232

[sefs]

back in gutsy my wireless usb use to start automactially at boot.

Now in herdy when it starts usb wireless card is not started...i have to wait until fully booted and physically unplug usb card and replug it back in.

Why is that? is there a way to fix it?

[kevdog]

Im not sure if I can help you with your problem since I don't have your particular USB wireless dongle and I don't use a wireless dongle. Perhaps starting a separate thread about the issue would be more appropriate.

[sefs]

i think once again its an issue with serial monkey rt73 driver and hardy...as two different versions of the driver gives two different results. One is borking the other, i am convinced of it.

[kevdog]

Well without posting anything related to chipset regarding your usb device, how I am supposed to know anything about your particular advice??? Hard to know your predicament if you dont give any details.

[jsdieorksw]

Hi guys, I'm very new to ubuntu, i recently dual booted ubuntu 7.10 onto my new laptop along with vista. I want to eventually remove vista completely but the internet won't work with ubuntu and i definetely can't remove vista until i can at least access the internet through ubuntu. Ubuntu doesn't seem to recognize my wireless internet connection. Can someone help me? There is a great sense of community within the ubuntu forums and any help would GREATLY appreciated! Thanks guys!

[sefs]

It's a cnet device that requires the ralink rt73 driver. I've been using the legacy driver from over at serialmonkey. I am seeking help there so I'll see how it goes and post back any results here or simply post a link to the thread.


Well without posting anything related to chipset regarding your usb device, how I am supposed to know anything about your particular advice??? Hard to know your predicament if you dont give any details.

[kevdog]

The rt73 legacy driver is very predictable. Please post back if you need help. It should work reliably.

[camerong]

I have completed instructions for WEP, and yet i get a NO DHCPOFFERS recieved error on the last step. Please see my thread and console outputs here:

http://ubuntuforums.org/showthread.php?t=769281&highlight=DHCPOFFERS

PLEASE help, I think I'm close to the solution and yet am rethinking this whole Ubuntu thing just becuase my internet isn't working...

I appreciate it.

[jo.cisco]

Hey, I have the intel 3945ABG wireless interface and its not working under hardy, i installed the driver using ndiswrapper but the problem is that it installs the driver on the wlan0 interface, leaving wmaster0 with iwl3945 which isn't working, can you help me install the driver onto wmaster0.

Here's the result of running some of the commands so you could get an idea. btw i'm connected to the internet through an ethernet connection

jo@jo-laptop:~$ lshw -C network
WARNING: you should run this program as super-user.
*-network
description: Wireless interface
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: wmaster0
version: 02
serial: 00:18:de:cb:05:62
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl3945 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11g
*-network
description: Ethernet interface
product: RTL-8139/8139C/8139C+
vendor: Realtek Semiconductor Co., Ltd.
physical id: 1
bus info: pci@0000:05:01.0
logical name: eth0
version: 10
serial: 00:0f:b0:ce:c2:0b
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=8139too driverversion=0.9.28 ip=10.0.0.88 latency=64 maxlatency=64 mingnt=32 module=8139too multicast=yes

jo@jo-laptop:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Failed to read scan data : Resource temporarily unavailable

jo@jo-laptop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

jo@jo-laptop:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:0f:b0:ce:c2:0b
inet addr:10.0.0.88 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::20f:b0ff:fece:c20b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15292 errors:0 dropped:0 overruns:0 frame:0
TX packets:8681 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7686970 (7.3 MB) TX bytes:1173620 (1.1 MB)
Interrupt:21 Base address:0x2000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1891 errors:0 dropped:0 overruns:0 frame:0
TX packets:1891 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:94908 (92.6 KB) TX bytes:94908 (92.6 KB)

wlan0 Link encap:Ethernet HWaddr 00:18:de:cb:05:62
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wmaster0 Link encap:UNSPEC HWaddr 00-18-DE-CB-05-62-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

[puifais]

Hi again kevdog :)

So after I followed this post, my speed went up from 2Mb/s to 11 Mb/s, which is great. But I have another laptop using wireless sitting right next to this Ubuntu desktop that's going at 54 Mb/s. And I know it's not the desktop's hardware limitation because a couple of days ago when it was running XP, it had the exact same connection speed as my laptop. Do you have a few guesses of why this might be? I just want to get an idea of what topics I need to be searching on the forum next :)

[kevdog]

What did you finally end up using? Are you sure you are using a version g driver and not a b driver. And how exactly are you getting your connection speed? Sometimes those numbers are not exactly correct. You may need to perform a few tests.

[kevdog]

Hey, I have the intel 3945ABG wireless interface and its not working under hardy, i installed the driver using ndiswrapper but the problem is that it installs the driver on the wlan0 interface, leaving wmaster0 with iwl3945 which isn't working, can you help me install the driver onto wmaster0.

Here's the result of running some of the commands so you could get an idea. btw i'm connected to the internet through an ethernet connection

jo@jo-laptop:~$ lshw -C network
WARNING: you should run this program as super-user.
*-network
description: Wireless interface
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: wmaster0
version: 02
serial: 00:18:de:cb:05:62
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl3945 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11g
*-network
description: Ethernet interface
product: RTL-8139/8139C/8139C+
vendor: Realtek Semiconductor Co., Ltd.
physical id: 1
bus info: pci@0000:05:01.0
logical name: eth0
version: 10
serial: 00:0f:b0:ce:c2:0b
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=8139too driverversion=0.9.28 ip=10.0.0.88 latency=64 maxlatency=64 mingnt=32 module=8139too multicast=yes

jo@jo-laptop:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Failed to read scan data : Resource temporarily unavailable

jo@jo-laptop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

jo@jo-laptop:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:0f:b0:ce:c2:0b
inet addr:10.0.0.88 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::20f:b0ff:fece:c20b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15292 errors:0 dropped:0 overruns:0 frame:0
TX packets:8681 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7686970 (7.3 MB) TX bytes:1173620 (1.1 MB)
Interrupt:21 Base address:0x2000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1891 errors:0 dropped:0 overruns:0 frame:0
TX packets:1891 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:94908 (92.6 KB) TX bytes:94908 (92.6 KB)

wlan0 Link encap:Ethernet HWaddr 00:18:de:cb:05:62
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wmaster0 Link encap:UNSPEC HWaddr 00-18-DE-CB-05-62-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)



chili555 is the person whom I might ask about intel based chipsets since I don't own one.

[kevdog]

Hi again kevdog :)

So after I followed this post, my speed went up from 2Mb/s to 11 Mb/s, which is great. But I have another laptop using wireless sitting right next to this Ubuntu desktop that's going at 54 Mb/s. And I know it's not the desktop's hardware limitation because a couple of days ago when it was running XP, it had the exact same connection speed as my laptop. Do you have a few guesses of why this might be? I just want to get an idea of what topics I need to be searching on the forum next :)

Could also try adding this to your list of parameters (a long shot!):
sudo iwconfig wlan0 rate 54M

[puifais]

What did you finally end up using? Are you sure you are using a version g driver and not a b driver. And how exactly are you getting your connection speed? Sometimes those numbers are not exactly correct. You may need to perform a few tests.

Um...what is g or b driver version? Are you talking about my wireless adapter version? As far as I can tell, it just uses ndiswrapper_dr71wu driverversion=1.52 +D-Link,07.26/2007,3.00.07

So I tried sudo iwconfig wlan0 rate 54M. I don't think it did anything. This code is suppose to configure the rate to be 54 Mb? But there might be something else limiting the speed to be 11 Mbs, so may be simply telling it to be 54 doesn't work?

By the way, I got the speed from right click the connection icon and click Connection Information. It says Speed: 11 Mb/s. In addition, I saw the difference from 2 to 11 Mb/s when browsing on Mozilla and adding applications.

[kevdog]

Does that driver support 54 mb/sec? ndiswrapper does, but so the underlying driver needs to support it also.

[puifais]

I looked up and found that the b version has a max of 11 Mbps, while the g can go up above 54. I'm fairly sure that I got the g version, but may be I'm wrong. Since my max download speed is 8kb/s on the Ubuntu machine and my other laptop is around 350 kb/s the last I remember, I'm gonna download the driver again and reinstall it the same way I did last time.

Is it necessary to uninstall the existing driver first?

By the way, I posted a thread and someone followed it and it fixed his problem in 10 minutes, woo hoo!

[puifais]

I looked up and found that the b version has a max of 11 Mbps, while the g can go up above 54. I'm fairly sure that I got the g version, but may be I'm wrong. Since my max download speed is 8kb/s on the Ubuntu machine and my other laptop is around 350 kb/s the last I remember, I'm gonna download the driver again and reinstall it the same way I did last time.

Is it necessary to uninstall the existing driver first?

By the way, I posted a thread and someone followed it and it fixed his problem in 10 minutes, woo hoo!

Alright, I forgot I could just type lshw -C network and check on the version. I definitely have the g version and yes, it's suppose to go above 54 Mbps

[kevdog]

Just to confirm that your router is set for g mode or mixed mode and not b mode -- Need to look in router settings.

[puifais]

Just to confirm that your router is set for g mode or mixed mode and not b mode -- Need to look in router settings.

I looked at the router setting and it just says 802.11 without specifying if it's g or b. But I think it's fine cuz my Ubuntu connection just went up to 12Mb/s, which exceeds the limit of 11 Mb/s. Also, other computers in the network is way above 11, so I think the router setting was correct.

[hodenkat]

Hmmm... when i got tired of keyring asking me for my password every time I just disabled roaming mode and set up a manual connection. easy as pie!

boy am I glad I never had to go though so much trouble.

excellent document though dude :popcorn:

[firas66]

Hello,
I'm a newbie in this whole Ubuntu thing. I just installed ubuntu 8.04 and right off the bat my wireless card isn't seeing any wireless network. I tried to manually enter the essid, however It just shows the wireless network with 0% signal (i tried pinging to see if there actually was a connection but timeout). it's an open wireless network no wep or wpa. I know that the card isn't malfunctioning, because it worked flawlessly in windows.

I tried to follow the guide here and here's what i got (i have no idea what all of this means though):

firas@firas-laptop:~$ lshw -C network
WARNING: you should run this program as super-user.
*-network
description: Wireless interface
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:05:00.0
logical name: wmaster0
version: 02
serial: 00:18:de:5c:64:d5
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl3945 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11g
*-network
description: Ethernet interface
product: PRO/100 VE Network Connection
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:08:08.0
logical name: eth0
version: 02
serial: 00:16:d3:12:21:b5
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=e100 driverversion=3.5.23-k4-NAPI firmware=N/A ip=192.168.2.146 latency=66 maxlatency=56 mingnt=8 module=e100 multicast=yes
firas@firas-laptop:~$ sudo ifconfig wmaster0 down
[sudo] password for firas:
firas@firas-laptop:~$ sudo dhclient -r wmaster0
There is already a pid file /var/run/dhclient.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wmaster0/
Sending on LPF/wmaster0/
Sending on Socket/fallback
firas@firas-laptop:~$ sudo ifconfig wmaster0 up
firas@firas-laptop:~$ iwconfig wmaster0 essid "firas-wireless 3"
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device wmaster0 ; Operation not permitted.
firas@firas-laptop:~$ iwconfig wmaster0 mode Managed
Error for wireless request "Set Mode" (8B06) :
SET failed on device wmaster0 ; Operation not permitted.
firas@firas-laptop:~$ sudo dhclient wmaster0
There is already a pid file /var/run/dhclient.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wmaster0/
Sending on LPF/wmaster0/
Sending on Socket/fallback
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
firas@firas-laptop:~$


please someone help

[wildbillnj1975]

Kevdog, I have a problem I don't see mentioned here yet.

Each time I run iwlist the output differs. Let's say there are eight wifi networks I can pick up from my living room: mine plus seven of my careless neighbors. Each time I run iwlist, I get six or seven of them. Sometimes mine is listed, sometimes it isn't.

This is more than an annoyance, see my other post in another thread (http://ubuntuforums.org/showthread.php?p=4850262#post4850262) which explains why this is a big deal for me.

Any suggestions?

[Skillachi]

Great post, i read thorugh it and now feel uber knowledgeable on the topic already lol.

I have a question though. I notice that one of the requirements is that the essid MUST be broadcasted. Is there a way to autoconnect even if the essid isnt being broadcasted, if so then how. If not, then i assume i'll have to enter username and password everytime i wanna log in then right?

[kevdog]

As far as hidden broadcasts, this sometimes works, if you just give it the name, however there is definitely a problem with linux in general connecting to hidden networks. If you do the manual connection way, proceed if you were seeing the networks. It might or might not work.

--iwlist scan only shows networks in the area. If yours is sometimes shown and sometimes not --- then are you really close to the access point? No interference nearby? I don't have an easy fix for your problem, b/c if you cant see your network, you obviously can't connect to it.

--wmaster0 is most likely the actual interface for the hardware, however I believe (I don't have an intel networking card), that when using an intel wireless device you actually have to issue commands through the virtual interface (which then talks to the real interface). Yes very confusing however the use of virtual interfaces is common if you need to set up two configurations or do something like airsnort in router mode (madwifi does the same thing). If you post ifconfig hopefully we can get this mess straightened out!

[togo59]

I really appreciate your collective help.

(Nevertheless I still need it!) Why, when I type sudo iwconfig eth1 essid "MyNetworkName" and then iwconfig eth1 does the essid still carry the wrong information?

Currently, I can only see a wireless signal when I turn on on "roaming mode". But I still can't connect.

My router is set to WPA-PSK (I control this) and an unsecured network is unworkable for me. I guess that's WPA(1) but it doesn't say.

Slowly..forced..to surrender.](*,)

[squabeggz]

The OP worked for my setup perfectly. I have used it with Mint (my current setup), Kubuntu, and Ubuntu Dapper & Gutsy. Thinkpad x22. My wireless card is one of those dang Linksys WPC54g v2 - acx111 chipset. No ndiswrapper needed!

[firas66]

firas@firas-laptop:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:d3:12:21:b5
inet addr:192.168.2.146 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::216:d3ff:fe12:21b5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:391 errors:0 dropped:0 overruns:0 frame:0
TX packets:291 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:208264 (203.3 KB) TX bytes:47203 (46.0 KB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1978 errors:0 dropped:0 overruns:0 frame:0
TX packets:1978 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:98900 (96.5 KB) TX bytes:98900 (96.5 KB)

wlan0 Link encap:Ethernet HWaddr 00:18:de:5c:64:d5
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wmaster0 Link encap:UNSPEC HWaddr 00-18-DE-5C-64-D5-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

firas@firas-laptop:~$

[kevdog]

firas
--Your interface is wlan0 and not wmaster0

togo59
There is no roaming mode -- that is completely related to network manager -- You could uninstall network manager and still completely connect through the command line if you wanted. This is a complete manual connection method -- you control everything!

You need to post some specific commands if you want to get appropriate help. Your posts are very vague.

[firas66]

firas@firas-laptop:~$ sudo ifconfig wlan0 down
[sudo] password for firas:
firas@firas-laptop:~$ sudo dhclient -r wlan0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:18:de:5c:64:d5
Sending on LPF/wlan0/00:18:de:5c:64:d5
Sending on Socket/fallback
firas@firas-laptop:~$ sudo ifconfig wlan0 up
firas@firas-laptop:~$ iwconfig wlan0 essid "firas-wireless 3"
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device wlan0 ; Operation not permitted.
firas@firas-laptop:~$ iwconfig wlan0 mode Managed
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Operation not permitted.
firas@firas-laptop:~$ sudo dhclient wmaster0
There is already a pid file /var/run/dhclient.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wmaster0/
Sending on LPF/wmaster0/
Sending on Socket/fallback
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 8
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
firas@firas-laptop:~$


I still got the same error... so i'm guess it doesn't have to do with the logical name of my card.

[SoyChulo]

I have a bit of a different problem. 8.04 installed without a hitch. AR5006EX recognized and installed no problem. But I got curious and decided to use ndiswrapper as an experiment. Installed ndiswrapper through Synaptic, then downloaded zip file from atheros site. Disabled HAL and Atheros support from restricted drivers support. Rebooted. Navigated to the inf file with ndiswrapper gui and used that driver.

Now I want to revert to the original setup. Uninstall ndiswrapper. Reboot. Enable HAL and Atheros support. Reboot. When I click on the network icon there is no option for "enable wireless networking".

Here is the state of my affairs:

scrib@dell-laptop:~$ sudo lshw -C network
[sudo] password for scrib:
*-network UNCLAIMED
description: Ethernet controller
product: AR242x 802.11abg Wireless PCI Express Adapter
vendor: Atheros Communications Inc.
physical id: 0
bus info: pci@0000:0b:00.0
version: 01
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix bus_master cap_list
configuration: latency=0


My wireless does not even have an ID. What do I do to enable wireless networking again? In the restricted drivers panel even both boxes are checked as 'enabled" the line following says, "Not in use" and has a red button. How do I put them into use?

Thanks in advance.:confused:

[greyspace2004]

Help me please, I am a MS-Dos expert; however, a newbe at all Linux systems.

Question One: Is there a way I can let you, or someone accessed my "wired" system to configure, test, and resolve my "wireless less" issues?
Since it is a new and clean system I have nothing to protect...

Question Two: I would like to have Wireless, is it possible to have Wireless internet actually work on Ubuntu, using a choice between my internal PRO/Wireless 2915ABG for normal internet and then later
using DLink DWL-AG660 and I have a DWL-G650 when I feel like putting WireShark to work.

My system is as follows:
I had a working internet; however, after I finished upgrading to Ubuntu released April 29 8.02 on a Dual boot Windows XP Pro System; and after
I changed my system to connect to the Dlink router via WPA, all wireless internet failed me. I can't even see a "Interface" in my choices within WireShark.

The Computer is a 17 inch Toshiba M60 and I would like to configure this computer to use the following Wireless interfaces:

Cardbus
DLink DWL-AG660 and I have a DWL-G650 which could be used for testing
both of which I believe use "Atheros"

Internal
Intel Corporation PRO/Wireless 2915ABG

Attached to a Dlink Router DI-624 which is configured as follows:
http://192.168.0.1/
SSID: greyspace
Channel: Auto Select
Super G Mode: Disabled (as I found less drops on Internal card)
Extended Range: Enabled
WMM Function: Enabled
802.11g Only mode: Enabled
SSID Broadcast: Enabled
Security: WPA personal
Cipher type: TKIP
PSK/EAP: PSK
Passphrase: dynamicXXXXX

The Goal
Is to use Ubuntu to program MicroChips.com devices and
enjoy Wireshark type software as I am interested in Electronics and
Computers related knowledge.

Email (nospaces just as it reads)
sir douglas cook 2004 at hotmail dot com

Confused with
Instructions never tell you how to; or where to install the package
or what to do when unpacking, making, installing a Tar. Which my results almost alway end with a mess of errors.

So I figure my error has to do with un-installing something before I could re-install it and the re-install bombed leaving me with component missing within my Ubuntu system.

What I have discovered, short version:

I have Internet via a Internet cable
And after typing a ton of commands
I was to UNPlug the Internet cable and use a undetermined Wireless
Which all disappeared after a reboot.

When I was Wireless the, "network manager"
and the "wireshark" couldn't show a the "Interface" and hence
wouldn't work.
--------------------------------------------------------------------------

Points to Ponder
================================================== ========================
as root administrator
# lshw -C network
Showed that the driver is missing
for PRO/Wireless 2915ABG Network Connection
also note: network:1 UNCLAIMED
physical id: 0
and
# ifconfig
shows that eth0, wifi0 doesn't have an ip address assigned to the device.

and
# dhclient
wifi0: unknown hardware address type 801
No DHCPOFFERS received.

and
ping -c 4 212.58.224.131
ping -c 4 bbc.co.uk
both work with no packet loss.

and
After a REBOOT I have no wireless .... again arrrrrrrrrrg
================================================== ========================

P.S.
I wish someone could just search my computer remotely and just fix it so that I can use wireless.

That said, many thanks for any help offered.

Grey.

[kevdog]

Sounds like your question is really related to a driver issue with your intel wireless card. Im not an expert in intel chipsets.

[greyspace2004]

I scrapped my total Ubuntu, and re-installed Ubuntu as I just don't know enough to decipher the tons of information relating to Networks, and figure what parts of that information would help me.

I know Ubuntu would be so easy if I just knew a couple of people in London Ontario that understood it.

Later,

Grey

[Yiftos]

This thread has been brilliant and informative when tackling the issue of what seems to be a black hole with UBUNTU, WIRELESS DRIVERS AND NETWORK MANAGER. Qudos to Kevdog!!!
=D>

[sennep]

Any clue what could cause this?

sudo wpa_supplicant -w -D wext -i wlan0 -c/etc/wpa_supplicant.conf

gives this output:


Trying to associate with 00:12:bf:2e:74:02 (SSID='Mynetwork' freq=2452 MHz)
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:12:bf:2e:74:02 (SSID='Mynetwork' freq=2452 MHz)
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:12:bf:2e:74:02 (SSID='Mynetwork' freq=2452 MHz)
Authentication with 00:00:00:00:00:00 timed out.
it goes on like that forever.

I'm using a wg111v2 with ndiswrapper and the win98 driver from majorgeeks, this worked like a charm on gutsy (didn't even have to connect at the command line, wicd would do the job just fine), but the same method I used to get it working on gutsy doesn't seem to work on hardy for some reason. So I tried your guide to troubleshoot it better. Any idea what could be causeing the above output? I'm using wpa with tkip.

I also tried your guide with the native rtl8187 driver just to compare, and it connected and got an IP and everything. (but the rtl8187 only stays connected for 10seonds at a time though, so it's useless, that's why I'm trying to make my wg111v2 work with ndiswrapper)

[kevdog]

sennep

Could you post your wpa_supplicant.conf file along with using this as your syntax:

sudo wpa_supplicant -w -D wext -i wlan0 -c/etc/wpa_supplicant.conf -dd

[sennep]

Here's the wpa_supplicant.conf:


ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="Mynetwork"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk="mysecretpass"
pairwise=TKIP
group=TKIP
}


And the sudo wpa_supplicant -w -D wext -i wlan0 -c/etc/wpa_supplicant.conf -dd gives a horribly long output:


sennep@sennepdata:~$ sudo ifconfig wlan0 down
sennep@sennepdata:~$ sudo dhclient -r wlan0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:14:6c:a7:f1:9c
Sending on LPF/wlan0/00:14:6c:a7:f1:9c
Sending on Socket/fallback
sennep@sennepdata:~$ sudo wpa_supplicant -w -D wext -i wlan0 -c/etc/wpa_supplicant.conf -dd
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ap_scan=1
ctrl_interface='/var/run/wpa_supplicant'
Line: 4 - start of a new network block
ssid - hexdump_ascii(len=7):
52 69 63 68 61 72 64 Mynetwork
scan_ssid=0 (0x0)
proto: 0x1
key_mgmt: 0x2
PSK (ASCII passphrase) - hexdump_ascii(len=12): [REMOVED]
pairwise: 0x8
group: 0x8
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='Mynetwork'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=22 WE(source)=18 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:14:6c:a7:f1:9c
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Added interface wlan0
RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 385 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:12:bf:2e:74:02 ssid='Mynetwork' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
1: 00:c0:02:ef:db:b0 ssid='wireless' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:12:bf:2e:74:02 ssid='Mynetwork' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - non-WPA network not allowed
1: 00:c0:02:ef:db:b0 ssid='wireless' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
No suitable AP found.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 451 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:12:bf:2e:74:02 ssid='Mynetwork' wpa_ie_len=28 rsn_ie_len=22 caps=0x11
selected based on WPA IE
selected WPA AP 00:12:bf:2e:74:02 ssid='Mynetwork'
Try to find non-WPA AP
Trying to associate with 00:12:bf:2e:74:02 (SSID='Mynetwork' freq=2452 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 24 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=28): dd 1a 00 50 f2 01 01 00 00 50 f2 02 02 00 00 50 f2 02 00 50 f2 04 01 00 00 50 f2 02
WPA: set AP RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 02 01 00
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RSN: added PMKSA cache candidate 00:12:bf:2e:74:02 prio 1000
RSN: processing PMKSA candidate list
RSN: not in suitable state for new pre-authentication
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=15
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:12:bf:2e:74:02 into blacklist
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 451 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:12:bf:2e:74:02 ssid='Mynetwork' wpa_ie_len=28 rsn_ie_len=22 caps=0x11
skip - blacklisted
1: 00:c0:02:ef:db:b0 ssid='wireless' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:12:bf:2e:74:02 ssid='Mynetwork' wpa_ie_len=28 rsn_ie_len=22 caps=0x11
skip - blacklisted
1: 00:c0:02:ef:db:b0 ssid='wireless' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
No APs found - clear blacklist and try again
Removed BSSID 00:12:bf:2e:74:02 from blacklist (clear)
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:12:bf:2e:74:02 ssid='Mynetwork' wpa_ie_len=28 rsn_ie_len=22 caps=0x11
selected based on WPA IE
selected WPA AP 00:12:bf:2e:74:02 ssid='Mynetwork'
Try to find non-WPA AP
Trying to associate with 00:12:bf:2e:74:02 (SSID='Mynetwork' freq=2452 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 24 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=28): dd 1a 00 50 f2 01 01 00 00 50 f2 02 02 00 00 50 f2 02 00 50 f2 04 01 00 00 50 f2 02
WPA: set AP RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 02 01 00
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RSN: added PMKSA cache candidate 00:12:bf:2e:74:02 prio 1000
RSN: processing PMKSA candidate list
RSN: not in suitable state for new pre-authentication
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=15
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:12:bf:2e:74:02 into blacklist
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 451 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:12:bf:2e:74:02 ssid='Mynetwork' wpa_ie_len=28 rsn_ie_len=22 caps=0x11
selected based on WPA IE
selected WPA AP 00:12:bf:2e:74:02 ssid='Mynetwork'
Try to find non-WPA AP
Trying to associate with 00:12:bf:2e:74:02 (SSID='Mynetwork' freq=2452 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 24 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=28): dd 1a 00 50 f2 01 01 00 00 50 f2 02 02 00 00 50 f2 02 00 50 f2 04 01 00 00 50 f2 02
WPA: set AP RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 02 01 00
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RSN: added PMKSA cache candidate 00:12:bf:2e:74:02 prio 1000
RSN: processing PMKSA candidate list
RSN: not in suitable state for new pre-authentication
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=15
Authentication with 00:00:00:00:00:00 timed out.
BSSID 00:12:bf:2e:74:02 blacklist count incremented to 2
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 451 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:12:bf:2e:74:02 ssid='Mynetwork' wpa_ie_len=28 rsn_ie_len=22 caps=0x11
skip - blacklisted
1: 00:c0:02:ef:db:b0 ssid='wireless' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:12:bf:2e:74:02 ssid='Mynetwork' wpa_ie_len=28 rsn_ie_len=22 caps=0x11
skip - blacklisted
1: 00:c0:02:ef:db:b0 ssid='wireless' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
No APs found - clear blacklist and try again
Removed BSSID 00:12:bf:2e:74:02 from blacklist (clear)
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:12:bf:2e:74:02 ssid='Mynetwork' wpa_ie_len=28 rsn_ie_len=22 caps=0x11
selected based on WPA IE
selected WPA AP 00:12:bf:2e:74:02 ssid='Mynetwork'
Try to find non-WPA AP
Trying to associate with 00:12:bf:2e:74:02 (SSID='Mynetwork' freq=2452 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 24 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=28): dd 1a 00 50 f2 01 01 00 00 50 f2 02 02 00 00 50 f2 02 00 50 f2 04 01 00 00 50 f2 02
WPA: set AP RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 02 01 00
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RSN: added PMKSA cache candidate 00:12:bf:2e:74:02 prio 1000
RSN: processing PMKSA candidate list
RSN: not in suitable state for new pre-authentication
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=15
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:12:bf:2e:74:02 into blacklist
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING

And it just keeps going and going...

[kevdog]

Remove the ap_scan and scan_ssid lines to see if it makes a difference. The output will go on for ever with the -dd flag, break with Cntl-C. It gives some useful output however.

[spaceboy909]

Thanks for the great guide, first of all. I did, however, find one hair-yanking typo in one of the sections that I needed, Static IP's. I guess no one else has needed this section as the guide has been here awhile (or maybe there's a workaround that I missed in another section).

Being a newbie, I tend to follow guides line for line, and only research when necessary. So, for two days I fiddled around with the Static IP section, as well as other guides, trying to figure out why I could get DHCP running but not Static.

About an hour ago I landed on it: The last line in the Static IP section should not be there.


sudo dhclient <interface>This apparently restarts the DHCP client and erases any Static settings that you have entered. Since my DHCP was switched off on my router, the client reset the IP to the 169 addy.

Once I spotted this, I reentered the info per the guide, leaving off the last line, and Walla! Instant successfull connection!

Oh,.........not quite....JFTR, I had to use apt to remove network-manager and network-manager-gnome because the manager was again resetting my manual settings and fouling everything up. (found that elsewhere.....not sure if it's in your guide) Hopefully this will be the end to my problems! That manager definitely needs some enhancement as it is way too limiting and a major PITB!

[kevdog]

Change made to the guide -- yes a major oversight by me -- thanks for submitting the correction!

[spaceboy909]

Change made to the guide -- yes a major oversight by me -- thanks for submitting the correction!

Hey, I found one more spot! I didn't think of it before, but the original page I landed on has a duplicate of the guide in this thread, and it's in the networking category. It needs the update as well.

http://ubuntuforums.org/showthread.php?t=684495

There may be a few other differences lurking about, too! ;)

[kevdog]

Its really hard to maintain two posts -- I wish there was a way that the BB program could just link to one post so changes made to one copy would be shown in both!!! Obviously the master copy for me is in the T&T section.

[spaceboy909]

Its really hard to maintain two posts -- I wish there was a way that the BB program could just link to one post so changes made to one copy would be shown in both!!! Obviously the master copy for me is in the T&T section.
I'm surprised there isn't a way since this is a fairly common situation on web forums. So I guess you're stuck with a copying the new version over the old one every time. :-k

You know, maybe just deleting the guts of the one sticky guide and replacing it with a URL to the main one. That should work fine, I think.

[wildbillnj1975]

As far as hidden broadcasts, this sometimes works, if you just give it the name, however there is definitely a problem with linux in general connecting to hidden networks. If you do the manual connection way, proceed if you were seeing the networks. It might or might not work.

--iwlist scan only shows networks in the area. If yours is sometimes shown and sometimes not --- then are you really close to the access point? No interference nearby? I don't have an easy fix for your problem, b/c if you cant see your network, you obviously can't connect to it.

--wmaster0 is most likely the actual interface for the hardware, however I believe (I don't have an intel networking card), that when using an intel wireless device you actually have to issue commands through the virtual interface (which then talks to the real interface). Yes very confusing however the use of virtual interfaces is common if you need to set up two configurations or do something like airsnort in router mode (madwifi does the same thing). If you post ifconfig hopefully we can get this mess straightened out!
kevdog, I get varying results from iwlist scan regardless of proximity...

My wifi router is in a small closet off my "office". Ok, I'll admit that there's a chance for interference, because in a 12 sq. ft. room I have:

* an Ubuntu server box
* wifi router
* laser printer
* inkjet printer
* mini printer server
* a 4-port switch

However, when I do connect to my home network, the connection is rock-solid (whether I'm 10 ft. away at my desk, or 50 ft. away in the back yard, through multiple walls). Same behavior happened last week in my hotel room: one moment the SSID was there, the next it disappeared (but when connected it's solid).

I'm beginning to wonder if SSID broadcast is not continuous - i.e. more of a "pulse" or repeating signal, and sometimes iwlist runs in between the pulses.

[spaceboy909]

Compaq r4010us w/ Broadcom 4306 on Gutsy

Well, I'm back. :( While I did get static IP running successfully, now I'm trying to get WPA up and running, and it just won't go.

My router is presently set to:

* Broadcast SSID
* TKIP

I have tried numerous combinations of things between the rc.local and wpa_supplicant.conf files, and have seen 3 different results, but no success. Too many combinations to list, but I'll give you the jist of it and then I can try your suggestions.

One difference is when I toggle the AP SCAN between 1 and 0. With one of them it stalls at something like "EAPOL: startwhen --> 0". With the other it stalls at something like " wireless event: cmd=0xcb08 len=8 ".

The other difference, which I've seen many times, but I am unable to recall how to get it this morning, results in a continuous, stream of data, pausing in two repeating spots.....actually, I think that's when I experimented by replacing 'wext' with 'ndiswrapper' in wpa...conf.

Ftr, iwlist scan shows the pairwise and group info to be " WEP-40 " for my router. Just as an experiment I typed these into wpa...conf, and it yielded cipher errors.

[kevdog]

With any WPA errors you need to post your wpa_supplicant.conf file, and your command line statement that invokes wpa_supplicant. Dont worry about the WEP40 line. Its wpa. Also post iwlist scan.

[spaceboy909]

Ok, here's the beef!

wpa_supplicant.conf:
ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={

ssid="stoog"
scan_ssid=1
proto=WPA
key_mgmt=WPA-PSK
psk="AAAAAAAA"
pairwise=TKIP
group=TKIP
}
I'm implementing wpa with the rc.local script per your guide:
ifconfig eth0 down
ifconfig wlan0 down
dhclient -r eth0
dhclient -r wlan0
ifconfig wlan0 192.168.1.102 netmask 255.255.255.0
route add default gw 192.168.1.1
wpa_supplicant -w -D wext -i wlan0 -c /etc/wpa_supplicant.conf -dd
ifconfig wlan0 up
iwconfig wlan0 essid "stoog"
iwconfig wlan0 mode Managed

exit 0
iwlist scan: (Cell 01 / stoog - is my router)
root@defaullt:/etc# iwlist scan
lo Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:0F:66:53:E9:E1
ESSID:"stoog"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.452 GHz (Channel 9)
Quality:81/100 Signal level:-44 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
Cell 02 - Address: 00:16:01:D1:19:3F
ESSID:"SkyRanch38"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:9/100 Signal level:-90 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 03 - Address: 00:16:01:B9:A3:AB
ESSID:"SkyRanch37"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:9/100 Signal level:-90 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0

eth0 Interface doesn't support scanning.

[kevdog]

Ok skip the rc.local file for a moment.

Try this

ctrl_interface=/var/run/wpa_supplicant
network={
ssid="stoog"
proto=WPA
key_mgmt=WPA-PSK
psk="AAAAAAAA"
pairwise=TKIP
group=TKIP
}

At command line:

sudo ifconfig wlan0 down
sudo dhclient -r wlan0
sudo ifconfig wlan0 192.168.1.102 netmask 255.255.255.0
sudo iwconfig wlan0 essid "stoog"
sudo iwconfig wlan0 mode Managed
sudo wpa_supplicant -Bw -Dwext -iwlan0 -c /etc/wpa_supplicant.conf

If that doesn't work, substiture the following:
sudo wpa_supplicant -w -Dwext -iwlan0 -c /etc/wpa_supplicant.conf -dd

Post output!

[GonzalitoUY]

I'm almost there...
I have an eMachines N-10, with a realtek rtl8185 wireless card.
I've installed the driver through this page method
http://www.willdaniels.co.uk/articles/10-howto/12-r8180-hardy
succefully, but I can't get WPA to work when i try to do manual configuration:
Here's the output when I type
sudo wpa_supplicant -w -D<****see footer below***> -i<interface> -c/etc/wpa_supplicant.conf on step 2 of WPA Connection(replacing where necessary)

root@gonzalo-laptop:/home/gonzalo/rtl8185# wpa_supplicant -w -Dipw -iwlan0 -c/etc/wpa_supplicant.conf
Linux wireless extensions version 22 detected.
ipw2x00 driver uses driver_wext (-Dwext) instead of driver_ipw.
Trying to associate with xx:xx:xx:xx:xx:xx (SSID='xxxxxxxxx' freq=2442 MHz)
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Associated with xx:xx:xx:xx:xx:xx
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Associated with xx:xx:xx:xx:xx:xx
WPA: Key negotiation completed with xx:xx:xx:xx:xx:xx [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to xx:xx:xx:xx:xx:xx completed (auth) [id=0 id_str=]

and then it freezes, i must CTRL-C to get back control.
Any guesses?

EDIT:Here are the results if I continue anyway

root@gonzalo-laptop:/home/gonzalo/rtl8185# dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/xx:xx:xx:xx:xx:xx
Sending on LPF/wlan0/xx:xx:xx:xx:xx:xx
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

[kevdog]

What driver are you trying to use?

wpa_supplicant -w -Dipw -iwlan0 -c/etc/wpa_supplicant


-D ipw tells me you are your an intel wireless driver however you mentioned something about realtek 8185. This is a separate driver.

[GonzalitoUY]

It's a Realtek RTL8185, but I've tried Dwext with no results.
Please help me!
According to this webpage http://willdaniels.co.uk/articles/howto-guides/10-howto/10-wpa-r8180-ubuntu Dwext doesn't work either

[kevdog]

Good link BTW

But lets go through that page slowly
1. What driver are you trying to use? The link mentions the r8180 driver. It also states you need to compile this with Hardy. Are you using the r8180 driver? and did you compile it? Or are you using a different driver?
2. It also mentioned that certain cryptographic modules be loaded first prior to invoking wpa_supplicant. These modules control either the TKIP or AES cipher. It quoted the following:

ieee80211_tkip_crypt-rtl - FOR TKIP

ieee80211_ccmp_crypt-rtl - FOR AES

Are these modules loaded or did you load them? Hint check lsmod since this lists the modules currently loaded in the kernel. lsmod should also list the r8180 driver if you are using this driver!

Here is a link how to build the r8180 (rtl8185) driver for ubunut. It seems quite informative:
http://willdaniels.co.uk/articles/howto-guides/10-howto/12-r8180-hardy

[GonzalitoUY]

I've followed that guide step by step, compiling the driver provided there.
I'm a rookie, but doing lsmod, ieee80211_tkip_crypt-rtl isn't loaded, however a similar one,ieee80211_crypt_rtl ,is loaded .How do I load the right one?
I've got this

root@gonzalo-laptop:~# sudo modprobe ieee80211_tkip_crypt-rtl
FATAL: Module ieee80211_tkip_crypt_rtl not found.

[kevdog]

Good question -- a good attempt. I'm not exactly sure what modules are going to be included on your system. lsmod only lists the installed modules, however as you know there are a bunch of other modules, simply not active in the kernel. Lets just see what you have available, please

sudo updatedb (Wait until process stops -- takes a while)
locate ieee80211* (or just try ieee80211)

Again Im looking for all the modules that begin with ieee80211.

At least it looks like we've probably stumbled upon the reason why WPA isn't working.


Update try the following (Seems like there may have been some typos in the referenced post):

sudo rmmod r8180
sudo rmmod ieee80211_rtl
sudo rmmod ieee80211_crypt_wep_rtl
sudo rmmod ieee80211_crypt_tkip_rtl
sudo rmmod ieee80211_crypt_ccmp_rtl
sudo rmmod ieee80211_crypt_rtl

sudo modprobe ieee80211_crypt_rtl
sudo modprobe ieee80211_crypt_wep_rtl
sudo modprobe ieee80211_crypt_tkip_rtl
sudo modprobe ieee80211_crypt_ccmp_rtl
sudo modprobe ieee80211_rtl
sudo modprobe r8180

[GonzalitoUY]

Same results as before...
Here are the output of the last set of instructions you told me

root@gonzalo-laptop:~/rtl8185# sudo updatedb
root@gonzalo-laptop:~/rtl8185# locate ieee80211*
/home/gonzalo/rtl8185/ieee80211
/home/gonzalo/rtl8185/ieee80211/.ieee80211-rtl.ko.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211-rtl.mod.o.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211-rtl.o.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211_crypt-rtl.ko.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211_crypt-rtl.mod.o.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211_crypt-rtl.o.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211_crypt.o.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211_crypt_ccmp-rtl.ko.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211_crypt_ccmp-rtl.mod.o.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211_crypt_ccmp-rtl.o.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211_crypt_ccmp.o.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211_crypt_tkip-rtl.ko.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211_crypt_tkip-rtl.mod.o.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211_crypt_tkip-rtl.o.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211_crypt_tkip.o.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211_crypt_wep-rtl.ko.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211_crypt_wep-rtl.mod.o.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211_crypt_wep-rtl.o.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211_crypt_wep.o.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211_module.o.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211_rx.o.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211_softmac.o.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211_softmac_wx.o.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211_tx.o.cmd
/home/gonzalo/rtl8185/ieee80211/.ieee80211_wx.o.cmd
/home/gonzalo/rtl8185/ieee80211/.tmp_versions
/home/gonzalo/rtl8185/ieee80211/Makefile
/home/gonzalo/rtl8185/ieee80211/Module.symvers
/home/gonzalo/rtl8185/ieee80211/ieee80211-rtl.ko
/home/gonzalo/rtl8185/ieee80211/ieee80211-rtl.mod.c
/home/gonzalo/rtl8185/ieee80211/ieee80211-rtl.mod.o
/home/gonzalo/rtl8185/ieee80211/ieee80211-rtl.o
/home/gonzalo/rtl8185/ieee80211/ieee80211.h
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt-rtl.ko
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt-rtl.mod.c
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt-rtl.mod.o
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt-rtl.o
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt.c
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt.h
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt.o
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt_ccmp-rtl.ko
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt_ccmp-rtl.mod.c
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt_ccmp-rtl.mod.o
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt_ccmp-rtl.o
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt_ccmp.c
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt_ccmp.o
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt_tkip-rtl.ko
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt_tkip-rtl.mod.c
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt_tkip-rtl.mod.o
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt_tkip-rtl.o
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt_tkip.c
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt_tkip.o
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt_wep-rtl.ko
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt_wep-rtl.mod.c
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt_wep-rtl.mod.o
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt_wep-rtl.o
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt_wep.c
/home/gonzalo/rtl8185/ieee80211/ieee80211_crypt_wep.o
/home/gonzalo/rtl8185/ieee80211/ieee80211_module.c
/home/gonzalo/rtl8185/ieee80211/ieee80211_module.o
/home/gonzalo/rtl8185/ieee80211/ieee80211_rx.c
/home/gonzalo/rtl8185/ieee80211/ieee80211_rx.o
/home/gonzalo/rtl8185/ieee80211/ieee80211_softmac.c
/home/gonzalo/rtl8185/ieee80211/ieee80211_softmac.o
/home/gonzalo/rtl8185/ieee80211/ieee80211_softmac_wx.c
/home/gonzalo/rtl8185/ieee80211/ieee80211_softmac_wx.o
/home/gonzalo/rtl8185/ieee80211/ieee80211_tx.c
/home/gonzalo/rtl8185/ieee80211/ieee80211_tx.o
/home/gonzalo/rtl8185/ieee80211/ieee80211_wx.c
/home/gonzalo/rtl8185/ieee80211/ieee80211_wx.o
/home/gonzalo/rtl8185/ieee80211/license
/home/gonzalo/rtl8185/ieee80211/readme
/home/gonzalo/rtl8185/ieee80211/tags
/home/gonzalo/rtl8185/ieee80211/.tmp_versions/ieee80211-rtl.mod
/home/gonzalo/rtl8185/ieee80211/.tmp_versions/ieee80211_crypt-rtl.mod
/home/gonzalo/rtl8185/ieee80211/.tmp_versions/ieee80211_crypt_ccmp-rtl.mod
/home/gonzalo/rtl8185/ieee80211/.tmp_versions/ieee80211_crypt_tkip-rtl.mod
/home/gonzalo/rtl8185/ieee80211/.tmp_versions/ieee80211_crypt_wep-rtl.mod
/home/gonzalo/rtl8185/rtl8185/ieee80211.h
/home/gonzalo/rtl8185/rtl8185/ieee80211_crypt.h
/lib/modules/2.6.24-16-generic/kernel/net/ieee80211
/lib/modules/2.6.24-16-generic/kernel/net/ieee80211/ieee80211.ko
/lib/modules/2.6.24-16-generic/kernel/net/ieee80211/ieee80211_crypt.ko
/lib/modules/2.6.24-16-generic/kernel/net/ieee80211/ieee80211_crypt_ccmp.ko
/lib/modules/2.6.24-16-generic/kernel/net/ieee80211/ieee80211_crypt_tkip.ko
/lib/modules/2.6.24-16-generic/kernel/net/ieee80211/ieee80211_crypt_wep.ko
/lib/modules/2.6.24-16-generic/kernel/net/ieee80211/softmac
/lib/modules/2.6.24-16-generic/kernel/net/ieee80211/softmac/ieee80211softmac.ko
/lib/modules/2.6.24-16-generic/kernel/net/wireless/ieee80211-rtl.ko
/lib/modules/2.6.24-16-generic/kernel/net/wireless/ieee80211_crypt-rtl.ko
/lib/modules/2.6.24-16-generic/kernel/net/wireless/ieee80211_crypt_ccmp-rtl.ko
/lib/modules/2.6.24-16-generic/kernel/net/wireless/ieee80211_crypt_tkip-rtl.ko
/lib/modules/2.6.24-16-generic/kernel/net/wireless/ieee80211_crypt_wep-rtl.ko
/root/rtl8185/ieee80211
/root/rtl8185/ieee80211/.ieee80211-rtl.ko.cmd
/root/rtl8185/ieee80211/.ieee80211-rtl.mod.o.cmd
/root/rtl8185/ieee80211/.ieee80211-rtl.o.cmd
/root/rtl8185/ieee80211/.ieee80211_crypt-rtl.ko.cmd
/root/rtl8185/ieee80211/.ieee80211_crypt-rtl.mod.o.cmd
/root/rtl8185/ieee80211/.ieee80211_crypt-rtl.o.cmd
/root/rtl8185/ieee80211/.ieee80211_crypt.o.cmd
/root/rtl8185/ieee80211/.ieee80211_crypt_ccmp-rtl.ko.cmd
/root/rtl8185/ieee80211/.ieee80211_crypt_ccmp-rtl.mod.o.cmd
/root/rtl8185/ieee80211/.ieee80211_crypt_ccmp-rtl.o.cmd
/root/rtl8185/ieee80211/.ieee80211_crypt_ccmp.o.cmd
/root/rtl8185/ieee80211/.ieee80211_crypt_tkip-rtl.ko.cmd
/root/rtl8185/ieee80211/.ieee80211_crypt_tkip-rtl.mod.o.cmd
/root/rtl8185/ieee80211/.ieee80211_crypt_tkip-rtl.o.cmd
/root/rtl8185/ieee80211/.ieee80211_crypt_tkip.o.cmd
/root/rtl8185/ieee80211/.ieee80211_crypt_wep-rtl.ko.cmd
/root/rtl8185/ieee80211/.ieee80211_crypt_wep-rtl.mod.o.cmd
/root/rtl8185/ieee80211/.ieee80211_crypt_wep-rtl.o.cmd
/root/rtl8185/ieee80211/.ieee80211_crypt_wep.o.cmd
/root/rtl8185/ieee80211/.ieee80211_module.o.cmd
/root/rtl8185/ieee80211/.ieee80211_rx.o.cmd
/root/rtl8185/ieee80211/.ieee80211_softmac.o.cmd
/root/rtl8185/ieee80211/.ieee80211_softmac_wx.o.cmd
/root/rtl8185/ieee80211/.ieee80211_tx.o.cmd
/root/rtl8185/ieee80211/.ieee80211_wx.o.cmd
/root/rtl8185/ieee80211/.tmp_versions
/root/rtl8185/ieee80211/Makefile
/root/rtl8185/ieee80211/Module.symvers
/root/rtl8185/ieee80211/ieee80211-rtl.ko
/root/rtl8185/ieee80211/ieee80211-rtl.mod.c
/root/rtl8185/ieee80211/ieee80211-rtl.mod.o
/root/rtl8185/ieee80211/ieee80211-rtl.o
/root/rtl8185/ieee80211/ieee80211.h
/root/rtl8185/ieee80211/ieee80211_crypt-rtl.ko
/root/rtl8185/ieee80211/ieee80211_crypt-rtl.mod.c
/root/rtl8185/ieee80211/ieee80211_crypt-rtl.mod.o
/root/rtl8185/ieee80211/ieee80211_crypt-rtl.o
/root/rtl8185/ieee80211/ieee80211_crypt.c
/root/rtl8185/ieee80211/ieee80211_crypt.h
/root/rtl8185/ieee80211/ieee80211_crypt.o
/root/rtl8185/ieee80211/ieee80211_crypt_ccmp-rtl.ko
/root/rtl8185/ieee80211/ieee80211_crypt_ccmp-rtl.mod.c
/root/rtl8185/ieee80211/ieee80211_crypt_ccmp-rtl.mod.o
/root/rtl8185/ieee80211/ieee80211_crypt_ccmp-rtl.o
/root/rtl8185/ieee80211/ieee80211_crypt_ccmp.c
/root/rtl8185/ieee80211/ieee80211_crypt_ccmp.o
/root/rtl8185/ieee80211/ieee80211_crypt_tkip-rtl.ko
/root/rtl8185/ieee80211/ieee80211_crypt_tkip-rtl.mod.c
/root/rtl8185/ieee80211/ieee80211_crypt_tkip-rtl.mod.o
/root/rtl8185/ieee80211/ieee80211_crypt_tkip-rtl.o
/root/rtl8185/ieee80211/ieee80211_crypt_tkip.c
/root/rtl8185/ieee80211/ieee80211_crypt_tkip.o
/root/rtl8185/ieee80211/ieee80211_crypt_wep-rtl.ko
/root/rtl8185/ieee80211/ieee80211_crypt_wep-rtl.mod.c
/root/rtl8185/ieee80211/ieee80211_crypt_wep-rtl.mod.o
/root/rtl8185/ieee80211/ieee80211_crypt_wep-rtl.o
/root/rtl8185/ieee80211/ieee80211_crypt_wep.c
/root/rtl8185/ieee80211/ieee80211_crypt_wep.o
/root/rtl8185/ieee80211/ieee80211_module.c
/root/rtl8185/ieee80211/ieee80211_module.o
/root/rtl8185/ieee80211/ieee80211_rx.c
/root/rtl8185/ieee80211/ieee80211_rx.o
/root/rtl8185/ieee80211/ieee80211_softmac.c
/root/rtl8185/ieee80211/ieee80211_softmac.o
/root/rtl8185/ieee80211/ieee80211_softmac_wx.c
/root/rtl8185/ieee80211/ieee80211_softmac_wx.o
/root/rtl8185/ieee80211/ieee80211_tx.c
/root/rtl8185/ieee80211/ieee80211_tx.o
/root/rtl8185/ieee80211/ieee80211_wx.c
/root/rtl8185/ieee80211/ieee80211_wx.o
/root/rtl8185/ieee80211/license
/root/rtl8185/ieee80211/readme
/root/rtl8185/ieee80211/tags
/root/rtl8185/ieee80211/.tmp_versions/ieee80211-rtl.mod
/root/rtl8185/ieee80211/.tmp_versions/ieee80211_crypt-rtl.mod
/root/rtl8185/ieee80211/.tmp_versions/ieee80211_crypt_ccmp-rtl.mod
/root/rtl8185/ieee80211/.tmp_versions/ieee80211_crypt_tkip-rtl.mod
/root/rtl8185/ieee80211/.tmp_versions/ieee80211_crypt_wep-rtl.mod
/root/rtl8185/rtl8185/ieee80211.h
/root/rtl8185/rtl8185/ieee80211_crypt.h
/usr/src/linux-headers-2.6.24-16/include/linux/ieee80211.h
/usr/src/linux-headers-2.6.24-16/include/net/ieee80211.h
/usr/src/linux-headers-2.6.24-16/include/net/ieee80211_crypt.h
/usr/src/linux-headers-2.6.24-16/include/net/ieee80211_radiotap.h
/usr/src/linux-headers-2.6.24-16/include/net/ieee80211softmac.h
/usr/src/linux-headers-2.6.24-16/include/net/ieee80211softmac_wx.h
/usr/src/linux-headers-2.6.24-16/net/ieee80211
/usr/src/linux-headers-2.6.24-16/net/ieee80211/Kconfig
/usr/src/linux-headers-2.6.24-16/net/ieee80211/Makefile
/usr/src/linux-headers-2.6.24-16/net/ieee80211/softmac
/usr/src/linux-headers-2.6.24-16/net/ieee80211/softmac/Kconfig
/usr/src/linux-headers-2.6.24-16/net/ieee80211/softmac/Makefile
/usr/src/linux-headers-2.6.24-16-generic/include/config/ieee80211
/usr/src/linux-headers-2.6.24-16-generic/include/config/ieee80211.h
/usr/src/linux-headers-2.6.24-16-generic/include/config/ieee80211/crypt
/usr/src/linux-headers-2.6.24-16-generic/include/config/ieee80211/softmac.h
/usr/src/linux-headers-2.6.24-16-generic/include/config/ieee80211/crypt/ccmp.h
/usr/src/linux-headers-2.6.24-16-generic/include/config/ieee80211/crypt/tkip.h
/usr/src/linux-headers-2.6.24-16-generic/include/config/ieee80211/crypt/wep.h
/usr/src/linux-headers-2.6.24-16-generic/include/linux/ieee80211.h
root@gonzalo-laptop:~/rtl8185#
root@gonzalo-laptop:~/rtl8185# sudo rmmod r8180
root@gonzalo-laptop:~/rtl8185# sudo rmmod ieee80211_rtl
root@gonzalo-laptop:~/rtl8185# sudo rmmod ieee80211_crypt_wep_rtl
root@gonzalo-laptop:~/rtl8185# sudo rmmod ieee80211_crypt_tkip_rtl
root@gonzalo-laptop:~/rtl8185# sudo rmmod ieee80211_crypt_ccmp_rtl
root@gonzalo-laptop:~/rtl8185# sudo rmmod ieee80211_crypt_rtl
root@gonzalo-laptop:~/rtl8185#
root@gonzalo-laptop:~/rtl8185# sudo modprobe ieee80211_crypt_rtl
root@gonzalo-laptop:~/rtl8185# sudo modprobe ieee80211_crypt_wep_rtl
root@gonzalo-laptop:~/rtl8185# sudo modprobe ieee80211_crypt_tkip_rtl
root@gonzalo-laptop:~/rtl8185# sudo modprobe ieee80211_crypt_ccmp_rtl
root@gonzalo-laptop:~/rtl8185# sudo modprobe ieee80211_rtl
root@gonzalo-laptop:~/rtl8185# sudo modprobe r8180

The results are the same: when i do
sudo wpa_supplicant -Dipw -cwpa.conf -iwlan0
, it seems to connect but then it freezes

Linux wireless extensions version 22 detected.
ipw2x00 driver uses driver_wext (-Dwext) instead of driver_ipw.
Trying to associate with 00:17:3f:65:f9:50 (SSID='PKNETWORK' freq=2442 MHz)
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Associated with 00:17:3f:65:f9:50
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Associated with 00:17:3f:65:f9:50
WPA: Key negotiation completed with 00:17:3f:65:f9:50 [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:17:3f:65:f9:50 completed (auth) [id=0 id_str=]
CTRL-EVENT-TERMINATING - signal 2 received
root@gonzalo-laptop:/home/gonzalo/Escritorio#

NOTE:It freezes on the ¨CTRL-EVENT-CONNECTED¨ line, i must do CTRL-C (break) to get control of the console again

Except for WPA everything looks fine (here's a pic on spanish ,showing which option it offers me when I detectect some WiFi network)
http://i26.tinypic.com/2gxn1hz.png

EDIT:I've just noticed something: every wifi network i detect, has no range??? even if i'm next to my router...
http://i30.tinypic.com/257zi4m.jpg

[kevdog]

Did you try what it told you?

sudo wpa_supplicant -Dipw -cwpa.conf -iwlan0

becomes

sudo wpa_supplicant -Dwext -cwpa.conf -iwlan0

[aolias]

Hi Kevdog

I followed your post regarding what you suggested me about my post (WPA not working after upgrade to Hardy)
My wireless card is a WPN111 usb, worked fine with Feisty + ndiswrapper 1.52 + WPA

I get stuck when running this command


sudo wpa_supplicant -w -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
Trying to associate with 00:18:4d:01:bc:5e (SSID='NETGEAR' freq=2437 MHz)
Associated with 00:18:4d:01:bc:5e
Associated with 00:18:4d:01:bc:5e
Associated with 00:18:4d:01:bc:5e
Associated with 00:18:4d:01:bc:5e
Authentication with 00:18:4d:01:bc:5e timed out.
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Trying to associate with 00:18:4d:01:bc:5e (SSID='NETGEAR' freq=2437 MHz)
Associated with 00:18:4d:01:bc:5e
Authentication with 00:18:4d:01:bc:5e timed out.
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Trying to associate with 00:18:4d:01:bc:5e (SSID='NETGEAR' freq=2437 MHz)
Associated with 00:18:4d:01:bc:5e
Associated with 00:18:4d:01:bc:5e
Associated with 00:18:4d:01:bc:5e
Associated with 00:18:4d:01:bc:5e
Associated with 00:18:4d:01:bc:5e
Authentication with 00:18:4d:01:bc:5e timed out.
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Trying to associate with 00:18:4d:01:bc:5e (SSID='NETGEAR' freq=2437 MHz)
Associated with 00:18:4d:01:bc:5e
Associated with 00:18:4d:01:bc:5e
Associated with 00:18:4d:01:bc:5e
Associated with 00:18:4d:01:bc:5e
Authentication with 00:18:4d:01:bc:5e timed out.
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
WPA: Driver used disabled pairwise cipher 0x10 (mask 0x8) - reject
Associated with 00:18:4d:01:bc:5e
WPA: Invalid TKIP key length 16 (src=00:18:4d:01:bc:5e)
WPA: Invalid TKIP key length 16 (src=00:18:4d:01:bc:5e)
WPA: Invalid TKIP key length 16 (src=00:18:4d:01:bc:5e)
WPA: Invalid TKIP key length 16 (src=00:18:4d:01:bc:5e)
Associated with 00:18:4d:01:bc:5e
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
CTRL-EVENT-TERMINATING - signal 2 received


My conf file is

ap_scan=1
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="NETGEAR"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk="the passwd in plain text"
#psk=e1f217aac9c73de737ad791bfa6a462e518a5a5a1ca5c 7e33dd7086f1aad5287
pairwise=TKIP
group=TKIP
}

I tried with the HEX key and also with scan_ssid=1. Not to 2 because the router broadcasts the ssid

sudo lshw -C network
*-network:0 UNCLAIMED
description: Ethernet controller
product: 88w8335 [Libertas] 802.11b/g Wireless
vendor: Marvell Technology Group Ltd.
physical id: a
bus info: pci@0000:02:0a.0
version: 03
width: 32 bits
clock: 66MHz
capabilities: pm bus_master cap_list
configuration: latency=32
*-network:1
description: Ethernet interface
product: RTL-8169 Gigabit Ethernet
vendor: Realtek Semiconductor Co., Ltd.
physical id: d
bus info: pci@0000:02:0d.0
logical name: eth1
version: 10
serial: 00:11:09:d2:fe:f8
size: 100MB/s
capacity: 1GB/s
width: 32 bits
clock: 66MHz
capabilities: pm bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.2LK duplex=half latency=64 link=no maxlatency=64 mingnt=32 module=r8169 multicast=yes port=twisted pair speed=100MB/s
*-network DISABLED
description: Wireless interface
physical id: 1
logical name: wlan0
serial: 00:18:4d:2b:ee:a0
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+netwpn11 driverversion=1.52+NETGEAR,09/26/2005,1.5.0.21 link=yes multicast=yes wireless=IEEE 802.11g

Any idea??? I am thinking to redo the ndiswrapper installation. But I am not sure if this might work

[kevdog]

The problem right now is not wpa_supplicant related since under your wireless info I see the big disclaimer:

*-network DISABLED

This may be a ndiswrapper problem -- you might want to check the message log -- dmesg to see after you modprobe ndiswrapper to see if you get any errors.

[aolias]

After rebooting the pc I run again the command
sudo lshw -C network
*-network:0 UNCLAIMED
description: Ethernet controller
product: 88w8335 [Libertas] 802.11b/g Wireless
vendor: Marvell Technology Group Ltd.
physical id: a
bus info: pci@0000:02:0a.0
version: 03
width: 32 bits
clock: 66MHz
capabilities: pm bus_master cap_list
configuration: latency=32
*-network:1
description: Ethernet interface
product: RTL-8169 Gigabit Ethernet
vendor: Realtek Semiconductor Co., Ltd.
physical id: d
bus info: pci@0000:02:0d.0
logical name: eth1
version: 10
serial: 00:11:09:d2:fe:f8
size: 100MB/s
capacity: 1GB/s
width: 32 bits
clock: 66MHz
capabilities: pm bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.2LK duplex=half latency=64 link=no maxlatency=64 mingnt=32 module=r8169 multicast=yes port=twisted pair speed=100MB/s
*-network
description: Wireless interface
physical id: 1
logical name: wlan0
serial: 00:18:4d:2b:ee:a0
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+netwpn11 driverversion=1.52+NETGEAR,09/26/2005,1.5.0.21 link=yes multicast=yes wireless=IEEE 802.11g

The wlan0 is working, So I run again the same stalled step
and got this

sudo wpa_supplicant -w -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Trying to associate with 00:18:4d:01:bc:5e (SSID='NETGEAR' freq=2437 MHz)
Associated with 00:18:4d:01:bc:5e
Associated with 00:18:4d:01:bc:5e
Associated with 00:18:4d:01:bc:5e
Authentication with 00:18:4d:01:bc:5e timed out.
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Trying to associate with 00:18:4d:01:bc:5e (SSID='NETGEAR' freq=2437 MHz)
Associated with 00:18:4d:01:bc:5e
WPA: Invalid TKIP key length 16 (src=00:18:4d:01:bc:5e)
WPA: Invalid TKIP key length 16 (src=00:18:4d:01:bc:5e)
WPA: Invalid TKIP key length 16 (src=00:18:4d:01:bc:5e)
WPA: Invalid TKIP key length 16 (src=00:18:4d:01:bc:5e)
Associated with 00:18:4d:01:bc:5e
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
Associated with 00:18:4d:01:bc:5e
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
CTRL-EVENT-TERMINATING - signal 2 received

I am going to reinstall the driver just in case, but it is working fine without security.

[aolias]

This is making me going nuts.
Ok, I reintalled the driver. I keep the ndiswrapper 1.52 (no reinstall). I turned of the security in my router and I tried the Wicd application. And it worked. So I turned on again the security and I am not able to connect. Neither step by step (command line) neither with Wicd.

Wicd worked fine in Feisty. So there must be something in Hardy. I do not want to go back to Feisty because Hardy performs better, but networking is really important.

So any idea??? Any body need some debug info?

[kevdog]

Rather than complaining it doesn't work, why don't you post some useful output from the command line that would help anyone like myself help you.

[aolias]

Sorry for may last post, but I was desperate after a few hours trying to make the wireless work with no result. :(

wpa_supplicant.conf looks like


ap_scan=1
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="NETGEAR"
scan_ssid=0
proto=WPA2 WPA RSN
key_mgmt=WPA-PSK
psk="the passwd in plain text"
#psk=e1f217aac9c73de737ad791bfa6a462e518a5a5a1ca5c 7e33dd7086f1aad5287
pairwise=TKIP CCMP
group=TKIP CCMP
}


I have tried also with scan_ssid=1 and also the psk in HEX instead of plain text.

sudo lshw -C network



*-network
description: Wireless interface
physical id: 1
logical name: wlan0
serial: 00:18:4d:2b:ee:a0
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+netwpn11 driverversion=1.52+NETGEAR,09/26/2005,1.5.0.21 link=yes multicast=yes wireless=IEEE 802.11g


But I get stuck in the following step. I have changed in my router the security level:
No security - connects ok
WPA
WPA2 can't connect

sudo wpa_supplicant -w -Dwext -iwlan0 -c/etc/wpa_supplicant.conf


CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Trying to associate with 00:18:4d:01:bc:5e (SSID='NETGEAR' freq=2437 MHz)
Associated with 00:18:4d:01:bc:5e
Associated with 00:18:4d:01:bc:5e
Associated with 00:18:4d:01:bc:5e
Authentication with 00:18:4d:01:bc:5e timed out.
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Trying to associate with 00:18:4d:01:bc:5e (SSID='NETGEAR' freq=2437 MHz)
Associated with 00:18:4d:01:bc:5e
WPA: Invalid TKIP key length 16 (src=00:18:4d:01:bc:5e)
WPA: Invalid TKIP key length 16 (src=00:18:4d:01:bc:5e)
WPA: Invalid TKIP key length 16 (src=00:18:4d:01:bc:5e)
WPA: Invalid TKIP key length 16 (src=00:18:4d:01:bc:5e)
Associated with 00:18:4d:01:bc:5e
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
Associated with 00:18:4d:01:bc:5e
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
CTRL-EVENT-TERMINATING - signal 2 received


So from the logs it seems there is a problem during the negotiation
Associated with 00:18:4d:01:bc:5e
WPA: Invalid TKIP key length 16 (src=00:18:4d:01:bc:5e)
:confused:

What this log means??? Because I think that's the key of the problem. So I do not know if it is a problem with the ndiswrapper 1.52, or with the Hardy version of wpa_supplicant. But as I said before in other, I had the wireless working with Feisty.

Thanks for your help!!!!

[kevdog]

What are your WPA2 settings on your router? Usually it is AES for ciphertype and if using a home router PSK rather than EAP.

Ive seen others use a wpa_supplicant.conf file in this format for WPA2 before:

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="ESSID_IN_QUOTES"
psk="ASCII PSK Password in Quotes" or in HEX_WITHOUT_QUOTES
key_mgmt=WPA-PSK
proto=RSN
pairwise=CCMP
}

[aolias]

Good news
wpa_supplicant.conf is working for NETGEAR WPN111 and a NETGEAR DG834PN router.
WPA2 works in the router as
WPA2-PSK - Wi-Fi Protected Access version 2 with Pre-Shared Key, use WPA2-PSK standard encryption with either TKIP or AES encryption type. WPA2 is the most secure security option available. Use WPA2 if your equipment supports it.



ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="NETGEAR"
psk=e1f217aac9c73de737ad791bfa6a462e518a5a5a1ca5c7 e33dd7086f1aad5287
key_mgmt=WPA-PSK
proto=WPA2
pairwise=CCMP
group=TKIP
}



sudo wpa_supplicant -w -Dwext -iwlan0 -c/etc/wpa_supplicant.conf


Trying to associate with 00:18:4d:01:bc:5e (SSID='NETGEAR' freq=2437 MHz)
Associated with 00:18:4d:01:bc:5e
WPA: Key negotiation completed with 00:18:4d:01:bc:5e [PTK=CCMP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:18:4d:01:bc:5e completed (auth) [id=0 id_str=]
WPA: Key negotiation completed with 00:18:4d:01:bc:5e [PTK=CCMP GTK=TKIP]
WPA: Key negotiation completed with 00:18:4d:01:bc:5e [PTK=CCMP GTK=TKIP]
WPA: Key negotiation completed with 00:18:4d:01:bc:5e [PTK=CCMP GTK=TKIP]
Associated with 00:18:4d:01:bc:5e
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet


But the the sudo dhclient wlan0 is not working. We are getting close!!! :)
sudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:18:4d:2b:ee:a0
Sending on LPF/wlan0/00:18:4d:2b:ee:a0
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

[kevdog]

Not sure if this is working or not

Open two command windows and type everything including:

sudo wpa_supplicant -w -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd

May need to open another window and then type

sudo dhclient wlan0

The -dd flag gives extra verbose output to see if the wpa_supplicant process actually is working.

[jerrallan]

Hi, I have struggled with the wireless connection since I have had Ubuntu 6.06. Now I have 8.04 and the same type of problems. I spent hours fiddling with ndiswrapper,modprobe,etc. I have a Belkin 54G usb wireless adapter. I think it is an rt2500 driver.

I had to reinstall Ubuntu yesterday. When I got to reinstalling the wireless, I tried installing through the System>Administration>Network. But that didn't work. I bypassed that when I had 6.04. I settled on a script that is very similar to kevdog's routine in his how to. It is after the section on Setting the Wireless Interface to Connect at Boot * It is very similar to that routine. Yesterday, I tried putting it in /etc/rc.local, but no cigar! I use WEP and do not broadcast my essid. I didn't do anything with ndiswrapper. It is not even installed.


On the command line enter $sudo gedit wireless

Enter the following:
#!/bin/bash
ifconfig <wired network connection interface> down
ifconfig eth0 down
dhclient -r eth0
iwconfig eth0 essid "myroutername" ## in quotes
##iwconfig <wireless_interface> mode Managed ##not used
iwconfig eth0 encryption on
iwconfig eth0 key 1x2y3z4a5b ASCII
ifconfig eth0 up
dhclient eth0

Save the file
On the file right click. Go to permissions and allow it to be executed.

Double click? on it to execute it. You may have to give your password.

Works for me. I cannot get wireless started on boot. Many hours spent trying to get that done. It is inelegant, but it works.

[aolias]

Ok I did it in 2 separate windows... and nothing :( The debug info of the wpa_supplicant process is the following

I put a bit, I did not redirected the ouput to a file




State: GROUP_HANDSHAKE -> COMPLETED
EAPOL: External notification - portValid=1
EAPOL: External notification - EAP success=1
EAP: EAP entering state DISABLED
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
Wireless event: cmd=0x8c09 len=32
PMKID candidate wireless event: flags=0x0 index=0 bssid=00:18:4d:01:bc:5e
RSN: PMKID candidate event - bssid=00:18:4d:01:bc:5e index=0 preauth=0
RSN: Ignored PMKID candidate without preauth flag
EAPOL: startWhen --> 0
RX EAPOL from 00:18:4d:01:bc:5e
RX EAPOL - hexdump(len=179): 01 03 00 af 02 13 ca 00 10 00 00 00 00 00 00 00 05 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 43 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e7 d0 62 09 a2 15 9b 11 b9 32 0b 9a 1c d6 47 97 00 50 7a 3d c3 58 56 82 16 39 62 bd 08 9c f6 a4 24 06 f7 bc d8 c9 59 2e 3c 22 7d a7 b3 6e ad 6c 5e 37 2e 83 b8 f3 62 52 7a fb de ce e4 26 12 09 72 b1 fe 80 a8 0e 6f ce b8 12 6f fd aa 0d a6 0b 20 52 8a 31 37 4e b8 a2 e7 e2 56 ff b1 ef af 8e e3 ce
IEEE 802.1X RX: version=1 type=3 length=175
EAPOL-Key type=2
key_info 0x13ca (ver=2 keyidx=0 rsvd=0 Pairwise Install Ack MIC Secure Encr)
key_length=16 key_data_length=80
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 05
key_nonce - hexdump(len=32): 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 43
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 02 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): e7 d0 62 09 a2 15 9b 11 b9 32 0b 9a 1c d6 47 97
WPA: RX EAPOL-Key - hexdump(len=179): 01 03 00 af 02 13 ca 00 10 00 00 00 00 00 00 00 05 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 43 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e7 d0 62 09 a2 15 9b 11 b9 32 0b 9a 1c d6 47 97 00 50 7a 3d c3 58 56 82 16 39 62 bd 08 9c f6 a4 24 06 f7 bc d8 c9 59 2e 3c 22 7d a7 b3 6e ad 6c 5e 37 2e 83 b8 f3 62 52 7a fb de ce e4 26 12 09 72 b1 fe 80 a8 0e 6f ce b8 12 6f fd aa 0d a6 0b 20 52 8a 31 37 4e b8 a2 e7 e2 56 ff b1 ef af 8e e3 ce
RSN: encrypted key data - hexdump(len=80): 7a 3d c3 58 56 82 16 39 62 bd 08 9c f6 a4 24 06 f7 bc d8 c9 59 2e 3c 22 7d a7 b3 6e ad 6c 5e 37 2e 83 b8 f3 62 52 7a fb de ce e4 26 12 09 72 b1 fe 80 a8 0e 6f ce b8 12 6f fd aa 0d a6 0b 20 52 8a 31 37 4e b8 a2 e7 e2 56 ff b1 ef af 8e e3 ce
WPA: decrypted EAPOL-Key key data - hexdump(len=72): [REMOVED]
State: COMPLETED -> 4WAY_HANDSHAKE
WPA: RX message 3 of 4-Way Handshake from 00:18:4d:01:bc:5e (ver=2)
WPA: IE KeyData - hexdump(len=72): 30 18 01 00 00 0f ac 02 02 00 00 0f ac 04 00 0f ac 02 01 00 00 0f ac 02 00 00 dd 26 00 0f ac 01 02 00 80 23 f3 df bd a2 18 74 2c ab fd 3c 3b f9 25 7a cf 14 d2 2a 58 47 e6 91 f2 ec ea eb 8f 75 d7 f2 dd 00 00 00 00 00
WPA: Sending EAPOL-Key 4/4
WPA: TX EAPOL-Key - hexdump(len=99): 01 03 00 5f 02 03 0a 00 00 00 00 00 00 00 00 00 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 6f 7b c6 ee c5 26 01 bf e9 56 2b 3d 4c af 18 01 00 00
WPA: Installing PTK to the driver.
wpa_driver_wext_set_key: alg=3 key_idx=0 set_tx=1 seq_len=6 key_len=16
EAPOL: External notification - portValid=1
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
RSN: received GTK in pairwise handshake - hexdump(len=34): [REMOVED]
WPA: Group Key - hexdump(len=32): [REMOVED]
WPA: Installing GTK to the driver (keyidx=2 tx=0).
WPA: RSC - hexdump(len=6): 02 00 00 00 00 00
wpa_driver_wext_set_key: alg=2 key_idx=2 set_tx=0 seq_len=6 key_len=32
WPA: Key negotiation completed with 00:18:4d:01:bc:5e [PTK=CCMP GTK=TKIP]
Cancelling authentication timeout
State: GROUP_HANDSHAKE -> COMPLETED
EAPOL: External notification - portValid=1
EAPOL: External notification - EAP success=1
EAP: EAP entering state DISABLED
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
Wireless event: cmd=0x8c09 len=32
PMKID candidate wireless event: flags=0x0 index=0 bssid=00:18:4d:01:bc:5e
RSN: PMKID candidate event - bssid=00:18:4d:01:bc:5e index=0 preauth=0
RSN: Ignored PMKID candidate without preauth flag
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
Wireless event: cmd=0x8c07 len=66
AssocReq IE wireless event - hexdump(len=58): 00 07 4e 45 54 47 45 41 52 01 08 02 04 0b 16 0c 12 18 24 32 04 30 48 60 6c 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00 dd 09 00 03 7f 01 01 00 15 ff 7f
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
Wireless event: cmd=0x8c08 len=35
AssocResp IE wireless event - hexdump(len=27): 01 08 82 84 8b 0c 12 96 18 24 32 04 30 48 60 6c dd 09 00 03 7f 01 01 00 15 ff 7f
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:18:4d:01:bc:5e
Association info event
req_ies - hexdump(len=58): 00 07 4e 45 54 47 45 41 52 01 08 02 04 0b 16 0c 12 18 24 32 04 30 48 60 6c 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00 dd 09 00 03 7f 01 01 00 15 ff 7f
resp_ies - hexdump(len=27): 01 08 82 84 8b 0c 12 96 18 24 32 04 30 48 60 6c dd 09 00 03 7f 01 01 00 15 ff 7f
WPA: set own WPA/RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
State: COMPLETED -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 1->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated with 00:18:4d:01:bc:5e
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RX EAPOL from 00:18:4d:01:bc:5e
RX EAPOL - hexdump(len=99): 01 03 00 5f 02 00 8a 00 10 00 00 00 00 00 00 00 01 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 44 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
EAPOL-Key type=2
key_info 0x8a (ver=2 keyidx=0 rsvd=0 Pairwise Ack)
key_length=16 key_data_length=0
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 01
key_nonce - hexdump(len=32): 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 44
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f 02 00 8a 00 10 00 00 00 00 00 00 00 01 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 44 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:18:4d:01:bc:5e (ver=2)
RSN: msg 1/4 key data - hexdump(len=0):
WPA: Renewed SNonce - hexdump(len=32): 6b 94 37 44 e6 b3 70 4d 56 57 22 6b 17 17 fa f3 68 22 79 86 af 4d aa f8 f5 d3 63 d6 1b a3 29 4c
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: WPA IE for msg 2/4 - hexdump(len=22): 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=121): 01 03 00 75 02 01 0a 00 00 00 00 00 00 00 00 00 01 6b 94 37 44 e6 b3 70 4d 56 57 22 6b 17 17 fa f3 68 22 79 86 af 4d aa f8 f5 d3 63 d6 1b a3 29 4c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 6f 63 06 c2 ce 13 2a 17 14 a6 a1 b9 5e e4 02 b8 00 16 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
RX EAPOL from 00:18:4d:01:bc:5e
RX EAPOL - hexdump(len=179): 01 03 00 af 02 13 ca 00 10 00 00 00 00 00 00 00 02 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 44 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3a cd 74 c5 9e 88 ca 92 19 af c2 a8 a5 5b 47 4c 00 50 b8 57 ca 0e 99 f3 64 f3 f5 c6 ae f9 e1 25 ca a6 43 67 1f 3b b9 a4 cc 4b 12 c5 e1 83 d5 ed 48 28 79 ac 41 1e 69 59 8d 6f ba 22 d8 1e 89 e8 20 c9 88 bf 15 04 0a 6d 9b 4d c4 60 85 a0 7d 76 47 86 aa 7f e9 86 9e 1c 26 4b ac 8e bb ca 72 13 34 e5
IEEE 802.1X RX: version=1 type=3 length=175
EAPOL-Key type=2
key_info 0x13ca (ver=2 keyidx=0 rsvd=0 Pairwise Install Ack MIC Secure Encr)
key_length=16 key_data_length=80
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 02
key_nonce - hexdump(len=32): 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 44
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 02 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 3a cd 74 c5 9e 88 ca 92 19 af c2 a8 a5 5b 47 4c
WPA: RX EAPOL-Key - hexdump(len=179): 01 03 00 af 02 13 ca 00 10 00 00 00 00 00 00 00 02 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 44 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3a cd 74 c5 9e 88 ca 92 19 af c2 a8 a5 5b 47 4c 00 50 b8 57 ca 0e 99 f3 64 f3 f5 c6 ae f9 e1 25 ca a6 43 67 1f 3b b9 a4 cc 4b 12 c5 e1 83 d5 ed 48 28 79 ac 41 1e 69 59 8d 6f ba 22 d8 1e 89 e8 20 c9 88 bf 15 04 0a 6d 9b 4d c4 60 85 a0 7d 76 47 86 aa 7f e9 86 9e 1c 26 4b ac 8e bb ca 72 13 34 e5
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c09 len=32
PMKID candidate wireless event: flags=0x0 index=0 bssid=00:18:4d:01:bc:5e
RSN: PMKID candidate event - bssid=00:18:4d:01:bc:5e index=0 preauth=0
RSN: Ignored PMKID candidate without preauth flag
RTM_NEWLINK: operstate=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RX EAPOL from 00:18:4d:01:bc:5e
RX EAPOL - hexdump(len=179): 01 03 00 af 02 13 ca 00 10 00 00 00 00 00 00 00 03 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 44 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 45 58 fd 2a a0 08 23 7d 51 b5 46 80 a1 ee d3 2e 00 50 b8 57 ca 0e 99 f3 64 f3 f5 c6 ae f9 e1 25 ca a6 43 67 1f 3b b9 a4 cc 4b 12 c5 e1 83 d5 ed 48 28 79 ac 41 1e 69 59 8d 6f ba 22 d8 1e 89 e8 20 c9 88 bf 15 04 0a 6d 9b 4d c4 60 85 a0 7d 76 47 86 aa 7f e9 86 9e 1c 26 4b ac 8e bb ca 72 13 34 e5
IEEE 802.1X RX: version=1 type=3 length=175
EAPOL-Key type=2
key_info 0x13ca (ver=2 keyidx=0 rsvd=0 Pairwise Install Ack MIC Secure Encr)
key_length=16 key_data_length=80
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 03
key_nonce - hexdump(len=32): 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 44
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 02 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 45 58 fd 2a a0 08 23 7d 51 b5 46 80 a1 ee d3 2e
WPA: RX EAPOL-Key - hexdump(len=179): 01 03 00 af 02 13 ca 00 10 00 00 00 00 00 00 00 03 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 44 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 45 58 fd 2a a0 08 23 7d 51 b5 46 80 a1 ee d3 2e 00 50 b8 57 ca 0e 99 f3 64 f3 f5 c6 ae f9 e1 25 ca a6 43 67 1f 3b b9 a4 cc 4b 12 c5 e1 83 d5 ed 48 28 79 ac 41 1e 69 59 8d 6f ba 22 d8 1e 89 e8 20 c9 88 bf 15 04 0a 6d 9b 4d c4 60 85 a0 7d 76 47 86 aa 7f e9 86 9e 1c 26 4b ac 8e bb ca 72 13 34 e5
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
RTM_NEWLINK: operstate=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
Wireless event: cmd=0x8c09 len=32
PMKID candidate wireless event: flags=0x0 index=0 bssid=00:18:4d:01:bc:5e
RSN: PMKID candidate event - bssid=00:18:4d:01:bc:5e index=0 preauth=0
RSN: Ignored PMKID candidate without preauth flag
RX EAPOL from 00:18:4d:01:bc:5e
RX EAPOL - hexdump(len=179): 01 03 00 af 02 13 ca 00 10 00 00 00 00 00 00 00 04 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 44 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0c 76 40 e8 13 49 52 56 1d f9 21 7e 0f 52 27 d1 00 50 b8 57 ca 0e 99 f3 64 f3 f5 c6 ae f9 e1 25 ca a6 43 67 1f 3b b9 a4 cc 4b 12 c5 e1 83 d5 ed 48 28 79 ac 41 1e 69 59 8d 6f ba 22 d8 1e 89 e8 20 c9 88 bf 15 04 0a 6d 9b 4d c4 60 85 a0 7d 76 47 86 aa 7f e9 86 9e 1c 26 4b ac 8e bb ca 72 13 34 e5
IEEE 802.1X RX: version=1 type=3 length=175
EAPOL-Key type=2
key_info 0x13ca (ver=2 keyidx=0 rsvd=0 Pairwise Install Ack MIC Secure Encr)
key_length=16 key_data_length=80
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 04
key_nonce - hexdump(len=32): 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 44
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 02 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 0c 76 40 e8 13 49 52 56 1d f9 21 7e 0f 52 27 d1
WPA: RX EAPOL-Key - hexdump(len=179): 01 03 00 af 02 13 ca 00 10 00 00 00 00 00 00 00 04 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 44 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0c 76 40 e8 13 49 52 56 1d f9 21 7e 0f 52 27 d1 00 50 b8 57 ca 0e 99 f3 64 f3 f5 c6 ae f9 e1 25 ca a6 43 67 1f 3b b9 a4 cc 4b 12 c5 e1 83 d5 ed 48 28 79 ac 41 1e 69 59 8d 6f ba 22 d8 1e 89 e8 20 c9 88 bf 15 04 0a 6d 9b 4d c4 60 85 a0 7d 76 47 86 aa 7f e9 86 9e 1c 26 4b ac 8e bb ca 72 13 34 e5
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
RTM_NEWLINK: operstate=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
Wireless event: cmd=0x8c09 len=32
PMKID candidate wireless event: flags=0x0 index=0 bssid=00:18:4d:01:bc:5e
RSN: PMKID candidate event - bssid=00:18:4d:01:bc:5e index=0 preauth=0
RSN: Ignored PMKID candidate without preauth flag
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
RX EAPOL from 00:18:4d:01:bc:5e
RX EAPOL - hexdump(len=179): 01 03 00 af 02 13 ca 00 10 00 00 00 00 00 00 00 05 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 44 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 83 15 0b 3b 21 2f 78 17 be 5f 4b 47 7c fb 80 b8 00 50 b8 57 ca 0e 99 f3 64 f3 f5 c6 ae f9 e1 25 ca a6 43 67 1f 3b b9 a4 cc 4b 12 c5 e1 83 d5 ed 48 28 79 ac 41 1e 69 59 8d 6f ba 22 d8 1e 89 e8 20 c9 88 bf 15 04 0a 6d 9b 4d c4 60 85 a0 7d 76 47 86 aa 7f e9 86 9e 1c 26 4b ac 8e bb ca 72 13 34 e5
IEEE 802.1X RX: version=1 type=3 length=175
EAPOL-Key type=2
key_info 0x13ca (ver=2 keyidx=0 rsvd=0 Pairwise Install Ack MIC Secure Encr)
key_length=16 key_data_length=80
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 05
key_nonce - hexdump(len=32): 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 44
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 02 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 83 15 0b 3b 21 2f 78 17 be 5f 4b 47 7c fb 80 b8
WPA: RX EAPOL-Key - hexdump(len=179): 01 03 00 af 02 13 ca 00 10 00 00 00 00 00 00 00 05 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 44 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 83 15 0b 3b 21 2f 78 17 be 5f 4b 47 7c fb 80 b8 00 50 b8 57 ca 0e 99 f3 64 f3 f5 c6 ae f9 e1 25 ca a6 43 67 1f 3b b9 a4 cc 4b 12 c5 e1 83 d5 ed 48 28 79 ac 41 1e 69 59 8d 6f ba 22 d8 1e 89 e8 20 c9 88 bf 15 04 0a 6d 9b 4d c4 60 85 a0 7d 76 47 86 aa 7f e9 86 9e 1c 26 4b ac 8e bb ca 72 13 34 e5
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
RTM_NEWLINK: operstate=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
Wireless event: cmd=0x8c09 len=32
PMKID candidate wireless event: flags=0x0 index=0 bssid=00:18:4d:01:bc:5e
RSN: PMKID candidate event - bssid=00:18:4d:01:bc:5e index=0 preauth=0
RSN: Ignored PMKID candidate without preauth flag
Authentication with 00:18:4d:01:bc:5e timed out.
Added BSSID 00:18:4d:01:bc:5e into blacklist
wpa_driver_wext_disassociate
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
State: 4WAY_HANDSHAKE -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Added BSSID 00:00:00:00:00:00 into blacklist
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
State: SCANNING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Scan timeout - try to get results
Received 258 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:18:4d:01:bc:5e ssid='NETGEAR' wpa_ie_len=0 rsn_ie_len=26 caps=0x11
selected based on RSN IE
selected WPA AP 00:18:4d:01:bc:5e ssid='NETGEAR'
Try to find non-WPA AP
Trying to associate with 00:18:4d:01:bc:5e (SSID='NETGEAR' freq=2437 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
RSN: using IEEE 802.11i/D9.0
WPA: Selected cipher suites: group 8 pairwise 24 key_mgmt 2 proto 2
WPA: clearing AP WPA IE
WPA: set AP RSN IE - hexdump(len=26): 30 18 01 00 00 0f ac 02 02 00 00 0f ac 04 00 0f ac 02 01 00 00 0f ac 02 00 00
WPA: using GTK TKIP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: DISCONNECTED -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=15
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c07 len=66
AssocReq IE wireless event - hexdump(len=58): 00 07 4e 45 54 47 45 41 52 01 08 02 04 0b 16 0c 12 18 24 32 04 30 48 60 6c 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00 dd 09 00 03 7f 01 01 00 15 ff 7f
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c08 len=35
AssocResp IE wireless event - hexdump(len=27): 01 08 82 84 8b 0c 12 96 18 24 32 04 30 48 60 6c dd 09 00 03 7f 01 01 00 15 ff 7f
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:18:4d:01:bc:5e
Association info event
req_ies - hexdump(len=58): 00 07 4e 45 54 47 45 41 52 01 08 02 04 0b 16 0c 12 18 24 32 04 30 48 60 6c 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00 dd 09 00 03 7f 01 01 00 15 ff 7f
resp_ies - hexdump(len=27): 01 08 82 84 8b 0c 12 96 18 24 32 04 30 48 60 6c dd 09 00 03 7f 01 01 00 15 ff 7f
WPA: set own WPA/RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:18:4d:01:bc:5e
No keys have been configured - skip key clearing
Associated with 00:18:4d:01:bc:5e
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RX EAPOL from 00:18:4d:01:bc:5e
RX EAPOL - hexdump(len=99): 01 03 00 5f 02 00 8a 00 10 00 00 00 00 00 00 00 01 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 45 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
EAPOL-Key type=2
key_info 0x8a (ver=2 keyidx=0 rsvd=0 Pairwise Ack)
key_length=16 key_data_length=0
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 01
key_nonce - hexdump(len=32): 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 45
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f 02 00 8a 00 10 00 00 00 00 00 00 00 01 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 45 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:18:4d:01:bc:5e (ver=2)
RSN: msg 1/4 key data - hexdump(len=0):
WPA: Renewed SNonce - hexdump(len=32): 0a ed 10 c9 82 ed 7c 78 fc 8d b9 22 f3 bc a4 7c 14 ae a3 99 92 40 3f 37 5e 60 d0 a8 f7 ad 22 2d
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: WPA IE for msg 2/4 - hexdump(len=22): 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=121): 01 03 00 75 02 01 0a 00 00 00 00 00 00 00 00 00 01 0a ed 10 c9 82 ed 7c 78 fc 8d b9 22 f3 bc a4 7c 14 ae a3 99 92 40 3f 37 5e 60 d0 a8 f7 ad 22 2d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c7 2b 52 d8 28 ee 63 61 f9 cd 9d 1b 0d 66 4a e9 00 16 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c09 len=32
PMKID candidate wireless event: flags=0x0 index=0 bssid=00:18:4d:01:bc:5e
RSN: PMKID candidate event - bssid=00:18:4d:01:bc:5e index=0 preauth=0
RSN: Ignored PMKID candidate without preauth flag
RTM_NEWLINK: operstate=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RX EAPOL from 00:18:4d:01:bc:5e
RX EAPOL - hexdump(len=179): 01 03 00 af 02 13 ca 00 10 00 00 00 00 00 00 00 02 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 45 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1e 0f fc 61 0f cf 5a 8f 8a 26 8b cb 3a ef 07 d6 00 50 5f 19 6f 55 fe 2c ea d1 41 2b e7 06 76 25 60 12 05 30 77 0b 31 68 ba d3 0e 78 ff d1 f4 d8 1f 0d 3e 2c c7 27 65 07 52 0d 14 c4 cf dd 3a 7a 52 8f 37 46 04 da e0 1a 04 79 a8 e6 9d 65 de 59 b1 e9 04 b8 02 a1 9c 04 c8 f0 86 e2 7c 9a a4 cf 8d 02
IEEE 802.1X RX: version=1 type=3 length=175
EAPOL-Key type=2
key_info 0x13ca (ver=2 keyidx=0 rsvd=0 Pairwise Install Ack MIC Secure Encr)
key_length=16 key_data_length=80
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 02
key_nonce - hexdump(len=32): 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 45
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 02 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 1e 0f fc 61 0f cf 5a 8f 8a 26 8b cb 3a ef 07 d6
WPA: RX EAPOL-Key - hexdump(len=179): 01 03 00 af 02 13 ca 00 10 00 00 00 00 00 00 00 02 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 45 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1e 0f fc 61 0f cf 5a 8f 8a 26 8b cb 3a ef 07 d6 00 50 5f 19 6f 55 fe 2c ea d1 41 2b e7 06 76 25 60 12 05 30 77 0b 31 68 ba d3 0e 78 ff d1 f4 d8 1f 0d 3e 2c c7 27 65 07 52 0d 14 c4 cf dd 3a 7a 52 8f 37 46 04 da e0 1a 04 79 a8 e6 9d 65 de 59 b1 e9 04 b8 02 a1 9c 04 c8 f0 86 e2 7c 9a a4 cf 8d 02
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
RX EAPOL from 00:18:4d:01:bc:5e
RX EAPOL - hexdump(len=179): 01 03 00 af 02 13 ca 00 10 00 00 00 00 00 00 00 03 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 45 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b7 74 39 7b 2f b7 5c 16 f3 8c 44 71 ab 21 3d b8 00 50 5f 19 6f 55 fe 2c ea d1 41 2b e7 06 76 25 60 12 05 30 77 0b 31 68 ba d3 0e 78 ff d1 f4 d8 1f 0d 3e 2c c7 27 65 07 52 0d 14 c4 cf dd 3a 7a 52 8f 37 46 04 da e0 1a 04 79 a8 e6 9d 65 de 59 b1 e9 04 b8 02 a1 9c 04 c8 f0 86 e2 7c 9a a4 cf 8d 02
IEEE 802.1X RX: version=1 type=3 length=175
EAPOL-Key type=2
key_info 0x13ca (ver=2 keyidx=0 rsvd=0 Pairwise Install Ack MIC Secure Encr)
key_length=16 key_data_length=80
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 03
key_nonce - hexdump(len=32): 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 45
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 02 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): b7 74 39 7b 2f b7 5c 16 f3 8c 44 71 ab 21 3d b8
WPA: RX EAPOL-Key - hexdump(len=179): 01 03 00 af 02 13 ca 00 10 00 00 00 00 00 00 00 03 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 45 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b7 74 39 7b 2f b7 5c 16 f3 8c 44 71 ab 21 3d b8 00 50 5f 19 6f 55 fe 2c ea d1 41 2b e7 06 76 25 60 12 05 30 77 0b 31 68 ba d3 0e 78 ff d1 f4 d8 1f 0d 3e 2c c7 27 65 07 52 0d 14 c4 cf dd 3a 7a 52 8f 37 46 04 da e0 1a 04 79 a8 e6 9d 65 de 59 b1 e9 04 b8 02 a1 9c 04 c8 f0 86 e2 7c 9a a4 cf 8d 02
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
RTM_NEWLINK: operstate=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
Wireless event: cmd=0x8c09 len=32
PMKID candidate wireless event: flags=0x0 index=0 bssid=00:18:4d:01:bc:5e
RSN: PMKID candidate event - bssid=00:18:4d:01:bc:5e index=0 preauth=0
RSN: Ignored PMKID candidate without preauth flag
RX EAPOL from 00:18:4d:01:bc:5e
RX EAPOL - hexdump(len=179): 01 03 00 af 02 13 ca 00 10 00 00 00 00 00 00 00 04 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 45 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0c f9 36 50 5f c2 dc 3c ea ee 7e 68 96 26 e2 6f 00 50 5f 19 6f 55 fe 2c ea d1 41 2b e7 06 76 25 60 12 05 30 77 0b 31 68 ba d3 0e 78 ff d1 f4 d8 1f 0d 3e 2c c7 27 65 07 52 0d 14 c4 cf dd 3a 7a 52 8f 37 46 04 da e0 1a 04 79 a8 e6 9d 65 de 59 b1 e9 04 b8 02 a1 9c 04 c8 f0 86 e2 7c 9a a4 cf 8d 02
IEEE 802.1X RX: version=1 type=3 length=175
EAPOL-Key type=2
key_info 0x13ca (ver=2 keyidx=0 rsvd=0 Pairwise Install Ack MIC Secure Encr)
key_length=16 key_data_length=80
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 04
key_nonce - hexdump(len=32): 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 45
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 02 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 0c f9 36 50 5f c2 dc 3c ea ee 7e 68 96 26 e2 6f
WPA: RX EAPOL-Key - hexdump(len=179): 01 03 00 af 02 13 ca 00 10 00 00 00 00 00 00 00 04 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 45 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0c f9 36 50 5f c2 dc 3c ea ee 7e 68 96 26 e2 6f 00 50 5f 19 6f 55 fe 2c ea d1 41 2b e7 06 76 25 60 12 05 30 77 0b 31 68 ba d3 0e 78 ff d1 f4 d8 1f 0d 3e 2c c7 27 65 07 52 0d 14 c4 cf dd 3a 7a 52 8f 37 46 04 da e0 1a 04 79 a8 e6 9d 65 de 59 b1 e9 04 b8 02 a1 9c 04 c8 f0 86 e2 7c 9a a4 cf 8d 02
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
RTM_NEWLINK: operstate=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
Wireless event: cmd=0x8c09 len=32
PMKID candidate wireless event: flags=0x0 index=0 bssid=00:18:4d:01:bc:5e
RSN: PMKID candidate event - bssid=00:18:4d:01:bc:5e index=0 preauth=0
RSN: Ignored PMKID candidate without preauth flag
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
RX EAPOL from 00:18:4d:01:bc:5e
RX EAPOL - hexdump(len=179): 01 03 00 af 02 13 ca 00 10 00 00 00 00 00 00 00 05 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 45 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ab 9e a1 6c 47 05 8b 45 83 8d f5 d3 b3 12 f9 6a 00 50 5f 19 6f 55 fe 2c ea d1 41 2b e7 06 76 25 60 12 05 30 77 0b 31 68 ba d3 0e 78 ff d1 f4 d8 1f 0d 3e 2c c7 27 65 07 52 0d 14 c4 cf dd 3a 7a 52 8f 37 46 04 da e0 1a 04 79 a8 e6 9d 65 de 59 b1 e9 04 b8 02 a1 9c 04 c8 f0 86 e2 7c 9a a4 cf 8d 02
IEEE 802.1X RX: version=1 type=3 length=175
EAPOL-Key type=2
key_info 0x13ca (ver=2 keyidx=0 rsvd=0 Pairwise Install Ack MIC Secure Encr)
key_length=16 key_data_length=80
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 05
key_nonce - hexdump(len=32): 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 45
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 02 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): ab 9e a1 6c 47 05 8b 45 83 8d f5 d3 b3 12 f9 6a
WPA: RX EAPOL-Key - hexdump(len=179): 01 03 00 af 02 13 ca 00 10 00 00 00 00 00 00 00 05 88 1d 6f ea 48 e6 1e 3b 51 da 98 a5 ef f2 02 0a 03 5c d2 90 38 16 10 34 6f bb 57 ac ce 30 26 45 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ab 9e a1 6c 47 05 8b 45 83 8d f5 d3 b3 12 f9 6a 00 50 5f 19 6f 55 fe 2c ea d1 41 2b e7 06 76 25 60 12 05 30 77 0b 31 68 ba d3 0e 78 ff d1 f4 d8 1f 0d 3e 2c c7 27 65 07 52 0d 14 c4 cf dd 3a 7a 52 8f 37 46 04 da e0 1a 04 79 a8 e6 9d 65 de 59 b1 e9 04 b8 02 a1 9c 04 c8 f0 86 e2 7c 9a a4 cf 8d 02
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
RTM_NEWLINK: operstate=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
Wireless event: cmd=0x8c09 len=32
PMKID candidate wireless event: flags=0x0 index=0 bssid=00:18:4d:01:bc:5e
RSN: PMKID candidate event - bssid=00:18:4d:01:bc:5e index=0 preauth=0
RSN: Ignored PMKID candidate without preauth flag
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface wlan0
State: 4WAY_HANDSHAKE -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_deauthenticate
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Removed BSSID 00:00:00:00:00:00 from blacklist (clear)
Removed BSSID 00:18:4d:01:bc:5e from blacklist (clear)
Cancelling scan request
Cancelling authentication timeout
WEXT: Operstate: linkmode=0, operstate=6

[bakarocket]

Hi folks. Thanks for the walkthrough, but I'm having a small problem.

I'm using a Buffalo Airstation WHR-HP-G with a Panasonic CF-W5. I followed the instructions for the WPA-PSK setup, but I get stuck on the final setup. I reinstalled the iwl3945 driver that I am apparently using, but now the wireless card is "unclaimed".

I should note that I have this installed inside Windows - because I wanted to check to see if the wireless would work before doing a full install - but I'm not sure if that is affecting it.

This is the original output:


*-network
description: Wireless interface
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: wmaster0
version: 02
serial: 00:18:de:aa:bd:6c
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl3945 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11g


Apparently the driver wasn't found.



sudo wpa_supplicant -w -Diwl3945 -iwmaster0 -c/etc/wpa_supplicant.conf
Unsupported driver 'iwl3945'.

So I tried reinstalling the driver, then running through the process and ignoring the output, and now...I have nothing. :-(



*-network UNCLAIMED
description: Network controller
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:03:00.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: cap_list
configuration: latency=0

Any help that anyone could give me would be appreciated, even just a pointing in a general direction.

p.s. I did fill in the other necessary stuff first (SSID,etc.), I just didn't include the details in the post.

p.p.s. The wireless card is now recognized again after a restart, but I still can't start the wireless service for some reason.

[timmyt]

I'm completely and utterly frustrated with my wireless connection... I've tried several different network adapters and several different machines, but the result is about the same... my connection is great for a few seconds and then seems to stop working. Everything indicates that the connection is still up and running, but not even a ping to the router gets through.

To simplify things, I'll just talk about the one network adapter and machine...

I'm using Ubuntu 8.04 with a Broadcomm "BCM94311MCG wlan mini-PCI" adapter using the "ndiswrapper+bcmwl5" driver.

When I run the wpa_supplicant, it seems to indicate that it's connected properly, but it never returns to the terminal to allow typing the rest of the commands (it's supposed to, right??). It ends with "EAPOL: startWhen --> 0". I then type the rest of the commands in another window (while wpa_supplicant is still running) and everything seems to work correctly. However, after about 5 seconds no traffic gets through.

After running the dhclient, I tried pinging the router until it stopped working... It started out with pings around 30-200ms, then jumped to 2000-10,000 ms pings, then dropped to 1-3ms pings. Then, it paused for a long while and started reporting "ping: sendmsg: No buffer space available". I stopped it and then restarted it and started getting:


PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 192.168.0.3 icmp_seq=3 Destination Host Unreachable
From 192.168.0.3 icmp_seq=6 Destination Host Unreachable
From 192.168.0.3 icmp_seq=7 Destination Host Unreachable
From 192.168.0.3 icmp_seq=9 Destination Host Unreachable
From 192.168.0.3 icmp_seq=10 Destination Host Unreachable
From 192.168.0.3 icmp_seq=13 Destination Host Unreachable

I've used this network adapter with this router before in Ubuntu 8.04 and had no trouble. The only change is that I moved it from one city to another. I'd chalk it up to radio interference, but it all works fine in Vista, XP, and Win2000.

[Sim777]

Hello,

This seems like a proper thread to ask this.

What can I do when everything works except for one thing..


sim@sim:~$ iwlist scanning
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 No scan results


I know there should be at least 12 different networks around....yet somehow iwlist doesn't pick up anything.

[kevdog]

Id double check the driver, dmesg, and ifconfig.

[timmyt]

My connection is still completely unreliable... Does any one have any suggestion at least where to look for a possible answer?


I'm completely and utterly frustrated with my wireless connection... I've tried several different network adapters and several different machines, but the result is about the same... my connection is great for a few seconds and then seems to stop working. Everything indicates that the connection is still up and running, but not even a ping to the router gets through.

To simplify things, I'll just talk about the one network adapter and machine...

I'm using Ubuntu 8.04 with a Broadcomm "BCM94311MCG wlan mini-PCI" adapter using the "ndiswrapper+bcmwl5" driver.

When I run the wpa_supplicant, it seems to indicate that it's connected properly, but it never returns to the terminal to allow typing the rest of the commands (it's supposed to, right??). It ends with "EAPOL: startWhen --> 0". I then type the rest of the commands in another window (while wpa_supplicant is still running) and everything seems to work correctly. However, after about 5 seconds no traffic gets through.

After running the dhclient, I tried pinging the router until it stopped working... It started out with pings around 30-200ms, then jumped to 2000-10,000 ms pings, then dropped to 1-3ms pings. Then, it paused for a long while and started reporting "ping: sendmsg: No buffer space available". I stopped it and then restarted it and started getting:


PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 192.168.0.3 icmp_seq=3 Destination Host Unreachable
From 192.168.0.3 icmp_seq=6 Destination Host Unreachable
From 192.168.0.3 icmp_seq=7 Destination Host Unreachable
From 192.168.0.3 icmp_seq=9 Destination Host Unreachable
From 192.168.0.3 icmp_seq=10 Destination Host Unreachable
From 192.168.0.3 icmp_seq=13 Destination Host Unreachable

I've used this network adapter with this router before in Ubuntu 8.04 and had no trouble. The only change is that I moved it from one city to another. I'd chalk it up to radio interference, but it all works fine in Vista, XP, and Win2000.

[timmyt]

Okay... This doesn't make a whole lot of sense, but my connection seems to be reliable now...

I changed my SSID and password to what I used before and it now works fine. The one that didn't work had an underscore in the name and the password was all uppercase. I now have an SSID with no underscore and an all lowercase password and there are no problems now. :(

[ubume2]

I use WEP encryption. I have spent many hours trying to get an internet connection on reboot, but no luck. I followed the WEP sections of this howto to the letter.

I made modifications to /etc/rc.local, but no luck.

I had been able to boot up using a simple script on my Desktop. Couldn't figure out why the same commands wouldn't work in rc.local and connect on boot up.

I noticed that rc.locals 1st line had #!/bin/sh -e. It's a shell command, but it wasn't working for me.

I commented that out and put #!/bin/bash. gave rc.local its permissions, rebooted and had internet!

Here is what my rc.local looks like:

#!/bin/bash
####!/bin/sh -e
#
# rc.local
#
#This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
ifconfig eth0 down

ifconfig eth1 down
dhclient -r eth1
ifconfig eth1 up
iwconfig eth1 essid "linksys"
iwconfig eth1 encryption on
iwconfig eth1 key a1b2c3d4e5 ASCII
dhclient eth1
exit 0

For what it's worth, it worked for me! This HowTo is the place to start if you have wireless problems and Network Manager just doesn't seem to work for you.

Edit: Important bit of information: My wireless device is a Belkin Wireless USB adapter. One of the inexpensive ones you can buy at Wal-Mart. Evidently, 8.04 has a compatible native driver for this wireless adapter. No need to use ndiswrapper.

[Atra_Phasma]

This is truly a great guide, and it got me further than anything else to setting up my wireless.
Atra

[compgeek83]

these directions worked great for me, when trying to set a static ip (on a wired connection) I could never get anything to work, but when I did it manually as these directions showed i'm up and running no problems.

[kevdog]

Manual configuration is the ultimate fallback, glad it has worked for you!

[vexingmodstwo]

I tried this as a fall back because my wireless card refuses to work. I turned off the encryption on my access point and tried the first option.

It all went smoothly until the last command and I got this:


There is already a pid file /var/run/dhclient.pid with pid 7856
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1b:fc:de:c6:9e
Sending on LPF/wlan0/00:1b:fc:de:c6:9e
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Any ideas?

[kevdog]

Yes, can you post the following:

lshw -C network
iwlist scan

I would just like to check a few parameters!

[vexingmodstwo]

Yes, can you post the following:

lshw -C network
iwlist scan

I would just like to check a few parameters!

Result of lshw -C network



*-network
description: Wireless interface
product: BCM94311MCG wlan mini-PCI
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:05:00.0
logical name: wlan0
version: 01
serial: 00:1b:fc:de:c6:9e
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.52+Broadcom,10/12/2006, 4.100. latency=0 link=no module=ndiswrapper multicast=yes wireless=IEEE 802.11g
*-network
description: Ethernet interface
product: BCM4401-B0 100Base-TX
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:08:00.0
logical name: eth0
version: 02
serial: 00:1c:23:8e:62:77
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=b44 driverversion=2.0 duplex=full ip=192.168.1.4 latency=64 link=yes module=ssb multicast=yes port=twisted pair speed=100MB/s


Result of iwlist scan



lo Interface doesn't support scanning.

wlan0 No scan results

eth0 Interface doesn't support scanning.


Thanks for the help! BTW... I'm going to eventually do the WEP option but I want to see if the wireless card can work at ALL first.

[kevdog]

Something is wrong with your wireless driver -- seems like you may be a victim of the new b44/ssb/ndiswrapper conflict, although from what you posted things seem correct.

Couple of things to check
dmesg
See jamie jackson's tutorial:
https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx/Feisty_No-Fluff

[vexingmodstwo]

Something is wrong with your wireless driver -- seems like you may be a victim of the new b44/ssb/ndiswrapper conflict, although from what you posted things seem correct.

Couple of things to check
dmesg
See jamie jackson's tutorial:
https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx/Feisty_No-Fluff

Thanks, I'll keep digging.

On a lark a remembered I had an old Linksys USB Network Adaptor and plugged that in. It shows up fine and even picks up a signal from my router and a couple of my neighbors' routers. BUT I can't connect to them. Could it be that my problem is in the wireless protocol itself and / or the Network Manager module? How would I check that?

[kevdog]

It could be a lot of things.

Manual connection initially is the way to go if you are having problems. A lot of times debugging messages are presented that give you a clue what is not working. Once you getting it working and figure some things out, you can then migrate to NWM or WICD.

[vexingmodstwo]

It could be a lot of things.

Manual connection initially is the way to go if you are having problems. A lot of times debugging messages are presented that give you a clue what is not working. Once you getting it working and figure some things out, you can then migrate to NWM or WICD.

Did everything in Jackson's how to. Still nothing.

the lshw thing is coming up with everything that it is supposed to come with (except the part that says link=no which is like the thing is mocking me, but that's another story).

Is anyone else having this problem?

[kevdog]

Check dmesg to see if you are getting any errors surround the install of the ndiswrapper/driver combo into the kernel.

[vexingmodstwo]

Check dmesg to see if you are getting any errors surround the install of the ndiswrapper/driver combo into the kernel.

The list of errors is so large I wouldn't know where to look. AND I rebooted and it's back to square one. Nothing stuck. The wireless card doesn't show the "wlan0" interface in lshw and the module is back to being ssb.

This is bordering on ridiculous.

EDIT: This is what I see when I reboot and then run the sudo lshw -C network:



*-network
description: Network controller
product: BCM94311MCG wlan mini-PCI
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:05:00.0
version: 01
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=b43-pci-bridge latency=0 module=ssb
*-network
description: Ethernet interface
product: BCM4401-B0 100Base-TX
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:08:00.0
logical name: eth0
version: 02
serial: 00:1c:23:8e:62:77
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=b44 driverversion=2.0 duplex=full ip=192.168.1.4 latency=64 link=yes module=ssb multicast=yes port=twisted pair speed=100MB/s


Then I go through the "Try it out" part of Jamie's How To.

Then I get this with lshw:




*-network
description: Wireless interface
product: BCM94311MCG wlan mini-PCI
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:05:00.0
logical name: wlan0
version: 01
serial: 00:1b:fc:de:c6:9e
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.52+Broadcom,10/12/2006, 4.100. latency=0 link=no module=ndiswrapper multicast=yes wireless=IEEE 802.11g
*-network DISABLED
description: Ethernet interface
product: BCM4401-B0 100Base-TX
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:08:00.0
logical name: eth0
version: 02
serial: 00:1c:23:8e:62:77
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=b44 driverversion=2.0 latency=64 link=no module=ssb multicast=yes port=twisted pair


This means it worked, right? But I still can't connect through the wireless card. And this time on reboot the friggin wifi light turned on just to taunt me.

[kevdog]

Did you do the following to make it permanent?:

echo -e '#Hardy ssb/ndiswrapper workaround, added' `date` '\ninstall ndiswrapper modprobe -r b43 b44 b43legacy ssb; modprobe --ignore-install ndiswrapper $CMDLINE_OPTS; modprobe ssb; modprobe b44;' | sudo tee -a /etc/modprobe.d/ndiswrapper

If you just cut and paste, it should bring you back to where you are currently at boot. You will never need to do this again since that script simply or addends things to the /etc/modprobe.d/ndiswrapper file. Take a look and the file to see if these things are not duplicated.

Please look in dmesg for something if regards to ndiswrapper. That is what you are looking for. Forget everything else.

[vexingmodstwo]

Did you do the following to make it permanent?:

echo -e '#Hardy ssb/ndiswrapper workaround, added' `date` '\ninstall ndiswrapper modprobe -r b43 b44 b43legacy ssb; modprobe --ignore-install ndiswrapper $CMDLINE_OPTS; modprobe ssb; modprobe b44;' | sudo tee -a /etc/modprobe.d/ndiswrapper

If you just cut and paste, it should bring you back to where you are currently at boot. You will never need to do this again since that script simply or addends things to the /etc/modprobe.d/ndiswrapper file. Take a look and the file to see if these things are not duplicated.

Please look in dmesg for something if regards to ndiswrapper. That is what you are looking for. Forget everything else.

Yeah, this second go around I made it permanent and the changes stuck. I still can't connect through wireless. WICD sees the wireless networks (mine and a few of my neighbors') but locks up when I try to connect to mine.

I ran the dmesg and found references to ndiswrapper (I'm putting in everything from the first reference to the last):



[ 47.261352] ndiswrapper version 1.52 loaded (smp=yes, preempt=no)
[ 47.376977] ndiswrapper: driver bcmwl5 (Broadcom,10/12/2006, 4.100.15.5) loaded
[ 47.377183] ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 18 (level, low) -> IRQ 16
[ 47.377219] PCI: Setting latency timer of device 0000:05:00.0 to 64
[ 47.380544] ndiswrapper: using IRQ 16
[ 47.755746] wlan0: ethernet device 00:1b:fc:de:c6:9e using NDIS driver: bcmwl5, version: 0x4640f05, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 14E4:4311.5.conf
[ 47.755789] wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
[ 47.759907] usbcore: registered new interface driver ndiswrapper

[kevdog]

Ok things look good.

With the wired device down, and the wireless device up, please make sure you can see some other networks with
(sudo ifconfig eth0 down, sudo ifconfig wlan0 up)

iwlist scan

Then try connecting if you can to a router or access point with no enabled encryption. Can you do this?

[vexingmodstwo]

Ok things look good.

With the wired device down, and the wireless device up, please make sure you can see some other networks with
(sudo ifconfig eth0 down, sudo ifconfig wlan0 up)

iwlist scan

Then try connecting if you can to a router or access point with no enabled encryption. Can you do this?

I can see networks with eth0 down and wlan0 up.

I then turned off encryption on my access point and tried to connect with wlan0 and it didn't work. It did lock up WCID again but amazingly I'm still connected after I turned eth0 back up.

The wifi light is on, I see networks, but any attempt to connect to one fails (and locks up WCID).

It's like this laptop doesn't want to be wireless... ;)

[kevdog]

Connect trying the command line:



sudo ifconfig eth0 down
sudo ifconfig wlan0 down
sudo ifconfig wlan0 up
sudo iwconfig wlan0 essid <ESSID>
sudo dhclient wlan0

[vexingmodstwo]

Connect trying the command line:



sudo ifconfig eth0 down
sudo ifconfig wlan0 down
sudo ifconfig wlan0 up
sudo iwconfig wlan0 essid <ESSID>
sudo dhclient wlan0

I received errors with the iwconfig and dhclient commands.

When I ran sudo iwconfig wlan0 essid <ESSID> I received this:

bash: syntax error near unexpected token `newline'

When I ran the sudo dhclient wlan0 I received this:

There is already a pid file /var/run/dhclient.pid with pid 6069
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Terminated

[kevdog]

sudo iwconfig wlan0 essid "ESSID_IN_QUOTES"

[vexingmodstwo]

sudo iwconfig wlan0 essid "ESSID_IN_QUOTES"

Ooops... :(

Here's the output the the sudo dhclient wlan0:

There is already a pid file /var/run/dhclient.pid with pid 23707
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1b:fc:de:c6:9e
Sending on LPF/wlan0/00:1b:fc:de:c6:9e
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

[kevdog]

can you post
iwlist scan

and tell me the exact parameters you typed on the command line?

[vexingmodstwo]

can you post
iwlist scan

and tell me the exact parameters you typed on the command line?

I typed exactly what you wrote: iwlist scan and got this:


lo Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:18:4D:80:23:3A
ESSID:"NETGEAR"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:10/100 Signal level:-89 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:15:05:EE:47:3F
ESSID:"pumpkin"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:95/100 Signal level:-35 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 03 - Address: 00:E0:98:CF:B2:26
ESSID:"04Z410189167"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:1/100 Signal level:-95 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=200
Extra:atim=0
Cell 04 - Address: 00:1C:10:34:BE:F0
ESSID:"Beaton Home Network"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.452 GHz (Channel 9)
Quality:3/100 Signal level:-94 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 05 - Address: 00:15:05:ED:D0:72
ESSID:"29OU7"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.452 GHz (Channel 9)
Quality:7/100 Signal level:-91 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0

eth0 Interface doesn't support scanning.

[kevdog]

Which network are you trying to connect to? If its Network #1 -- the signal quality 10/100 is very poor. The remainder of the networks have some form of encryption.

[vexingmodstwo]

Which network are you trying to connect to? If its Network #1 -- the signal quality 10/100 is very poor. The remainder of the networks have some form of encryption.

Cell 2 That's mine.

EDIT: I don't know how or why but while I was waiting for some further help I decided to scrap WICD and install wifiradar... and it worked! Now let's hope it stays that way.

[kevdog]

Good luck -- I hope it stays working. If I look at Cell #2:

Cell 02 - Address: 00:15:05:EE:47:3F
ESSID:"pumpkin"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:95/100 Signal level:-35 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0

It states the encryption key=on. I wasn't feeding you any encryption parameters with my earlier instructions b/c I had instructed you to initially turn off the encryption. I'm assuming its WEP encrypted by your output, but this requires an additional configuration parameter in order to connect

sudo ifconfig wlan0 key <key>

[vexingmodstwo]

Good luck -- I hope it stays working. If I look at Cell #2:

Cell 02 - Address: 00:15:05:EE:47:3F
ESSID:"pumpkin"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:95/100 Signal level:-35 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0

It states the encryption key=on. I wasn't feeding you any encryption parameters with my earlier instructions b/c I had instructed you to initially turn off the encryption. I'm assuming its WEP encrypted by your output, but this requires an additional configuration parameter in order to connect

sudo ifconfig wlan0 key <key>

Oh, right. That was after I had turned encryption back on on the router because everything else (besides this laptop) trying to connect to it was encrypted and offline.

I'm still trying to figure out how it finally started working so as to help anyone else with the same issue. I think it was a combination of this How To, this one (http://ubuntuforums.org/showthread.php?t=760568), and Jamie Jackson's how to, along with using wifiradar. I had tried to do a manual configuration with WICD, but it didn't work. With wifiradar it worked right after I entered the default gateway address.

So basically I had a driver issue, a config issue, then a network manager issue.

Hope this helps anyone else trying to figure this out.

And Kevdog, I can't thank you enough for your patience and help.

[ljungkvist]

Hi

I use a Compaq presario V6000 laptop with the Broadcom BCM94311 wireless card. When I first installed ubuntu (hardy) it didn't work, so I followed this (http://ubuntuforums.org/showthread.php?t=769990&highlight=presario&page=1) guide, which made it work. My only problem now is that the network manager for some reason doesn't manage to connect automatically at boot. I have to check/uncheck the "enable wireless" option in tray icon. Then it works.

So because of that, and the fact that I would like to know how these things work :D, I decided to give this thing a shoot.

The network I'm trying to connect to uses WPA, so I naturally followed the instruction listed under that one: I created the wpa_supplicant.conf-file as described, and then followed the commands. Here is my output on the first two:


╔═compres═▷ ~
╚kalle 20$ sudo ifconfig wlan0 down
╔═compres═▷ ~
╚kalle 21$ sudo dhclient -r wlan0
There is already a pid file /var/run/dhclient.pid with pid 8708
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:14:a5:d9:49:e4
Sending on LPF/wlan0/00:14:a5:d9:49:e4
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.178.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.


Is there something going wrong already here? Because when I then run the next command

sudo wpa_supplicant -w -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd
It just gives me endless of error output (i can post it). I tried with both the wext and the ndiswrapper flags (since I use ndiswrapper).

Another question: Don't I have to shut off the network assistant? (how?)

[kevdog]

Just a few things.

I think the only way to turn Network Manager off, is to uninstall the program:
sudo aptitude purge network-manager-gnome

As far as bring up interfaces its the command
sudo ifconfig <interface> up

The -dd flag in the statement:
sudo wpa_supplicant -w -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd

Is to give debugging messages. Once its up and running and you do not need the messages you can do the following:
sudo wpa_supplicant -Bw -Dwext -iwlan0 -c/etc/wpa_supplicant.conf

The B flag sends it to the background

If you are having good luck connecting with the manual approach, I would either put the commands in a script file, or switch to the WICD gui program. It works in much the same way as the manual approach.

[SammyBoy247]

[SOLVED] see posts below

I have happily had a wired network since copper was invented but my wife recently get a new laptop a we decided to take advantage of it's on board Realtek RTL8187B. We bought a cheap Netgear WGR614 router and within 10 novice minutes we were up and running with msXP on the laptop and 8.04 x64 on the main desktop.

Two days later the windows laptop had massive spyware and virus issues dispite a full norton suite.

ANY-WAY - installed Hardy on laptop (dual boot) started to configure wifi with ndiswrapper and windows XP drivers. Got hardware up and running using wired LAN but in process I mucked up the domain resolution somehow and lost all networking and things just got worse from there.

Gave up.... Fresh install over all partitions from live CD with wired LAN update.

ANY-WAY (again)
Currently I am looking at a fresh install of Hardy.
I have purged network manager.
I have installed ndiswrapper and the appropriate winXP drivers.
I have a wlan0 device.
iwlist scan reveals my home wifi network.
I have turned off all security on the router.
sudo dhclient wlan0 results in "No DHCPOFFERS"

I am a complete novice to wireless but have spent three solid days on this and have learnt alot but not enough.

I officially give up and could do with some help. Please let me know what you need me to post. I can do another fresh install if you'd like a fresh canvas.

Thanks in advance.

PS Following a recent post who's situation seemed very similar I installed wifi-radar. I too found my router but could not obtain an ip from it.

Also I have a Nokia N95 which has no problem connecting to the router with and without wep+/-wpa.

[kevdog]

The realtek chipset is very difficult - there is a 8187b and 8187l varieties. For the 8187b drivers I thought the win98 driver was the appropriate choice rather than winxp. The 8187l driver I am in the process of figuring out -- however it is different.

[SammyBoy247]

I definately have the 8187b chipset I will try the '98 drivers instead of the XP. I chose the XP drivers following a HOWTO on the subect NDISing 8187b chipset.

So many people have trouble with this chip however many more claim they have it up and running under ubuntu.

Am I better off just forgeting the onboard chipset and buying a more widely supported usb dongle?

[SammyBoy247]

I can't believe it....

win98 drivers
eth0 down
wlan0 down
wlan0 up
dhclient wlan0

And I'm up and running
Please find enclosed another thank-you for your collection

[chrisbedford]

PLEASE won't you rename this thread Manual WIRELESS Network config...

[n6k6t6]

Please help!
My problem is really fascinating.
I have a Dell Inspiron 1420n laptop. Wireless worked fine except for
one annoying issue: upon return from suspend at a different physical
location the network manager took a VERY LONG time to update its list
of networks. New networks would be visible via "iwlist scanning"
and yet the NetworkManager is still attempting to connect to a network
that is miles and miles away...
Don't get me wrong, I, as others with this problem, did have a
decent workaround. Mine was:
modprobe -r ipw3945
modprobe ipw3945

The only problem was that it took too long.

It is annoyance by the lack of something as simple as a rescan button
that made we install wicd, uninstalling NetworkManager in the process.

Ever since my wireless doesn't work.
To troubleshoot I followed the instructions in this howto,
but had no luck.

First, the following output says "DISABLED"

~# lshw -C network
*-network DISABLED
description: Wireless interface
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0c:00.0
logical name: eth1
version: 02
serial: 00:1c:bf:a8:d3:0f
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ipw3945 driverversion=1.2.2mp firmware=14.2 1:0 () latency=0 link=no module=ipw3945 multicast=yes wireless=unassociated


It looked suspicious, but I carried on, until the final command
that failed:

~# wpa_supplicant -w -Dwext -i eth1 -c/etc/wpa_supplicant.conf
Trying to associate with 00:1d:7e:65:12:a6 (SSID='LocustSwarm' freq=2437 MHz)
Associated with 00:1d:7e:65:12:a6
WPA: Key negotiation completed with 00:1d:7e:65:12:a6 [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:1d:7e:65:12:a6 completed (auth) [id=0 id_str=]

This command never exited.
Here is my wpa_supplicant.conf:

:~# cat /etc/wpa_supplicant.conf
ap_scan=1

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="LocustSwarm"
scan_ssid=1
proto=WPA
key_mgmt=WPA-PSK
psk="MYPASSPHRASE"
pairwise=TKIP
group=TKIP
}

Please, any insight will be much appreciated!

[kevdog]

PLEASE won't you rename this thread Manual WIRELESS Network config...

Please send a PM to a forum moderator -- that would probably be a better title. The thread used to be entitled something different, however when it was bumped to stick status it was renamed. I have no control of the naming of the thread. Only a moderator can change the title.

Thanks.

[kevdog]

Yes you picked up on the first problem:

First, the following output says "DISABLED"

~# lshw -C network
*-network DISABLED
description: Wireless interface
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0c:00.0
logical name: eth1
version: 02
serial: 00:1c:bf:a8:d3:0f
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ipw3945 driverversion=1.2.2mp firmware=14.2 1:0 () latency=0 link=no module=ipw3945 multicast=yes wireless=unassociated

Disabled is not a good sign. If you do a sudo ifconfig eth1 up, is the interface still listed as disabled. You need enabled first prior to passing commands to the interface.

Next, the output of this looks very good!!!:
~# wpa_supplicant -w -Dwext -i eth1 -c/etc/wpa_supplicant.conf
Trying to associate with 00:1d:7e:65:12:a6 (SSID='LocustSwarm' freq=2437 MHz)
Associated with 00:1d:7e:65:12:a6
WPA: Key negotiation completed with 00:1d:7e:65:12:a6 [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:1d:7e:65:12:a6 completed (auth) [id=0 id_str=]

Either pop open a new terminal window to complete the remainder of the instruction set, or change wpa supplicant to run in the background (however no debug messages will be seen):
wpa_supplicant -Bw -Dwext -i eth1 -c/etc/wpa_supplicant.conf

[SlingerXL]

route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.0.1.0 * 255.255.255.0 U 0 0 0 eth0
default girlfess.local 0.0.0.0 UG 0 0 0 eth0

iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSIDff/any
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:32 dBm
RTS thr:2347 B Fragment thr:2346 B
Power Managementff
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

[b]sudo iwlist scan[b/]
lo Interface doesn't sudo iwlist scan
support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:17:3F:6AD:99
ESSID:"houseoflove"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:35/100 Signal level:-73 dBm Noise level:-96 dBm
Encryption keyn
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Preauthentication Supported
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
Cell 02 - Address: 00:1B:63:2D:20:A9
ESSID:"girlfess"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:100/100 Signal level:-32 dBm Noise level:-96 dBm
Encryption keyn
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 03 - Address: 00:1C:10:14:AB:84
ESSID:"Citgo-3"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:17/100 Signal level:-85 dBm Noise level:-96 dBm
Encryption keyn
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 04 - Address: 00:1E:2A:53:F6:52
ESSID:"511nfess"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:7/100 Signal level:-91 dBm Noise level:-96 dBm
Encryption keyn
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0

sudo lshw -C network
*-network DISABLED
description: Wireless interface
product: BCM94311MCG wlan mini-PCI
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: wlan0
version: 02
serial: 00:1a:73:a6:9d:b4
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.52+Broadcom,10/12/2006, 4.100. latency=0 link=no module=ndiswrapper multicast=yes wireless=IEEE 802.11g

sudo cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
address 192.168.168.40
gateway 192.168.168.230
dns-nameservers 192.168.168.230
netmask 255.255.255.0
wpa-driver wext
wpa-ssid girlfess
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk b9dbbd5c85da38be466fbaaeba58183a6d5b3f17e5cab567ec 695f7530062cb2

sudo ifdown -v wlan0
ifdown: interface wlan0 not configured

sudo ifup -v
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 2 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "girlfess" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise CCMP -- OK
wpa_supplicant: wpa-group CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

ifconfig wlan0 192.168.168.40 netmask 255.255.255.0 up
route add default gw 192.168.168.230 metric 100 wlan0
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant




I have no idea what I'm doing. All I know is that I can't see the wireless networks despite seeing them with some terminal commands. What do I need to do to connect??

[Monarch2007]

First off, let me thank you for the excellent tutorial and guidance. I have followed your tutorial and was able to enable WLAN at home. But, I couldnt do so at work. Would highly appreciate your advice. I have used WLAN at work under windows xp. I must admit that I dont understand the security stuff of WLAN. We use a profile and dont enter any password as far as I understand...
Here are the outputs from both work WLAN and home configuration:
================================================== ===============
*work config *
$lshw -C network
*-network
description: Wireless interface
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0c:00.0
logical name: wmaster0
version: 02
serial: 00:1b:77:2d:c4:ae
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl3945 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11g
*-network
description: Ethernet interface
product: NetXtreme BCM5752 Gigabit Ethernet PCI Express
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:09:00.0
logical name: eth0
version: 02
serial: 00:18:8b:d0:97:bd
size: 100MB/s
capacity: 1GB/s
width: 64 bits
clock: 33MHz
capabilities: pm vpd msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=3.86 duplex=full firmware=5752-v3.19 ip=10.232.176.83 latency=0 link=yes module=tg3 multicast=yes port=twisted pair speed=100MB/s

$/etc/network# lspci | grep Network
0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)

$ndiswrapper -l
w39n51 : driver installed
device (8086:4222) present (alternate driver: iwl3945)

$/etc/network# ndiswrapper -v
utils version: '1.9', utils version needed by module: '1.9'
module details:
filename: /lib/modules/2.6.24-16-generic/ubuntu/misc/ndiswrapper/ndiswrapper.ko
version: 1.52
vermagic: 2.6.24-16-generic SMP mod_unload 586

$iwconfig
wlan0 IEEE 802.11g ESSID:"bridge" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:0000-0002-DE60-030A
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

$lsmod
Module Size Used by
isofs 36388 1
udf 88612 0
ipv6 267780 10
i915 32512 2
drm 82580 3 i915
binfmt_misc 12808 1
rfcomm 41744 2
l2cap 25728 13 rfcomm
bluetooth 61156 4 rfcomm,l2cap
ppdev 10372 0
bay 6912 0
container 5632 0
sbs 15112 0
sbshc 7680 1 sbs
dock 11280 1 bay
iptable_filter 3840 0
ip_tables 14820 1 iptable_filter
x_tables 16132 1 ip_tables
aes_i586 33536 0
dm_crypt 15364 0
dm_mod 62660 1 dm_crypt
ndiswrapper 192920 0
lp 12324 0
arc4 2944 2
ecb 4480 2
blkcipher 8324 1 ecb
pcmcia 40876 0
joydev 13120 0
af_packet 23812 6
dcdbas 9504 0
evdev 13056 10
parport_pc 36260 1
parport 37832 3 ppdev,lp,parport_pc
serio_raw 7940 0
pcspkr 4224 0
psmouse 40336 0
yenta_socket 27276 1
rsrc_nonstatic 13696 1 yenta_socket
pcmcia_core 40596 3 pcmcia,yenta_socket,rsrc_nonstatic
iwl3945 89844 0
iTCO_wdt 13092 0
iTCO_vendor_support 4868 1 iTCO_wdt
usbhid 31872 0
hid 38784 1 usbhid
snd_hda_intel 344728 3
iwlwifi_mac80211 219108 1 iwl3945
snd_pcm_oss 42144 0
snd_mixer_oss 17920 1 snd_pcm_oss
cfg80211 15112 1 iwlwifi_mac80211
snd_pcm 78596 2 snd_hda_intel,snd_pcm_oss
snd_page_alloc 11400 2 snd_hda_intel,snd_pcm
snd_hwdep 10500 1 snd_hda_intel
snd_seq_dummy 4868 0
snd_seq_oss 35584 0
snd_seq_midi 9376 0
snd_rawmidi 25760 1 snd_seq_midi
snd_seq_midi_event 8320 2 snd_seq_oss,snd_seq_midi
video 19856 0
output 4736 1 video
snd_seq 54224 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
snd_timer 24836 2 snd_pcm,snd_seq
snd_seq_device 9612 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
wmi_acer 9644 0
button 9232 0
battery 14212 0
snd 56996 17 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,sn d_hwdep,snd_seq_dummy,snd_seq_oss,snd_rawmidi,snd_ seq,snd_timer,snd_seq_device
ac 6916 0
soundcore 8800 1 snd
shpchp 34452 0
pci_hotplug 30880 1 shpchp
intel_agp 25492 1
agpgart 34760 3 drm,intel_agp
ext3 136712 1
jbd 48404 1 ext3
mbcache 9600 1 ext3
loop 18948 2
sg 36880 0
sr_mod 17956 1
cdrom 37408 1 sr_mod
sd_mod 30720 2
ata_piix 19588 2
ata_generic 8324 0
pata_acpi 8320 0
libata 159344 3 ata_piix,ata_generic,pata_acpi
ehci_hcd 37900 0
scsi_mod 151436 4 sg,sr_mod,sd_mod,libata
uhci_hcd 27024 0
tg3 116228 0
usbcore 146028 5 ndiswrapper,usbhid,ehci_hcd,uhci_hcd
thermal 16796 0
processor 36872 3 thermal
fan 5636 0
fbcon 42912 0
tileblit 3456 1 fbcon
font 9472 1 fbcon
bitblit 6784 1 fbcon
softcursor 3072 1 bitblit
fuse 50580 5

$iwlist scan
wlan0 Scan completed :
Cell 01 - Address: 00:15:FA:B3:2D:50
ESSID:""
Mode:Master
Channel:3
Frequency:2.422 GHz (Channel 3)
Quality=62/100 Signal level=-70 dBm Noise level=-127 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=00001d7a233b0199
Cell 02 - Address: 02:0C:F1:59:68:33
ESSID:"bridge"
Mode:Ad-Hoc
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=51/100 Signal level=-78 dBm Noise level=-127 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Extra:tsf=00000004077203ab
Cell 03 - Address: 00:15:FA:B3:2D:80
ESSID:""
Mode:Master
Channel:3
Frequency:2.422 GHz (Channel 3)
Quality=38/100 Signal level=-86 dBm Noise level=-127 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=00001d7a355a1193

On my home computer:
================================================== ==============
$dmesg
............
............
[ 145.216963] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 146.360302] wlan0: Initial auth_alg=0
[ 146.360311] wlan0: authenticate with AP 00:1b:da:29:a3:64
[ 146.361282] wlan0: RX authentication from 00:1b:da:29:a3:64 (alg=0 transaction=2 status=0)
[ 146.361290] wlan0: authenticated
[ 146.361294] wlan0: associate with AP 00:1b:da:29:a3:64
[ 146.362607] wlan0: RX AssocResp from 00:1b:da:29:a3:64 (capab=0x411 status=0 aid=1)
[ 146.362613] wlan0: associated
[ 146.366518] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 153.342162] wlan0: no IPv6 routers present

$ifconfig
............
wlan0 Link encap:Ethernet HWaddr 00:1b:77:2d:c4:ae
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21b:77ff:fe2d:c4ae/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:20 errors:0 dropped:0 overruns:0 frame:0
TX packets:43 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2261 (2.2 KB) TX bytes:6845 (6.6 KB)

wmaster0 Link encap:UNSPEC HWaddr 00-1B-77-2D-C4-AE-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

[kevdog]

I'm a little confused by what you posted -- I don't need to know what is going on with networks that work. With your iwlist scan results, there are a bunch of blank essids listed except for bridge. Are these the actual results?

[Monarch2007]

Thank you for the prompt response. Yes, these are from actual scans. One thing I remember is that the SSID is not broadcasted from the APs at work. Whereas at home, my AP broadcasts the SSID. Is that why you see blanks in the SSID field? Also, I couldn't get the logical name to be wlan0 (it is wmaster0); however, it works with the same logical name at my home network.
Once again, I appreciate your help and guidance.

[Monarch2007]

Also, to avoid confusion, if any, when I say "at work" I meant "in office". It actually doesn't work in office but works only in my home.
Apologize for the confusion.

[kevdog]

wmaster is the actual interface, while wlan0 looks like the virtual interface -- this is the one you want to work with -- not wmaster0.

A Hidden SSID could be a problem. Do you know the SSID at work?

[Monarch2007]

Thanks again for your help and advice.
I did some more trials and now I can scan and attempt to connect.
Here is my /etc/wpa_supplicant.conf file:
network={
ssid="wheeler"
# scan_ssid=1
# ap_scan=2
key_mgmt=IEEE8021X
eap=LEAP
identity="my_userid"
password="my_passwd"
}
But here is what I get by running wpa_supplicant -Dwext -iwlan0 -dd -c/etc/wpa_supplicant.conf

wpa_supplicant -Dwext -iwlan0 -dd -c/etc/wpa_supplicant.conf
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
Line: 1 - start of a new network block
ssid - hexdump_ascii(len=9):
46 52 33 33 77 68 65 65 31 wheeler
key_mgmt: 0x8
eap methods - hexdump(len=16): 00 00 00 00 11 00 00 00 00 00 00 00 00 00 00 00
identity - hexdump_ascii(len=10):
password - hexdump_ascii(len=8): [REMOVED]
Priority group 0
id=0 ssid='wheeler'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1b:77:2d:c4:ae
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Added interface wlan0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 0
Try to find WPA-enabled AP
Try to find non-WPA AP
No suitable AP found.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=8
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
Scan results: -1
Failed to get scan results
Failed to get scan results - try scanning again
Setting scan request: 1 sec 0 usec
Starting AP scan (broadcast SSID)
ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
Setting scan request: 10 sec 0 usec
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=8
Received 359 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:15:fa:b3:2d:50 ssid='wheeler' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
1: 02:0c:f1:59:d0:fb ssid='bridge' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:15:fa:b3:2d:50 ssid='wheeler' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
selected non-WPA AP 00:15:fa:b3:2d:50 ssid='wheeler'
Trying to associate with 00:15:fa:b3:2d:50 (SSID='wheeler' freq=2422 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x4
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=17
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:15:fa:b3:2d:50 into blacklist
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=8
Received 359 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:15:fa:b3:2d:50 ssid='wheeler' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
1: 02:0c:f1:59:d0:fb ssid='bridge' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:15:fa:b3:2d:50 ssid='wheeler' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
selected non-WPA AP 00:15:fa:b3:2d:50 ssid='wheeler'
Trying to associate with 00:15:fa:b3:2d:50 (SSID='wheeler' freq=2422 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x4
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=17
Authentication with 00:00:00:00:00:00 timed out.
BSSID 00:15:fa:b3:2d:50 blacklist count incremented to 2
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=8
Received 359 bytes of scan results (2 BSSes)
Scan results: 2
================================================== =============
Here are the dmesg messages:

[10867.780178] wlan0: authenticated
[10867.780180] wlan0: associate with AP 00:15:fa:b3:2d:50
[10867.780182] wlan0: mismatch in privacy configuration and mixed-cell disabled - abort association
[10867.781938] wlan0: RX deauthentication from 00:15:fa:b3:2d:50 (reason=2)
[10867.781941] wlan0: deauthenticated
[10868.775028] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[10868.775960] wlan0: RX deauthentication from 00:15:fa:b3:2d:50 (reason=2)
[10879.099190] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[10879.100084] wlan0: RX deauthentication from 00:15:fa:b3:2d:50 (reason=2)
[10879.101429] wlan0: Initial auth_alg=128
[10879.101433] wlan0: authenticate with AP 00:15:fa:b3:2d:50
[10879.101443] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[10879.102392] wlan0: RX authentication from 00:15:fa:b3:2d:50 (alg=128 transaction=2 status=0)
[10879.102398] wlan0: authenticated
[10879.102402] wlan0: associate with AP 00:15:fa:b3:2d:50
[10879.102406] wlan0: mismatch in privacy configuration and mixed-cell disabled - abort association
[10879.103294] wlan0: RX deauthentication from 00:15:fa:b3:2d:50 (reason=2)
[10879.103297] wlan0: deauthenticated
[10879.300897] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[10879.301809] wlan0: RX deauthentication from 00:15:fa:b3:2d:50 (reason=2)
[11219.510394] ADDRCONF(NETDEV_UP): wlan0: link is not ready

Can you please help?

Thanks!

[SlingerXL]

Is there anything you need to know about my connection? Do you know which step I should be following? I've completed the tutorial twice now with the original step and my wicd is still not showing wireless connections nor has it connected.

[kevdog]

Sling

Its likely its a driver issue rather than a configuration issue -- impossible to know really since you have posted anything to help your cause! Please be more informative.

[karlatsaic]

I am having trouble with my iwl3945 driver (dell xps m1330) on Hardy 8.04 (amd64) and have seen several references across these forums, none of which helped, so I tried something simple here, following this excellent tutorial.

1.. turned off all encryption on my wireless router (linksys BEFW11S4 802.11b)
2. khr@khr-laptop:~$ lshw -C network
*-network
description: Wireless interface
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0c:00.0
logical name: wmaster0
version: 02
serial: 00:1f:3c:54:d4:6d
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl3945 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11g

3. khr@khr-laptop:~$ sudo ifconfig wmaster0 down

4. khr@khr-laptop:~$ sudo dhclient -r wmaster0
There is already a pid file /var/run/dhclient.pid with pid 0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wmaster0/
Sending on LPF/wmaster0/
Sending on Socket/fallback
[does unkown hardware reflect 802.11g of driver vs 802.11b of router? This same laptop and wireless router worked great on 7.10 with ipw3945.]

5. khr@khr-laptop:~$ sudo ifconfig wmaster0 up

6. khr@khr-laptop:~$ sudo iwconfig wmaster0 essid "myssid"
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device wmaster0 ; Operation not supported.

7. khr@khr-laptop:~$ sudo iwconfig wmaster0 mode Managed
Error for wireless request "Set Mode" (8B06) :
SET failed on device wmaster0 ; Operation not supported.

8. khr@khr-laptop:~$ sudo dhclient wmaster0
There is already a pid file /var/run/dhclient.pid with pid 0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wmaster0/
Sending on LPF/wmaster0/
Sending on Socket/fallback
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 12
DHCPDISCOV...
No DHCPOFFERS received....

I am a long-time ubuntu fan and wireless has always worked on 2 other laptops (on Gutsy and Hardy) and this computer out of the box (with 7.10) so I have no experience troubleshooting this. Any help from anyone is appreciated. [Edit] I am also somewhat confused between the logical name of wmaster0 vs wlan0, which shows up under Network Manager. I still get no connection if I do all steps above with wlan0 - however, with wlan0, I get no error with the 'iwconfig wlan0 essid' and '...mode Managed' commands.

[Monarch2007]

I did some more experiments..
I looked at the Windows Config which is working... It says:
Enterprise Security.
Network Auth: Open
Data Encryption: CKIP
Enable 802.1x, Authentication Type : LEAP.

I changed Data Encryption to WEP, it still works.It prompts for user name and password and I can go on air.

tried adding group=WEP40 WEP104, no success.
The dmesg output always reports:
281.586196] wlan0: Initial auth_alg=128
[ 281.586200] wlan0: authenticate with AP 00:15:fa:b3:2d:50
[ 281.586209] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 281.587343] wlan0: RX deauthentication from 00:15:fa:b3:2d:50 (reason=2)
[ 281.589779] wlan0: RX authentication from 00:15:fa:b3:2d:50 (alg=128 transaction=2 status=0)
[ 281.589782] wlan0: authenticated
[ 281.589784] wlan0: associate with AP 00:15:fa:b3:2d:50
[ 281.589786] wlan0: mismatch in privacy configuration and mixed-cell disabled - abort association
[ 281.591330] wlan0: RX deauthentication from 00:15:fa:b3:2d:50 (reason=2)
[ 281.591333] wlan0: deauthenticated

Is there any clue on this? Or is it known that i3945 does not work in Ubuntu Hardy? I would really appreciate your inputs and guidance.
Thanks and regards.

[kevdog]

karlatsaic

wmaster0 is not the correct interface. Its likely wlan0. Do a ifconfig a see what shows besides wmaster0. You need to use the virtual interface the accesses wmaster0.

monarch2007

Enterprise Security.
Network Auth: Open
Data Encryption: CKIP
Enable 802.1x, Authentication Type : LEAP.

You are attempting to use authentication that wasnt covered in this guide. Ive never had to do enterprise authentication before. Here are some examples of how to configure wpa_supplicant.conf for various configurations, however none exactly matches your setup:
http://linux.die.net/man/5/wpa_supplicant.conf

Possibly something like this:?
# LEAP with dynamic WEP keys
network={
ssid="leap-example"
key_mgmt=IEEE8021X
eap=LEAP
identity="user"
password="foobar"
}

[karlatsaic]

karlatsaic

wmaster0 is not the correct interface. Its likely wlan0. Do a ifconfig a see what shows besides wmaster0. You need to use the virtual interface the accesses wmaster0.


output of ifconfig:

wlan0 Link encap:Ethernet HWaddr 00:1f:3c:54:d4:6d
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wmaster0 Link encap:UNSPEC HWaddr 00-1F-3C-54-D4-6D-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

So why does wmaster0 show as the logical name out of 'lshw -C network' ? I am starting with a clean install of 64-bit 8.04 so my configuration is yet untouched by me. The same commands with wlan0 and output is:
khr@khr-laptop:~$ sudo ifconfig wlan0 down
khr@khr-laptop:~$ sudo dhclient -r wlan0
There is already a pid file /var/run/dhclient.pid with pid 6622
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:1f:3c:54:d4:6d
Sending on LPF/wlan0/00:1f:3c:54:d4:6d
Sending on Socket/fallback
khr@khr-laptop:~$ sudo ifconfig wlan0 up
khr@khr-laptop:~$ sudo iwconfig wlan0 essid "myssid"
khr@khr-laptop:~$ sudo iwconfig wlan0 mode Managed
khr@khr-laptop:~$ sudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:1f:3c:54:d4:6d
Sending on LPF/wlan0/00:1f:3c:54:d4:6d
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

So, it is indeed talking to the hardware - just no connection via DHCP
Thanks...

[SlingerXL]

Sling

Its likely its a driver issue rather than a configuration issue -- impossible to know really since you have posted anything to help your cause! Please be more informative.
Er, I have all my info posted above my last post. It's above Monarch's info on page 55. It's not a driver problem since I already went through all that and my lshw -C shows my network 'girlfess', I just can't find any networks through wicd. I was told in the installing drivers thread that now I just had to configure my WPA: http://ubuntuforums.org/showpost.php?p=5207160&postcount=135

[Monarch2007]

Kevdog,
Thanks.
I did try the configuration that you have mentioned but it didnt work... Can you please direct me to an appropriate post/forum, if you are aware, where I can ask my questions.
I appreciate your help, guidance and patience.

[kevdog]

Monarch,

Im not sure of the appropriate forum, possibly repost in the Networking subforum asking for help with LEAP. I've never worked with LEAP before.

[drpaul]

This is a long thread. I have looked thru a bit of it without seeing my particular problem. Please forgive me if I've missed it in there.

I am running an HP dv6150 laptop; it has the Intel 3945 wireless chips. When I was running Edgy it all worked. I have not tested it thru 3 upgrades. Now it doesn't work in Hardy.

Looking at the info from lshw it says that the wireless is wmaster0 and its using the iwl3945 driver.

*-network
description: Wireless interface
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: wmaster0
version: 02
serial: 00:18:de:1c:27:7e
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl3945 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11g

However, iwconfig says that eth1 is the only interface that supports wireless

~$ sudo iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

eth1 IEEE 802.11g ESSID:"" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

I have gone thru your suggested commands for connecting to WEP enabled router with eth1. The final dhclient request failed, but going to network manager and working with the wireless entry now allows a connection.

lshw still shows wmaster0 as owning the wireless network interface.

I'm baffled and would like to know how to enable auto connection on wireless upon boot.

Please.

Thanks

Paul

[thesoffish]

I seem to be having the same problem as a couple other people in this thread. I have a new Sager NP2092 laptop with an Intel PRO/Wireless 4965 card and running Hardy 8.04. When I first tried entering the WEP key with Network Manager it would try to connect, but wouldn't accept the key. Eventually (I don't know what I did) it was able to connect to the network, but every couple minutes it would prompt me for the key again, and there was never any connectivity to the internet.

I tried the How To in this thread with this result:


thesoffish@Alice:~$ lshw -C network
WARNING: you should run this program as super-user.
*-network
description: Ethernet interface
product: NetLink BCM5787M Gigabit Ethernet PCI Express
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:04:00.0
logical name: eth0
version: 02
serial: 00:1b:38:e4:ac:26
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=tg3 driverversion=3.86 ip=192.168.2.110 latency=0 module=tg3 multicast=yes
*-network
description: Wireless interface
product: PRO/Wireless 4965 AG or AGN Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0c:00.0
logical name: wmaster0
version: 61
serial: 00:1d:e0:b7:41:bd
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl4965 latency=0 module=iwl4965 multicast=yes wireless=IEEE 802.11g
thesoffish@Alice:~$ sudo ifconfig wmaster0 down
[sudo] password for thesoffish:
thesoffish@Alice:~$ sudo dhclient -r wmaster0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wmaster0/
Sending on LPF/wmaster0/
Sending on Socket/fallback
thesoffish@Alice:~$ sudo ifconfig wmaster0 up
thesoffish@Alice:~$ sudo iwconfig wmaster0 essid "Sierra"
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device wmaster0 ; Operation not supported.
thesoffish@Alice:~$ sudo iwconfig wmaster0 key *******
Error for wireless request "Set Encode" (8B2A) :
SET failed on device wmaster0 ; Operation not supported.
thesoffish@Alice:~$ sudo iwconfig wmaster0 key open
Error for wireless request "Set Encode" (8B2A) :
SET failed on device wmaster0 ; Operation not supported.
thesoffish@Alice:~$ sudo iwconfig wmaster0 mode Managed
Error for wireless request "Set Mode" (8B06) :
SET failed on device wmaster0 ; Operation not supported.
thesoffish@Alice:~$ sudo dhclient wmaster0
There is already a pid file /var/run/dhclient.pid with pid 0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wmaster0/
Sending on LPF/wmaster0/
Sending on Socket/fallback
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


I thought the SET failed on device wmaster0 ; Operation not supported might be due to some issue with the driver, so I followed Anton Khokhlov's instructions from https://answers.launchpad.net/ubuntu/+question/16768
However I don't know if what I did made any change at all, and if it did it's entirely possible it messed things up rather than helped.

Then I tried using the wlan0 interface instead of wmaster0, and this allowed me to talk to the hardware alright, but it still gets the same No DHCPOFFERS received in the end:


thesoffish@Alice:~$ sudo ifconfig wlan0 down
thesoffish@Alice:~$ sudo dhclient -r wlan0
There is already a pid file /var/run/dhclient.pid with pid 0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:1d:e0:b7:41:bd
Sending on LPF/wlan0/00:1d:e0:b7:41:bd
Sending on Socket/fallback
thesoffish@Alice:~$ sudo ifconfig wlan0 up
thesoffish@Alice:~$ sudo iwconfig wlan0 essid "Sierra"
thesoffish@Alice:~$ sudo iwconfig wlan0 key *******
thesoffish@Alice:~$ sudo iwconfig key open
iwconfig: unknown command "open"
thesoffish@Alice:~$ sudo iwconfig wlan0 key open
thesoffish@Alice:~$ sudo iwconfig wlan0 mode Managed
thesoffish@Alice:~$ sudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:1d:e0:b7:41:bd
Sending on LPF/wlan0/00:1d:e0:b7:41:bd
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


I tried running dhclient both while disconnected and connected to the network, but it had the same output. When I was connected, right when the terminal had spat out the last DCHPDISCOVER line and was about to fail to receive a DHCPOFFER, the Network Manager popped up and asked me for the WEP key; but I don't know if this was related to what the terminal was doing or if it was just the same problem of it asking for the key randomly every few minutes.

Any help/advice would be appreciated =)

[drpaul]

To thesoffish

Your problem does seem similar to mine. What is shown when you execute ifconfig in the terminal? Mine shows four: eth0 eth1 lo wmaster0. Only the eth1 was recognized as wireless even though wmaster0 is associated with the wireless card in the result from lshw.

If you execute iwconfig it will tell you which the system thinks is wireless.

HTH

Paul

[thesoffish]

Here are the results of ifconfig, iwconfig, and lshw:


thesoffish@Alice:~$ sudo ifconfig
[sudo] password for thesoffish:
eth0 Link encap:Ethernet HWaddr 00:1b:38:e4:ac:26
inet addr:192.168.2.110 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::21b:38ff:fee4:ac26/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:608 errors:0 dropped:0 overruns:0 frame:0
TX packets:637 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:541849 (529.1 KB) TX bytes:119907 (117.0 KB)
Interrupt:17

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1592 errors:0 dropped:0 overruns:0 frame:0
TX packets:1592 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:79600 (77.7 KB) TX bytes:79600 (77.7 KB)

wlan0 Link encap:Ethernet HWaddr 00:1d:e0:b7:41:bd
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:55 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:11875 (11.5 KB)

wmaster0 Link encap:UNSPEC HWaddr 00-1D-E0-B7-41-BD-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

thesoffish@Alice:~$ sudo iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"" Nickname:""
Mode:Managed Frequency:2.437 GHz Access Point: 00:18:F8:CD:AB:BD
Bit Rate=54 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:off
Power Management:off
Link Quality=100/100 Signal level=-42 dBm Noise level=-93 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

thesoffish@Alice:~$ lshw -C network
WARNING: you should run this program as super-user.
*-network
description: Ethernet interface
product: NetLink BCM5787M Gigabit Ethernet PCI Express
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:04:00.0
logical name: eth0
version: 02
serial: 00:1b:38:e4:ac:26
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=tg3 driverversion=3.86 ip=192.168.2.110 latency=0 module=tg3 multicast=yes
*-network
description: Wireless interface
product: PRO/Wireless 4965 AG or AGN Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0c:00.0
logical name: wmaster0
version: 61
serial: 00:1d:e0:b7:41:bd
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl4965 latency=0 module=iwl4965 multicast=yes wireless=IEEE 802.11g


So it thinks wlan0 is wireless. I tried the procedure again using wlan0, but it still fails the final dhclient request.

[kevdog]

wlan0 is definitely your wireless interface. In order to help us however please post the exact commands you are typing along with your wpa-supplicant.conf file. Additionally, please verify your wireless driver actually supports wpa (or wpa2). I believe you can do this by either looking through dmesg:

dmesg | more

or by:
dmesg | egrep ('wpa|WPA')

[drpaul]

thesoffish:

I had the same experience with mine. When I went thru the suggested procedure at the beginning of this thread using [eth1 for me wlan0 for you], I also had the last DHCP request fail. At that point I opened Network Manager [from System:Admin:Networks] and tried to activate the wireless entry. It worked!

Since then I have rebooted, and the wireless connection was reestablished automagically.

HTH

Paul

[kevdog]

I'm glad things are working for you now!

[drpaul]

Me, too. But I'ld really like to understand what that wmaster0 thing is all about. lshw seems like it is really confused.

Any idea what's going on?

Paul

[thesoffish]

I went to look for my wpa_supplicant.conf file and discovered I did not have one; perhaps this was part of the problem? I created one from the WEP template, though I'm not sure if I did it right:


# Static WEP keys

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="Sierra"
key_mgmt=NONE
wep_key0=MY_PASSWD
wep_tx_keyidx=0
}


The only things I changed from the example template were the ssid, the key, and I deleted two lines for wep_key1 and 2, respectively, since my network has only the one key. It's a 128-bit key by the way, with 26 characters, while the placeholder had only a small number of characters. Is that important?

Anyway then I fiddled around with the network manager GUI some, following drpaul's advice, and now it is connected and working! (I did this all over the course of several hours earlier in the day though, and I feel like I'm forgetting a step or two in this writeup because I don't remember it being so simple..)

In a moment I'm going to reboot and see if it still connects afterwards. I'm somewhat dissatisfied with this solution, because while it works, I'd still like to know more about what is going on or at least what it was that fixed it.

Also, I'm not really sure how to tell from dmesg whether the wireless driver supports wpa (I'm actually using wep, but I don't know how to tell that either.) When I look at it's output though, quite noticeably there are many lines of:

[ 1329.577468] wlan0: RX WEP frame, decrypt failed

repeated over and over, as well as this:

[ 1345.983072] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate

Is this indicative of an error or bad configuration? Or is it not enough info to tell.

I'll edit this post after I reboot.

Edit: It automatically connected to my network without a problem after reboot and continues to work.

Here is what I get when I run dhclient now, for reference:


thesoffish@Alice:~$ sudo dhclient wlan0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:1d:e0:b7:41:bd
Sending on LPF/wlan0/00:1d:e0:b7:41:bd
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPOFFER of 192.168.2.100 from 192.168.2.1
DHCPREQUEST of 192.168.2.100 on wlan0 to 255.255.255.255 port 67
DHCPACK of 192.168.2.100 from 192.168.2.1
bound to 192.168.2.100 -- renewal in 34683 seconds.


Also, the wireless status LED on the front of my laptop is a steady red (instead of blue), even though the wireless seems to be working now. I assume this is a totally minor/unrelated issue having more to do with LED drivers than wireless ones though.

[kevdog]

No, the error you posted is stating you are supplying bad authentication principles. What does

dmesg | grep wlan0

show?


drpaul
In the tutorial there is an explanation regarding wmaster0 and why this is listed rather than wlan0.

[thesoffish]

thesoffish@Alice:~$ dmesg | grep wlan0
[ 47.510554] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 59.094184] wlan0: Initial auth_alg=0
[ 59.094191] wlan0: authenticate with AP 00:18:f8:cd:ab:bd
[ 59.098166] wlan0: RX authentication from 00:18:f8:cd:ab:bd (alg=0 transaction=2 status=0)
[ 59.098171] wlan0: authenticated
[ 59.098174] wlan0: associate with AP 00:18:f8:cd:ab:bd
[ 59.101892] wlan0: RX AssocResp from 00:18:f8:cd:ab:bd (capab=0x411 status=0 aid=1)
[ 59.101897] wlan0: associated
[ 59.105484] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 62.266645] wlan0: no IPv6 routers present
thesoffish@Alice:~$


Hm, I no longer get that string of error messages.

[kevdog]

It looks like you made a connection?

Are you taking the wired interface down prior to using the wireless? Both cannot be up and running at once!

[drpaul]

thesoffish:
I don't think you need wpasupplicant to deal with WEP, but I'm in the camp of "if it works don't fix it" :)

kevdog:
thanks for the pointer. It's good to know that they intend it that way, but why?????

Apparently, I have both eth0 [wired] and eth1 [wireless] now both connected and running at the same time :confused:
How would you suggest that I turn off the wireless connection in a way that will allow it to come back should I need to roam around?

Thanks

Paul

[SlingerXL]

Can someone please tell me which step to do? I don't know what all those acronyms mean. My info was posted on page 55 above Monarch's and nobody's acknowledged it yet. I did the whole tutorial but it still won't let me connect.

[drpaul]

SlingerXL:
In all the info you posted I did not see the result of ifconfig in a terminal. From what you posted you might have been connected. ???

Paul

[SlingerXL]

SlingerXL:
In all the info you posted I did not see the result of ifconfig in a terminal. From what you posted you might have been connected. ???

Paul
Well, actually, reading through the previous posts, my lshw showed

*-network DISABLED
on the first line. kev said that's a bad sign on page 55 or 56 and told someone to try putting in:

sudo ifconfig eth1 up
So put that in and this is the output:

eth1: ERROR while getting interface flags: No such device

What does that mean? I think this is where I need to start before I even try the tutorial again. Also, I'm trying to connect to a passworded wireless network so I don't know how that affects anything.

[SlingerXL]

Well, actually, reading through the previous posts, my lshw showed

*-network DISABLED
on the first line. kev said that's a bad sign on page 55 or 56 and told someone to try putting in:

sudo ifconfig eth1 up
So put that in and this is the output:

eth1: ERROR while getting interface flags: No such device

What does that mean? I think this is where I need to start before I even try the tutorial again. Also, I'm trying to connect to a passworded wireless network so I don't know how that affects anything.
OK I figured out how to get rid of the "DISABLED". I just had to go to System/Admin/Network and check the box next to it. Now I'm going to try to the tutorial again.

[kevdog]

You can create multiple virtual interfaces on some driver/chipsets combinations -- specifically I have done this with the madwifi atheros combination. This would allow you to separate multiple configurations if needed. I use this specifically when I want to run aircrack-ng and place my card into monitor or AP mode. When I don't need monitor mode, I simply bring down that virtual interface, and then bring up the normal client interface (switch between ath0 and ath1).

Again to bring up and down interfaces its simple:
sudo ifconfig <interface_name> up
sudo ifconfig <interface_name> down

To see the available networks around you:
iwlist scan

As far as WEP goes you can use wpa_supplicant however you definitely don't need to do so. Its called wpa_supplicant for a reason -- it was made specifically for WPA authentication.

[drpaul]

To slingerXL

If you just post the result of ifconfig [no other inputs] then you will see the interfaces available on your system. It might be that eth1 is not the right one for your system.

Paul

[Laen]

EDIT:

Got things working with wicd.

[karlatsaic]

I am having trouble with my iwl3945 driver (dell xps m1330) on Hardy 8.04 (amd64) and have seen several references across these forums, none of which helped, so I tried something simple here, following this excellent tutorial.

1.. turned off all encryption on my wireless router (linksys BEFW11S4 802.11b)
2. khr@khr-laptop:~$ lshw -C network
*-network
description: Wireless interface
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0c:00.0
logical name: wmaster0
version: 02
serial: 00:1f:3c:54:d4:6d
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl3945 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11g
.....

I was surprised to see the 802.11g protocol on the wireless configuration for this driver, iwl3945. Since my old trusty linksys 802.11b wireless router was long overdue for an upgrade, I bought a new linksys WRT160N (802.11n) wireless router and all my problems are solved It looks like either the driver doesn't work with 802.11b (seems unlikely) or something in network-manager or elsewhere is incorrectly configuring the driver to 802.11g when it detected my old 802.11b router. Still mildly concerned about connecting in geeneral, but at least the problem is now SOLVED for my home connection, which is 99% of my requirment for wireless right now.

[SlingerXL]

dan@dan-hp:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:1b:24:ab:e0:8f
inet addr:10.0.1.195 Bcast:10.0.1.255 Mask:255.255.255.0
inet6 addr: 2002:62df:fb06:0:21b:24ff:feab:e08f/64 Scope:Global
inet6 addr: fe80::21b:24ff:feab:e08f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7336 errors:0 dropped:0 overruns:0 frame:0
TX packets:7617 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5921925 (5.6 MB) TX bytes:1437877 (1.3 MB)
Interrupt:19 Base address:0x2000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:259 errors:0 dropped:0 overruns:0 frame:0
TX packets:259 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:15456 (15.0 KB) TX bytes:15456 (15.0 KB)

wlan0 Link encap:Ethernet HWaddr 00:1a:73:a6:9d:b4
inet addr:192.168.168.40 Bcast:192.168.168.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:17 errors:0 dropped:0 overruns:0 frame:0
TX packets:35 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1921 (1.8 KB) TX bytes:4727 (4.6 KB)
Interrupt:16 Memory:c8000000-c8004000

Here's another question. When I try the tutorial and get to do the hex key replacement step for the password, it won't let me put in a password less than 8 chars long when the network password is only 3 characters long. What do I do about that, or am I entering the wrong thing in?

[drpaul]

I don't know about the password thing, but your output shows that you are connected over wireless [wlan0] and you have been assigned an IP address.

What more are you trying to do?

Paul

OBTW, you could always put the hex key in instead of the password.

[thesoffish]

kevdog, I'm not using the wired interface anymore now that the wireless is working, but that may have been the cause of those errors earlier when I was using it.

Thanks for all your help, kevdog and drpaul. Now it just remains to be seen if I can connect to other networks, but I'll cross that bridge when I come to it :)

[SlingerXL]

I don't know about the password thing, but your output shows that you are connected over wireless [wlan0] and you have been assigned an IP address.

What more are you trying to do?

Paul

OBTW, you could always put the hex key in instead of the password.
See, it SAYS I'm connected since I tried to connect through System/Admin/Network then unlock it, and click properties on my wireless network, choose WPA (Personal), and enter the password 519. However, as soon as I get out of properties and it refreshes or whatever, and I go back into properties, the password is erased every time and I don't get internet despite what my ifconfig says about my having an IP address.

Here's the output when I edited the wpa supplicant file with the hex equivalent of 519 (which is %35%31%39, right?)

dan@dan-hp:~$ sudo wpa_supplicant -w -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ap_scan=1
ctrl_interface='/var/run/wpa_supplicant'
Line: 4 - start of a new network block
ssid - hexdump_ascii(len=8):
67 69 72 6c 66 65 73 73 girlfess
scan_ssid=0 (0x0)
proto: 0x1
key_mgmt: 0x2
PSK (ASCII passphrase) - hexdump_ascii(len=9): [REMOVED]
pairwise: 0x8
group: 0x8
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='girlfess'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=22 WE(source)=18 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1a:73:a6:9d:b4
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Using existing control interface directory.
ctrl_iface bind(PF_UNIX) failed: Address already in use
ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore
Failed to initialize control interface '/var/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.

Failed to add interface wlan0
State: DISCONNECTED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Cancelling scan request
Cancelling authentication timeout
WEXT: Operstate: linkmode=0, operstate=6


And here's what happens when I enter the the ASCII password into the wpa supplicant file(519):

Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ap_scan=1
ctrl_interface='/var/run/wpa_supplicant'
Line: 4 - start of a new network block
ssid - hexdump_ascii(len=8):
67 69 72 6c 66 65 73 73 girlfess
scan_ssid=0 (0x0)
proto: 0x1
key_mgmt: 0x2
Line 9: Invalid passphrase length 3 (expected: 8..63) '519"'.
Line 9: failed to parse psk '"519"'.
pairwise: 0x8
group: 0x8
Line 12: WPA-PSK accepted for key management, but no PSK configured.
Line 12: failed to parse network block.
Failed to read or parse configuration '/etc/wpa_supplicant.conf'.
Failed to add interface wlan0
Cancelling scan request
Cancelling authentication timeout


So what gives?

[kevdog]

First I'm really confused by what you are doing. If you are trying to use Network Manager, WICD or any other GUI, thats fine, but you can't do a manual connection and use a GUI at the same time. It would work. So I dont quite understand the things you were saying about System/Admin/Network and such.

Second if you read your output:

ctrl_iface bind(PF_UNIX) failed: Address already in use
ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore
Failed to initialize control interface '/var/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.

You seem to have a process (a GUI perhaps??) already using the /var/run/wpa_supplicant/wlan0 socket. So you must delete this socket (which can be treated like a file) with:
sudo rm -rf /var/run/wpa_supplicant

And just for reference (since a lot of people are responding to this thread all of a sudden and its hard for me to keep people straight) if you could post your wpa_supplicant.conf file along with your commands you are typing that would be great for reference.

[dilipmannil]

I am following the steps described in this HOWTO to connect to WPA1 encrypted wifi network. But sometimes I am unable to connect to my wifi network(No working leases in persistent database - sleeping). Am using the following script to connect to wifi network.


cat wifi_scripts/wifi_start.sh
#!/bin/sh
sudo ifconfig wlan0 down
sudo dhclient -r wlan0
sudo wpa_supplicant -Bw -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
sudo ifconfig wlan0 up
sudo iwconfig wlan0 mode Managed
sudo dhclient wlan0


Once in a while ,I am getting the following output while running this script and connection fails ,


#./wifi_start.sh

Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:16:cf:71:b4:5e
Sending on LPF/wlan0/00:16:cf:71:b4:5e
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 10.0.0.1 port 67
There is already a pid file /var/run/dhclient.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:16:cf:71:b4:5e
Sending on LPF/wlan0/00:16:cf:71:b4:5e
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


When I tried scanning for network at this moment I got the following output,


# sudo iwlist scanning
[sudo] password for dilip:
lo Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1B:2F:FE:48:A8
ESSID:"CESC"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:100/100 Signal level:-20 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

eth0 Interface doesn't support scanning.

Can anyone give some pointer regarding how to resolve this problem?

[SlingerXL]

First I'm really confused by what you are doing. If you are trying to use Network Manager, WICD or any other GUI, thats fine, but you can't do a manual connection and use a GUI at the same time. It would work. So I dont quite understand the things you were saying about System/Admin/Network and such.
I'm trying to just get wireless internet to work. Be it through the terminal or through a GUI. I was explaining to Paul why my ifconfig was showing an IP address but I still couldn't get any internet. But since GUI has failed me I guess I'm just trying to connect through the terminal.


Second if you read your output:

ctrl_iface bind(PF_UNIX) failed: Address already in use
ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore
Failed to initialize control interface '/var/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.

You seem to have a process (a GUI perhaps??) already using the /var/run/wpa_supplicant/wlan0 socket. So you must delete this socket (which can be treated like a file) with:
sudo rm -rf /var/run/wpa_supplicant

And just for reference (since a lot of people are responding to this thread all of a sudden and its hard for me to keep people straight) if you could post your wpa_supplicant.conf file along with your commands you are typing that would be great for reference.

OK I entered what you told me to enter and how here's my output for:
sudo wpa_supplicant -w -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd

wpa_driver_wext_set_drop_unencrypted
State: DISCONNECTED -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=16
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c07 len=96
AssocReq IE wireless event - hexdump(len=88): 00 08 67 69 72 6c 66 65 73 73 01 08 82 84 8b 96 24 30 48 6c 21 02 08 12 24 02 01 0e 32 04 0c 12 18 60 dd 06 00 40 96 01 01 00 dd 09 00 10 18 02 00 10 00 00 00 dd 07 00 50 f2 02 00 01 00 dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c08 len=162
AssocResp IE wireless event - hexdump(len=154): 01 08 82 84 8b 0c 12 96 18 24 32 04 30 48 60 6c 2d 1a 4c 10 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3d 16 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 dd 18 00 50 f2 02 01 01 07 00 02 a4 00 00 27 a4 00 00 42 43 5e 00 62 32 2f 00 dd 1e 00 90 4c 33 4c 10 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 dd 1a 00 90 4c 34 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:1b:63:2d:20:a9
Association info event
req_ies - hexdump(len=88): 00 08 67 69 72 6c 66 65 73 73 01 08 82 84 8b 96 24 30 48 6c 21 02 08 12 24 02 01 0e 32 04 0c 12 18 60 dd 06 00 40 96 01 01 00 dd 09 00 10 18 02 00 10 00 00 00 dd 07 00 50 f2 02 00 01 00 dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
resp_ies - hexdump(len=154): 01 08 82 84 8b 0c 12 96 18 24 32 04 30 48 60 6c 2d 1a 4c 10 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3d 16 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 dd 18 00 50 f2 02 01 01 07 00 02 a4 00 00 27 a4 00 00 42 43 5e 00 62 32 2f 00 dd 1e 00 90 4c 33 4c 10 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 dd 1a 00 90 4c 34 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: set own WPA/RSN IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:1b:63:2d:20:a9
No keys have been configured - skip key clearing
Associated with 00:1b:63:2d:20:a9
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c07 len=96
AssocReq IE wireless event - hexdump(len=88): 00 08 67 69 72 6c 66 65 73 73 01 08 82 84 8b 96 24 30 48 6c 21 02 08 12 24 02 01 0e 32 04 0c 12 18 60 dd 06 00 40 96 01 01 00 dd 09 00 10 18 02 00 10 00 00 00 dd 07 00 50 f2 02 00 01 00 dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c08 len=162
AssocResp IE wireless event - hexdump(len=154): 01 08 82 84 8b 0c 12 96 18 24 32 04 30 48 60 6c 2d 1a 4c 10 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3d 16 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 dd 18 00 50 f2 02 01 01 07 00 02 a4 00 00 27 a4 00 00 42 43 5e 00 62 32 2f 00 dd 1e 00 90 4c 33 4c 10 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 dd 1a 00 90 4c 34 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:1b:63:2d:20:a9
Association info event
req_ies - hexdump(len=88): 00 08 67 69 72 6c 66 65 73 73 01 08 82 84 8b 96 24 30 48 6c 21 02 08 12 24 02 01 0e 32 04 0c 12 18 60 dd 06 00 40 96 01 01 00 dd 09 00 10 18 02 00 10 00 00 00 dd 07 00 50 f2 02 00 01 00 dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
resp_ies - hexdump(len=154): 01 08 82 84 8b 0c 12 96 18 24 32 04 30 48 60 6c 2d 1a 4c 10 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3d 16 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 dd 18 00 50 f2 02 01 01 07 00 02 a4 00 00 27 a4 00 00 42 43 5e 00 62 32 2f 00 dd 1e 00 90 4c 33 4c 10 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 dd 1a 00 90 4c 34 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: set own WPA/RSN IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
State: ASSOCIATED -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated with 00:1b:63:2d:20:a9
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RX EAPOL from 00:1b:63:2d:20:a9
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 01 ec 58 bd e8 39 c3 14 f7 a5 51 a9 9d 8c 48 3c ac 06 7b 51 3d 32 61 9f d7 9b 94 8a 11 65 71 65 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
EAPOL-Key type=254
key_info 0x89 (ver=1 keyidx=0 rsvd=0 Pairwise Ack)
key_length=32 key_data_length=0
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 01
key_nonce - hexdump(len=32): ec 58 bd e8 39 c3 14 f7 a5 51 a9 9d 8c 48 3c ac 06 7b 51 3d 32 61 9f d7 9b 94 8a 11 65 71 65 10
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 01 ec 58 bd e8 39 c3 14 f7 a5 51 a9 9d 8c 48 3c ac 06 7b 51 3d 32 61 9f d7 9b 94 8a 11 65 71 65 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:1b:63:2d:20:a9 (ver=1)
WPA: Renewed SNonce - hexdump(len=32): 0f a8 1e 16 53 1c 95 89 d7 a5 35 50 9d 98 d8 c1 fe 27 e8 a3 a5 af ee b5 df 18 91 16 2d dd 27 07
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: WPA IE for msg 2/4 - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=125): 01 03 00 79 fe 01 09 00 20 00 00 00 00 00 00 00 01 0f a8 1e 16 53 1c 95 89 d7 a5 35 50 9d 98 d8 c1 fe 27 e8 a3 a5 af ee b5 df 18 91 16 2d dd 27 07 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 34 9a a0 ce 51 cc fd c2 d9 b0 d6 08 8e d8 9e 25 00 1a dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c07 len=96
AssocReq IE wireless event - hexdump(len=88): 00 08 67 69 72 6c 66 65 73 73 01 08 82 84 8b 96 24 30 48 6c 21 02 08 12 24 02 01 0e 32 04 0c 12 18 60 dd 06 00 40 96 01 01 00 dd 09 00 10 18 02 00 10 00 00 00 dd 07 00 50 f2 02 00 01 00 dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c08 len=162
AssocResp IE wireless event - hexdump(len=154): 01 08 82 84 8b 0c 12 96 18 24 32 04 30 48 60 6c 2d 1a 4c 10 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3d 16 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 dd 18 00 50 f2 02 01 01 07 00 02 a4 00 00 27 a4 00 00 42 43 5e 00 62 32 2f 00 dd 1e 00 90 4c 33 4c 10 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 dd 1a 00 90 4c 34 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:1b:63:2d:20:a9
Association info event
req_ies - hexdump(len=88): 00 08 67 69 72 6c 66 65 73 73 01 08 82 84 8b 96 24 30 48 6c 21 02 08 12 24 02 01 0e 32 04 0c 12 18 60 dd 06 00 40 96 01 01 00 dd 09 00 10 18 02 00 10 00 00 00 dd 07 00 50 f2 02 00 01 00 dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
resp_ies - hexdump(len=154): 01 08 82 84 8b 0c 12 96 18 24 32 04 30 48 60 6c 2d 1a 4c 10 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3d 16 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 dd 18 00 50 f2 02 01 01 07 00 02 a4 00 00 27 a4 00 00 42 43 5e 00 62 32 2f 00 dd 1e 00 90 4c 33 4c 10 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 dd 1a 00 90 4c 34 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: set own WPA/RSN IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
State: 4WAY_HANDSHAKE -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated with 00:1b:63:2d:20:a9
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RX EAPOL from 00:1b:63:2d:20:a9
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 01 ec 58 bd e8 39 c3 14 f7 a5 51 a9 9d 8c 48 3c ac 06 7b 51 3d 32 61 9f d7 9b 94 8a 11 65 71 65 11 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
EAPOL-Key type=254
key_info 0x89 (ver=1 keyidx=0 rsvd=0 Pairwise Ack)
key_length=32 key_data_length=0
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 01
key_nonce - hexdump(len=32): ec 58 bd e8 39 c3 14 f7 a5 51 a9 9d 8c 48 3c ac 06 7b 51 3d 32 61 9f d7 9b 94 8a 11 65 71 65 11
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 01 ec 58 bd e8 39 c3 14 f7 a5 51 a9 9d 8c 48 3c ac 06 7b 51 3d 32 61 9f d7 9b 94 8a 11 65 71 65 11 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:1b:63:2d:20:a9 (ver=1)
WPA: Renewed SNonce - hexdump(len=32): f6 c0 69 06 e6 9d 8f e2 38 db 4a 7c f1 b5 5b 34 61 19 e1 e4 83 e7 8a b7 8c 33 95 e6 90 96 d4 9f
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: WPA IE for msg 2/4 - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=125): 01 03 00 79 fe 01 09 00 20 00 00 00 00 00 00 00 01 f6 c0 69 06 e6 9d 8f e2 38 db 4a 7c f1 b5 5b 34 61 19 e1 e4 83 e7 8a b7 8c 33 95 e6 90 96 d4 9f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 88 b2 91 a7 34 75 be 0b 0b 9f bc 46 10 a5 19 8d 00 1a dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
RX EAPOL from 00:1b:63:2d:20:a9
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 01 ec 58 bd e8 39 c3 14 f7 a5 51 a9 9d 8c 48 3c ac 06 7b 51 3d 32 61 9f d7 9b 94 8a 11 65 71 65 12 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
IEEE 802.1X RX: version=1 type=3 length=95
EAPOL-Key type=254
key_info 0x89 (ver=1 keyidx=0 rsvd=0 Pairwise Ack)
key_length=32 key_data_length=0
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 01
key_nonce - hexdump(len=32): ec 58 bd e8 39 c3 14 f7 a5 51 a9 9d 8c 48 3c ac 06 7b 51 3d 32 61 9f d7 9b 94 8a 11 65 71 65 12
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 01 ec 58 bd e8 39 c3 14 f7 a5 51 a9 9d 8c 48 3c ac 06 7b 51 3d 32 61 9f d7 9b 94 8a 11 65 71 65 12 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:1b:63:2d:20:a9 (ver=1)
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: WPA IE for msg 2/4 - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=125): 01 03 00 79 fe 01 09 00 20 00 00 00 00 00 00 00 01 f6 c0 69 06 e6 9d 8f e2 38 db 4a 7c f1 b5 5b 34 61 19 e1 e4 83 e7 8a b7 8c 33 95 e6 90 96 d4 9f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a9 2e 00 eb a6 73 ea 12 58 e4 e8 79 ca fc 25 d7 00 1a dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)

I dont know where it starts and stops, because it just keeps going. It never gives me a chance to go on to the next step since it seems to be stuck in some loop.

Here's my wpa supplicant file:

ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="girlfess"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk="%35%31%39"
pairwise=TKIP
group=TKIP
}

[kevdog]

Try doing the following b/c it looks like things are working

Instead of this:
sudo wpa_supplicant -w -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd

Do this:
sudo wpa_supplicant -Bw -Dwext -iwlan0 -c/etc/wpa_supplicant.conf

You will not get any debug parameters with the second command since it will be run in the background (hence the B flag). It looked like your debug output was positive from the previous post, so you might be in luck.

[SlingerXL]

Try doing the following b/c it looks like things are working

Instead of this:
sudo wpa_supplicant -w -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd

Do this:
sudo wpa_supplicant -Bw -Dwext -iwlan0 -c/etc/wpa_supplicant.conf

You will not get any debug parameters with the second command since it will be run in the background (hence the B flag). It looked like your debug output was positive from the previous post, so you might be in luck.

Thanks a lot for helping me out so much. I'd be completely at a loss without your help.

OK so this is what happened when I tried to connect via command line:

dan@dan-hp:~$ sudo ifconfig wlan0 down
[sudo] password for dan:
Sorry, try again.
[sudo] password for dan:
dan@dan-hp:~$ sudo dhclient -r wlan0
There is already a pid file /var/run/dhclient.pid with pid 8612
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1a:73:a6:9d:b4
Sending on LPF/wlan0/00:1a:73:a6:9d:b4
Sending on Socket/fallback
dan@dan-hp:~$ sudo wpa_supplicant -Bw -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
dan@dan-hp:~$ sudo ifconfig wlan0 up
dan@dan-hp:~$ sudo iwconfig wlan0 mode Managed
dan@dan-hp:~$ sudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1a:73:a6:9d:b4
Sending on LPF/wlan0/00:1a:73:a6:9d:b4
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


I'm excited because this is as far as I've got in my 2 week long quest for wireless! It's like a puzzle that I just have to solve. Unfortunately, I'm not there yet. Do you know what went wrong this time? What's a pid?

[kevdog]

OK

Do the following:

1. Change the wpa password to only contain letter or numbers -- no funky stuff -- this sometimes is a problem -- make it really simple for right now!

2. Pop open two command windows

Window #1:
sudo ifconfig wlan0 down
sudo dhclient -r wlan0
sudo wpa_supplicant -w -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd

The output in this window will likely not stop

Stop with Cntl-C when need be but run commands in Window#2 while output is going in Window#1

Window #2:
sudo ifconfig wlan0 up
sudo iwconfig wlan0 mode Managed
sudo dhclient wlan0

Can you lastly check dmesg for me. I don't want you to post the entire file. dmesg is a long file. Probably best checked right after boot since its a lot smaller, but it doesnt matter. Scan the output (dmesg | more -- use spacebar to get next page) and look for wlan0 or something about your network card. Make sure you see specifically that wpa is supported by your wireless driver, and there are no errors associated with your card -- read carefully -- they are easy to miss).

Lastly post
iwlist scan

[SlingerXL]

OK

Do the following:

1. Change the wpa password to only contain letter or numbers -- no funky stuff -- this sometimes is a problem -- make it really simple for right now!

2. Pop open two command windows

Window #1:
sudo ifconfig wlan0 down
sudo dhclient -r wlan0
sudo wpa_supplicant -w -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd

The output in this window will likely not stop

Stop with Cntl-C when need be but run commands in Window#2 while output is going in Window#1

Window #2:
sudo ifconfig wlan0 up
sudo iwconfig wlan0 mode Managed
sudo dhclient wlan0
Output for this method was the same as my last post where I added -Bw.Ended in:

No DHCPOFFERS received.
No working leases in persistent database - sleeping.


Can you lastly check dmesg for me. I don't want you to post the entire file. dmesg is a long file. Probably best checked right after boot since its a lot smaller, but it doesnt matter. Scan the output (dmesg | more -- use spacebar to get next page) and look for wlan0 or something about your network card. Make sure you see specifically that wpa is supported by your wireless driver, and there are no errors associated with your card -- read carefully -- they are easy to miss).

Here's what I found:

[ 205.710420] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 208.955590] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 217.832023] wlan0: no IPv6 routers present



[ 42.736342] ndiswrapper: using IRQ 16
[ 42.869532] wlan0: ethernet device 00:1a:73:a6:9d:b4 using NDIS driver: bcmwl5, version: 0x4640f05, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 14E4:4311.5.conf
[ 42.869559] wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK



[ 42.578544] wlan0: ethernet device 00:1a:73:a6:9d:b4 using NDIS driver: bcmwl5, version: 0x4640f05, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 14E4:4311.5.conf

[ 42.578959] wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
[ 42.585328] usbcore: registered new interface driver ndiswrapper
[ 42.649247] ndiswrapper: device wlan0 removed


[ 42.578544] wlan0: ethernet device 00:1a:73:a6:9d:b4 using NDIS driver: bcmwl5, version: 0x4640f05, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 14E4:4311.5.conf


Lastly post
iwlist scan
OK


Usage: iwlist [interface] scanning [essid NNN] [last]
[interface] frequency
[interface] channel
[interface] bitrate
[interface] rate
[interface] encryption
[interface] keys
[interface] power
[interface] txpower
[interface] retry
[interface] ap
[interface] accesspoints
[interface] peers
[interface] event
[interface] auth
[interface] wpakeys
[interface] genie
[interface] modulation

[kevdog]

Thanks -- just post
iwlist scan

[SlingerXL]

Thanks -- just post
iwlist scan

dan@dan-hp:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 No scan results


With sudo though I get this:

[sudo] password for dan:
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:17:3F:6A:DD:99
ESSID:"houseoflove"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:39/100 Signal level:-71 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Preauthentication Supported
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
Cell 02 - Address: 02:E0:62:4D:5F:38
ESSID:"ANY"
Protocol:IEEE 802.11g
Mode:Ad-Hoc
Frequency:2.412 GHz (Channel 1)
Quality:28/100 Signal level:-78 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : none
Authentication Suites (1) : 802.1x
Cell 03 - Address: 00:1B:63:2D:20:A9
ESSID:"girlfess"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:89/100 Signal level:-39 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 04 - Address: 00:1C:10:14:AB:84
ESSID:"Citgo-3"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:15/100 Signal level:-86 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

[kevdog]

Does you wireless card connect if for example wpa is turned off and no wireless encryption is used?

[SlingerXL]

Does you wireless card connect if for example wpa is turned off and no wireless encryption is used?
I'm working on getting admin access to the Base Station right now. I probably won't know until tomorrow though.

[adante]

howdy, hoping someone can help here, I'm trying to connect to a hidden ssid and don't really know what I'm doing.

It support (who don't support linux clients) have kindly given me this information:
Network name: csiro-internal
Network Authentication: WPA-Enterprise EAP method PEAP
Inner EAP method: MS-CHAP v2

my wpa_supplicant.conf is like this:



ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
ap_scan=1
fast_reauth=1
network={
ssid="csiro-internal"
scan_ssid=1
key_mgmt=WPA-EAP
proto=RSN
eap=PEAP
phase2="auth=MSCHAPV2"
identity="cha623"
password="" # removed
}


running wpa_supplicant -i wlan0 -D wext -c /etc/wpa_supplicant.conf -dd gives:



Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
eapol_version=1
ap_scan=1
fast_reauth=1
Line: 8 - start of a new network block
ssid - hexdump_ascii(len=14):
63 73 69 72 6f 2d 69 6e 74 65 72 6e 61 6c csiro-internal
scan_ssid=1 (0x1)
key_mgmt: 0x1
proto: 0x2
eap methods - hexdump(len=16): 00 00 00 00 19 00 00 00 00 00 00 00 00 00 00 00
phase2 - hexdump_ascii(len=13):
61 75 74 68 3d 4d 53 43 48 41 50 56 32 auth=MSCHAPV2
identity - hexdump_ascii(len=6):
63 68 61 36 32 33 cha623
password - hexdump_ascii(len=9): [REMOVED]
Priority group 0
id=0 ssid='csiro-internal'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1f:3b:51:e1:4f
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Added interface wlan0
RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
Wireless event: cmd=0x8b06 len=8
Ignore event for foreign ifindex 3
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=14):
63 73 69 72 6f 2d 69 6e 74 65 72 6e 61 6c csiro-internal
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 0
Try to find WPA-enabled AP
Try to find non-WPA AP
No suitable AP found.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=8
Received 1717 bytes of scan results (8 BSSes)
Scan results: 8
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:1f:c9:66:78:b0 ssid='csiro-internal' wpa_ie_len=0 rsn_ie_len=22 caps=0x11
selected based on RSN IE
selected WPA AP 00:1f:c9:66:78:b0 ssid='csiro-internal'
Try to find non-WPA AP
Trying to associate with 00:1f:c9:66:78:b0 (SSID='csiro-internal' freq=2412 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
RSN: using IEEE 802.11i/D9.0
WPA: Selected cipher suites: group 16 pairwise 16 key_mgmt 1 proto 2
WPA: clearing AP WPA IE
WPA: set AP RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 01 28 00
WPA: using GTK CCMP
WPA: using PTK CCMP
WPA: using KEY_MGMT 802.1X
WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 01 00 00
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - portControl=Auto
RSN: Ignored PMKID candidate without preauth flag
RSN: Ignored PMKID candidate without preauth flag
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=22
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c02 len=245
WEXT: Custom wireless event: 'ASSOCINFO(ReqIE010802040b160c12182432043048606c30 140100000fac040100000fac040100000fac010000dd070050 f202000100 RespIEdd180050f2020101820003a5000027a500004254bc00 62436600)'
Association info event
req_ies - hexdump(len=63): 00 0e 63 73 69 72 6f 2d 69 6e 74 65 72 6e 61 6c 01 08 02 04 0b 16 0c 12 18 24 32 04 30 48 60 6c 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 01 00 00 dd 07 00 50 f2 02 00 01 00
resp_ies - hexdump(len=42): 01 08 82 84 8b 0c 12 96 18 24 32 04 30 48 60 6c dd 18 00 50 f2 02 01 01 82 00 03 a5 00 00 27 a5 00 00 42 54 bc 00 62 43 66 00
WPA: set own WPA/RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 01 00 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:1f:c9:66:78:b0
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:1f:c9:66:78:b0
No keys have been configured - skip key clearing
Associated with 00:1f:c9:66:78:b0
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RX EAPOL from 00:1f:c9:66:78:b0
RX EAPOL - hexdump(len=61): 01 00 00 39 01 01 00 39 01 00 6e 65 74 77 6f 72 6b 69 64 3d 63 73 69 72 6f 2d 69 6e 74 65 72 6e 61 6c 2c 6e 61 73 69 64 3d 72 62 68 2d 63 63 72 2d 61 70 31 2c 70 6f 72 74 69 64 3d 30
Setting authentication timeout: 70 sec 0 usec
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_PAE entering state RESTART
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request id=1 method=1 vendor=0 vendorMethod=0
EAP: EAP entering state IDENTITY
CTRL-EVENT-EAP-STARTED EAP authentication started
EAP: EAP-Request Identity data - hexdump_ascii(len=52):
00 6e 65 74 77 6f 72 6b 69 64 3d 63 73 69 72 6f _networkid=csiro
2d 69 6e 74 65 72 6e 61 6c 2c 6e 61 73 69 64 3d -internal,nasid=
72 62 68 2d 63 63 72 2d 61 70 31 2c 70 6f 72 74 rbh-ccr-ap1,port
69 64 3d 30 id=0
EAP: using real identity - hexdump_ascii(len=6):
63 68 61 36 32 33 cha623
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=15): 01 00 00 0b 02 01 00 0b 01 63 68 61 36 32 33
EAPOL: SUPP_BE entering state RECEIVE
EAPOL: startWhen --> 0
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b19 len=8
Received 810 bytes of scan results (4 BSSes)
Scan results: 4
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:1f:c9:66:78:b0 ssid='csiro-internal' wpa_ie_len=0 rsn_ie_len=22 caps=0x11
selected based on RSN IE
selected WPA AP 00:1f:c9:66:78:b0 ssid='csiro-internal'
Try to find non-WPA AP
Already associated with the selected AP.
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
Added BSSID 00:1f:c9:66:78:b0 into blacklist
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
State: ASSOCIATED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
EAPOL: authWhile --> 0
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=14):
63 73 69 72 6f 2d 69 6e 74 65 72 6e 61 6c csiro-internal
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c02 len=245
WEXT: Custom wireless event: 'ASSOCINFO(ReqIE010802040b160c12182432043048606c30 140100000fac040100000fac040100000fac010000dd070050 f202000100 RespIEdd180050f2020101820003a5000027a500004254bc00 62436600)'
Association info event
req_ies - hexdump(len=63): 00 0e 63 73 69 72 6f 2d 69 6e 74 65 72 6e 61 6c 01 08 02 04 0b 16 0c 12 18 24 32 04 30 48 60 6c 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 01 00 00 dd 07 00 50 f2 02 00 01 00
resp_ies - hexdump(len=42): 01 08 82 84 8b 0c 12 96 18 24 32 04 30 48 60 6c dd 18 00 50 f2 02 01 01 82 00 03 a5 00 00 27 a5 00 00 42 54 bc 00 62 43 66 00
WPA: set own WPA/RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 01 00 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:1f:c9:66:78:b0
State: SCANNING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:1f:c9:66:78:b0
No keys have been configured - skip key clearing
Associated with 00:1f:c9:66:78:b0
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RX EAPOL from 00:1f:c9:66:78:b0
RX EAPOL - hexdump(len=61): 01 00 00 39 01 01 00 39 01 00 6e 65 74 77 6f 72 6b 69 64 3d 63 73 69 72 6f 2d 69 6e 74 65 72 6e 61 6c 2c 6e 61 73 69 64 3d 72 62 68 2d 63 63 72 2d 61 70 31 2c 70 6f 72 74 69 64 3d 30
Setting authentication timeout: 70 sec 0 usec
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_PAE entering state RESTART
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request id=1 method=1 vendor=0 vendorMethod=0
EAP: EAP entering state IDENTITY
CTRL-EVENT-EAP-STARTED EAP authentication started
EAP: EAP-Request Identity data - hexdump_ascii(len=52):
00 6e 65 74 77 6f 72 6b 69 64 3d 63 73 69 72 6f _networkid=csiro
2d 69 6e 74 65 72 6e 61 6c 2c 6e 61 73 69 64 3d -internal,nasid=
72 62 68 2d 63 63 72 2d 61 70 31 2c 70 6f 72 74 rbh-ccr-ap1,port
69 64 3d 30 id=0
EAP: using real identity - hexdump_ascii(len=6):
63 68 61 36 32 33 cha623
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=15): 01 00 00 0b 02 01 00 0b 01 63 68 61 36 32 33
EAPOL: SUPP_BE entering state RECEIVE
EAPOL: startWhen --> 0
Scan timeout - try to get results
Received 0 bytes


with it trying to run the auth over and over and timing out.

can someone please advise on what I need to do?

[kevdog]

I have no experience with MSCHAPV2 so I'm not going to be much help to you. I haven't found a lot of info in the ubuntu forums about this either. Unfortunately google might be your best friend on this one.

[adante]

I have no experience with MSCHAPV2 so I'm not going to be much help to you. I haven't found a lot of info in the ubuntu forums about this either. Unfortunately google might be your best friend on this one.

well I sort of got it working maybe, but not sure how.

firstly I left the above config listed 2 posts up running while I went to lunch. When I came back it seemed to have connected so I ran sudo dhclient wlan0 and it worked and all was good.

Then I killed it and attempted to re-run wpa_supplicant and had the same problem. So I fiddled with some settings and it worked again. Who knows what will happen if I try to reconnect, heh.

anyway current settings (changes: disabled EAP, fast_reauth, added full domain to my username (but was explicitly told this was not necessary)



ctrl_interface=/var/run/wpa_supplicant

eapol_version=1
ap_scan=1
fast_reauth=0


network={
ssid="csiro-internal"
scan_ssid=1
key_mgmt=WPA-EAP
proto=RSN
#eap=PEAP
phase1="peaplabel=1"
phase2="auth=MSCHAPV2"
identity=""
password=""
}


wpa_supplicant connection log:


zmc@zts:~$ sudo ifconfig wlan0 down; sudo wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf -dd
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
eapol_version=1
ap_scan=1
fast_reauth=0
Line: 8 - start of a new network block
ssid - hexdump_ascii(len=14):
63 73 69 72 6f 2d 69 6e 74 65 72 6e 61 6c csiro-internal
scan_ssid=1 (0x1)
key_mgmt: 0x1
proto: 0x2
phase1 - hexdump_ascii(len=11):
70 65 61 70 6c 61 62 65 6c 3d 31 peaplabel=1
phase2 - hexdump_ascii(len=13):
61 75 74 68 3d 4d 53 43 48 41 50 56 32 auth=MSCHAPV2
identity - hexdump_ascii(len=15):

password - hexdump_ascii(len=9): [REMOVED]
Priority group 0
id=0 ssid='csiro-internal'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1f:3b:51:e1:4f
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Added interface wlan0
RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
Wireless event: cmd=0x8b06 len=8
Ignore event for foreign ifindex 3
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=14):
63 73 69 72 6f 2d 69 6e 74 65 72 6e 61 6c csiro-internal
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 248 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:1f:c9:66:78:b0 ssid='csiro-internal' wpa_ie_len=0 rsn_ie_len=22 caps=0x11
selected based on RSN IE
selected WPA AP 00:1f:c9:66:78:b0 ssid='csiro-internal'
Try to find non-WPA AP
Trying to associate with 00:1f:c9:66:78:b0 (SSID='csiro-internal' freq=2412 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
RSN: using IEEE 802.11i/D9.0
WPA: Selected cipher suites: group 16 pairwise 16 key_mgmt 1 proto 2
WPA: clearing AP WPA IE
WPA: set AP RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 01 28 00
WPA: using GTK CCMP
WPA: using PTK CCMP
WPA: using KEY_MGMT 802.1X
WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 01 00 00
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - portControl=Auto
RSN: Ignored PMKID candidate without preauth flag
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=22
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c02 len=245
WEXT: Custom wireless event: 'ASSOCINFO(ReqIE010802040b160c12182432043048606c30 140100000fac040100000fac040100000fac010000dd070050 f202000100 RespIEdd180050f2020101820003a5000027a500004254bc00 62436600)'
Association info event
req_ies - hexdump(len=63): 00 0e 63 73 69 72 6f 2d 69 6e 74 65 72 6e 61 6c 01 08 02 04 0b 16 0c 12 18 24 32 04 30 48 60 6c 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 01 00 00 dd 07 00 50 f2 02 00 01 00
resp_ies - hexdump(len=42): 01 08 82 84 8b 0c 12 96 18 24 32 04 30 48 60 6c dd 18 00 50 f2 02 01 01 82 00 03 a5 00 00 27 a5 00 00 42 54 bc 00 62 43 66 00
WPA: set own WPA/RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 01 00 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:1f:c9:66:78:b0
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:1f:c9:66:78:b0
No keys have been configured - skip key clearing
Associated with 00:1f:c9:66:78:b0
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RX EAPOL from 00:1f:c9:66:78:b0
RX EAPOL - hexdump(len=61): 01 00 00 39 01 01 00 39 01 00 6e 65 74 77 6f 72 6b 69 64 3d 63 73 69 72 6f 2d 69 6e 74 65 72 6e 61 6c 2c 6e 61 73 69 64 3d 72 62 68 2d 63 63 72 2d 61 70 31 2c 70 6f 72 74 69 64 3d 30
Setting authentication timeout: 70 sec 0 usec
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_PAE entering state RESTART
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request id=1 method=1 vendor=0 vendorMethod=0
EAP: EAP entering state IDENTITY
CTRL-EVENT-EAP-STARTED EAP authentication started
EAP: EAP-Request Identity data - hexdump_ascii(len=52):
00 6e 65 74 77 6f 72 6b 69 64 3d 63 73 69 72 6f _networkid=csiro
2d 69 6e 74 65 72 6e 61 6c 2c 6e 61 73 69 64 3d -internal,nasid=
72 62 68 2d 63 63 72 2d 61 70 31 2c 70 6f 72 74 rbh-ccr-ap1,port
69 64 3d 30 id=0
EAP: using real identity - hexdump_ascii(len=15):
63 68 61 36 32 33 40 63 73 69 72 6f 2e 61 75 cha623@csiro.au
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=24): 01 00 00 14 02 01 00 14 01 63 68 61 36 32 33 40 63 73 69 72 6f 2e 61 75
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:1f:c9:66:78:b0
RX EAPOL - hexdump(len=46): 01 00 00 1f 01 8a 00 1f 11 01 00 08 c8 19 1e 9a f6 6a 6a 66 63 68 61 36 32 33 40 63 73 69 72 6f 2e 61 75 00 00 00 00 00 00 00 00 00 00 00
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request id=138 method=17 vendor=0 vendorMethod=0
EAP: EAP entering state GET_METHOD
EAP: Initialize selected EAP method: vendor 0 method 17 (LEAP)
CTRL-EVENT-EAP-METHOD EAP vendor 0 method 17 (LEAP) selected
EAP: EAP entering state METHOD
EAP-LEAP: Processing EAP-Request
EAP-LEAP: Challenge from AP - hexdump(len=8): c8 19 1e 9a f6 6a 6a 66
EAP-LEAP: Generating Challenge Response
EAP-LEAP: Response - hexdump(len=24): 16 27 91 20 dc 1f 7e fb 1a 9d 85 18 63 78 b3 13 67 9b ac 64 aa 9e b7 48
EAP: method process -> ignore=FALSE methodState=MAY_CONT decision=FAIL
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=51): 01 00 00 2f 02 8a 00 2f 11 01 00 18 16 27 91 20 dc 1f 7e fb 1a 9d 85 18 63 78 b3 13 67 9b ac 64 aa 9e b7 48 63 68 61 36 32 33 40 63 73 69 72 6f 2e 61 75
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:1f:c9:66:78:b0
RX EAPOL - hexdump(len=46): 01 00 00 04 03 8a 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Success
EAP: EAP entering state METHOD
EAP-LEAP: Processing EAP-Success
EAP-LEAP: Challenge to AP/AS - hexdump(len=8): 06 e1 1c 04 93 a9 06 f7
EAP: method process -> ignore=FALSE methodState=MAY_CONT decision=FAIL
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=35): 01 00 00 1f 01 8a 00 1f 11 01 00 08 06 e1 1c 04 93 a9 06 f7 63 68 61 36 32 33 40 63 73 69 72 6f 2e 61 75
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:1f:c9:66:78:b0
RX EAPOL - hexdump(len=51): 01 00 00 2f 02 8a 00 2f 11 01 00 18 f7 6b 9d 95 bd 94 b2 86 94 50 72 cf a2 90 ce 9a 28 04 d2 4c 0a 73 8e 06 63 68 61 36 32 33 40 63 73 69 72 6f 2e 61 75
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Response for LEAP method=17 id=138
EAP: EAP entering state METHOD
EAP-LEAP: Processing EAP-Response
EAP-LEAP: Response from AP - hexdump(len=24): f7 6b 9d 95 bd 94 b2 86 94 50 72 cf a2 90 ce 9a 28 04 d2 4c 0a 73 8e 06
EAP: method process -> ignore=FALSE methodState=DONE decision=UNCOND_SUCC
EAP-LEAP: pw_hash_hash - hexdump(len=16): [REMOVED]
EAP-LEAP: peer_challenge - hexdump(len=8): c8 19 1e 9a f6 6a 6a 66
EAP-LEAP: peer_response - hexdump(len=24): 16 27 91 20 dc 1f 7e fb 1a 9d 85 18 63 78 b3 13 67 9b ac 64 aa 9e b7 48
EAP-LEAP: ap_challenge - hexdump(len=8): 06 e1 1c 04 93 a9 06 f7
EAP-LEAP: ap_response - hexdump(len=24): f7 6b 9d 95 bd 94 b2 86 94 50 72 cf a2 90 ce 9a 28 04 d2 4c 0a 73 8e 06
EAP-LEAP: master key - hexdump(len=16): [REMOVED]
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAP: EAP entering state SUCCESS
CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
EAPOL: SUPP_BE entering state RECEIVE
EAPOL: SUPP_BE entering state SUCCESS
EAPOL: SUPP_BE entering state IDLE
RX EAPOL from 00:1f:c9:66:78:b0
RX EAPOL - hexdump(len=121): 02 03 00 75 02 00 8a 00 10 00 00 00 00 00 00 00 01 db 38 6f 30 b9 4e 69 02 a5 a5 01 24 00 ef 68 11 5e 4d 6f d2 f0 f4 75 35 f8 71 32 1a 5f d7 f2 cd 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 16 dd 14 00 0f ac 04 b6 0d 39 bd 9c 39 eb 9d 30 50 87 1e 8c af 96 51
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=2 type=3 length=117
EAPOL-Key type=2
key_info 0x8a (ver=2 keyidx=0 rsvd=0 Pairwise Ack)
key_length=16 key_data_length=22
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 01
key_nonce - hexdump(len=32): db 38 6f 30 b9 4e 69 02 a5 a5 01 24 00 ef 68 11 5e 4d 6f d2 f0 f4 75 35 f8 71 32 1a 5f d7 f2 cd
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX EAPOL-Key - hexdump(len=121): 02 03 00 75 02 00 8a 00 10 00 00 00 00 00 00 00 01 db 38 6f 30 b9 4e 69 02 a5 a5 01 24 00 ef 68 11 5e 4d 6f d2 f0 f4 75 35 f8 71 32 1a 5f d7 f2 cd 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 16 dd 14 00 0f ac 04 b6 0d 39 bd 9c 39 eb 9d 30 50 87 1e 8c af 96 51
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:1f:c9:66:78:b0 (ver=2)
RSN: msg 1/4 key data - hexdump(len=22): dd 14 00 0f ac 04 b6 0d 39 bd 9c 39 eb 9d 30 50 87 1e 8c af 96 51
RSN: PMKID from Authenticator - hexdump(len=16): b6 0d 39 bd 9c 39 eb 9d 30 50 87 1e 8c af 96 51
RSN: no matching PMKID found
WPA: PMK from EAPOL state machines - hexdump(len=16): [REMOVED]
RSN: added PMKSA cache entry for 00:1f:c9:66:78:b0
RSN: the new PMK matches with the PMKID
WPA: Renewed SNonce - hexdump(len=32): 0e b3 cb cf 39 b6 2d d9 18 b2 1e 2d f9 94 29 c1 09 7d 1c a2 77 65 7a c6 c5 3f 15 63 b1 1f 0e c1
WPA: PMK - hexdump(len=16): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: WPA IE for msg 2/4 - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 01 00 00
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=121): 01 03 00 75 02 01 0a 00 00 00 00 00 00 00 00 00 01 0e b3 cb cf 39 b6 2d d9 18 b2 1e 2d f9 94 29 c1 09 7d 1c a2 77 65 7a c6 c5 3f 15 63 b1 1f 0e c1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d9 f0 78 10 29 10 96 00 27 c2 e3 ed e5 24 6f 7f 00 16 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 01 00 00
RX EAPOL from 00:1f:c9:66:78:b0
RX EAPOL - hexdump(len=155): 02 03 00 97 02 13 ca 00 10 00 00 00 00 00 00 00 02 db 38 6f 30 b9 4e 69 02 a5 a5 01 24 00 ef 68 11 5e 4d 6f d2 f0 f4 75 35 f8 71 32 1a 5f d7 f2 cd 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 63 8e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 77 81 91 c6 76 c8 12 eb 08 78 b5 ca 10 8b 16 53 00 38 72 a9 4b 20 ef 0d 6f 0a 39 e5 e3 9a 85 14 74 56 bc 78 2e 3a 00 43 d8 e3 82 e9 f3 06 6b a0 a6 da a0 9a ce bd b6 ec fe 91 50 47 bb 15 b4 e3 71 b5 5f 97 d8 d5 7e b4 74 74
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=2 type=3 length=151
EAPOL-Key type=2
key_info 0x13ca (ver=2 keyidx=0 rsvd=0 Pairwise Install Ack MIC Secure Encr)
key_length=16 key_data_length=56
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 02
key_nonce - hexdump(len=32): db 38 6f 30 b9 4e 69 02 a5 a5 01 24 00 ef 68 11 5e 4d 6f d2 f0 f4 75 35 f8 71 32 1a 5f d7 f2 cd
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 63 8e 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 77 81 91 c6 76 c8 12 eb 08 78 b5 ca 10 8b 16 53
WPA: RX EAPOL-Key - hexdump(len=155): 02 03 00 97 02 13 ca 00 10 00 00 00 00 00 00 00 02 db 38 6f 30 b9 4e 69 02 a5 a5 01 24 00 ef 68 11 5e 4d 6f d2 f0 f4 75 35 f8 71 32 1a 5f d7 f2 cd 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 63 8e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 77 81 91 c6 76 c8 12 eb 08 78 b5 ca 10 8b 16 53 00 38 72 a9 4b 20 ef 0d 6f 0a 39 e5 e3 9a 85 14 74 56 bc 78 2e 3a 00 43 d8 e3 82 e9 f3 06 6b a0 a6 da a0 9a ce bd b6 ec fe 91 50 47 bb 15 b4 e3 71 b5 5f 97 d8 d5 7e b4 74 74
RSN: encrypted key data - hexdump(len=56): 72 a9 4b 20 ef 0d 6f 0a 39 e5 e3 9a 85 14 74 56 bc 78 2e 3a 00 43 d8 e3 82 e9 f3 06 6b a0 a6 da a0 9a ce bd b6 ec fe 91 50 47 bb 15 b4 e3 71 b5 5f 97 d8 d5 7e b4 74 74
WPA: decrypted EAPOL-Key key data - hexdump(len=48): [REMOVED]
State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 3 of 4-Way Handshake from 00:1f:c9:66:78:b0 (ver=2)
WPA: IE KeyData - hexdump(len=48): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 01 28 00 dd 16 00 0f ac 01 01 00 38 1f 8e 9b 46 3e 7c 95 51 96 b5 69 9c 01 8d ea dd 00
WPA: Sending EAPOL-Key 4/4
WPA: TX EAPOL-Key - hexdump(len=99): 01 03 00 5f 02 03 0a 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 43 d5 28 8f 9d c4 34 5e 43 46 63 5d a2 cc 04 15 00 00
WPA: Installing PTK to the driver.
wpa_driver_wext_set_key: alg=3 key_idx=0 set_tx=1 seq_len=6 key_len=16
EAPOL: External notification - portValid=1
EAPOL: SUPP_PAE entering state AUTHENTICATED
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
RSN: received GTK in pairwise handshake - hexdump(len=18): [REMOVED]
WPA: Group Key - hexdump(len=16): [REMOVED]
WPA: Installing GTK to the driver (keyidx=1 tx=0).
WPA: RSC - hexdump(len=6): 63 8e 00 00 00 00
wpa_driver_wext_set_key: alg=3 key_idx=1 set_tx=0 seq_len=6 key_len=16
WPA: Key negotiation completed with 00:1f:c9:66:78:b0 [PTK=CCMP GTK=CCMP]
Cancelling authentication timeout
State: GROUP_HANDSHAKE -> COMPLETED
CTRL-EVENT-CONNECTED - Connection to 00:1f:c9:66:78:b0 completed (auth) [id=0 id_str=]
wpa_driver_wext_set_operstate: operstate 0->1 (UP)
WEXT: Operstate: linkmode=-1, operstate=6
EAPOL: External notification - portValid=1
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
EAPOL: startWhen --> 0
EAPOL: authWhile --> 0
EAPOL: idleWhile --> 0

[kevdog]

adante

Inform me if this is successful with repeated attempts and I will add it to the front page of the guide with credit to you.

[Yondergod22]

I found a mistake. in a few places it says mode Managed with a capital "M" in managed, but it should be lower case. Thanks for the guide, it helped me on 2 computers.:)

[kevdog]

No it should be Managed with a capitol M:
http://linux.die.net/man/8/iwconfig

[adante]

adante

Inform me if this is successful with repeated attempts and I will add it to the front page of the guide with credit to you.

sadly, no

well, in the literal sense, it IS successful with repeated attempts :confused: - if I run the command and just let it sit there for some time it does eventually work. Sometimes it connects immediately and other times it will take a lunch break.

odd. I will keep you informed if I ever manage to solve this reliably.

[kinrose]

I am new to linux but followed the instructions OK. Got the desired results: sending on, listening on, DHCPREQEST, DHCPACK and bound to. I still can't get onto the internet. I eventfully get a timed out error message. Is there somewhere I should be typing in my ISP's name and password? I have tried the email set up but can't send or receive email, it times out.
Thanks

[kevdog]

You might have a dns problem. If you do a:

ping 72.14.207.99

Do you get a response (this is google's ip).

[kinrose]

thanks.
I get: packets transmitted 5 Packets received 0 Successful packets 0%

[kinrose]

I have re run the instructions and should have used eth0 and not eth1. I now get the error message: SET failed on device eth0 operation not supported, after typing in: sudo iwconfig eth0 essid "name_WIRELES"

Any assistance appreciated

[kevdog]

Are you sure your interface is eth0 -- that is usually the ethernet wired interface.

[tornsolitude]

I have successfully connected wirelessly when it's unencrypted. I have also connected when it's encrypted, manually. It says when putting the commands in the rc.local file for an encrypted network, I must make the necessary changes. I'm assuming that I put in the commands I did manually minus the "sudo", which I have. And I did make it so it runs at boot. But it does not connect when I start the computer. Help, please?

[kevdog]

Can you post your rc.local file so I can troubleshoot?

[tornsolitude]

ifconfig eth0 down
ifconfig ath0 down
dhclient -r ath0
wpa_supplicant -w -Dmadwifi -iath0 -c/etc/wpa_supplicant.conf
ifconfig ath0 up
iwconfig ath0 mode Managed
dhclient ath0

exit 0

[tornsolitude]

wpa_supplicant.conf

ap_scan=1
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="zoom"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk="kaP=&PAJupr4RuYe"
pairwise=TKIP
group=TKIP
}

[kevdog]

Just to confirm that this runs manually when you type it at the command file, or when you put all the commands in a script file (owned by root), and run the script file.

If the answer is yes, the script file runs, then in the rc.local file I would put a statement like
sleep 20

prior to the networking lines. The reason for the sleep statement is that networking is dependent on other services to be up and running at boot, and possibly the services are not established when the rc.local file is run.

[kinrose]

Are you sure your interface is eth0 -- that is usually the ethernet wired interface.

Hi, MeThinks I was confused by our Eee's which show ath0 as the interface.

I have re-run the instructions several times and now have the message:
No DHCPOFFERS received.
No working leases in persitent database - sleeping.

[kevdog]

kinrose

Best advice

Figure out the interface
Try an unencrypted connection
Use an ESSID with only letters or numbers -- no spaces or crazy characters.
Broadcast the Essid

Make sure you can see your router with
iwlist scan

Hmm. maybe you could provide more info.

[tornsolitude]

I put "sleep 20" in, and still nothing.

I tried it again manually (deleted the commands out of rc.local) and it does work that way. But when I enter the line "sudo wpa_supplicant -w -Dmadwifi -iath0 -c/etc/wpa_supplicant.conf" with and without "-dd", it either goes in a loop or just sits there without returning back to commandline. I then open up another terminal, type the rest of the commands, and voila, it connects. Could this be the problem when rc.local runs at boot?

[kevdog]

Can you try with a -Bw flag instead of a -w flag? B sends it into the background. Not sure if this will make a difference in your case.

[tornsolitude]

It worked! Thank you so much!

[kevdog]

Does it work without the sleep statement and only the -Bw flag?

[tornsolitude]

Yes, I took out the sleep statement and used -Bw.

[elegua]

Hi Guys,

Please i need help with my wireless conection, i have a Toshiba P25 with Atheros AR5211 802.11ab NIC, i installed the lastest version of madwifi and WICD Manager, i can see my router but i can't conect to it, i'm using WPA-PSK.

Here some output:


gabby@gabby-laptop:~$ lshw -C network
WARNING: you should run this program as super-user.
*-network:0
description: Ethernet interface
product: RTL-8139/8139C/8139C+
vendor: Realtek Semiconductor Co., Ltd.
physical id: 1
bus info: pci@0000:02:01.0
logical name: eth0
version: 10
serial: 00:02:3f:82:3c:02
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=8139too driverversion=0.9.28 ip=192.168.4.8 latency=32 maxlatency=64 mingnt=32 module=8139too multicast=yes
*-network:1
description: Wireless interface
product: AR5211 802.11ab NIC
vendor: Atheros Communications Inc.
physical id: 2
bus info: pci@0000:02:02.0
logical name: wifi0
version: 01
serial: 00:90:96:59:f5:dc
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=ath_pci latency=168 maxlatency=28 mingnt=10 module=ath_pci multicast=yes wireless=IEEE 802.11a
gabby@gabby-laptop:~$

gedit /etc/network/interfaces


auto lo
iface lo inet loopback

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-ssid ITCS
wpa-key-mgmt WPA-PSK
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-psk mykey


sudo iwlist scan


o Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wifi0 Interface doesn't support scanning.

ath0 Scan completed :
Cell 01 - Address: 00:13:10:27:24:31
ESSID:"thegirls"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=25/70 Signal level=-70 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Cell 02 - Address: 00:1A:2F:91:E2:D0
ESSID:"ITCS"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=43/70 Signal level=-52 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra:wme_ie=dd180050f2020101830003a4000027a400004 2435e0062322f00
Cell 03 - Address: 00:11:20:1B:5B:DC
ESSID:"ITCS"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=32/70 Signal level=-63 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Extra:bcn_int=100
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra:wme_ie=dd180050f20201018c0003a4000027a400004 2435e0062322f00
Cell 04 - Address: 00:0A:95:F6:48:6C
ESSID:"Maxx Network"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=10/70 Signal level=-85 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

gksu gedit /etc/wpa_supplicant.conf


ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="ITCS"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk="mykey"
pairwise=TKIP
group=TKIP
}


Do i need to do something else?.

Thanks in advance.

[jerremy-tamlin]

Brilliant!! I love you!!
It's so great to go back to the very basic level, that's why I love Linux when things aren't working you can start from scratch and build them up.

Thank you!

[kevdog]

elegua

What's the problem?? -- We are not using the /etc/network/interfaces file in this example. -- neither does wicd.

Did you type any commands on the command line?

[twistbit]

I have a Palm Tungsten C and seem unable to connect to my BT Voyager 2500V router, I have a laptop and two PC one wireless and one wired. These all work fine, any clues or advice would be very much appreciated.

I have contacted Palm and BT who seem unable to help, my Palm seems to recognise the Router but will not connect to the internet.

[jaron.schut]

Hello,

Read the article, set it all up.


ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="lacasa"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk="mypass"
pairwise=TKIP
group=TKIP

Then when I run the command "sudo wpa_supplicant -w -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd" I get the following output:


Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ap_scan=1
ctrl_interface='/var/run/wpa_supplicant'
Line: 4 - start of a new network block
ssid - hexdump_ascii(len=6):
6c 61 63 61 73 61 lacasa
scan_ssid=0 (0x0)
proto: 0x1
key_mgmt: 0x2
PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED]
pairwise: 0x8
group: 0x8
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='lacasa'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=22 WE(source)=18 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1c:26:66:94:20
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Added interface wlan0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 4093 bytes of scan results (17 BSSes)
Scan results: 17
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:1e:e5:67:09:19 ssid='lacasa' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
selected based on WPA IE
selected WPA AP 00:1e:e5:67:09:19 ssid='lacasa'
Try to find non-WPA AP
Trying to associate with 00:1e:e5:67:09:19 (SSID='lacasa' freq=2462 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=14
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c07 len=56
AssocReq IE wireless event - hexdump(len=48): 00 06 6c 61 63 61 73 61 01 08 02 04 0b 16 0c 18 30 48 32 04 12 24 60 6c dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c08 len=24
AssocResp IE wireless event - hexdump(len=16): 01 08 82 84 8b 96 0c 18 30 48 32 04 12 24 60 6c
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:1e:e5:67:09:19
Association info event
req_ies - hexdump(len=48): 00 06 6c 61 63 61 73 61 01 08 02 04 0b 16 0c 18 30 48 32 04 12 24 60 6c dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
resp_ies - hexdump(len=16): 01 08 82 84 8b 96 0c 18 30 48 32 04 12 24 60 6c
WPA: set own WPA/RSN IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated with 00:00:00:00:00:00
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
Added BSSID 00:1e:e5:67:09:19 into blacklist
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
State: ASSOCIATED -> DISCONNECTED

After this it goes on trying to connect a few times more failing.

Can anyone explain what I am doing / is going wrong?
I also tried the ndsiwrapper for -D.

Thank you for your time.

[Tom--d]

Hello,

I have been using the manual configuration to get a conenction.
This is my rc.local

ifconfig wlan0 up
dhclient -r wlan0
iwconfig wlan0 mode Managed essid "onone" key 443c6a1426 open
dhclient wlan0

Network manager does not work, nor does wicd.
This is due to my wireless card being its self. The only way i can make an connection is by iwconfig key open . its the open which makes the conenction. Network manager just loops around.

But the thing is,
If I have a period of inactivity. maybe 10 mins..
It drops the connection. And I cannot reconnect. even by running the commands again. No connection.
I have to restart to connect.


Please help me here. I really need help!

[kevdog]

You need closing brackets in your config file:

ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="lacasa"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk="mypass"
pairwise=TKIP
group=TKIP
}

Notice the last closing bracket which you didnt post.

[nomaddog]

I recently installed Ubuntu 8.04 with Wubi and I've been trying to get my wireless connection, but have been unsuccessful. I followed the step-by-step guide, but alas, no connection. Here is some info about my settings. Please let me know what I'm missing. Thanks in advance.

james@james-laptop:~$ sudo ifconfig wlan0 down
james@james-laptop:~$ sudo dhclient -r wlan0
There is already a pid file /var/run/dhclient.pid with pid 6296
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1a:73:1e:38:f7
Sending on LPF/wlan0/00:1a:73:1e:38:f7
Sending on Socket/fallback
james@james-laptop:~$ sudo ifconfig wlan0 up
james@james-laptop:~$ sudo iwconfig wlan0 essid "Rubis"
james@james-laptop:~$ sudo iwconfig wlan0 key MY_WEP_KEY
james@james-laptop:~$ sudo iwconfig wlan0 mode Managed
james@james-laptop:~$ sudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1a:73:1e:38:f7
Sending on LPF/wlan0/00:1a:73:1e:38:f7
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

james@james-laptop:~$ lshw -C network
WARNING: you should run this program as super-user.
*-network DISABLED
description: Ethernet interface
product: 88E8038 PCI-E Fast Ethernet Controller
vendor: Marvell Technology Group Ltd.
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 14
serial: 00:e0:b8:bb:22:87
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=sky2 driverversion=1.20 firmware=N/A latency=0 module=sky2 multicast=yes
*-network
description: Wireless interface
product: BCM94311MCG wlan mini-PCI
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:05:00.0
logical name: wlan0
version: 01
serial: 00:1a:73:1e:38:f7
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.52+Broadcom,10/12/2006, 4.100. latency=0 module=ndiswrapper multicast=yes wireless=IEEE 802.11

james@james-laptop:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:13:10:E9:CA:96
ESSID:"linksys_SES_57009"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:3/100 Signal level:-94 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:13:10:0E:E4:93
ESSID:"Rubis"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:62/100 Signal level:-56 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 03 - Address: 00:18:3F:22:B5:79
ESSID:"2WIRE455"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:29/100 Signal level:-77 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0

james@james-laptop:~$ ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:224 errors:0 dropped:0 overruns:0 frame:0
TX packets:224 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:11504 (11.2 KB) TX bytes:11504 (11.2 KB)

wlan0 Link encap:Ethernet HWaddr 00:1a:73:1e:38:f7
inet6 addr: fe80::21a:73ff:fe1e:38f7/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:3 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1240 (1.2 KB) TX bytes:2288 (2.2 KB)
Interrupt:17 Memory:c0300000-c0304000

wlan0:avahi Link encap:Ethernet HWaddr 00:1a:73:1e:38:f7
inet addr:169.254.7.14 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:17 Memory:c0300000-c0304000

[kevdog]

Hmm try with unencrypted first -- always do a stepwise confirmation to prove the driver is working before adding security measures.

[nomaddog]

Ok, I followed the unencrypted how-to and still nothing. Here's the results of the step by step.

james@james-laptop:~$ sudo ifconfig wlan0 down
james@james-laptop:~$ sudo dhclient -r wlan0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1a:73:1e:38:f7
Sending on LPF/wlan0/00:1a:73:1e:38:f7
Sending on Socket/fallback
james@james-laptop:~$ sudo ifconfig wlan0 up
james@james-laptop:~$ sudo iwconfig wlan0 essid "Rubis"
james@james-laptop:~$ sudo iwconfig wlan0 mode Managed
james@james-laptop:~$ sudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1a:73:1e:38:f7
Sending on LPF/wlan0/00:1a:73:1e:38:f7
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

[bohuroopee]

Hello,

I have recently bought a Dell M1330 with Ubuntu 7.10. I am having an issue with the wireless connection. During boot it gets stuck at a place, while the wifi light keeps blinking on and off. After around a minute of this the boot continues but the wifi light keeps blinking with no internet connection. I have to run

sudo /etc/init.d/networking restart

to get the internet connection working. Although it works, but it is a bit irritating. Is there anything I can do to avoid this boot problem.

Thanks.

[kevdog]

noma

What driver/card/chipset are you using? Also router type.

[nomaddog]

Driver being used is Ndiswrapper+bcmwl5. Card is a Broadcom BCM94311MCG wlan mini-PCI. Router is a Linksys WRT54G v2.2. I hope I didn't muck something up by ndiswrapper. I was following another how-to on getting this specific card to work.

[kevdog]

everything seems right on the surface -- there are a few bcmwl5 drivers -- did you consult the link by jamie jackson (do a search) he lists a bunch of drivers for certain chipset types. I just want to confirm you have the correct driver installed. Also check dmesg to see if there is any errors listed pertaining to your wireless driver.

[nomaddog]

Thanks for all the help. I had first used someone else's how-to instead of Jamie's. I went through Jamie's how-to step by step, got everything set up and am now enjoying wireless connection. I appreciate the guidance! Rock on! :guitar:

[sputnikkk]

Is there a WPA2 guide or set of instructions?


WPA-PSK with Ra Based Chipsets

Ra cards do not require the wpa_supplicant package to use WPA. Here is how to connect from the command line with these cards:
References: http://ubuntuforums.org/showthread.p...=serial+monkey, http://rt2x00.serialmonkey.com/wiki/...owto#Using_WPA

WPA-PSK(1)
Code:

sudo ifconfig <interface> down
sudo dhclient -r <interface>
sudo ifconfig <interface> up
sudo iwconfig <inteface> essid "ESSID_IN_QUOTES"
sudo iwpriv <interface> set AuthMode=WPAPSK
sudo iwpriv <interface> set EncrypType=TKIP
sudo iwpriv <interface> set WPAPSK="YOUR_WPA_PSK_KEY"
sudo dhclient <interface>

For WPA-PSK(2), I have no working configuration yet. If someone would like to help me refine these instructions for WPA2 with Ra-based chipsets, I would appreciate your help!

[kevdog]

Just want to confirm that are you sure you have an ra chipset? This would be with the lshw -C network
output.


Lastly I think (but can not confirm) that these may be the settings:


sudo ifconfig <interface> down
sudo dhclient -r <interface>
sudo ifconfig <interface> up
sudo iwconfig <inteface> essid "ESSID_IN_QUOTES"
sudo iwpriv <interface> set AuthMode=WPA2PSK
sudo iwpriv <interface> set EncrypType=AES
sudo iwpriv <interface> set WPAPSK="YOUR_WPA_PSK_KEY"
sudo dhclient <interface>


You are going to have to confirm the cipher type on your router. If you are using TKIP the EncrypType=TKIP, if you are using AES, EncrypType=AES. AES is more efficient than TKIP and supposedly theoretically a better algorithm in terms of security, however I have never read anything about TKIP practically being broken.

I'll definitely add this to the guide if you get it up and running!! :)

[maxxjr]

My apologies in advanced if this has already been covered...I went through a couple dozen pages of this thread, and did not see anything directly related to my issue.

I am running Xubuntu/Hardy Heron. I have no issue connecting through the GUI with DHCP. However, my goal is a static IP that starts at boot. Using the guide on the first page of this thread, I was able to get what I needed to do from command line using ifconfig/iwconfig, etc. But when I put it into rc.local, it does not connect for me...but when I then login, the GUI connection has no problem starting.

I am guessing that something coming after rc.local is trampling over the settings.

Anyway, the wireless card is orinoco_cs, and the following is my rc.local. This script does work after I have logged into the GUI.

Through the GUI, I have the wireless network configured as SHARED KEY Authentication

ifconfig eth1 down
dhclient -r eth1
ifconfig eth1 192.168.2.129 netmask 255.255.255.0 up
route add default gw 192.168.2.1
iwconfig eth1 essid "SSID"
iwconfig eth1 key MYKEY
#iwconfig eth1 key open
iwconfig eth1 mode Managed
#dhclient eth1
exit 0

Any advice on how to track down my issue here is greatly appreciated.

[sputnikkk]

Thanks Kev ...

Here's the output to confirm for ya.



*-network
description: Wireless interface
product: RT2500 802.11g Cardbus/mini-PCI
vendor: RaLink
physical id: d
bus info: pci@0000:02:0d.0
logical name: wmaster0
version: 01
serial: 00:12:17:86:53:6b
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=rt2500pci ip=192.168.1.18 latency=32 module=rt2500pci multicast=yes wireless=IEEE 802.11g


Im using a static IP setup as well ... what changes need to be made there as well?

I have this working with NetworkManager currently - but I have to re do the settings in NetworkManager after every reboot. It changes the settings to WPA and borks the passkey info???

My Linksys wireless router WRT310N has an option for AES or TKIP or both under the WPA2 settings. "WPA Personal" setting on the router requires me to choose either AES or TKIP. I'll :guitar: the AES and see how we roll with that.

Do you have the syntax Id need to make sure these settings persist thru reboots? This is a desktop rig for one of the kids - I dont want them in the ip and security settings

TIA,

Steve - aka Sputnikkk

[kevdog]

Let me know if you can connect using dhcp with the rt2500pci driver with wpa2. As far as setting a static ip, and allowing it to boot on startup --- that's a no brainer and very easy to set up. Setting these up at startup can either be made through adding the correct commands to the /etc/rc.local file or through just making a startup script (which is really very easy), adding it to the init.d folder and then adding the script to the appropriate run levels (which is a one line command -- so don't get hung up on this if it seems intimidating).

Keep taking baby steps and not big leaps. I'm definitely in uncharted waters with ra and wpa2.

[kevdog]

I don't know what this means:

Through the GUI, I have the wireless network configured as SHARED KEY Authentication


Are you using WEP (seems like it)? Is your router set to OPEN or SHARED key?

[sputnikkk]

Many thanks again.

Im going to try this ... your thoughts? I pieced this together from the main How To.

Just to confirm, I need to use the wlan0 alias/logical name for my <interface> and not the wmaster0 - correct?


sudo ifconfig wlan0 down
sudo dhclient -r wlan0 <--- [why? whats this doing?]
sudo ifconfig wlan0 192.168.1.18 netmask 255.255.255.0 up
sudo route add default gw 192.168.1.2
sudo ifconfig wlan0 up
sudo iwconfig wlan0 essid "ESSID_IN_QUOTES"
sudo iwpriv wlan0 set AuthMode=WPA2PSK
sudo iwpriv wlan0 set EncrypType=AES
sudo iwpriv wlan0 set WPAPSK="YOUR_WPA_PSK_KEY"

Do I need to have these 2 following items in this sequence of commands as well, and what do they do? They were in the main how to ...



sudo dhclient <interface>
sudo iwconfig <interface> mode Managed

PS - trying this all in DHCP mode first means the machine Im on right now - Win2k, and the rest of the LAN needs to be reconfigured for DHCP in Windows on 2 servers and 2 other desktops. For the time being static ip seems the smaller baby step for me ... no?

Your help is much appreciated!

Sputnikk

[sputnikkk]

@ maxxjr


Any advice on how to track down my issue here is greatly appreciated.

I cannot locate it at this time, but Im pretty confident I read in one of the current forums How To's, that if you are going to go for Static IP and set it to connect from the command line and at every boot from the rc.local file, it is either recommended or mandatory to REMOVE the NetworkManager GUI from your system. Thats whats trampling your setup.

PLEASE PLEASE PLEASE double check that info via searching on these forums. If I locate that for you, I will post it up and the link ASAP.

EDIT: Found It ...

http://ubuntuforums.org/showthread.php?t=571188


***Spaceboy909 has also reported that when using this technique with static IP addresses, network manager has to be uninstalled because it keeps trying to reset the connection. In order to uninstall networkmanager:

In Ubuntu:
Code:

sudo aptitude uninstall network-manager-gnome

In Kbuntu:
Code:

sudo aptitude uninstall knetworkmanager

__________________________________________________ _________

[sputnikkk]

RutilT vs. NetworkManager?

[sputnikkk]

Ok So I gave this a go ...


sudo ifconfig wlan0 down
sudo ifconfig wlan0 192.168.1.18 netmask 255.255.255.0 up
sudo route add default gw 192.168.1.2
sudo ifconfig wlan0 up
sudo iwconfig wlan0 essid "myESSID"
sudo iwpriv wlan0 set AuthMode=WPA2PSK
sudo iwpriv wlan0 set EncrypType=AES
sudo iwpriv wlan0 set WPAPSK="myPasskey"
sudo iwconfig wlan0 mode Managed

First problem ...

sudo : unable to resolve host myKid-desktop

then

sudo iwpriv wlan0 set EncrypType=AES
sudo: unable to resolve host


wlan0 no private ioctls.

sudo iwpriv wlan0 set WPAPSK="myPasskey"
sudo: unable to resolve host


wlan0 no private ioctls.

Went into Network Manager and reset all the usual suspects info - connected again to the router.

So now what shall I do?

[kevdog]

Please post exactly what you are typing and the results of iwlist scan.

[sputnikkk]

I pasted this in a terminal window at the command line.


sudo ifconfig wlan0 down
sudo ifconfig wlan0 192.168.1.18 netmask 255.255.255.0 up
sudo route add default gw 192.168.1.2
sudo ifconfig wlan0 up
sudo iwconfig wlan0 essid "myESSID"
sudo iwpriv wlan0 set AuthMode=WPA2PSK
sudo iwpriv wlan0 set EncrypType=AES
sudo iwpriv wlan0 set WPAPSK="myPasskey"
sudo iwconfig wlan0 mode Managed

I also opened up the file to add my ISP's nameserver, and they were alreayd in there along with the windows DOMAIN name, not that it is related to these other issues - just FYI


results of iwlist scan [machine is currently on the LAN and out to the internet]



lo Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 No scan results

[kevdog]

Ok, Im seeing some problems already -- your network card can not even see any available networks (iwlist scan results), and this can't be possibly what your are typing:

sudo iwconfig wlan0 essid "myESSID"

Your ESSID name is "myESSID"???

[sputnikkk]

Sorry ... didnt realize my EXACT essid being posted was critical to a resolution, my BAD. Im not sure the EXACT passkey is wise but I guess I can change that later ...

sudo ifconfig wlan0 down
sudo ifconfig wlan0 192.168.1.18 netmask 255.255.255.0 up
sudo route add default gw 192.168.1.2
sudo ifconfig wlan0 up
sudo iwconfig wlan0 essid "Sputnikkk"
sudo iwpriv wlan0 set AuthMode=WPA2PSK
sudo iwpriv wlan0 set EncrypType=AES
sudo iwpriv wlan0 set WPAPSK="*******"
sudo iwconfig wlan0 mode Managed

[kevdog]

Ok, I don't need your password, but the problem is wlan0 can not scan for any available networks. iwlist scan doesnt detect available networks, so how are you going to connect to your router? Is your ESSID possibly hidden?

[sputnikkk]

I really appreciate trying to get me thru this!


At the router

SSID Broadcast = enabled

and perhaps this helps too ...


*-network
description: Wireless interface
product: RT2500 802.11g Cardbus/mini-PCI
vendor: RaLink
physical id: d
bus info: pci@0000:02:0d.0
logical name: wmaster0
version: 01
serial: 00:12:17:86:53:6b
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=rt2500pci ip=192.168.1.18 latency=32 module=rt2500pci multicast=yes wireless=IEEE 802.11g




wmaster0 Interface doesn't support scanning.

Since wmaster0 = wlan0 - does this card not support SCANNING?
Is that possible?

Im at a total loss as - this card will connect using WPA2 / WPA1 / WEP via the NetworkManager setup. I just need that app to maintain the settings and connection thru a reboot/start.

[kevdog]

What does ifconfig show? Please post ifconfig when you are connected with NWM and when you are not.

[sputnikkk]

Connected


lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2195 errors:0 dropped:0 overruns:0 frame:0
TX packets:2195 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:131938 (128.8 KB) TX bytes:131938 (128.8 KB)

wlan0 Link encap:Ethernet HWaddr 00:12:17:86:53:6b
inet addr:192.168.1.18 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::212:17ff:fe86:536b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:465103 errors:0 dropped:0 overruns:0 frame:0
TX packets:441081 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:34319407 (32.7 MB) TX bytes:51698492 (49.3 MB)

wmaster0 Link encap:UNSPEC HWaddr 00-12-17-86-53-6B-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


Not Connected


cierra@cc-desktop:~$ ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2234 errors:0 dropped:0 overruns:0 frame:0
TX packets:2234 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:142858 (139.5 KB) TX bytes:142858 (139.5 KB)

wlan0 Link encap:Ethernet HWaddr 00:12:17:86:53:6b
inet addr:192.168.1.18 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:472035 errors:0 dropped:0 overruns:0 frame:0
TX packets:446628 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:34828492 (33.2 MB) TX bytes:53117379 (50.6 MB)

wmaster0 Link encap:UNSPEC HWaddr 00-12-17-86-53-6B-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


Here's when I try to do the manual command line connection ... note Im now trying it with just WPA Personal


cierra@cc-desktop:~$ sudo ifconfig wlan0 down
sudo: unable to resolve host cc-desktop
[sudo] password for cierra:
cierra@cc-desktop:~$
cierra@cc-desktop:~$ sudo ifconfig wlan0 down
sudo: unable to resolve host cc-desktop
cierra@cc-desktop:~$ sudo ifconfig wlan0 192.168.1.18 netmask 255.255.255.0 up
sudo: unable to resolve host cc-desktop
cierra@cc-desktop:~$ sudo route add default gw 192.168.1.2
sudo: unable to resolve host cc-desktop
cierra@cc-desktop:~$ sudo ifconfig wlan0 up
sudo: unable to resolve host cc-desktop
cierra@cc-desktop:~$ sudo iwconfig wlan0 essid "Sputnikkk"
sudo: unable to resolve host cc-desktop
cierra@cc-desktop:~$ sudo iwpriv wlan0 set AuthMode=WPAPSK
sudo: unable to resolve host cc-desktop
wlan0 no private ioctls.

cierra@cc-desktop:~$ sudo iwpriv wlan0 set EncrypType=AES
sudo: unable to resolve host cc-desktop
wlan0 no private ioctls.

cierra@cc-desktop:~$ sudo iwpriv wlan0 set WPAPSK="********"
sudo: unable to resolve host cc-desktop
wlan0 no private ioctls.

cierra@cc-desktop:~$ sudo iwconfig wlan0 mode Managed

sudo: unable to resolve host cc-desktop

[kevdog]

Can you fix this problem first:

sudo: unable to resolve host cc-desktop

Is that the name of your computer -- its seem like there is a problem with this?

Seems like iwpriv statements dont work with your driver either -- that is strange. Have you tried the wpa_supplicant.conf method as configured in the original post? I would try for wpa(1) first.

[sputnikkk]

sudo: unable to resolve host cc-desktop

That is the name of the desktop - is that an illegal name? Can I change it without fornicating the system like it would on a windows install :-)

Seems to happen when the networking adapter goes DOWN, and then the system can longer connect to the LAN or network effectively. In fact when the networking isnt operable on this box - EVERYTHING either fails or takes for ever to WORK/Launch.

I think Im going to throw in the towel on this Adapter and just go get one that works ... well this one works, just not after a reboot! I would have bought a new one sooner but it really appears this is a software issue [drivers/NetworkMisManager] more than hardware. I wanted to get a newer Linksys card but suspect it too will have either broadcom or RaLink chipset issues.

Thought RaLink drivers/chipsets didnt require the wpa_supplicant.conf method?

[sputnikkk]

using the command iwlist scanning results in this



cierra@cc-desktop:~$ iwlist scanning
lo Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1E:E5:4E:A9:A1
ESSID:"Sputnikkk"
Mode:Master
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=52/100 Signal level=-47 dBm
Encryption key:on
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=000000000290ac15

[kevdog]

Im glad to see your network showing up.

Just the low down. Ra chipsets are a pain. To prove this point there are many options to get these cards working. Just think about it for a minute -- if there are so many options it usually just means that no one option is great and works for everyone.

Ra chipsets I believe sometime in Gutsy or possibly with Hardy moved to using the r2x00 driver rather than the old style rt2500 or rtxx drivers. It seems like you are using the older style chipset. Ra (the company itself) offers legacy drivers, but so does the open source serial monkey project. Beginning with Hardy specifically it began to offer the r2x00 driver, however this assumed some options (the ieee, and mac modules) to be compiled into the kernel natively to support wpa. I'm not sure if these modules are contained in the default Hardy installation, and if they are, if they actually work. I don't get a lot of feedback - - and I don't own an Ra card. With the newer style modules, the iwpriv statements have become obsolete.

To complicate things further, beyond the legacy/serial monkey/rt2x00 drivers, ndiswrapper is yet another option.

I can't tell you what option is best for you. I am very shaky on the status of the ra drivers contained within the hardy kernel. Its hard to filter the noise in the forums (help stuff doesn't work, etc) from actual solutions. Oftentimes driver/chipset combinations work, its just the fault of the individual operator that cant configure the combination appropriately. In other cases -- there is really a conflict. I was at the pinnacle of my knowledge with the feisty release, however with the rt2x00 transition things became very complicated and without a card to test, I quickly became very confused on what options would work, and what options would not. Throw in a buggy network manager on top of the equation and it further convulutes the situation.

My best advice for you at this point would be to either be patient and try a lot of the different options (you will actually learn a lot during this process and it would be beneficial in the long run if you are interested in learning how things work with the linux kernel), settle for what you have, go with ndiswrapper, or just get another wireless adapter (specifically I would recommend an atheros based chipset that is compatible with madwifi drivers). There is no right or wrong answer here, just how much time you want to spend learning a solution, and potentially how much money you can spend on various wireless adapters.

[sputnikkk]

Thanks Kev ...

Well Im just not sure what to do at this point.

Frankly, looking thru the forums one will see the same issues across a broad spectrum of wireless nics/users. This doesnt AT ALL seem to be RaLink specific - but yet I see they do add add'l problems to the mix.

The troubling thing to me as a newb - was all the banter about SCURITY over windows networking. Apparently they didnt really mean WIRELESS ? Seems like all the work-arounds - I cant really bring myself to call them solutions yet ... revolve around either a hack or decreased security or NO Security.

It might work with DHCP
Doesnt work or isnt been known to work with static ip
Cant enable WAP / WEP or WAP2
Requires windows software to actually run - :lolflag:

Probably one of the most end user popular brands of wireless nics cannot be effectively used in Linux without either installing windows drivers, or foregoing security and static ip addressing schemes ... and the problem has been known and ongoing for over a year? [ scratches head ]

Why cant the NetworkManager retain my working settings thru a REBOOT?

Kev ... I really want to thank you for your help and assistance and time. I think I have to throw in the towel on this card and try and find another linksys model that has a KNOWN working solution.

Good luck to all ... and many Thanks!

[Yigido]

Hi,
I have to connect to a wpa(2?) protected AP without network manager too.
My System: Hardy Heron (updatet from 7.10)
AthlonXP 1800+, WLAN-USB-Stick: Edmiax EW-7318USg with RT73 serialmonkey drivers
The are two types of AP's i could use(both from Campus), one is without any encryption (in this case vpn tunneling is needed). I can use it via following:


sudo ifconfig wlan3 up
sudo iwconfig wlan3 essid mops
sudo iwconfig wlan3 key "off"
sudo dhclient wlan3
sudo vpnc-connect /etc/vpnc/vpnc.conf
but the problem with mops its slower than the other one, will not be offered in near future. (and is not recommended if not necessary)

The other AP is the famous Eduroam. The ESSIDs I can receive here are "eduroam-ttls-pap" and "eduroam-peap-mschapv2"

"eduroam-peap-mschapv2" is working well in Windows with my Edimax WLAN USB Stick. But wpa_supplicant here cannot.

it replies:

aak@k7:~$ sudo wpa_supplicant -c/etc/wpa_supplicant.conf -iwlan3 -Dwext
[sudo] password for aak:
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported

What am i doing wrong? If you need more details i'll reply them as soon as i know what.

Thanks in advance
Yigi

[kevdog]

Can you post your wpa_supplicant.conf file?

[kevdog]

sputnikk

Have you just tried manually adding your commands to the /etc/network/interfaces file as per the sticky thread written by Weiman?

[Yigido]

hi,


Can you post your wpa_supplicant.conf file?

yeah

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
network={
ssid="eduroam-ttls-pap"
proto=WPA2
key_mgmt=WPA-EAP
eap=TTLS
anonymous_identity="anonymous@rwth-aachen.de"
identity="*******@rwth-aachen.de"
password="*******"
ca_cert="/etc/ssl/certs/eduroam-chain.pem"
phase2="auth=PAP"
}

[sputnikkk]

Kevdog,

wienmans guide #1 ...


HOWTO: RT2500, etc. wireless cards
Dapper Drake users should take a look at this thread if this one doesn't work. This guide was tested with Feisty Fawn, Gutsy Gibbon, and Hardy Heron.
--
To all RT73 users, please also see this post. Thanks to Kiefer Rodriguez for this solution.

Please post to this Launchpad bug report with all of your specs, if you have problems with a Ralink based wireless adapter.

This is a simple guide for all Ralink based wireless adapters and everyone who wants to replace the Linux driver with "ndiswrapper" (e.g. because you want to make use of either Network Manager or WICD).

The drivers I have are actually WORKING. They network and do what they are supposed to DO. Linux/Ubuntu as an OS doesnt appear to be doing what it should. I dont want to add another piece of software around a Windows driver ... if I can avoid it - seems like a hack. Id rather just go buy a new card that doesnt require that. Maybe Im wrong but NetworkManager is whats really BROKEN [as I see it].


Wienmans guide # 2 ... still caveats apply. How to do it - except if you use RaLink chipsets :-) [such is my luck]


HOWTO: Wireless Security - WPA1, WPA2, LEAP, etc.
This guide was tested with Dapper Drake, Feisty Fawn, Gutsy Gibbon, and Hardy Heron.
--
Since it appears that very few people take wireless security seriously, I'd like to come up with my first HOWTO and explain how I was able to configure a secure home network using WPA2, the latest encryption & authentication standard. There are also other types of configuration (WPA1, mixed mode, LEAP, PEAP, DHCP, etc.) shown in the appendix. Feedback is much appreciated.

Common stumbling blocks - Make sure that:
1. Ethernet cable is unplugged.
2. No firewall & configuration tool is running (e.g. Firestarter).
3. MAC filtering is disabled.
4. NetworkManager, Wifi-Radar & similar wireless configuration tools are disabled/turned off and not in use.
5. Some cards/drivers (e.g. Madwifi) do not support WPA2 (AES). Try WPA1 (TKIP) if WPA2 secured connections fail.
6. RTxxx (Ralink) drivers do not support this approach. Either install "ndiswrapper" replacing Serialmonkey's driver or visit this site.
7. Turn off "roaming" if you repeatedly fail to establish a connection.

[sputnikkk]

SOLVED ...

Heard it mentioned before but didnt have a clue what it was - Wicd - read a post that it worked for them with Linksys stuff

http://wicd.net/

Gave it a try and it ... JUST Worked!!! [the way it should be]

[kevdog]

Go into wicd, and see what they have listed in their profile for ra cards with wpa2. This will tell you the exact options they are using to connect -- you may be surprised since they are probably very similar to what you were attempting to use.

[wwastro]

Hi kevdog,

Your thread has been a great help in getting my wireless working with Gutsy (on a Dell Inspiron 6400 laptop, with Intel wireless card PRO/Wireless 3945ABG/BG), as Network Manager failed to work for me.

However on upgrading to Hardy, the wireless now fails to work. The problems I am getting seem to echo those of others who have responded to your thread. In particular reply #559 by drpaul is the closest I have seen so far. I am now connected by ethernet (on eth0), and the diagnostic messages I get are as follows:

In response to sudo lshw -C network:

*-network
description: Wireless interface
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0b:00.0
logical name: wmaster0
version: 02
serial: 00:18:de:94:65:62
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl3945 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11g
*-network
description: Ethernet interface
product: BCM4401-B0 100Base-TX
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: eth0
version: 02
serial: 00:15:c5:bd:3e:2f
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=b44 driverversion=2.0 duplex=full ip=192.168.1.3 latency=64 link=yes module=ssb multicast=yes port=twisted pair speed=100MB/s

- note that the correct MAC address appears in connection with the w/less interface, but it is now labelled wmaster0 rather than the previous eth1, and the old driver ipw3945 is now replaced by iwl3945.

The response to ifconfig is:

eth0 Link encap:Ethernet HWaddr 00:15:c5:bd:3e:2f
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:942 errors:0 dropped:0 overruns:0 frame:0
TX packets:795 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1128059 (1.0 MB) TX bytes:111504 (108.8 KB)
Interrupt:22

eth1 Link encap:Ethernet HWaddr 00:18:de:94:65:62
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:1080 (1.0 KB)

eth1:avahi Link encap:Ethernet HWaddr 00:18:de:94:65:62
inet addr:169.254.7.15 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:36 errors:0 dropped:0 overruns:0 frame:0
TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2340 (2.2 KB) TX bytes:2340 (2.2 KB)

wmaster0 Link encap:UNSPEC HWaddr 00-18-DE-94-65-62-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

and the reponse to iwconfig is

lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

eth1 IEEE 802.11g ESSID:"NETGEAR" Nickname:""
Mode:Managed Frequency:2.462 GHz Access Point: 00:14:6C:D3:B3:6E
Bit Rate=54 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Power Management:off
Link Quality=96/100 Signal level=-29 dBm Noise level=-50 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Perhaps you could be kind enough to guide me through this problem, as I am sure you have done this with others, but I cannot see your answers to them.

Many thanks.

[kevdog]

Can you describe your problem more specifically possibly with some error messages? By your output your wireless interface is definitely eth1 -- its a virtual interface for the physical device known as wifi0 or your wireless card. To configure the card you need to pipe commands through eth1 (the virtual interface) and not through wifi0 the actual interface. I know its weird, but it just works that way.

[wwastro]

Can you describe your problem more specifically possibly with some error messages? By your output your wireless interface is definitely eth1 -- its a virtual interface for the physical device known as wifi0 or your wireless card. To configure the card you need to pipe commands through eth1 (the virtual interface) and not through wifi0 the actual interface. I know its weird, but it just works that way.

Looking at the output from lshw -C network, it seems the system now thinks that the wireless interface is wmaster0 (with the correct MAC address 00:18:de:94:65:62, since eth1 used this address when the wireless was working in Gutsy), which I understand from your original post cannot be cited directly in setup commands. Thus from your latest comments, I guess I need to "pipe commands through eth1", but I'm not sure how to do this; my setup sequence of commands refers only to eth1. Presumably, then, I need somehow to tell the system to associate eth1 with wmaster0. How can this be done? Setting up aliases? (how is this done?)

As for actual errors, the information I have is:

- The wireless light does not come on at all;
- The message from the setup process "wmaster0: unknown hardware address type 801" [although this also appeared when I (successfully) set up the present ethernet connection];
- The connection failure messages "No DHCPOFFERS received.
No working leases in persistent database - sleeping."
- No internet connection.

Please also note that I have just tried the command

dmesg | more

and the (very lengthy) output contained the following lines, which may well be relevant to the problem:

[ 25.880345] iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels
[ 25.880754] wmaster0: Selected rate control algorithm 'iwl-3945-rs'
[ 27.953244] udev: renamed network interface wlan0 to eth1
[ 26.191242] lp: driver loaded but no devices found

and a bit further down:

[ 30.569637] eth1: Initial auth_alg=0
[ 30.569643] eth1: authenticate with AP 00:14:6c:d3:b3:6e
[ 30.570979] eth1: RX authentication from 00:14:6c:d3:b3:6e (alg=0 transaction
=2 status=0)
[ 30.570982] eth1: authenticated
[ 30.570984] eth1: associate with AP 00:14:6c:d3:b3:6e
[ 28.682971] eth1: RX AssocResp from 00:14:6c:d3:b3:6e (capab=0x411 status=0 a
id=1)
[ 28.682975] eth1: associated

- this suggests to me that (1) there now exists an interface wlan0, which I did not know existed on this system, and (2) I am ending up with eth1 being associated with the wrong MAC address (and hence the wrong device).

I hope that makes things a bit clearer! Thanks for your attention. Please let me know if I can pass on any other diagnostic info.

[kevdog]

Can you post

ifconfig

iwlist scan

Thanks

[daparker1710]

Great guide. Thanks.

[daparker1710]

Kevdog,

With the help of your manual I was able (one time) to connect wirelessly using static ip procedure with WEP key step added. I tried it again today and failed.

I've include my terminal session in hopes you can identify my problem. First a little background.

Eth0, if plugged in, comes up connected at boot. If I take it down I can not restore the connection.

I'm trying to switch to wireless connection using dynamic ip assignment. I have been unable to make this happen.

As mentioned above I did get wireless connection with static ip one time only.

I hope you can help. Thanks for trying.

Here's the terminal session:

user@ubuntu:~$ sudo ifconfig
eth0 Link encap:Ethernet HWaddr 00:e0:29:0d:5b:43
inet6 addr: fe80::2e0:29ff:fe0d:5b43/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:113 dropped:0 overruns:0 carrier:113
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:11 Base address:0xac00

eth0:avahi Link encap:Ethernet HWaddr 00:e0:29:0d:5b:43
inet addr:169.254.4.21 Bcast:169.254.255.255

Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1
Interrupt:11 Base address:0xac00

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:602 errors:0 dropped:0 overruns:0 frame:0
TX packets:602 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:30468 (29.7 KB) TX bytes:30468 (29.7 KB)

wlan0 Link encap:Ethernet HWaddr 00:90:47:06:e9:3e
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

user@ubuntu:~$ sudo ifconfig eth0 down
user@ubuntu:~$ sudo ifconfig wlan0 down
user@ubuntu:~$ sudo dhclient -r wlan0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:90:47:06:e9:3e
Sending on LPF/wlan0/00:90:47:06:e9:3e
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.0.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast

address.
user@ubuntu:~$ sudo ifconfig w.an0 up
w.an0: ERROR while getting interface flags: No such device
user@ubuntu:~$ sudo ifconfig wlan0 up
user@ubuntu:~$ sudo ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:602 errors:0 dropped:0 overruns:0 frame:0
TX packets:602 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:30468 (29.7 KB) TX bytes:30468 (29.7 KB)

wlan0 Link encap:Ethernet HWaddr 00:90:47:06:e9:3e
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

user@ubuntu:~$ sudo iwconfig wlan0 essid "NETGEAR"
user@ubuntu:~$ sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:16:B6:58:DE:09
ESSID:"the4cs"
Mode:Master
Channel:6
Bit Rates:1 Mb/s
Bit Rates:2 Mb/s
Bit Rates:5.5 Mb/s
Bit Rates:11 Mb/s
Bit Rates:6 Mb/s
Bit Rates:12 Mb/s
Bit Rates:24 Mb/s
Bit Rates:36 Mb/s
Encryption key:on
Quality=7/128 Signal level=-97 dBm Noise

level=-97 dBm
Cell 02 - Address: 00:09:5B:AA:66:0E
ESSID:"NETGEAR"
Mode:Master
Channel:7
Bit Rates:1 Mb/s
Bit Rates:2 Mb/s
Bit Rates:5.5 Mb/s
Bit Rates:11 Mb/s
Encryption key:on
Quality=76/128 Signal level=-70 dBm Noise

level=-97 dBm

user@ubuntu:~$ sudo iwconfig wlan0 key c2a1d1897b
user@ubuntu:~$ sudo iwconfig wlan0 mode Managed
user@ubuntu:~$ sudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid

134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:90:47:06:e9:3e
Sending on LPF/wlan0/00:90:47:06:e9:3e
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
user@ubuntu:~$ sudo ifconfig wlan0 down
user@ubuntu:~$ sudo dhclient -r wlan0
There is already a pid file /var/run/dhclient.pid with pid 5397
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:90:47:06:e9:3e
Sending on LPF/wlan0/00:90:47:06:e9:3e
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.0.1 port 67
user@ubuntu:~$ sudo ifconfig wlan0 192.168.0.4 netmask

255.255.255.0 up
user@ubuntu:~$ sudo route add default gw 192.168.0.1
user@ubuntu:~$ sudo iwconfig wlan0 essid "NETGEAR"
user@ubuntu:~$ sudo iwconfig wlan0 key c2a1d1897b
user@ubuntu:~$ sudo iwconfig wlan0 mode Managed
user@ubuntu:~$ sudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid

134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:90:47:06:e9:3e
Sending on LPF/wlan0/00:90:47:06:e9:3e
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
user@ubuntu:~$ sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:09:5B:AA:66:0E
ESSID:"NETGEAR"
Mode:Master
Channel:7
Bit Rates:1 Mb/s
Bit Rates:2 Mb/s
Bit Rates:5.5 Mb/s
Bit Rates:11 Mb/s
Encryption key:on
Quality=77/128 Signal level=-69 dBm Noise

level=-97 dBm

user@ubuntu:~$

[kevdog]

It looks like you are doing things right -- can you just tell me all the commands you are typing (without the output).

[daparker1710]

Here are a few command sequences with no output and purely information requests excluded. I also threw in some eth0 sequences that don't work as I expected.

*** try for dynamic ip
sudo ifconfig wlan0 down
sudo dhclient -r wlan0
sudo ifconfig wlan0 up
sudo iwconfig wlan0 essid "NETGEAR"
sudo iwconfig wlan0 key c2a1d1897b
sudo iwconfig wlan0 mode Managed
sudo dhclient wlan0


*** try for static ip which I believe worked once
sudo ifconfig wlan0 down
sudo dhclient -r wlan0
sudo ifconfig wlan0 192.168.0.4 netmask 255.255.255.0 up
sudo route add default gw 192.168.0.1
sudo iwconfig wlan0 essid "NETGEAR"
sudo iwconfig wlan0 key c2a1d1897b
sudo iwconfig wlan0 mode Managed
sudo dhclient wlan0

*** after boot with eth0 working
sudo dhclient eth0
*** (re)binds correctly


*** attempt to disconnect and reconnect
sudo ifconfig eth0 down
sudo ifconfig eth0 up
*** fails subsequent sudo dhclient eth0 fails

[kevdog]

Are you taking both interfaces down initially and then releases any leases on the connected client, and then attempting to bring up only one interface and trying to connect?

What drivers are you using for the wireless device?

[wwastro]

Can you post

ifconfig

iwlist scan

Thanks

[This is now a new session; I am connected via eth0/ethernet]:

ifconfig gives:

eth0 Link encap:Ethernet HWaddr 00:15:c5:bd:3e:2f
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1044 errors:0 dropped:0 overruns:0 frame:0
TX packets:865 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1402610 (1.3 MB) TX bytes:106433 (103.9 KB)
Interrupt:22

eth1 Link encap:Ethernet HWaddr 00:18:de:94:65:62
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:55 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:7103 (6.9 KB)

eth1:avahi Link encap:Ethernet HWaddr 00:18:de:94:65:62
inet addr:169.254.7.15 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:26 errors:0 dropped:0 overruns:0 frame:0
TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1840 (1.7 KB) TX bytes:1840 (1.7 KB)

wmaster0 Link encap:UNSPEC HWaddr 00-18-DE-94-65-62-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

iwlist scan gives:

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

eth1 No scan results

Thanks.

[daparker1710]

Are you taking both interfaces down initially and then releases any leases on the connected client, and then attempting to bring up only one interface and trying to connect?

What drivers are you using for the wireless device?
I tried again just to be sure. I came up with eth0 attached and working. Then I downed eth0, downed wlan0, did dhclient -r against each then went through the static ip steps for wlan0. Still no DHC Offers.

As to drivers, I have no idea. How do I find out?

I'm using a GIGAFAST WF741-UIC USB Wireless 11 Mbps adapter.

I also don't know what driver is used for the eth0 connection just that Ubuntu installation recognized it and made it operable for installation and subsequent boots.

The PC is a 1998 vintage gateway I'm trying to give a few more years of productive student use.

[kevdog]

wwastro

Your scan results are not detecting any nearby networks!

daparker

You could post the results of lsmod to find the driver.

[daparker1710]

You could post the results of lsmod to find the driver.

I think the salient result from lsmod is:

usbcore 146028 3 zd1201,uhci_hcd

Here's the whole thing in case there are other clues.

Module Size Used by
rfcomm 41744 2
l2cap 25728 13 rfcomm
bluetooth 61156 4 rfcomm,l2cap
ppdev 10372 0
apm 22616 2
cpufreq_powersave 2688 0
cpufreq_stats 7104 0
cpufreq_ondemand 9740 0
freq_table 5536 2 cpufreq_stats,cpufreq_ondemand
cpufreq_userspace 5284 0
cpufreq_conservative 8712 0
iptable_filter 3840 0
ip_tables 14820 1 iptable_filter
x_tables 16132 1 ip_tables
ipv6 267780 8
lp 12324 0
loop 18948 0
snd_ens1371 27168 3
gameport 16008 1 snd_ens1371
snd_ac97_codec 101028 1 snd_ens1371
ac97_bus 3072 1 snd_ac97_codec
snd_pcm_oss 42144 0
snd_mixer_oss 17920 1 snd_pcm_oss
snd_pcm 78596 3 snd_ens1371,snd_ac97_codec,snd_pcm_oss
snd_seq_dummy 4868 0
snd_seq_oss 35584 0
snd_seq_midi 9376 0
snd_rawmidi 25760 2 snd_ens1371,snd_seq_midi
zd1201 23556 0
evdev 13056 1
snd_seq_midi_event 8320 2 snd_seq_oss,snd_seq_midi
snd_seq 54224 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
parport_pc 36260 1
parport 37832 3 ppdev,lp,parport_pc
af_packet 23812 2
snd_timer 24836 2 snd_pcm,snd_seq
snd_seq_device 9612 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
serio_raw 7940 0
snd 56996 17 snd_ens1371,snd_ac97_codec,snd_pcm_oss,snd_mixer_o ss,snd_pcm,snd_seq_dummy,snd_seq_oss,snd_rawmidi,s nd_seq,snd_timer,snd_seq_device
psmouse 40336 0
soundcore 8800 1 snd
intel_agp 25492 1
snd_page_alloc 11400 1 snd_pcm
agpgart 34760 1 intel_agp
i2c_piix4 9612 0
pcspkr 4224 0
shpchp 34452 0
i2c_core 24832 1 i2c_piix4
pci_hotplug 30880 1 shpchp
ext3 136712 1
jbd 48404 1 ext3
mbcache 9600 1 ext3
sg 36880 0
sr_mod 17956 0
sd_mod 30720 3
cdrom 37408 1 sr_mod
pata_acpi 8320 0
ata_generic 8324 0
ata_piix 19588 2
libata 159344 3 pata_acpi,ata_generic,ata_piix
uhci_hcd 27024 0
floppy 59588 0
de2104x 24576 0
scsi_mod 151436 4 sg,sr_mod,sd_mod,libata
usbcore 146028 3 zd1201,uhci_hcd
fbcon 42912 0
tileblit 3456 1 fbcon
font 9472 1 fbcon
bitblit 6784 1 fbcon
softcursor 3072 1 bitblit
fuse 50580 3

[kevdog]

Dont know a lot about the zydas driver you have, but I would suspect that might be part of the problem. That is not a very common chipset, and my knowledge of it is very elementary at best.

[daparker1710]

The zydas driver may, as you say, be part of the problem but only part. A striking clue that points elsewhere is the eth0 behavior. It comes up at boot based on what was discovered automatically at installation and ifconfig eth0 down kills it but ifconfig eth0 up fails to restore it. Solving that puzzle might shed some light on the wireless puzzle.

Any thoughts?

[d.avid]

Hi.

I'm experiencing some difficulties with WPA1+2. WEP and unencrypted connections work.

Using static IPs I tried the following:


sudo su
ifconfig wlan0 down
dhclient -r wlan0
route add default gw 192.168.178.1
ifconfig wlan0 192.168.178.22 netmask 255.255.255.0
iwconfig wlan0 essid "Sub-Etha-Net"
iwconfig wlan0 mode Managed
wpa_supplicant -Bw -Dwext -iwlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf


No success. Without the route-line I think I could at least ping my router once (no connection to the rest of the world) but I wasn't able to reproduce this. I tried both variants many times without success.

iwconfig


wlan0 IEEE 802.11g ESSID:"Sub-Etha-Net"
Mode:Managed Frequency:2.427 GHz Access Point: 00:1C:4A:A3:1F:AD
Bit Rate=54 Mb/s Tx-Power:32 dBm
RTS thr:2347 B Fragment thr:2346 B
Encryption key:AC96-E57A-F9B1-09CF-352B-FF4D-0FB9-25C2-3676-7C0D-2EB5-4F19-F586-CA80-0F4C-1D4F Security mode:restricted
Power Management:off
Link Quality:62/100 Signal level:-56 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


(about every third time I enter iwconfig (without having made any changes) the encryption key is set to "off" for no reason)

wpa_supplicant.conf


ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
ap_scan=1

network={
ssid="Sub-Etha-Net"
psk="mykey"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
}


Output: wpa_supplicant -w -Dwext -iwlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf -dd


Initializing interface 'wlan0' conf '/etc/wpa_supplicant/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant/wpa_supplicant.conf' -> '/etc/wpa_supplicant/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
eapol_version=1
ap_scan=1
Line: 11 - start of a new network block
ssid - hexdump_ascii(len=12):
53 75 62 2d 45 74 68 61 2d 4e 65 74 Sub-Etha-Net
PSK (ASCII passphrase) - hexdump_ascii(len=20): [REMOVED]
proto: 0x1
key_mgmt: 0x2
pairwise: 0x8
group: 0x8
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='Sub-Etha-Net'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=22 WE(source)=18 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1e:4c:14:b9:2e
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Added interface wlan0
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Added BSSID 00:00:00:00:00:00 into blacklist
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
State: DISCONNECTED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)





WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 1923 bytes of scan results (7 BSSes)
Scan results: 7
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:1c:4a:a3:1f:ad ssid='Sub-Etha-Net' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
selected based on WPA IE
selected WPA AP 00:1c:4a:a3:1f:ad ssid='Sub-Etha-Net'
Try to find non-WPA AP
Trying to associate with 00:1c:4a:a3:1f:ad (SSID='Sub-Etha-Net' freq=2427 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=20
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c07 len=100
AssocReq IE wireless event - hexdump(len=92): 00 0c 53 75 62 2d 45 74 68 61 2d 4e 65 74 01 08 82 84 8b 96 24 30 48 6c 21 02 08 12 24 02 01 0e 32 04 0c 12 18 60 dd 06 00 40 96 01 01 00 dd 09 00 10 18 02 00 10 00 00 00 dd 07 00 50 f2 02 00 01 00 dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c08 len=50
AssocResp IE wireless event - hexdump(len=42): 01 08 82 84 8b 96 24 30 48 6c 32 04 0c 12 18 60 dd 18 00 50 f2 02 01 01 80 00 03 a4 00 00 27 a4 00 00 42 43 5e 00 62 32 2f 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:1c:4a:a3:1f:ad
Association info event
req_ies - hexdump(len=92): 00 0c 53 75 62 2d 45 74 68 61 2d 4e 65 74 01 08 82 84 8b 96 24 30 48 6c 21 02 08 12 24 02 01 0e 32 04 0c 12 18 60 dd 06 00 40 96 01 01 00 dd 09 00 10 18 02 00 10 00 00 00 dd 07 00 50 f2 02 00 01 00 dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
resp_ies - hexdump(len=42): 01 08 82 84 8b 96 24 30 48 6c 32 04 0c 12 18 60 dd 18 00 50 f2 02 01 01 80 00 03 a4 00 00 27 a4 00 00 42 43 5e 00 62 32 2f 00
WPA: set own WPA/RSN IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:1c:4a:a3:1f:ad
No keys have been configured - skip key clearing
Associated with 00:1c:4a:a3:1f:ad
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RX EAPOL from 00:1c:4a:a3:1f:ad
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 01 71 d9 ae c4 17 21 38 48 20 c2 6d c2 93 af 05 cd e1 39 0e 81 77 68 7a 73 29 7f 16 67 90 44 5b 55 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
EAPOL-Key type=254
key_info 0x89 (ver=1 keyidx=0 rsvd=0 Pairwise Ack)
key_length=32 key_data_length=0
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 01
key_nonce - hexdump(len=32): 71 d9 ae c4 17 21 38 48 20 c2 6d c2 93 af 05 cd e1 39 0e 81 77 68 7a 73 29 7f 16 67 90 44 5b 55
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 01 71 d9 ae c4 17 21 38 48 20 c2 6d c2 93 af 05 cd e1 39 0e 81 77 68 7a 73 29 7f 16 67 90 44 5b 55 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:1c:4a:a3:1f:ad (ver=1)
WPA: Renewed SNonce - hexdump(len=32): ad 0c 71 07 6f a4 ea b9 c6 4f cd 2f 86 87 df a9 a3 f0 4e 12 65 4b 39 ed 6a 1d 84 5a 5e b4 1e f9
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: WPA IE for msg 2/4 - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=125): 01 03 00 79 fe 01 09 00 20 00 00 00 00 00 00 00 01 ad 0c 71 07 6f a4 ea b9 c6 4f cd 2f 86 87 df a9 a3 f0 4e 12 65 4b 39 ed 6a 1d 84 5a 5e b4 1e f9 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ed c5 06 41 3a 63 78 66 c3 71 62 7c c5 0a b9 5f 00 1a dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
RX EAPOL from 00:1c:4a:a3:1f:ad
RX EAPOL - hexdump(len=125): 01 03 00 79 fe 01 c9 00 20 00 00 00 00 00 00 00 02 71 d9 ae c4 17 21 38 48 20 c2 6d c2 93 af 05 cd e1 39 0e 81 77 68 7a 73 29 7f 16 67 90 44 5b 55 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 18 c3 ec f7 88 82 9f 90 ba a9 89 02 b6 82 ea 6c 00 1a dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
IEEE 802.1X RX: version=1 type=3 length=121
EAPOL-Key type=254
key_info 0x1c9 (ver=1 keyidx=0 rsvd=0 Pairwise Install Ack MIC)
key_length=32 key_data_length=26
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 02
key_nonce - hexdump(len=32): 71 d9 ae c4 17 21 38 48 20 c2 6d c2 93 af 05 cd e1 39 0e 81 77 68 7a 73 29 7f 16 67 90 44 5b 55
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 18 c3 ec f7 88 82 9f 90 ba a9 89 02 b6 82 ea 6c
WPA: RX EAPOL-Key - hexdump(len=125): 01 03 00 79 fe 01 c9 00 20 00 00 00 00 00 00 00 02 71 d9 ae c4 17 21 38 48 20 c2 6d c2 93 af 05 cd e1 39 0e 81 77 68 7a 73 29 7f 16 67 90 44 5b 55 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 18 c3 ec f7 88 82 9f 90 ba a9 89 02 b6 82 ea 6c 00 1a dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Could not verify EAPOL-Key MIC - dropping packet
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface wlan0
State: 4WAY_HANDSHAKE -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_deauthenticate
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Removed BSSID 00:00:00:00:00:00 from blacklist (clear)
Cancelling scan request
Cancelling authentication timeout
WEXT: Operstate: linkmode=0, operstate=6
.. etc pp. Apparently the key is involved? That's what the router log says aswell: authorization failed due to an invalid key. I made sure it's correct of course.

I use BCM 4312-winxp drivers with ndiswrapper. WPA2 worked before with the standard Hary drivers but the speed was incredibly slow and unreliable (in contrast to my connection with Vista) so I wanted to try other drivers.

Thanks for your kind help!

david


PS: Just checked dmesg and found several entries:
:
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: no IPv6 routers present
:
Don't know whether this is relevant?

[kevdog]

daparker

What driver is eth0 using??
lshw -C network


d.avid

What is result of iwlist scan? What if you delete the eapol_version=1
ap_scan=1
lines? Is your router set for wpa1 encryption? Where did you obtain your ndiswrapper winxp driver for your setup?

[d.avid]

Thanks for your prompt reply.
It doesn't seem like there's any difference when I delete those lines. I didn't compare the wpa_supplicant debugging output too closely but it looks similar. The iwconfig report is the same and "ping 192.168.178.1" (=router) still produces "Destination host unreachable".

iwlist scan


Address: 00:1C:4A:A3:1F:AD
ESSID:"Sub-Etha-Net"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.427 GHz (Channel 4)
Quality:60/100 Signal level:-57 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK



Yes, the router uses WPA1.

I installed ndiswrapper following this tutorial: http://ubuntuforums.org/showthread.php?t=760568 and chose the first driver from this page: http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list_b/
The driver itself is from hp for "Broadcom Corporation BCM4312 802.11a/b/g (rev 02)". My card is apparently "rev 01", didn't know whether it made any difference. Maybe that's it? WEP works though!

[wwastro]

wwastro

Your scan results are not detecting any nearby networks!

daparker

You could post the results of lsmod to find the driver.

This computer is sitting very close to the router, and the wireless signal is clearly detected. Thus the output from

iwconfig

is (practically as quoted before):

lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

eth1 IEEE 802.11g ESSID:"NETGEAR" Nickname:""
Mode:Managed Frequency:2.462 GHz Access Point: 00:14:6C:D3:B3:6E
Bit Rate=54 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Power Management:off
Link Quality=99/100 Signal level=-20 dBm Noise level=-51 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

while the output from

lshw -C network

is

*-network
description: Wireless interface
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0b:00.0
logical name: wmaster0
version: 02
serial: 00:18:de:94:65:62
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl3945 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11g
*-network
description: Ethernet interface
product: BCM4401-B0 100Base-TX
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: eth0
version: 02
serial: 00:15:c5:bd:3e:2f
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=b44 driverversion=2.0 ip=192.168.1.3 latency=64 module=ssb multicast=yes

- note that:

(1) the wireless card driver is iwl3945 (in the original Windows XP setup it was iwp3945, and this also applied for Gutsy);

(2) eth1 sees the radio signal but itself seems to be associated with a wrong MAC/physical address for the wireless interface (which should be
00:18:de:94:65:62, judging by the past Windows/Gutsy setups etc, but this is now somehow associated with wmaster0).

For the record, the output from lsmod is:

Module Size Used by
i915 32512 2
drm 82452 3 i915
rfcomm 41744 2
l2cap 25728 13 rfcomm
bluetooth 61156 4 rfcomm,l2cap
ppdev 10372 0
acpi_cpufreq 10796 1
cpufreq_ondemand 9740 1
cpufreq_powersave 2688 0
cpufreq_stats 7104 0
freq_table 5536 3 acpi_cpufreq,cpufreq_ondemand,cpufreq_stats
cpufreq_userspace 5284 0
cpufreq_conservative 8712 0
container 5632 0
dock 11280 0
sbs 15112 0
sbshc 7680 1 sbs
iptable_filter 3840 0
ip_tables 14820 1 iptable_filter
x_tables 16132 1 ip_tables
af_packet 23812 6
aes_i586 33536 0
dm_crypt 15364 0
dm_mod 62660 1 dm_crypt
sbp2 24072 0
parport_pc 36260 0
lp 12324 0
parport 37832 3 ppdev,parport_pc,lp
arc4 2944 2
ecb 4480 2
blkcipher 8324 1 ecb
joydev 13120 0
snd_hda_intel 344728 1
snd_pcm_oss 42144 0
snd_mixer_oss 17920 1 snd_pcm_oss
snd_pcm 78596 2 snd_hda_intel,snd_pcm_oss
snd_page_alloc 11400 2 snd_hda_intel,snd_pcm
snd_hwdep 10500 1 snd_hda_intel
snd_seq_dummy 4868 0
snd_seq_oss 35584 0
snd_seq_midi 9376 0
snd_rawmidi 25760 1 snd_seq_midi
sdhci 19076 0
video 19856 0
iwl3945 89844 0
output 4736 1 video
snd_seq_midi_event 8320 2 snd_seq_oss,snd_seq_midi
serio_raw 7940 0
ricoh_mmc 4352 0
wmi_acer 9644 0
mmc_core 51460 1 sdhci
iwlwifi_mac80211 219108 1 iwl3945
iTCO_wdt 13092 0
iTCO_vendor_support 4868 1 iTCO_wdt
snd_seq 54224 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
snd_timer 24836 2 snd_pcm,snd_seq
snd_seq_device 9612 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
button 9232 0
battery 14212 0
ac 6916 0
intel_agp 25492 1
snd 56996 13 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,sn d_hwdep,snd_seq_dummy,snd_seq_oss,snd_rawmidi,snd_ seq,snd_timer,snd_seq_device
cfg80211 15112 1 iwlwifi_mac80211
agpgart 34760 3 drm,intel_agp
evdev 13056 8
dcdbas 9504 0
soundcore 8800 1 snd
pcspkr 4224 0
psmouse 40336 0
shpchp 34452 0
pci_hotplug 30880 1 shpchp
ext3 136712 1
jbd 48404 1 ext3
mbcache 9600 1 ext3
sg 36880 0
sr_mod 17956 0
cdrom 37408 1 sr_mod
sd_mod 30720 3
ata_piix 19588 2
ata_generic 8324 0
b44 28432 0
pata_acpi 8320 0
libata 159344 3 ata_piix,ata_generic,pata_acpi
ohci1394 33584 0
scsi_mod 151436 5 sbp2,sg,sr_mod,sd_mod,libata
ieee1394 93752 2 sbp2,ohci1394
ssb 34308 1 b44
mii 6400 1 b44
ehci_hcd 37900 0
uhci_hcd 27024 0
usbcore 146028 3 ehci_hcd,uhci_hcd
thermal 16796 0
processor 36872 4 acpi_cpufreq,thermal
fan 5636 0
fbcon 42912 0
tileblit 3456 1 fbcon
font 9472 1 fbcon
bitblit 6784 1 fbcon
softcursor 3072 1 bitblit
fuse 50708 1


Any further insights, kevdog? Thanks.

[kevdog]

wwastro

PM chili555 -- he has an intel card and is an expert with intel setups. He is very responsive -- perhaps he can shed some light on the situation. dmizer might be another good resource (can't remember if he runs an Intel card or not). He's a forum mod now, so I'm not sure if he responds to PMs (he used to) but I would give it a try. He is also an excellent resource. Hopefully they can shed some light on what is going on here. There was some problem I think I remember chili555 talking about during the Gutsy -> Hardy crossover with intel cards. I just can't remember what he said??:confused:

[kinrose]

kinrose

Best advice

Figure out the interface
Try an unencrypted connection
Use an ESSID with only letters or numbers -- no spaces or crazy characters.
Broadcast the Essid

Make sure you can see your router with
iwlist scan

Hmm. maybe you could provide more info.

Hi I now have, Wireless connection to 'wirless name' (100%)
I still can't get onto the internet but found message in /var/log/syslog laptop ppoe - discovery: Time out waiting for PADO packets
What information do you need and where would I find it? Thanks

[mauris]

And another happy HP presario v3000 (64x2) WiFi user.
A BIG THANK YOU to kevdog. =D>
It really works. \\:D/

[stackman1]

Hello Guys/Gals...Another post sent me to your instructions because my Network Admin was not responsive. I followed your commands and have posted the results. I have a 2002 Dell Inspiron 2500 and am using a Linksys WRT54G Router w/ a Linksys WPC54GS pcmcia card.
I am currently connected with the same card and router on my other Dell laptop using XP. I first tried to provide the status and then the commands to connect to the device. It appears that one of my devices is sleeping. Any help would be greatly appreciated, been working for a couple of weeks just to get this far. Thanks.

peter@i2500:~$ sudo lshw -C network
[sudo] password for peter:
*-network
description: Wireless interface
product: BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 02
serial: 00:14:bf:76:15:64
width: 32 bits
clock: 33MHz
capabilities: bus_master ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+lbscmnds driverversion=1.45+The Linksys Group, Inc.,02/ latency=64 link=no module=ndiswrapper multicast=yes wireless=IEEE 802.11g
peter@i2500:~$
peter@i2500:~$ sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Scan completed :
Cell 01 - Address: 00:1D:7E:E8:74:86
ESSID:"minnesota_router"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:53/100 Signal level:-62 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0

peter@i2500:~$

**

peter@i2500:~$ sudo ifconfig eth0 down
[sudo] password for peter:
peter@i2500:~$ sudo dhclient -r eth0
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:14:bf:76:15:64
Sending on LPF/eth0/00:14:bf:76:15:64
Sending on Socket/fallback
peter@i2500:~$ sudo ifconfig eth0 up
peter@i2500:~$ sudo iwconfig eth0 essid "minnesota_router"
peter@i2500:~$ sudo iwconfig eth0 key 549C4AEC4CB046A95058E9032
peter@i2500:~$ sudo iwconfig eth0 mode managed
peter@i2500:~$ sudo dhclient eth0
There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:14:bf:76:15:64
Sending on LPF/eth0/00:14:bf:76:15:64
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
peter@i2500:~$

[stackman1]

PS. I am running Gutsy Gibbon on the above 2500 having done a complete wipeout of XP..

[stackman1]

There is already a pid file /var/run/dhclient.pid with pid 134519120

Just wondering if I am causing a problem by using the same nic card between my XP laptop (this one connected to the web) and my Gutsy Gibbon machine. Do I need to rest the router or something if I pull out the pcmcia card and then insert it and boot up the Ubuntu machine?

[kinrose]

kinrose

Best advice

Figure out the interface
Try an unencrypted connection
Use an ESSID with only letters or numbers -- no spaces or crazy characters.
Broadcast the Essid

Make sure you can see your router with
iwlist scan

Hmm. maybe you could provide more info.

Thanks I now have 'wireless connection to wireless name (100%)'.
I get a connection timed out when trying to send email or get onto the internet and
/var/log/syslog laptop ppoe -discovery:Time out waiting for PADO packets.
What kind of information do you need.

[kevdog]

kinrose -- I dont know what PADO packets are. Have you googled the topic?


Stackman -- Upgrade first to the latest ndiswrapper version -- I think it is 1.52 if you have not done so. To find out your current version:

modinfo ndiswrapper

[d.avid]

Hi kevdog, you asked me to post my 'iwlist scan' result (which I did, first post on the previous page). Can you help me getting WPA to work?

(see my first post in this thread: http://ubuntuforums.org/showthread.php?p=5481462#post5481462
second post: http://ubuntuforums.org/showthread.php?p=5483320#post5483320 )

I would appreciate any help :)

[kinrose]

kinrose -- I dont know what PADO packets are. Have you googled the topic?


Stackman -- Upgrade first to the latest ndiswrapper version -- I think it is 1.52 if you have not done so. To find out your current version:

modinfo ndiswrapper

Hi I understand a PADI is aPPPoE Active Discovery Package Initiation. It sends a package via Ethernet broadcast of the PC's MAC address. A PADO is a PPPoE Active Discovery Offer. The DSL-AC replies with a PADO packet containing the DSL's MAC address for POP using a supplied name or service. Apparently this means I need a PPeO over ethernet. I have googled all of this, found others with my plight but no solution.

My ndiswrapper is v1,45. I would need instructions on exactly what to do to load it onto the laptop top with no internet connection if I download it onto this lap top. I am a newby to linux. Thanks for your replies.

[stackman1]

Hi I understand a PADI is aPPPoE Active Discovery Package Initiation. It sends a package via Ethernet broadcast of the PC's MAC address. A PADO is a PPPoE Active Discovery Offer. The DSL-AC replies with a PADO packet containing the DSL's MAC address for POP using a supplied name or service. Apparently this means I need a PPeO over ethernet. I have googled all of this, found others with my plight but no solution.

My ndiswrapper is v1,45. I would need instructions on exactly what to do to load it onto the laptop top with no internet connection if I download it onto this lap top. I am a newby to linux. Thanks for your replies.

Kinrose, I am a newbie like you trying to get my wireless to work. I discovered I have version 1.45 of ndiswrapper as well. Similarly the Ubuntu machine I am trying to get to work has no internet connection.

Here is the site to download the latest version 1.53.
http://ndiswrapper.sourceforge.net/joomla/
It will download a file called
ndiswrapper-1.53.tar.gz
which you should port over to your ubuntu machine. I like you will await instructions from KevDog. (I don't think I am not leading you astray on this.)

Obviously you have a internet connection available to you but if you are wondering how to move files over to a machine without a connection. Go to Walmart and buy a USB flash drive, you can pick up a 2g for about $12 or so; works well for me so far.
Hope that helps.

[kevdog]

You guys still need instructions how to build ndiswrapper? Here is an old post I wrote along time ago:
http://ubuntuforums.org/showthread.php?t=574501

[chili555]

wwastro

PM chili555 -- he has an intel card and is an expert with intel setups. He is very responsive -- perhaps he can shed some light on the situation. dmizer might be another good resource (can't remember if he runs an Intel card or not). He's a forum mod now, so I'm not sure if he responds to PMs (he used to) but I would give it a try. He is also an excellent resource. Hopefully they can shed some light on what is going on here. There was some problem I think I remember chili555 talking about during the Gutsy -> Hardy crossover with intel cards. I just can't remember what he said??:confused:wwastro is running now. He had a few issues in /etc/network/interfaces and after he amended his evil ways, connected immediately. Thanks for your confidence, kevdog.

[MrPickle12481632]

When I run 'lshw -C network', my wireless is split into two categories. One for "network controller" and one for "wireless interface".

"network controller" has the drivers, but "wireless interface" has the logical name (wlan0). Also, wheras "network controller", which appears first, under the title '*-network:1' appears to be running just fine, "wireless interface" is headed with '*-network:0 DISABLED'.

When I go through the steps in the how-to, the third command, 'sudo ifconfig wlan0 up' cannot find the file and reads "SIOCSIFLAGS: No such file or directory".

What really is concerning in this trial, is that I finally got my drivers for a Broadcom card [go ahead, laugh], installed and recognized through ndiswrapper/ndisgtk, but the wireless card does not show up as an option under network tools.

Also, it looks like the physical id-3 is being shared by the Network controller[wireless], and the ethernet interface. The Ethernet controller and wireless interface both have unique id's, but share the network heading of '*-network:0'.

Does your head hurt yet? Mine's near exploding. halp?

[acreech]

When I run



lshw -C network


I get the following:



*-network
description: Ethernet interface
product: MCP67 Ethernet
vendor: nVidia Corporation
physical id: a
bus info: pci@0000:00:0a.0
logical name: eth0
version: a2
serial: 00:1b:38:c8:1c:d2
width: 32 bits
clock: 66MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=forcedeth driverversion=0.61 ip=192.168.0.64 latency=0 maxlatency=20 mingnt=1 module=forcedeth multicast=yes
*-network UNCLAIMED
description: Ethernet controller
product: AR242x 802.11abg Wireless PCI Express Adapter
vendor: Atheros Communications Inc.
physical id: 0
bus info: pci@0000:05:00.0
version: 01
width: 64 bits
clock: 33MHz
capabilities: cap_list
configuration: latency=0


However I can not find:


There may be multiple interfaces listed, however look under the section appropriate to your wireless device for the line labeled logical name. Here is an example:

Which line am I looking for to get the Logical name.

[kevdog]

You dont get assigned a logical name if your device is UNCLAIMED -- ie your network driver is not installed correctly.

[tehcheesepuff]

I followed all the steps for a WEP connection, and it seemed to work correctly, but it still is not connected. The end result is exactly like the successful connection in all cases. The top right network manager icon doesn't do anything either. Any help would be appreciated. :confused:

[kevdog]

The icon is for Network Manager and the title of this thread is how to connect without network manager. So hence the icon is never going to do anything. Can you show us what you have typed into the command line and post the output.

[tehcheesepuff]

Okay here:


******@******-desktop:~$ sudo ifconfig wlan0 down
[sudo] password for ******:
******@******-desktop:~$ sudo dhclient -r wlan0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:12:17:a4:86:1d
Sending on LPF/wlan0/00:12:17:a4:86:1d
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.1.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
******@******-desktop:~$ sudo ifconfig wlan0 up
******@******-desktop:~$ sudo iwconfig wlan0 essid "linksys"
******@******-desktop:~$ sudo iwconfig wlan0 key BEBF1F089C
******@******-desktop:~$ sudo iwconfig wlan0 key open
******@******-desktop:~$ sudo iwconfig wlan0 mode Managed
******@******-desktop:~$ sudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:12:17:a4:86:1d
Sending on LPF/wlan0/00:12:17:a4:86:1d
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPOFFER of 192.168.1.101 from 192.168.1.1
DHCPREQUEST of 192.168.1.101 on wlan0 to 255.255.255.255 port 67
DHCPACK of 192.168.1.101 from 192.168.1.1
bound to 192.168.1.101 -- renewal in 35917 seconds.
******@******-desktop:~$


And one thing I noticed, when I try to go into Firefox after doing this, it only says Firefox is in offline mode, not that Firefox cannot find the server. Could that be the problem?

[tehcheesepuff]

How would you want me to organize it? It's an exact copy/paste of the terminal, except I edited the username. Tell me what to change please.

[jw5801]

How would you want me to organize it? It's an exact copy/paste of the terminal, except I edited the username. Tell me what to change please.

I think he meant kevdog's post, but it's been reported and is all gone now.

[cardinalp]

thanks kevdog - this was the final step in a quite a bit of effort to get a ZyXEL M-102 PCMCIA wireless card running on an old thinkpad 600X with hardy.
For the record, this has an Atheros AR5513 chip (which is equivalent apparently to a AR5005VA). Eventually what is working is using ndiswrapper 1.53 and version 2.0.0 of the windows driver from zyxel. I can't describe exactly what is required - I've tried so many combinations, but it is possible!

[strat1227]

hi, i have a unencrypted network, and i finished doing everything, it seemed to work out ok, but after the last line instead of saying
user@computer:~$ sudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:12:17:35:17:10
Sending on LPF/wlan0/00:12:17:35:17:10
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 192.168.1.1
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.101 -- renewal in 299133 seconds.

it said
user@computer:~$ sudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:12:17:35:17:10
Sending on LPF/wlan0/00:12:17:35:17:10
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS recieved.
No working leases in persistent database - sleeping.

any idea what this means?

[unutbu]

Here are some things you might want to try:

Try

sudo /etc/init.d/networking restart
Type


iwlist scan

This should report all the routers that your wireless adapter can see. Make sure your router's ESSID and Address are present. You should be able to see your router even if you can't yet obtain a DHCP lease.

If you can't see your router using the "iwlist scan" command, then at least you'll know that this is the primary problem (not having to do with leases). Try moving the adapter, the router, or stuff in between so that there is less dense matter along the straight-line path between the two. Moving them closer together may also help.

If you can see your router:


Connect a computer to the router, perhaps by ethernet cable. Open a browser to 192.168.1.1 (or whatever the address of your router is).
Look through the configuration options, pay particular attention to anything having to do with DHCP. Make sure it is enabled, and that there is a range of IP addresses from which the router to assign.

Make sure the router is not doing MAC filtering (at least until you get the connection working).

Try powering-off then powering-on the machine instead of doing a soft reboot. This may reset the wireless adapter to a good state that is not achieved by a soft reboot.


If none of the above helps, you might want to try going for a static connection. If you are using Network Manager, then one way to do it is to edit your /etc/network/interfaces file:


gksu gedit /etc/network/interfaces
Edit the wlan0 section to look something like this:


auto wlan0
iface wlan0 inet static
address 192.168.1.46
netmask 255.255.255.0
gateway 192.168.1.1


"gateway" should be your router's IP address.
"netmask 255.255.255.0" means that your computer should consider addresses of the form 192.168.1.xxx are part of its local network.
"address" should be of the form 192.168.1.xxx (assuming your gateway address starts with 192.168.1). xxx can be any number between 0 and 255.


Power down, power up, and hopefully you'll then have a static connection. If not, try

sudo /etc/init.d/networking restart

[strat1227]

Thanks for the ideas, i'll try them, but i know the problem isn't with the modem or router, because we have 3 other computers on the network.

I just recently decided i wanted to try Linux, and of course dumb me didn't even think about partitioning for a dual boot, and they don't even make the drivers for this computer any more, so there's no option of going back to windows until i get a new computer, so i'm hoping i can get the hang of this lol.

i'll report back after i try your suggestions if i'm still having trouble.

[wariskampar]

Hopefully someone in here can help me with my problem. My wireless work out of box, meaning I do not set anything but just use Network Manager to establish connection. However, I must enter ESSID and WPA password and disable broadcasting everytime I want to re-connect wirelessly (mostly I use ethernet connection). I can not broadcast ESSID to enable wireless connection. Another thing is pertaining to conky. After I dis-connect my wireless connection, ESSID will still displayed in conky. As a matter of fact, it will only be cleared if I log out or restart.

Before I follow the first post, I would like to know whether my problem is related to it (first post)? Hope someone can assist me

[jimistephen]

ok, i had this working once for about 3 days and then it quit working and i was trying to do it again, as seeing i didn't put it in the rc.local and when i get to "sudo dhclient -r wlan" it says:

...listening on LPF/wlan0/00:19:7e:5f:d7:b5
sending on LPF/wlan0/00:19:7e:5f:d7:b5
sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.1.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.

then i just noticed that the instead of saying stephen@... it said "sstephen@..." then i hit enter and it when back to normal.

any help here would be great thanks in advance
~stephen

[RadioMirchi]

great info dude

[hal10001]

I keep getting "Unsupported driver 'ndiswrapper=wext'" whenever I type the following command:

sudo wpa_supplicant -w -D ndiswrapper=wext -i wlan0 -c /etc/wpa_supplicant.conf

I've tried several different combinations, but I obviously am not typing the driver name correctly. Below is the results of running:

sudo lshw -C network

*-network:0
description: Wireless interface
product: 88w8335 [Libertas] 802.11b/g Wireless
vendor: Marvell Technology Group Ltd.
physical id: 2
bus info: pci@0000:02:02.0
logical name: wlan0
version: 03
serial: 00:18:e7:0e:e1:1c
width: 32 bits
clock: 66MHz
capabilities: pm bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+mrv8000c driverversion=1.52+Marvell,09/17/2004,3.1.0.19 latency=32 link=yes module=ndiswrapper multicast=yes wireless=IEEE 802.11b
*-network:1
description: Ethernet interface
product: RTL-8139/8139C/8139C+
vendor: Realtek Semiconductor Co., Ltd.
physical id: 3
bus info: pci@0000:02:03.0
logical name: eth0
version: 10
serial: 00:40:ca:b5:2a:d1
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=8139too driverversion=0.9.28 duplex=full ip=192.168.1.109 latency=32 link=yes maxlatency=64 mingnt=32 module=8139too multicast=yes port=MII speed=100MB/s

My networks are claimed, my driver is installed correctly, and I can see available wireless networks in my area, but I just can't get the stupid thing to connect, so I'm going through this manually.

My system:

Release 8.04 (hardy)
Kernel Linux 2.6.24-19
GNOME 2.22.3

Intel(R) Pentium(R) 4 CPU 1500MHZ

This only started happening after my upgrade from 7.10. Before that my wireless card was working just fine. I removed the driver and reinstalled after the upgrade, but that did not help either.

Thanks for any help you can offer.

[wapa17]

Kevdog:

and YESSS .. I got connection after searching for weeks for a solution (DELL Vostro 1510 BCM4312 (Rev.1)) !!

Thanks a lot !!!

[kevdog]

Glad it worked for you!

[stathol]

This works, however as soon as I log in, the NetworkManager applet pops up the "Network Secret Required ..." box and asks me for my WEP key again. This would only be a minor annoyance except that I just set up remote login by VNC. When you log in by VNC, resetting the network like that kills the connection and you can't reconnect to that session again (or at least, I don't know how).

Any idea what's causing that? I'm using Intrepid (my video card simply wouldn't work with Hardy, but that's another story).

[kevdog]

so why don't you uninstall network manager?

[stathol]

I could do that, and for now I have; however, there are some problems with that approach.

One is that it leaves me with no way to connect VPN sessions. I also can't monitor the WiFi. For some reason, my signal fluctuates quite a bit. I have to readjust my antenna periodically to get a decent connection. As well, if I get dropped from the network, not having the network manager is a pain. My router is kind of on the fritz. It has a habit of crashing sometimes when I run heavy traffic through it (ex. bittorrents). I guess I can reconnect by running some shell scripts, but that's not very convenient.

Is this an "XOR" solution? That is, I can either have the network connect at boot time, or I can have the graphical manager, but not both? I'd like to find a solution that initiates the network automatically at boot time, but still leaves the option of managing after logging in.

Then there's the separate issue of why the NetworkManager plugin isn't remembering the WEP key. It remembered it correctly in Hardy, but not in Intrepid. Any idea what would cause that?

[mlnsharma]

Hi Guys, I am a new user...iHave Ubuntu 8.04 installed in my pc now.. I use an ethernet card for accessing Internet in a LAN..When i use in xp it automatically detected the ethernet card..But in ubuntu it didnt...And even after manually configuring it is not detecting the card...Can any one help me with this issue...Pls do reply !!:(

[DSundquist]

I'm completely new to Ubuntu and Linux so need a little assistance if you can help.

I have a dual boot with Windows XP. Wireless works fine in Windows and also works in Ubuntu if I boot with Ethernet wire plugged in and then disconnect. The network manager switches to manual network configuration when I unplug and I'm able to get an ip configuration over that wireless connection. Subsequent boots fail to give me a wireless connection no matter what I try.

I followed the instructions in this post for setting up a WPA connection at the command line but it ends in "No DHCPOFFERS received". The "iwpriv wlan0 set ..." commands all return "wlan0 no private ioctls". I have no idea what that means but is that part of the problem?

Thanks,
Doug

[kevdog]

It would be very helpful if you gave me info about your wireless card and driver:

lspci -nn
lshw -C network
iwlist scan

Security on the wireless network?

[xshakakee]

Hey, kevdog, great tutorial. I was beating myself up for hours trying to get my wireless to work, and when I found your tute, I put it together pretty quickly. Learned a little about my setup as well.

OK, for starters, I have the following setup:

Ubuntu Hardy, 8.04, on an AMD socket 754 (i386, not X_64).
Atheros Chipset wifi (I am pretty sure Hardy has native support)
wifi0 and ath0 appear when running iwconfig and ifconfig.
ath_pci appears when you do an lspci.

I want to connect to my "home" wireless router from my "home" computer. I am not interested in roaming around (keep WICD around just in case you want to roam). Also, I want a static ip. I know what ip address, subnet mask, and default gateway I need. Also, I'm sure what I need to have in my resolv.conf to keep my DNS information from floating away.

Last, my router is set to hidden SSID and WPA-1 security.

One major caveat: you should be able to connect to your router via wired ethernet. You should have, minimally, in your /etc/network/interfaces file:


auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp


I start by uninstalling Network Manager and installing WICD. Then I use WICD to connect to my chosen wireless router. I will not go over these gui-intensive steps here, because I'm primarily focused on getting this to work at startup, using scripts. If all goes well, WICD should tell me that I'm connected. I cd to /opt/wicd/encryption/configurations/ and look for a file that looks like 00ab00cd00ef. Copy this file to /etc/wpa_supplicant.conf:


cp /opt/wicd/encryption/configurations/<router mac address> /etc/wpa_supplicant.conf
if you really want to. I made my own wpa_supplicant.conf file by pulling information from around the web. Mine looks like this:


network={
scan_ssid=1
ssid="Your SSID Here"
proto=WPA
key_mgmt=WPA-PSK
psk="your wpa passphrase in text here"
pairwise=TKIP
group=TKIP
}

Great, now I have my wpa_supplicant settings. How do I use this?

Thanks to Maricaibo, by way of kevdog, we have this handy script:
First,

gedit /etc/rc.local
Make it look more like this:


#By default this script does nothing
ifconfig ath0 down
ifconfig eth0 down
dhclient -r ath0
wpa_supplicant -B -Dmadwifi -iath0 -c/etc/wpa_supplicant.conf
sleep 15
ifconfig ath0 up
dhclient ath0
exit 0

I am not sure that the "sleep 15" is doing anything. I just wanted to make sure that wpa was doing its thing before dhclient started requesting an ip address.

Make sure wpa_supplicant.conf is read-writable by root:


chown root:root /etc/wpa_supplicant.conf

and

chmod 644 /etc/wpa_supplicant.conf

or

chmod 600 /etc/wpa_supplicant.conf

Also, rc.local should be executable:


chmod 700 /etc/rc.local

or

chmod 777 /etc/rc.local

Restart your computer and make sure ifconfig and iwconfig show that you are connected to the internet via your wireless connection.

If you are not, get back on the wired and run "sudo su" then "/etc/init.d/networking restart". Or use WICD to connect.

If the above works for you, let's give yourself a static ip address:

Edit the /etc/rc.local file to look like this:


ifconfig ath0 down
ifconfig eth0 down
dhclient -r ath0
wpa_supplicant -B -Dmadwifi -iath0 -c/etc/wpa_supplicant.conf
sleep 15
ifconfig ath0 <your ip address> netmask 255.255.255.0 up
route add default gw <ip address of router>
exit 0

You should know your router's ip, your own preferred ip address, and the subnet mask, which is x.x.x.0 in so many cases that I didn't bother to change it.

Let's look at "tail /etc/resolv.conf"


nameserver 192.168.x.y

If dhclient keeps wiping out your other DNS entries, then you will need to add them in manually:

echo "nameserver **primary dns from isp**" >> /etc/resolv.conf
echo "nameserver **secondary dns from isp**" >> /etc/resolv.conf


If you are using OpenDNS, for instance, these lines would be:


echo "nameserver 208.67.220.220" >> /etc/resolv.conf
echo "nameserver 208.67.222.222" >> /etc/resolv.conf


Or just add these two lines to the bottom of the rc.local file, just before the "exit 0" line.

OK. That's it. Uninstall or disable WICD. Wipe or comment out every line in /etc/network/interfaces except for those referring to loopback or eth0, then restart your computer. You should connect automatically to your chosen network every time, after rebooting.

It takes me a couple of minutes post-restart for my network card to kick in, but when it does, it works fine. No hitches.

[Vietman]

Thanks for this post...Intrepid screwed up Network Manager with a recent update, and this did the trick for me. :guitar:

[s34nn4]

Hi everyone... I currently own an Acer Aspire one I did all the steps in Ubuntu Community Acer aspire one forum but whenever I try to connect to wifi it wont allow me...
I saw a thread where you need to configure your aes-ccmp

this is what it shows whenever I try to get an output on wireless card

lo no wireless extensions.

eth0 no wireless extensions.

wifi0 no wireless extensions.

ath0 IEEE 802.11g ESSID:"" Nickname:""
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:16 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=0/70 Signal level=-96 dBm Noise level=-96 dBm
Rx invalid nwid:3389 Rx invalid crypt:0 Rx invalid frag:0

anyone know how can I configure aes-ccmp?

[Kiefer Rodriguez]

Wow Kevdog,
Looks like you've got wireless sussed ;) Awesome source of info.
If you wanna link to my GUI installer for RT73 chipsets (http://ubuntuforums.org/showthread.php?t=923387), feel free. :)

-Kiefer

[kevdog]

Wow Kevdog,
Looks like you've got wireless sussed ;) Awesome source of info.
If you wanna link to my GUI installer for RT73 chipsets (http://ubuntuforums.org/showthread.php?t=923387), feel free. :)

-Kiefer

If you add WPA capabilities I will be sure to add it to the list!!

[Kiefer Rodriguez]

If you add WPA capabilities I will be sure to add it to the list!!

Eh just because you asked :)
Give me a few days.

[kevdog]

I'm not trying to jerk your chain, its that no one these days should use WEP. Its no excuse. WPA is so widely available.

[Kiefer Rodriguez]

I'm not trying to jerk your chain, its that no one these days should use WEP. Its no excuse. WPA is so widely available.

I agree mate, plus it gives me an excuse to update it. :)

[bionnaki]

I am connecting to a WEP network with an atheros/madwifi based card.

I am using the following commands:

sudo ifconfig ath0 up
sudo iwconfig ath0 essid ABCD key 0123456789
sudo dhcpcd ath0

Sometimes it works flawlessly. Other times I get a dhcpcd time out.

Any ideas on why it times out seemingly at random?

[kevdog]

Is the syntax of this statement correct??

sudo dhcpcd ath0

[stankopp]

Why is IP addressing so difficult in Linux?

I want to do a simple wired static connection that allows me to connect to the internet as well as our corporate network in Ubuntu 8.10. We do not do DHCP here at work. I have tried literally eveything suggested here to no avail. I could connect to local network assets, but could not browse the internet.

By the way, when I removed the network-manager-gnome, I could not re-install it. I now have a system that has no routing table at all and will not allow the addition of one. When I try "sudo route add default gw 1.1.1.88" the system responds with "no such process." Sudo route -n returns a totally empty routing table.

I am very close to scrapping 8.10 and Linux in general.

[kevdog]

What does your ifconfig show along with route -n

[stankopp]

As you can see nothing is retained after reboot. Here's what I get:

kopp@nats:~$ sudo ifconfig

[sudo] password for kopp:

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX packets:2566 errors:0 dropped:0 overruns:0 frame:0

TX packets:2566 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:131492 (131.4 KB) TX bytes:131492 (131.4 KB)



kopp@nats:~$ ifconfig eth0 up

SIOCSIFFLAGS: Permission denied

kopp@nats:~$ sudo ifconfig eth0 up

kopp@nats:~$ sudo ifconfig

eth0
Link encap:Ethernet HWaddr 00:04:e2:35:0d:3c

inet6 addr: fe80::204:e2ff:fe35:d3c/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:32 errors:0 dropped:0 overruns:0 frame:0

TX packets:3 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:6350 (6.3 KB) TX bytes:250 (250.0 B)

Interrupt:17

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX packets:2566 errors:0 dropped:0 overruns:0 frame:0

TX packets:2566 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:131492 (131.4 KB) TX bytes:131492 (131.4 KB)



kopp@nats:~$ sudo ifconfig eth0 down

kopp@nats:~$ sudo ifconfig eth0 1.1.8.52 netmask 255.0.0.0 up

kopp@nats:~$ sudo ifconfig

eth0 Link encap:Ethernet HWaddr 00:04:e2:35:0d:3c

inet addr:1.1.8.52 Bcast:1.255.255.255 Mask:255.0.0.0

inet6 addr: fe80::204:e2ff:fe35:d3c/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:121 errors:0 dropped:0 overruns:0 frame:0

TX packets:17 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:13201 (13.2 KB) TX bytes:2276 (2.2 KB)

Interrupt:17


lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX packets:2566 errors:0 dropped:0 overruns:0 frame:0

TX packets:2566 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:131492 (131.4 KB) TX bytes:131492 (131.4 KB)



kopp@nats:~$ sudo route add default gw 1.1.1.88 netmask 255.0.0.0 dev eth0

kopp@nats:~$ route -n

Kernel IP routing table

Destination Gateway Genmask Flags Metric Ref Use Iface

0.0.0.0 1.1.1.88 255.0.0.0 UG 0 0 0 eth0

1.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 eth0

kopp@nats:~$


Well it actually let me add the default gateway now after re-boot, though I still cannot browse the internet.

[aduplat]

HI:

I have a very basic question. How I can find what is my ESSYD name... and and how can I check its config.

Thanks,

[kevdog]

The ESSID comes from the router itself -- its the wireless network name. You can scan for ESSID

iwlist scan

however the settings are going to be in the router itself. If you don't have access to the router, you need to ask the system admin.

[Rocktman2]

Shouldn't this really have been called, "How To: Manual WIRELESS Network Configuration without the need for Network Manager"?

As an IT/Network Manager, a network can be either wired, wireless or both. So someone looking to configure a wired network (yes, there are still some of us who want real security, reliability & speed) would be initially confused by the title & their search would include unnecessary returns.

Just my 2 cents. FWIW

[aduplat]

Hi There:

I follow your instructions but I can't reach the internet. This is the message:

There is already a pid file /var/run/dhclient.pid with pid 0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:1f:e1:7d:e2:ac
Sending on LPF/eth1/00:1f:e1:7d:e2:ac
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

------------------------------------------------------------------

I am trying to use the unencrypted connection because I assume that my router's key in turned off.
Actually I have two laptops but I have problems just with one.
-------------------------------------------------------------------

alfredo@alfredo-laptop:~$ sudo iwlist scan
lo Interface doesn't support scanning.

irda0 Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:1D:7E:D3:74:63
ESSID:"linksys"
Mode:Managed
Frequency=2.437 GHz (Channel 6)
Quality:5/5 Signal level:-42 dBm Noise level:-86 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s

[kevdog]

Im not sure this is the exact reason however look at this:

Quality:5/5 Signal level:-42 dBm

This would imply the signal strength is really low. Usually quality is 5/100 or x/100. I don't know what 5/5 means. -42 dBm = low

[kevdog]

This method will work for wired or wireless networks. You would simply not include the parts with the iwconfig statements or those that make use of the wireless-tools library:

http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html

[lswb]

kevdog,

Very nice howto. I would add that certain wifi drivers, notably ipw2200 for Intel Pro Wireless 2200 and 2915, will reset other parameters to default when the mode is changed. In you examples it may be necessary for these drivers to do

iwconfig eth1 mode managed

before setting the essid or other parameters, or to combine all settings into a single command line.

[kevdog]

I would add that certain wifi drivers, notably ipw2200 for Intel Pro Wireless 2200 and 2915, will reset other parameters to default when the mode is changed. In you examples it may be necessary for these drivers to do

iwconfig eth1 mode managed

before setting the essid or other parameters, or to combine all settings into a single command line.


I'll have to change the order of commands to reflect this. Nice find!

[drpaul]

The power level doesn't look low, but the S/N doesn't look good.

Here is an example from my machine;

eth1 Scan completed :
Cell 01 - Address: 00:15:E9:D3:B4:72
ESSID:"Erik"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=58/100 Signal level=-73 dBm Noise level=-127 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=0000159fd9a61117
Cell 02 - Address: 00:30:BD:C2:C1:22
ESSID:"WLAN"
Mode:Master
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=74/100 Signal level=-60 dBm Noise level=-127 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Extra:tsf=000000d21a732a76

You can see both a b and a g router near me.

HTH

Paul

[Rosycode]

Gurus please help,
I have spent hrs trying to setup internet connection but alas :(.

When I am using the pppoeconf there dsl-provider file gets generated. But to connect to my ISP i need to specify the Service provider.

There is no option to specify the service provider name".

I am using REALTEK Ethernet USB. In the GUI network configuration I am not getting ETHERNET Card option. Do I need to download anything here ? I am getting only a telephone picture.

Please please advise.

Regards
Rosy

[stankopp]

I have given up on 8.10 beta.

[kevdog]

I have given up on 8.10 beta.

Sorry to hear that. I gave up on Hardy and am only using the "Gibbon".

[StephenG]

Kevdog, I thank you for the exhaustive and exhausting manual. Unfortunately, it didn't quite work for me. I've attached the relevant files. I suspect I know why but have no idea how to rectify the issue. (I am very new at Linux -- first machine -- though am very comfortable with DOS command line stuff.) I'm running an old K6-300 machine with a Linksys WMP54G card. I've found tons of info on the issues surronding the RT61PCI, but haven't yet beat the machine and gotten it to work. So, here I am ...

My suspicions revolve around the fact that when I do the lshw -C network command, the reply indicates that the logical name is "wmaster0" but with the iwconfig command there are "no wireless extensions" for wmaster0, though there is a reply for "wlan0."

Iwlist for wmaster0 indicates no scanning supported. Iwlist for wlan0 has lots of information, including the proper info about my router: right channel, right name, right address (though no IP address). Having said that, the first time I ran iwconfig, the ESSID was this: " ". The second time I ran it, after running the iwlist, the ESSID was correct and returned my router's name.

Running dhclient for wlan0 and wmaster0 told me that both were "sleeping." A ping test on 192.168.2.1 (my router) was entirely unproductive -- 100% packet loss. Ping test on the card at 127.0.0.1 was fully productive -- 0% packet loss. Ping test at 192.168.1.47 was completely unproductive -- and I can't remember where I got that address from. A subsequent ifconfig command gave me some info that it hadn't given before, on "wlan0:avahi" and produced another IP. The ping test on that at 169.254.4.43 was entirely productive - again a 0% packet loss.

So, it seems to me that for whatever reason, the driver is loading, but loading for a device called wmaster0, while all indications are that the actual card is installed at wlan0. Whatever "wlan0:avahi" is, is beyond me.

Any thoughts or ideas or suggestions as to what needs to be changed?

Unfortunately, I have no idea how to get those nice little boxes within my post to display the text I got from the screen, and had to simply attach the file for your perusal.

I didn't figure out those nice boxes, but I know how to cut and paste:


Me@My-desktop:~$ lshw -C network
*-network
description: Wireless interface
product: RT2561/RT61 802.11g PCI
vendor: RaLink
physical id: 8
bus info: pci@0000:00:08.0
logical name: wmaster0
version: 00
serial: 00:1d:7e:95:11:36
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=rt61pci latency=64 module=rt61pci multicast=yes wireless=IEEE 802.11g


Me@My-desktop:~$ lsmod
Module Size Used by
ipv6 267780 8
rfcomm 41744 2
l2cap 25728 13 rfcomm
bluetooth 61156 4 rfcomm,l2cap
ppdev 10372 0
apm 22616 2
cpufreq_conservative 8712 0
cpufreq_userspace 5284 0
cpufreq_powersave 2688 0
cpufreq_stats 7104 0
cpufreq_ondemand 9740 0
freq_table 5536 2 cpufreq_stats,cpufreq_ondemand
iptable_filter 3840 0
ip_tables 14820 1 iptable_filter
x_tables 16132 1 ip_tables
lp 12324 0
af_packet 23812 0
arc4 2944 2
ecb 4480 2
blkcipher 8324 1 ecb
serio_raw 7940 0
evdev 13056 1
parport_pc 36260 1
parport 37832 3 ppdev,lp,parport_pc
psmouse 40336 0
rt61pci 25472 0
rt2x00pci 11264 1 rt61pci
rt2x00lib 22528 2 rt61pci,rt2x00pci
i2c_via 5124 0
rfkill 8592 1 rt2x00lib
i2c_algo_bit 7300 1 i2c_via
input_polldev 5896 1 rt2x00lib
crc_itu_t 3072 1 rt2x00lib
pcspkr 4224 0
i2c_core 24832 2 i2c_via,i2c_algo_bit
via_agp 11136 1
mac80211 165652 3 rt61pci,rt2x00pci,rt2x00lib
shpchp 34452 0
pci_hotplug 30880 1 shpchp
agpgart 34760 1 via_agp
cfg80211 15112 1 mac80211
eeprom_93cx6 3200 1 rt61pci
ext3 136712 1
jbd 48404 1 ext3
mbcache 9600 1 ext3
sg 36880 0
sr_mod 17956 0
cdrom 37408 1 sr_mod
sd_mod 30720 3
pata_acpi 8320 0
pata_via 13316 2
ata_generic 8324 0
libata 159344 3 pata_acpi,pata_via,ata_generic
floppy 59588 0
uhci_hcd 27024 0
scsi_mod 151436 4 sg,sr_mod,sd_mod,libata
usbcore 146028 2 uhci_hcd
fbcon 42912 0
tileblit 3456 1 fbcon
font 9472 1 fbcon
bitblit 6784 1 fbcon
softcursor 3072 1 bitblit
fuse 50580 3


Me@My-desktop:~$ iwconfig
lo no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.437 GHz Access Point: 00:18:F8:66:A3:58
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


Me@My-desktop:~$ sudo iwlist wmaster0 scan
wmaster0 Interface doesn't support scanning.


Me@My-desktop:~$ sudo iwlist wlan0 scan
wlan0 Scan completed :
Cell 01 - Address: 00:13:10:2B:FA:37
ESSID:"[Name Removed]"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=67/100 Signal level=-74 dBm
Encryption key:on
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=000001942043218b
Cell 02 - Address: 00:1C:10:32:69:B6
ESSID:"[Name Removed]"
Mode:Master
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=46/100 Signal level=-82 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=0000019421ea9189
Cell 03 - Address: 00:18:F8:66:A3:58
ESSID:"[My Router - Name Removed]"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=69/100 Signal level=-62 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=0000008f7ac17183



Me@My-desktop:~$ iwconfig
lo no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"[My Router - Name Removed]"
Mode:Managed Frequency:2.437 GHz Access Point: 00:18:F8:66:A3:58
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


Me@My-desktop:~$ ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:516 errors:0 dropped:0 overruns:0 frame:0
TX packets:516 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:27368 (26.7 KB) TX bytes:27368 (26.7 KB)

wlan0 Link encap:Ethernet HWaddr 00:1d:7e:95:11:36
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wmaster0 Link encap:UNSPEC HWaddr 00-1D-7E-95-11-36-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)



Me@My-desktop:~$ sudo dhclient wlan0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:1d:7e:95:11:36
Sending on LPF/wlan0/00:1d:7e:95:11:36
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.



Me@My-desktop:~$ sudo invoke-rc.d networking restart
* Reconfiguring network interfaces... [ OK ]



Me@My-desktop:~$ sudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 9083
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:1d:7e:95:11:36
Sending on LPF/wlan0/00:1d:7e:95:11:36
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20
No DHCPOFFERS received.
No working leases in persistent database - sleeping.



Me@My-desktop:~$ ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
From 169.254.4.43 icmp_seq=2 Destination Host Unreachable
From 169.254.4.43 icmp_seq=3 Destination Host Unreachable
From 169.254.4.43 icmp_seq=4 Destination Host Unreachable
--- 192.168.2.1 ping statistics ---
32 packets transmitted, 0 received, +24 errors, 100% packet loss, time 31002ms
, pipe 3



Me@My-desktop:~$ sudo dhclient wmaster0
[sudo] password for Me:
There is already a pid file /var/run/dhclient.pid with pid 9136
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wmaster0/
Sending on LPF/wmaster0/
Sending on Socket/fallback
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.
No working leases in persistent database - sleeping.



Me@My-desktop:~$ ping -c 4 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.186 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.177 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.178 ms
64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.181 ms
--- 127.0.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 0.177/0.180/0.186/0.013 ms



Me@My-desktop:~$ ping 192.168.2.1 [My Router's IP]
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
From 169.254.4.43 icmp_seq=1 Destination Host Unreachable
From 169.254.4.43 icmp_seq=2 Destination Host Unreachable
From 169.254.4.43 icmp_seq=3 Destination Host Unreachable
--- 192.168.2.1 ping statistics ---
6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5017ms
, pipe 3


Me@My-desktop:~$ ping -c 4 192.168.1.47 [I don't rmember where I got this address]
PING 192.168.1.47 (192.168.1.47) 56(84) bytes of data.
From 169.254.4.43 icmp_seq=1 Destination Host Unreachable
From 169.254.4.43 icmp_seq=2 Destination Host Unreachable
From 169.254.4.43 icmp_seq=3 Destination Host Unreachable
From 169.254.4.43 icmp_seq=4 Destination Host Unreachable
--- 192.168.1.47 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3009ms
, pipe 3


Me@My-desktop:~$ ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:622 errors:0 dropped:0 overruns:0 frame:0
TX packets:622 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:37224 (36.3 KB) TX bytes:37224 (36.3 KB)

wlan0 Link encap:Ethernet HWaddr 00:1d:7e:95:11:36
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wlan0:avahi Link encap:Ethernet HWaddr 00:1d:7e:95:11:36
inet addr:169.254.4.43 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1

wmaster0 Link encap:UNSPEC HWaddr 00-1D-7E-95-11-36-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


Me@My-desktop:~$ ping -c 4 169.254.4.43
PING 169.254.4.43 (169.254.4.43) 56(84) bytes of data.
64 bytes from 169.254.4.43: icmp_seq=1 ttl=64 time=0.237 ms
64 bytes from 169.254.4.43: icmp_seq=2 ttl=64 time=0.164 ms
64 bytes from 169.254.4.43: icmp_seq=3 ttl=64 time=0.165 ms
64 bytes from 169.254.4.43: icmp_seq=4 ttl=64 time=0.185 ms
--- 169.254.4.43 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 0.164/0.187/0.237/0.034 ms

[kevdog]

The way those devices were setup -- wmaster0 is the actual device, and wlan0 is a virtual interface to the actual device. ALWAYS communicate through the virtual device (wlan0) in your case and never through the wmaster0 device. Just a fine point.

That being said, I see wlan0 sees networks in the area. That is a good sign (iwlist scan).

How are you trying to connect to your network using wlan0. sudo dhclient wlan0 is not enough. You must at least specify a essid.

[StephenG]

I'm afraid you've lost me there, sir. I thought that the OS set up the device once there was a usable driver. Within the Network Manager, I've gone through the setup procedure several times, directing the card to the wireless network that shows up (my router downstairs), but although the router shows up (with pretty good strength - 69/100) and I choose it from the menu, I can not get the two to shake hands.

The very first time I installed the card, it hooked on and I was able to get onto the internet, although the downloading was very slow and there were disconnects every couple of minutes. After several times of that cycle, the card/router honeymoon was over and they've avoided each other ever since. I made no changes during that time, except to reinitiate the NM and reintroduce the card to the router, via the menu. I have tried configuring the card both as DHCP and set IP, but neither way works.

It sounds like you're telling me that I need to modify a file somewhere, with a specific ESSID line. Where would that be? Up to now, I have only tried modifying the /etc/network/interfaces file, per several threads I've found dealing specifically with the WMP54G card, to no avail. I've since set them back to their original forms. What file and what lines need to be added to specify the ESSID?

Or is the driver defective under Ubuntu -- as many claim, which is why they are using a ndiswrapper, apparently -- and though the driver is there and the card is there, they're not playing nicely together?

[stankopp]

I have re-installed 8.04 32-bit (Hardy) from scratch and have no issues. I had installed Hardy 64-bit on my previous laptop and had the wireless working somewhat. The only problem I had was with secured wireless sites, so I gave up on the 64-bit version.

When 8.10 is actually released, I'll probably give it a try.

[kevdog]

The rt61 chipset is tricky! Meaning there is a built in driver in the kernel that works for some people, others use the third part serial-monkey driver, and still others use ndiswrapper that encapsulates (or "wraps") a windows driver. In order to best troubleshoot your card you need to use the command line -- the topic of this thread if you look at the first post. If you are losing connections or getting frequent drops, this may indicate a driver problem, so you may need to change drivers. There is an old post by author deprius (search for the user name) that describes how to install and configure serial monkey drivers.

[kevdog]

I'll try to update to Ibex with the official release, but I've heard rumors that the kernel bugs that plagued Hardy are still not fixed in the Ibex kernel. Knowing this, I might just plan on sticking to what I know works!

[StephenG]

Well, I'm not dropping connections any longer -- I can't get them at all. I've followed all the steps in the first long posting of this thread -- the the "T" as far as I can tell and am still at a loss. I've tried with and without encryption; I've tried changing channels; I've searched the wireless CD read-mes, lookng for clues or special needs. The card shows, the driver shows, the router shows, but they aren't willing to play with each other. I hate to give up on Ubuntu, but I do need internet connection for the machine, so I have to solve this, and i'm not certain I'm sufficiently fluent in Linux to do a ndiswrapper install. For one thing, every file I need will have to be imported from some other machine and even the Synaptic updater can't work form that machine, so the installs will need to be hand-done, as far as I can tell. I'm feeling overwhelmed here, I must admit.

[kevdog]

I've only been with Ubuntu for about 1.5 years, so to give you some perspective, I remember trying to first get wireless up and going -- it was a pain in the butt!! Ok -- try this thread -- its about the rt73 chipset -- but remember you have the rt61 chipset, so modify accordingly:

http://ubuntuforums.org/showthread.php?t=400236&highlight=serial+monkey

Its slightly different than my method. Just go through it slowly. Its been tested by many. But you want the rt61 download -- good luck.

[StephenG]

Do you realize, Kevdog, that when you add tings like "so modify accordingly" and "good luck" in the same post, you scare me to death? I warned you that this is my first Linux install and experience. I'm trying but 118 pages of post is a lot to absorb especially when the solution found on one page is changed or proven not to work 30 pages later -- and I'm supposed to remember that!?!

I'm still at it and will let you know if I EVER get it working. Thanks for the encouragement.

Damn, damn, damn ... it turns out the whole time that the transmit section of this brand-new-out-of-the-box card was defective. I ended up installing RutilT and when I looked at the control panel and realized that it was telling me that the system was receiving tons of packets but transmitting none I swapped the card out for an identical one I had (I had bought two) and everything immediately started working. Forewarned is forearmed.

Thanks anyway, folks, for the lesson and the help along the way.

[kevdog]

Glad you got it fixed and working. The only way to learn things is to jump in with both feet!

[perriccolo]

Hello.

Today i've installed kubuntu 8.10RC.

I installed drivers for my wi-fi usb card using ndiswrapper, and it works well (i tested it on suse and fedora).

My netword config:
Ip computer: 10.0.0.3
Subnet mask: 255.0.0.0
Gateway (my router IP): 10.0.0.1

WEP password: 12345612345612345612345612
Wi-fi name "Wireless_Mike"

My router doesn' t support DHCP, so i can't use it and i MUST use manual configuration.

Here is what i did:
sudo ifconfig wlan0 down
sudo dhclient -r wlan0
sudo ifconfig wlan0 10.0.0.3 netmask 255.0.0.0 up
sudo route add default gw 10.0.0.1
sudo iwconfig wlan0 essid "Wireless_Mike"
sudo iwconfig wlan0 key 12345612345612345612345612
sudo iwconfig wlan0 mode Managed
sudo dhclient wlan0



but i have in output:
sudo dhclient wlan0
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:14:78:72:97:01
Sending on LPF/wlan0/00:14:78:72:97:01
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
enrico@compiuter:~$


so my pc doesn't connect to wi-fi lan. Is it normal that DHCPDISCOVER uses 255.255.255.255?

Is something wrong in my script? Thank you

[kevdog]

That is strange. Can you post iwlist scan and lshw -C network? Thanks -- very strange.

[StephenG]

Can you tell me what the "dhclient -r" option is, please? I thought it meant remove, but then in the next line you're giving it isntructions. I'm confused about that. These results also seem oddly similar to those I was getting and that turned out to be a non-operable transmitter on the card itself.

[perriccolo]

That is strange. Can you post iwlist scan and lshw -C network? Thanks -- very strange.

i solved using wicd.... So i wont' t touch configuration files....

Thank you for your support

[kevdog]

The dhclient -r statement release any previous dhcp lease.

[scullkrusher]

Hello I have an Atheros wifi card. Last night I installed madwifi drivers and restarted and it worked excellent. Even when I started my computer today it worked fine. However when I put my laptop in suspend and turned it back on I haven't gotten it to work again. Is there some way I can get it working again? Even though I have wireless activated in network manager I cant find a signal.

The reason why I'm asking here is because I'm thinking I may have to manually reactivate my wifi card and I don't know how to go about doing that. I looked everywhere for an answer so any help would be greatly appreciated. I don't want to seem rude and that I'm hijacking your thread but I think there's something to this method that may help get my card working again.

Never mind I got it resolved. Sorry about posting it here. Turns out my problem actually was completely unrelated but I honestly had no clue what was wrong or how to go about fixing it. I was clueless I really thought it had something to do with the discussion here.

[ben22]

Hi,

I am using Hardy. Previously I had no problems to connect to internet either by wifi / ethernet card. Last night I thought someone attacked my ubuntu machine (yeah... it was already very late)... and thus disabled the networking in the top right (Network-Tools). After enabling it today again, it didn't work, so I manually edited the "interfaces" file.


The interfaces file contains



atuo eth0
iface eth0 inet dhcp


When restarting the network with



sudo /etc/init.d/networking restart


It throws a message:



There is already a pid file /var/run/dhclient.eth0.pid with pid 0


then



wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/eth0/00:13:8g:9gd2:dd
Sending on LPF/eth0/00:13:8g:9gd2:dd
Sending on Socket/fallback
DHCPDISCOVER on eht0 to 255.255.255.255 port 67 interval 4
...
No DHCPOFFERS received
No working leases in persistent database - sleeping.


Next it stops NTP server and restarts it


*Stopping NTP server ntpd
... done.
*Starting NTP server ntpd
... done.


My assumption is that there is something wrong with the pid file but don't really know how to continue from here.


iwlist scan shows:


lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
wifi0 Interface doesn't support scanning.

ath0 Scan completed:
...

thx for suggestions
Ben

[ben22]

I reenabled wireless on the affected machine, to have internet again.

When rebooting the following error appeared:



"There was an error starting Gnome Settings Deamon
...
Did not receive a reply. Possible causes incude: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
"



Hi,

I am using Hardy. Previously I had no problems to connect to internet either by wifi / ethernet card. Last night I thought someone attacked my ubuntu machine (yeah... it was already very late)... and thus disabled the networking in the top right (Network-Tools). After enabling it today again, it didn't work, so I manually edited the "interfaces" file.


The interfaces file contains



auto eth0
iface eth0 inet dhcp


When restarting the network with



sudo /etc/init.d/networking restart


It throws a message:



There is already a pid file /var/run/dhclient.eth0.pid with pid 0


then



wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/eth0/00:13:8g:9gd2:dd
Sending on LPF/eth0/00:13:8g:9gd2:dd
Sending on Socket/fallback
DHCPDISCOVER on eht0 to 255.255.255.255 port 67 interval 4
...
No DHCPOFFERS received
No working leases in persistent database - sleeping.


Next it stops NTP server and restarts it


*Stopping NTP server ntpd
... done.
*Starting NTP server ntpd
... done.


My assumption is that there is something wrong with the pid file but don't really know how to continue from here.


iwlist scan shows:


lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
wifi0 Interface doesn't support scanning.

ath0 Scan completed:
...

thx for suggestions
Ben

[kevdog]

Im not sure, however what driver are you trying to use with your wireless card. It seems like you might be trying the madwifi kernel module, but you are going to have to confirm this for me.

lsmod will show you all the currently loaded kernel modules, however please don't post the entire output.

[Akpy]

So.. I'm running Xubuntu 8.10 with RTL 8185 wlan card and I cannot connect to my unencrypted wireless network. Here is what i get..

lshw -C network
*-network
description: Ethernet interface
product: 82557/8/9/0/1 Ethernet Pro 100
vendor: Intel Corporation
physical id: 3
bus info: pci@0000:00:03.0
logical name: eth0
version: 09
serial: 00:10:a4:86:93:ba
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=e100 driverversion=3.5.23-k4-NAPI firmware=N/A ip=192.168.0.106 latency=66 maxlatency=56 mingnt=8 module=e100 multicast=yes
*-network
description: Wireless interface
product: RTL-8185 IEEE 802.11a/b/g Wireless LAN Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:02:00.0
logical name: wmaster0
version: 20
serial: 00:1a:9f:91:8d:67
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=rtl8180 latency=64 maxlatency=64 mingnt=32 module=rtl8180 multicast=yes wireless=IEEE 802.11bg
*-network DISABLED
description: Ethernet interface
physical id: 1
logical name: pan0
serial: 0a:31:34:f1:08:58
capabilities: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A multicast=yes

dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 5673
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:1a:9f:91:8d:67
Sending on LPF/wlan0/00:1a:9f:91:8d:67
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

irda0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1E:AB:A2:78:A0
ESSID:"Telehell"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=79/100 Signal level:17/65
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=0000019154e7e1f3
Extra: Last beacon: 40ms ago

pan0 Interface doesn't support scanning.

First I tried with drivers that come's with Xubuntu 8.10 but didn't get further. So I installed with ndiswrapper WinXp drivers that come with this card. And I did do ifconfig eth0 down. Any ideas?

[kevdog]

The card you have is tricky. I haven't been doing my homework and keeping up with what driver is currently working for rtl based cards. It used to a long time ago (Feisty) be ndiswrapper with the win98 driver (yes win98). I know there is a built-in driver in the kernel but it is buggy. I'm not sure what the current driver to use is.

It seems like wlan0 is picking up networks.

Can you list

ifconfig
iwlist scan
lshw -C network

I think you may have posted some of this stuff up above, just want to verify a few things.

[Akpy]

ifconfig
eth0 Link encap:Ethernet HWaddr 00:10:a4:86:93:ba
inet addr:192.168.0.104 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::210:a4ff:fe86:93ba/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3736 errors:0 dropped:0 overruns:0 frame:0
TX packets:3044 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4429059 (4.4 MB) TX bytes:421849 (421.8 KB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:352 errors:0 dropped:0 overruns:0 frame:0
TX packets:352 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:27616 (27.6 KB) TX bytes:27616 (27.6 KB)

wlan0 Link encap:Ethernet HWaddr 00:1a:9f:91:8d:67
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wmaster0 Link encap:UNSPEC HWaddr 00-1A-9F-91-8D-67-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


iwlist scan mostly (and now) gives this
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

irda0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 No scan results

pan0 Interface doesn't support scanning.


but sometimes
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

irda0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1E:AB:A2:78:A0
ESSID:"Telehell"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=79/100 Signal level:17/65
Encryption keyff
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=0000019154e7e1f3
Extra: Last beacon: 40ms ago

pan0 Interface doesn't support scanning.


and lshw -C network

*-network DISABLED
description: Ethernet interface
product: 82557/8/9/0/1 Ethernet Pro 100
vendor: Intel Corporation
physical id: 3
bus info: pci@0000:00:03.0
logical name: eth0
version: 09
serial: 00:10:a4:86:93:ba
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=e100 driverversion=3.5.23-k4-NAPI firmware=N/A latency=66 maxlatency=56 mingnt=8 module=e100 multicast=yes
*-network
description: Wireless interface
product: RTL-8185 IEEE 802.11a/b/g Wireless LAN Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:02:00.0
logical name: wmaster0
version: 20
serial: 00:1a:9f:91:8d:67
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=rtl8180 latency=64 maxlatency=64 mingnt=32 module=rtl8180 multicast=yes wireless=IEEE 802.11bg
*-network DISABLED
description: Ethernet interface
physical id: 1
logical name: pan0
serial: 0a:31:34:f1:08:58
capabilities: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A multicast=yes

Should I try with win98 driver or have you any other tricks to try?

[kevdog]

I would guess the rtl8180 driver is the problem. Have you done a search on the Ubuntu forums or in google to discover if any other workarounds for this driver are offered by others? Again its very difficult for me to troubleshoot this particular chipset without owning a card which contains the chipset. If you know how to install ndiswrapper, you could quickly blacklist the rtl8180 driver, install ndiswrapper in combination with the win98 driver and see if this works. You would know within minutes if this was a viable solution.

[tsunadehime]

cool thx for ur help dude:KS

[thierrybo]

__________________________________________________ __________________________
WPA Connection - WPA-PSK or WPA2-PSK (PSK=Pre-Shared Key) or WPA-EAP-TLS

For uses of Ra-based chipsets: rt61, rt73, rt2500 please skip directly to the WPA Section entitled WPA with Ra based chipsets

Hi,

this is not true since Hardy using new rt20xx Serialmonkey drivers compatibles with "wext" driver. I just used your standard instructions for "WPA Connection - WPA-PSK or WPA2-PSK (PSK=Pre-
Shared Key) or WPA-EAP-TLS" with my RT2500 PCI card and WPA2 on Intrepid and it works out of the box.

[drpaul]

kevdog:

This isn't wireless, but you seem to know how to deal with network connections.

I'm running 8.04 up to date. When I try to run 8.10 from the basic version, my hardwired connection can't get an address from dhclient. Here is the output [my wireless connection works fine]


ubuntu@ubuntu:~$ sudo ifconfig eth0 down
ubuntu@ubuntu:~$ sudo dhclient -r eth0
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:16:36:b3:b4:24
Sending on LPF/eth0/00:16:36:b3:b4:24
Sending on Socket/fallback
ubuntu@ubuntu:~$ sudo ifconfig eth0 up
ubuntu@ubuntu:~$ sudo dhclient eth0
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
SIOCSIFADDR: No buffer space available
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:16:36:b3:b4:24
Sending on LPF/eth0/00:16:36:b3:b4:24
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
send_packet: Message too long
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Thanks for your help.

Paul

[kevdog]

Paul

What does ifconfig and lshw -C network show.

[drpaul]

OK. Here's ifconfig in the state where I enabled wireless [have to bring down eth0 or connection to the Web doesn't work. different from 8.04 where whichever interface is working seems to be used. this is b4 I took eth0 down]


eth0 Link encap:Ethernet HWaddr 00:16:36:b3:b4:24
UP BROADCAST RUNNING MULTICAST MTU:64 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2295 (2.2 KB) TX bytes:1835 (1.8 KB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:3592 errors:0 dropped:0 overruns:0 frame:0
TX packets:3592 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:168832 (168.8 KB) TX bytes:168832 (168.8 KB)

wlan0 Link encap:Ethernet HWaddr 00:18:de:1c:27:7e
inet addr:192.168.2.47 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::218:deff:fe1c:277e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1450 (1.4 KB) TX bytes:4427 (4.4 KB)

wmaster0 Link encap:UNSPEC HWaddr 00-18-DE-1C-27-7E-37-37-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Here is lshw -C network
This is after I took eth0 down


*-network
description: Wireless interface
product: PRO/Wireless 3945ABG [Golan] Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: wmaster0
version: 02
serial: 00:18:de:1c:27:7e
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl3945 ip=192.168.2.47 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11abg
*-network DISABLED
description: Ethernet interface
product: PRO/100 VE Network Connection
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:05:08.0
logical name: eth0
version: 02
serial: 00:16:36:b3:b4:24
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.23-k4-NAPI duplex=full firmware=N/A latency=64 link=yes maxlatency=56 mingnt=8 module=e100 multicast=yes port=MII speed=100MB/s
*-network DISABLED
description: Ethernet interface
physical id: 1
logical name: pan0
serial: 06:4d:21:03:14:9e
capabilities: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes

Hope this tells you something.

Paul

[kevdog]

This part tells me your interface is disabled:

*-network DISABLED
description: Ethernet interface
product: PRO/100 VE Network Connection
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:05:08.0
logical name: eth0
version: 02
serial: 00:16:36:b3:b4:24
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e100

e100 is a wired interface. Something is happening to disable the interface. Have you checked:
dmesg | more

[drpaul]

kevdog-

I haven't checked dmesg yet, but when that data was collected eth0 was down because I executed

sudo ifconfig eth0 down

so that the system would use wlan0 to connect to the internet. This seems to be necessary with 8.10. Note that there is no IP address assigned to that interface. If I did that in 8.04 it would have one.

Paul

[kevdog]

Ok, so did you get the problem solved?

[drpaul]

Kevdog-

No. I'm just about to reboot into 8.10. What should I look for in dmesg?

Paul

[kevdog]

Make sure you take the wireless interface down, and then enable the wired interface

something like

sudo ifconfig wlan0 down
sudo ifconfig eth0 up


Dont post all of desmg. If you do end up posting part of it, only the part relevant to your network card -- it will be in a group so it should be easy to spot!

[drpaul]

kevdog-

Summary

Did as you suggested. dmesg contains only 2 lines that refer to eth0


[ 4.223709] e100 0000:05:08.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 4.223771] e100 0000:05:08.0: setting latency timer to 64
[ 4.250272] e100 0000:05:08.0: PME# disabled
[ 4.250663] e100: eth0: e100_probe: addr 0xd8000000, irq 20, MAC addr 00:16:36:b3:b4:24


[ 130.088519] pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
[ 135.180135] e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex

Not very informative to me.

After taking wlan0 down and eth0 up, I tried sudo dhclient eth0

Result


ubuntu@ubuntu:~$ sudo dhclient eth0
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
SIOCSIFADDR: No buffer space available
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:16:36:b3:b4:24
Sending on LPF/eth0/00:16:36:b3:b4:24
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
send_packet: Message too long
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Any ideas?

Paul

[kevdog]

Can you post the following -- I don't know why you have a wmaster0. Is this a networking card?

lshw -C network

lsmod

[drpaul]

kevdog-

This has gotten a little weird. I have attached files with the output from the commands you mentioned, but ...

I happened to right click on the little Network Manager icon on the top bar and looked at the connection configuration for eth0. The window that pops up says it has an IP address [the one that I normally get from my router]. However, in a terminal window the ifconfig command does not show that, and ping doesn't work anywhere [says network unreachable].

As to the hardware, it's a hp dv6000 series notebook with Intel chips. It has been working fine through several versions of Ubuntu.

I'm clueless but thankful for your help.

Paul

[kevdog]

Are you trying to connect with the wired e100 driver or the intel iwl driver? Are you using the wired or wireless interface?

[drpaul]

I'm trying to connect with the wired driver, e100. If I disable it and plug in my WEP key, then wireless works fine.

Paul

[kevh]

Hello Paul and Kevdog
I have been experiencing the same problem with the "send_packet: message too long" error message. I had done a clean install of 8.04.1 to an Acer Aspire One and successfully followed a couple of threads to get it working ok-ish. I upgraded to 8.10 and went through a number of issues before it was once more ok-ish. Having tinkered a lot with the set up of wireless, I decided to do a fresh install of 8.10 rather than use the upgrade. Thats when I lost my wired connection. Apologies but I did not keep any of the ouput but I can say that the syslog was reporting Network Manager errors. Having experimented with various commands from your guide, Kevdog, I notice that, whilst following the syslog updates, the error message "send_packet......" continued to get posted after I had disconnected the ethernet cable. It was then that I guessed it likely to be a software problem.
I have just re-installed 8.04.1 and the wired connection is up and running again.
I will goback through the upgrade route unless you think it worthwhile recreating the problem to log it as a bug.
Kev

[kevh]

Hello,
Just noticed that even with wired up and running I am getting a lot of dropped packets. This was the case when 8.10 was installed. PC sat next to laptop does not have this problem. Please see output from ifconfig in attached txt file. Could this be part of the cause of the problem?

[drpaul]

kevh-

that's a huge # of dropped packets compared to # rx'd or tx'd. Is that in 8.10 or 8.04? I would suspect there is a software problem :-))

Paul

[kevh]

Paul,
Problem solved for me. I noticed that MTU was set to 64 on eth0 and when I changed it to 1500 I was able to make the wired connection. I now need to find out how to permanently set MTU to 1500 as it gets reset when I reboot. I still don't know why I am getting all the dropped packets. I have tried using the same cable and port as I use on a PC thats running 8.10 without any connection problems. I suppose it points to a Network card / driver problem.
I have added the ifconfig before and after changing MTU.
Kev

[goodamr]

Thanks alot for this great tutorial!

[kevdog]

Paul,
Problem solved for me. I noticed that MTU was set to 64 on eth0 and when I changed it to 1500 I was able to make the wired connection. I now need to find out how to permanently set MTU to 1500 as it gets reset when I reboot. I still don't know why I am getting all the dropped packets. I have tried using the same cable and port as I use on a PC thats running 8.10 without any connection problems. I suppose it points to a Network card / driver problem.
I have added the ifconfig before and after changing MTU.
Kev

Well, I don't know your method you used to change the setting, but it can always be done manually like:
sudo ifconfig wlan0 mtu 1500

[drpaul]

kevh-

I've got the same problem! Now we've got something to fix!

:KS

Paul

[kevdog]

Thanks alot for this great tutorial!

A good thanks is always nice amidst a plethora of off-topic rants!:)

[drpaul]

kevdog, kevh-

Yes, indeed, changing MTU manually does allow me to connect with eth0. Still don't know how to make it permanent, but I can't test that until I install to disk.

Seems to me that this should be reported as a bug. This would be a disaster for someone trying to evaluate Ubuntu.

Sorry to have bugged you, kevdog, but that's what you get for being smart. :lolflag:

Paul

[kevdog]

dr paul

Once you get things up and running, it is rather easy to make thing permanent.

You can add the line in a few places
/etc/rc.local

/etc/network/interfaces

Run a script or .bash file prior to using the card

Run network manager with manual configuration so it reads the parameters in /etc/network/interfaces

Dump network manager, use wicd, and add this parameter to the wired template it uses when connecting.

The easiest would be to add the following to /etc/rc.local (editing the file as root)

Above the exit 0 line
ifconfig eth0 mtu 1500

save the file. This file is read during the boot process so it will be active at the next boot.

Easy right?

[kevh]

Thanks from me too kevdog. It was reading through your how to that gave me the confidence to try out a few of the commands in terminal. I will try the change to /etc/rc.local.

[kevdog]

Try to report back too guys and let me know if it works. I'll add it to the tutorial with credit to both of you if you can give me some feedback.

Also if you can specifically tell me what cards you guys have:
lspci -nnm

Along with the specific driver you are using:
lshw -C network (only present whatever networking device you are using).

I don't know if this is a chipset issue, or just specific to a few specific cards in general. Perhaps you could help me out with this one.


As far as terminal commands -- you don't want to get me started on the utility of knowing some basic network terminal commands. Please learn at least the basics. They are going to get you out of a jam more than once. I was once a novice just like all of you only a year ago. After going back and forth between network manager/wicd, I finally made a comittment to learn some terminal commands to help me figure out what was going on. After reading hundreds of hours on many, many websites, I finally summarized my findings and wrote my tutorial. I'm not saying its a definitive piece of work, however it will give you the basics to get out of just about any jam you are in -- or at least the ability to recognize where the problem exists. If you are serious about using linux, take the time -- like an hour or two -- to sit down and play with the terminal commands. You will quickly figure out, you need no gui or third party interface to make a network connection over than the basic networking libraries contained within the kernel itself. It would be well worth your effort if you are serious about expanding your knowledge base and overall confidence.

[kevh]

Hello kevdog. Apologies for the tardy reply.
I have listed the output from lcpci -nnm and from lshw -C network (for eth0) as you requested. I hope this helps someone else.
Once again thanks for the help. I will continue to "have a play" and enjoy the quest to learn more about Ubuntu. (even if I do sometimes seem to be going round the same circles)
Regards
Kev

[drpaul]

kevdog-

Now I've got a wireless question! Have replaced my old Belkin router with a brand spanking new Linksys WRT110. I have no trouble connecting computers with WEP [in 8.04]. When trying WPA, I have got to the stage where I get this output


paul@hppaul:~$ sudo wpa_supplicant -Dwext -ieth1 -c/etc/wpa_supplicant.conf
Trying to associate with 00:1e:e5:a1:f1:1f (SSID='cozycave' freq=2452 MHz)
Associated with 00:1e:e5:a1:f1:1f
WPA: Key negotiation completed with 00:1e:e5:a1:f1:1f [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:1e:e5:a1:f1:1f completed (auth) [id=0 id_str=]



The command never completes?????? What am I doing wrong?

Second issue is when booting from an Intrepid Live CD. iwlist shows many wireless networks in my neighborhood, but not mine. Any ideas?

Thanks

Paul

[kevdog]

No that command is working as expected -- that is what you want!! You should be smiling right now and very relieved.

This is what you want to do to connect (do either of the following):

#1 Use this as your syntax to send it to the background:
sudo wpa_supplicant -B -Dwext -ieth1 -c/etc/wpa_supplicant.conf

Then type
sudo dhclient eth1

#2 Just pop open another terminal window and type and the command prompt

sudo dhclient eth1

That is all you need to do --- this is no guarantee you will be given dhcp lease, however the wpa authentication is definitely a go!!!

BTW
What chipset comes with that device?? I'm guessing it Broadcom based?
lshw -C network will give you the driver you are using!

[drpaul]

Thanks. the -B makes it work. STSOADH.

I'm working on a hp dv6000 series notebook with all Intel chips. Driver is iwl3945. Have only tried WPA so far, but if I can get my old [2003] SP Toshiba to handle WPA then I will experiment further.

Still don't have a clue to the failure of 8.10 to see the wireless output from the new router.

Paul

[msbealo]

OK,

I have a Belkin F5D7010 wireless PCIMCIA card on an Acer 1350.

I'm following the guide and I have the following problems.

Unencrypted Connection - I turn off my routers security and follow the instructions. I get no errors but when I do the last line I get:

:~$ sudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 12263
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:11:50:04:31:aa
Sending on LPF/wlan0/00:11:50:04:31:aa
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Again, after reboot I tried again and got the same result. i.e. Nothing. When I try this the first time I got it working with no security with both static and dhcp. However, I then moved onto the security section and somehow broke the wireless again.

Anyhow, I am confused about one of the WPA based commands.


:~$ sudo wpa_supplicant -w -D wext -i wlan0 -c /etc/wpa_supplicant.conf -dd
wpa_supplicant: invalid option -- 'w'

If I remove the 'w' I get a whole LOAD of output which I don't think I should bother posting here, but I unfortunately do not get a connection.

It was about at this point that I thought that I might just go with an un-secure network for a day or two.. however I couldn't get things working again even though I traced my steps back and even rebooted a couple of times. Thoroughly head scratching.

Mark

[kevdog]

I need to update the thread b/c the newer version of wpa_supplicant doesn't recognize the -w option anymore. They dropped this option. So you don't need it. With your output do not include the -dd flag, but post the result of wpa_supplicant when you run the command along with
iwlist scan.

[miromiro]

This is quite odd (at least to me). I have been running Ubuntu 7.10 and then 8.04 on my laptop and both had wireless working out of the box. Last weekend I installed Debian Etch (stable) and during the install I entered my WEP key and was able to download the necessary packages. Once the install was complete and I booted into the GUI, I could see the wireless network, but can't connect.

I am keen to stick with Debian & understand what is happening, so any assistance would be greatly appreciated.

lscpi


00:00.0 Host bridge: ATI Technologies Inc RS200/RS200M AGP Bridge [IGP 340M] (rev 02)
00:01.0 PCI bridge: ATI Technologies Inc PCI Bridge [IGP 340M]
00:06.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link Controller Audio Device (rev 02)
00:07.0 ISA bridge: ALi Corporation M1533/M1535 PCI to ISA Bridge [Aladdin IV/V/V+]
00:08.0 Modem: ALi Corporation M5457 AC'97 Modem Controller
00:09.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01)
00:0a.0 CardBus bridge: O2 Micro, Inc. OZ601/6912/711E0 CardBus/SmartCardBus Controller
00:0b.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 50)
00:0b.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 50)
00:0b.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 51)
00:0c.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link)
00:10.0 IDE interface: ALi Corporation M5229 IDE (rev c4)
00:11.0 Bridge: ALi Corporation M7101 Power Management Controller [PMU]
00:12.0 Ethernet controller: National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon IGP 330M/340M/350M

lshw -C network

*-network:0
description: Wireless interface
product: Prism 2.5 Wavelan chipset
vendor: Intersil Corporation
physical id: 9
bus info: pci@00:09.0
logical name: eth1
version: 01
serial: 00:02:8a:99:a1:8a
width: 32 bits
clock: 33MHz
capabilities: cap_list logical wireless ethernet physical
configuration: broadcast=yes driver=hostap driverversion=0.4.4-kernel firmware=1.4.9 latency=64 multicast=yes wireless=IEEE 802.11b
resources: iomemory:d000a000-d000afff irq:10
*-network:1
description: Ethernet interface
product: DP83815 (MacPhyter) Ethernet Controller
vendor: National Semiconductor Corporation
physical id: 12
bus info: pci@00:12.0
logical name: eth2
version: 00
serial: 00:0b:cd:aa:87:33
size: 10MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical tp mii fibre 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=natsemi driverversion=2.0 duplex=half latency=90 link=no maxlatency=52 mingnt=11 multicast=yes port=twisted pair speed=10MB/s
resources: ioport:2400-24ff iomemory:d0008000-d0008fff irq:10
*-network DISABLED
description: IEEE1394 interface
physical id: 1
logical name: eth0
serial: 00:0b:cd:71:a0:aa
capabilities: ieee1394 physical
configuration: broadcast=yes driver=eth1394 multicast=yes

[kevdog]

What commands are you trying?

[miromiro]

Thanks kevdog: I followed the instructions on page 1 of this thread for secured network. I have also disabled WEP to see if that helps. In both cases I got the 'could not bind to DHCP' error...

[kevdog]

Does
sudo iwlist scan

show any networks.

[miromiro]

Yes, it outputs:

eth1 Scan completed :
Cell 01 - Address: 00:20:A6:4F:48:07
ESSID:"cafenet"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Signal level=-82 dBm Noise level=-100 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s
Extra:bcn_int=100
Extra:resp_rate=10

wlan0_rename Scan completed :
Cell 01 - Address: 00:20:A6:4F:48:07
ESSID:"cafenet"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Signal level=-76 dBm Noise level=-100 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s
Extra:bcn_int=100
Extra:resp_rate=10


-- is that helpful?

Cheers,

/J

[kevdog]

Yes it is -- how are providing scan results on interface eth1 and wlan0? Do you have two wirless cards up at the same time?

Please provide the exact commands you are typing also.

[miromiro]

To generate those scan results I just entered 'iwlist scan' - I don't believe that I have two cards up at the same time.

Thanks for perservering with this for me...

/J

[kevdog]

Ok it looks like you are using a prism chipset which I dont know a lot about.

How are you trying to connect to your networks?

[miromiro]

Three ways. First, I tried using the Gnome Network Manager - I can see my network, but entering the WEP key fails. Second, I disabled WEP and tried using GNM - same deal - plenty of spinning icon, no action. Third, I followed the steps on the first page of this thread:

sudo ifconfig eth1 down
sudo dhclient -r eth1
sudo ifconfig eth1 up
sudo iwconfig eth1 essid "ESSID_IN_QUOTES"
sudo iwconfig eth1 key HEX_KEY
sudo iwconfig eth1 mode Managed
sudo dhclient eth1

No result for that either - message about can't bind to DHCP.


/J

[kevdog]

Try connecting manually with no WEP key. Before you enter the commands I want you to open another terminal window and type the following:

tail -f /var/log/syslog

See if any error messages are generated.

Cntl-C will stop the output.

Also change the channel your router is operating on to Channel 11.

[miromiro]

I have changed my operating channel to 11 and disabled WEP. Tried to manually connect, with no result. The output from /var/log/syslog is:

Dec 5 17:47:03 localhost kernel: hdc: tray open
Dec 5 17:47:03 localhost kernel: end_request: I/O error, dev hdc, sector 4
Dec 5 17:49:05 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
Dec 5 17:49:05 localhost kernel: eth1: invalid skb->cb magic (0x00000000, expected 0xf08a36a2)
Dec 5 17:49:12 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9
Dec 5 17:49:12 localhost kernel: eth1: invalid skb->cb magic (0x00000000, expected 0xf08a36a2)
Dec 5 17:49:19 localhost dhclient: receive_packet failed on eth1: Network is down
Dec 5 17:49:21 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 17
Dec 5 17:49:21 localhost dhclient: send_packet: Network is down
Dec 5 17:49:38 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 21
Dec 5 17:49:38 localhost dhclient: send_packet: Network is down
Dec 5 17:49:41 localhost dhclient: Internet Systems Consortium DHCP Client V3.0.4
Dec 5 17:49:41 localhost dhclient: Copyright 2004-2006 Internet Systems Consortium.
Dec 5 17:49:41 localhost dhclient: All rights reserved.
Dec 5 17:49:41 localhost dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Dec 5 17:49:41 localhost dhclient:
Dec 5 17:49:41 localhost dhclient: eth1: unknown hardware address type 801
Dec 5 17:49:41 localhost dhclient: eth1: unknown hardware address type 801
Dec 5 17:49:41 localhost dhclient: Listening on LPF/eth1/
Dec 5 17:49:41 localhost dhclient: Sending on LPF/eth1/
Dec 5 17:49:41 localhost dhclient: Sending on Socket/fallback
Dec 5 17:49:53 localhost kernel: eth1: LinkStatus=1 (Connected)
Dec 5 17:49:53 localhost kernel: eth1: LinkStatus: BSSID=00:1e:e5:51:d1:63
Dec 5 17:49:59 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
Dec 5 17:49:59 localhost kernel: eth1: invalid skb->cb magic (0x00000000, expected 0xf08a36a2)
Dec 5 17:50:06 localhost dhclient: No DHCPOFFERS received.
Dec 5 17:50:06 localhost dhclient: No working leases in persistent database - sleeping.
Dec 5 17:50:06 localhost avahi-autoipd(eth1)[3691]: Found user 'avahi-autoipd' (UID 103) and group 'avahi-autoipd' (GID 104).
Dec 5 17:50:06 localhost avahi-autoipd(eth1)[3691]: Successfully called chroot().
Dec 5 17:50:06 localhost avahi-autoipd(eth1)[3691]: Successfully dropped root privileges.
Dec 5 17:50:06 localhost avahi-autoipd(eth1)[3691]: Interface not suitable.
Dec 5 17:50:15 localhost kernel: eth1: LinkStatus=2 (Disconnected)
Dec 5 17:50:15 localhost kernel: eth1: LinkStatus: BSSID=00:1e:e5:51:d1:63
Dec 5 17:50:15 localhost kernel: eth1: LinkStatus=1 (Connected)
Dec 5 17:50:15 localhost kernel: eth1: LinkStatus: BSSID=00:1e:e5:51:d1:63
Dec 5 17:50:35 localhost dhclient: Internet Systems Consortium DHCP Client V3.0.4
Dec 5 17:50:35 localhost dhclient: Copyright 2004-2006 Internet Systems Consortium.
Dec 5 17:50:35 localhost dhclient: All rights reserved.
Dec 5 17:50:35 localhost dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Dec 5 17:50:35 localhost dhclient:
Dec 5 17:50:35 localhost dhclient: eth1: unknown hardware address type 801
Dec 5 17:50:36 localhost dhclient: eth1: unknown hardware address type 801
Dec 5 17:50:36 localhost dhclient: Listening on LPF/eth1/
Dec 5 17:50:36 localhost dhclient: Sending on LPF/eth1/
Dec 5 17:50:36 localhost dhclient: Sending on Socket/fallback
Dec 5 17:50:38 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
Dec 5 17:50:38 localhost kernel: eth1: invalid skb->cb magic (0x00000000, expected 0xf08a36a2)
Dec 5 17:50:42 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
Dec 5 17:50:42 localhost kernel: eth1: invalid skb->cb magic (0x00000000, expected 0xf08a36a2)
Dec 5 17:50:46 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
Dec 5 17:50:46 localhost kernel: eth1: invalid skb->cb magic (0x00000000, expected 0xf08a36a2)
Dec 5 17:50:51 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 14
Dec 5 17:50:51 localhost kernel: eth1: invalid skb->cb magic (0x00000000, expected 0xf08a36a2)
Dec 5 17:51:05 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 20
Dec 5 17:51:05 localhost kernel: eth1: invalid skb->cb magic (0x00000000, expected 0xf08a36a2)
Dec 5 17:51:25 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10
Dec 5 17:51:25 localhost kernel: eth1: invalid skb->cb magic (0x00000000, expected 0xf08a36a2)
Dec 5 17:51:35 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
Dec 5 17:51:35 localhost kernel: eth1: invalid skb->cb magic (0x00000000, expected 0xf08a36a2)
Dec 5 17:51:39 localhost dhclient: No DHCPOFFERS received.
Dec 5 17:51:39 localhost dhclient: No working leases in persistent database - sleeping.
Dec 5 17:51:39 localhost avahi-autoipd(eth1)[3748]: Found user 'avahi-autoipd' (UID 103) and group 'avahi-autoipd' (GID 104).
Dec 5 17:51:39 localhost avahi-autoipd(eth1)[3748]: Successfully called chroot().
Dec 5 17:51:39 localhost avahi-autoipd(eth1)[3748]: Successfully dropped root privileges.
Dec 5 17:51:39 localhost avahi-autoipd(eth1)[3748]: Interface not suitable.

[kevdog]

I'm really no help to you on this one, however this is the problem:

Dec 5 17:49:05 localhost kernel: eth1: invalid skb->cb magic (0x00000000, expected 0xf08a36a2)

I have no idea what that means!!! Possibly some googling would provide some insight. Use of the hostap driver (the one you are using) is really problematic in Ubuntu. I haven't seen much written about it with Hardy/Intrepid, however with Feisty/Edgy -- big pain in the butt!

Edit -- Google is littered with posts containing that error. Wow!! How old is your wireless card? I'm usually not much of a defeatest, however you might consider another wireless device such as an Atheros based card supported by madwifi. hostap/prism/orinoco etc -- I've seen a lot of kernel issues with modules not being loaded in the right order. I don't have a card, but I haven't figured out any pattern for module loading.

[miromiro]

Thanks kevdog. It is an old laptop & hardly worth the effort of a new card... I think I will just give up on Debian with this one and go back to Hardy.

I appreciate your efforts on this. Cheers.

UPDATE: Reinstalled Hardy and it worked from the get-go. Not sure why it fails in Debian, but most likely reason is PEBKAC...

[kevdog]

Its probably related to the kernel version. The hostap drivers are compiled into the linux kernel. With different kernel versions, linus and his team, seem always to screw up configurations that were working previously, and fix others. My laptops graphics controller (intel 850) worked great in Feisty, but has been on the fritz since. I never understand why things break depending on kernel version. I guess it shows you that hardware compatibility is an issue any linux system.

[KC1117]

In continuing from my original thread you replied to...I successfully changed my router settings to WPA-personal and my laptop with Vista 0/S connected properly. If you need more info than follows to offer guidance let me know. Thanks again. KC

The scan with Ubuntu shows all the available networks- Mine is "OurNetwork" but I'm not connected to either the unsecure or the secure.

I read on an answer to an earlier comment in this thread that following this chain of commands will keep me from connecting to wireless at roaming locations. Did I interpret that correctly or was it referring to a specific problem that user asked you about?

I did run the commands on the first post with these results:
kelly@kelly-laptop:~$ sudo ifconfig ath0 down
[sudo] password for kelly:
kelly@kelly-laptop:~$ sudo dhclient -r ath0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:1b:9e:ad:15:5f
Sending on LPF/ath0/00:1b:9e:ad:15:5f
Sending on Socket/fallback
kelly@kelly-laptop:~$ sudo wpa_supplicant -Dwext -iath0 -c/etc/wpa_supplicant.conf -dd

Initializing interface 'ath0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'

Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'

Reading configuration file '/etc/wpa_supplicant.conf'
ap_scan=1
ctrl_interface='/var/run/wpa_supplicant'
Line: 4 - start of a new network block
ssid - hexdump_ascii(len=10):
4f 75 72 4e 65 74 77 6f 72 6b OurNetwork
scan_ssid=0 (0x0)
proto: 0x1
key_mgmt: 0x2
PSK (ASCII passphrase) - hexdump_ascii(len=28): [REMOVED]
pairwise: 0x8
group: 0x8
Line 12: network block was not terminated properly.
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Line 12: failed to parse network block.
Failed to read or parse configuration '/etc/wpa_supplicant.conf'.
Failed to add interface ath0
Cancelling scan request
Cancelling authentication timeout
kelly@kelly-laptop:~$
kelly@kelly-laptop:~$ sudo dhclient ath0
There is already a pid file /var/run/dhclient.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:1b:9e:ad:15:5f
Sending on LPF/ath0/00:1b:9e:ad:15:5f
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
kelly@kelly-laptop:~$
kelly@kelly-laptop:~$ iwlist scan
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
wifi0 Interface doesn't support scanning.
ath0 Scan completed :
Cell 01 - (left out all the details of my neighbors networks)
Cell 02 -
Cell 03 - (This is the one my computer connected to and got stuck in until I deleted it)
Address: 00:09:5B:AB:78:EC
ESSID:"NETGEAR"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=7/70 Signal level=-88 dBm Noise level=-95 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Extra:bcn_int=100
Cell 04 -
CELL 5 is my personal home network
Cell 05 - Address: 00:1E:C7:1C:41:61
ESSID:"OurNetwork"
Mode:Master
Frequency:2.412 GHz (Channel 1)
Quality=65/70 Signal level=-30 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

[kevdog]

Thanks for posting output

From what you posted:

Line 12: network block was not terminated properly

It seems to be a problem with your wpa_supplicant.conf file. Possibly you could troubleshoot this or simply post the file.

Thanks.

[KC1117]

Thanks for posting output

From what you posted:

Line 12: network block was not terminated properly

It seems to be a problem with your wpa_supplicant.conf file. Possibly you could troubleshoot this or simply post the file.

Thanks.

First I realized I had typed my passphrase incorrectly. Fixed that and got the same output as above. I think this is the file you are asking for:

ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="OurNetwork"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk="hannah...this is a long sentence with nos spaces...made of 62 alphabetic characters"
pairwise=TKIP
group=TKIP

[kevdog]

You forgot the closing }.

So hence it should be like this:

ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="OurNetwork"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk="hannah...this is a long sentence with nos spaces...made of 62 alphabetic characters"
pairwise=TKIP
group=TKIP
}

[KC1117]

Corrected my mistake and finished the instructions. I am now connected to my secure network. Thank you so much.

[kevdog]

If you proceed ever to WPA2 let me know your results. I am lacking on the feedback from this instruction set.

[thierrybo]

here is my interfaces for a WPA2, blind SSID and static IP.

auto lo
iface lo inet loopback


auto wlan0
iface wlan0 inet static
wpa-driver wext
wpa-ssid "MYSSID"
wpa-psk e40...b
wpa-key-mgmt WPA-PSK
wpa-pairwise CCMP
wpa-group CCMP
wpa-proto WPA
wpa-scan-ssid 1
wpa-ap-scan 1
# static ip settings
address 192.168.1.10
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.254
dns-nameservers 208.67.220.220 208.67.222.222 212.27.40.240 212.27.40.240

Note that a full WPA2 would require :
wpa-pairwise CCMP
wpa-group CCMP
wpa-proto RSN (or WPA2 alias)

But my router is not fully compliant, so it use CCMP/AES as WPA2 specs but does not works with wpa-proto RSN. Note also that with Debian wpassupplicant, a separated conf file is not needed.

[kevdog]

Does it work with the following sections modified?

wpa-pairwise CCMP TKIP
wpa-group CCMP TKIP
wpa-proto RSN WPA

According to the man specs you should be able to list more than one value.

[thierrybo]

Yes, but it does'nt help to know "How you are really connected", because in you example, you say "hey, I can connect using all protocols", so the driver will try them until one works (For now I don't know if the order of appearance is relevant or not). If wpa-pairwise CCMP does not work, the driver will try TKIP.
If I use your example, I can connect, but if I check how (using wpa_gui) I can see that I really use

wpa-pairwise CCMP
wpa-group CCMP
wpa-proto WPA

[kevdog]

Which is really WPA(1) with the AES cipher. Which is weird since I thought only AES was described for WPA2. Never understood this phenomena -- then again I don't know how the protocol and encryption schemes actually interact.

[KC1117]

If you proceed ever to WPA2 let me know your results. I am lacking on the feedback from this instruction set.

Okay, before I do that I have another issue that cropped up. My system freezes if I do a "restart" for any reason. It will properly shut down, but won't process through a restart. Any suggestions?
The only system changes I have made are related to the wireless connection.
I noticed this problem before I inserted the final bracket in the conf file. I thought it was a shut down problem that fixed itself, but it appears to only happen on a restart.
I also noticed a new notification (don't know the correct lingo) upon start up about an unrecognized partition that needs to be corrected.

[kevdog]

Why don't you check dmesg which is the boot log for errors. A partition problem shouldn't be a wireless problem per se.

[thierrybo]

Which is really WPA(1) with the AES cipher. Which is weird since I thought only AES was described for WPA2. Never understood this phenomena -- then again I don't know how the protocol and encryption schemes actually interact.

After googling, I found somes (serious?) sources saying that both WPA and WPA2 can use TKIP or AES. So it appears I use WPA with AES. So it means something in WIFI adapter / driver / AP is not WPA2 compatible.

http://www.openxtra.co.uk/articles/wpa-vs-80211i.php -> What is 802.11i? -> 2nd paragraph

http://lists.shmoo.com/pipermail/hostap/2006-January/012443.html (http://lists.shmoo.com/pipermail/hostap/2006-January/012443.html)

[flintflake]

I'm struggling to get WPA2 working. I've reinstalled Hardy 3 times and I still can't get it work. I want to get a static IP so i can use Samba but I can't get the DHCP IP to work first.

Here's my rc.local


ifconfig eth0 down
wpa_supplicant -Dwext -ieth1 -c/etc/wpa_supplicant.conf -dd
dhclient eth1


Upon login, it appears that part of this code works because iwconfig shows that it's connected to my network but it doesn't hand me an IP. If i run sudo dhclient eth1, it hands me a IP in the scope of my network. But I still can't get on the internet.

What am I missing???

**edit**

If i run the sudo dhclient eth1 in a terminal, it does hand me an IP and I can get online with it. Why won't it work within the rc.local script??? I even added sudo to all of those commands in rc.local and it still doesn't work. Any ideas?

__________________________________________________ _______________

Ok.. I added -B to the wpa_supplicant command and i'm on the internet now. It seems to be working ok. Now, how do i turn this connection to a static IP???

[kevdog]

You want this command to be the following:

wpa_supplicant -Dwext -ieth1 -c/etc/wpa_supplicant.conf -dd

replace to

wpa_supplicant -B -Dwext -ieth1 -c/etc/wpa_supplicant.conf

To set a static IP you dont need the dhclient command since this is asking the server for a dynamic IP address.

To set a static IP address this would be similar to the following:

ifconfig eth1 <Desired IP static address> netmask <netmask>

So replace
ifconfig eth1 up

with something like
ifconfig eth1 192.168.1.100 netmask 255.255.255.0 up

Most likely you will also have to specify a default gateway, so in addition you will need something like:

route add default gw 192.168.1.1

[flintflake]

that worked perfectly thanks!

[kevdog]

Please send me your completed script if possible so I can post it on the front page. Thanks

[Heide264]

I have been reading most of this thread trying to establish my WPA connection with a static IP. looking at everything it seems great and as if it is connected, but it will not access any internet pages or log on anything. Any ideas of where to start the debugging process? I have tried the above suggestion, and it seemed to work flawlessly only I cannot actually connect (phantom type connection i guess I would call it). Let me know what outputs would help to diagnose the problem. I really have no idea where the issue is - I was thinking maybe DNS problems.

EDIT - thought I would add that I am running a broadcom chip with the newer STA drivers. the wpasupplicant command didn't come up with any errors and seemed to run flawlessly after adding the -B in.

Please just let me know what outputs would help diagnose where the issue is. Thanks in advance =).

[kevdog]

the -B flag forces the process to run in the background and will not log any errors to the console, so I usually at least the first time run it without the -B flag to see any generated errors. This means however that the remainder of the other commands must be run in a separate terminal to complete the process since the wpa_supplicant process is using the first terminal

Determine first if you are actually assigned an IP address. This is with ifconfig. If you are granted a local IP address, then try to ping your router and an external IP address by IP address rather than name.

Usually if you are granted a legitimate IP address by the router, it usually comes down to one of two possible scenarios -- either a malconfigured route statement (which specifies the gateway) (use route -n), or no available dhcp servers for name lookups. The dns server issue is by far the more common error.

[KC1117]

kevdog: Long story short, I ended up reinstalling and am now setting up my internet connection again. I again have unsecured connection. I thought I could easily redo the same steps I did before, but something else must have changed I am not aware of. After looking around and redoing, I'm getting these messages. Any suggestions:

~$ lshw -C network
WARNING: you should run this program as super-user.
*-network
description: Ethernet interface
product: RTL8101E PCI Express Fast Ethernet controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:11:00.0
logical name: eth0
version: 01
serial: 00:1e:ec:04:a4:4f
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=r8169 driverversion=2.2LK latency=0 module=r8169 multicast=yes
*-network
description: Wireless interface
product: AR242x 802.11abg Wireless PCI Express Adapter
vendor: Atheros Communications Inc.
physical id: 0
bus info: pci@0000:17:00.0
logical name: wifi0
version: 01
serial: 00:1b:9e:ad:15:5f
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=ath_pci ip=192.168.0.8 latency=0 module=ath_pci multicast=yes wireless=IEEE 802.11g
kelly@kelly-laptop:~$ ifconfig
ath0 Link encap:Ethernet HWaddr 00:1b:9e:ad:15:5f
inet addr:192.168.0.8 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::21b:9eff:fead:155f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1
RX packets:198 errors:0 dropped:0 overruns:0 frame:0
TX packets:180 errors:4 dropped:4 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:24988 (24.4 KB) TX bytes:25573 (24.9 KB)

eth0 Link encap:Ethernet HWaddr 00:1e:ec:04:a4:4f
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:220 Base address:0xc000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:264 errors:0 dropped:0 overruns:0 frame:0
TX packets:264 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:13200 (12.8 KB) TX bytes:13200 (12.8 KB)

wifi0 Link encap:UNSPEC HWaddr 00-1B-9E-AD-15-5F-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8334 errors:0 dropped:0 overruns:0 frame:455
TX packets:683 errors:0 dropped:4 overruns:0 carrier:0
collisions:0 txqueuelen:280
RX bytes:727584 (710.5 KB) TX bytes:57365 (56.0 KB)
Interrupt:21



kelly@kelly-laptop:~$ sudo ifconfig ath0 down
kelly@kelly-laptop:~$ sudo dhclient -r ath0
There is already a pid file /var/run/dhclient.pid with pid 7357
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:1b:9e:ad:15:5f
Sending on LPF/ath0/00:1b:9e:ad:15:5f
Sending on Socket/fallback
DHCPRELEASE on ath0 to 192.168.0.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
kelly@kelly-laptop:~$ sudo wpa_supplicant -Dwext -iath0 -c/etc/wpa_supplicant.conf -B
ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/wpa_supplicant/ath0' manually if it is not used anymore
Failed to initialize control interface '/var/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.

kelly@kelly-laptop:~$ sudo dhclient ath0
There is already a pid file /var/run/dhclient.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:1b:9e:ad:15:5f
Sending on LPF/ath0/00:1b:9e:ad:15:5f
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database – sleeping.

My wpa_supplicant.conf file has this in it:

ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="OurNetwork"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk="hannah...the rest of my phrase..."
pairwise=TKIP
group=TKIP
}

[kevdog]

Please instead of using this:

sudo wpa_supplicant -Dwext -iath0 -c/etc/wpa_supplicant.conf -B

do

sudo wpa_supplicant -Dwext -iath0 -c/etc/wpa_supplicant.conf -dd

I need to see some debugging output?

Have you tried the ath5k driver in addition?

[KC1117]

Is your suggestion to change to -Dath5k in the command?

Here is the output:
sudo wpa_supplicant -Dwext -iath0 -c/etc/wpa_supplicant.conf -dd

[sudo] password for kelly:

Initializing interface 'ath0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'

Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'

Reading configuration file '/etc/wpa_supplicant.conf'

ap_scan=1

ctrl_interface='/var/run/wpa_supplicant'

Line: 4 - start of a new network block

ssid - hexdump_ascii(len=10):

4f 75 72 4e 65 74 77 6f 72 6b OurNetwork

scan_ssid=0 (0x0)

proto: 0x1

key_mgmt: 0x2

PSK (ASCII passphrase) - hexdump_ascii(len=58): [REMOVED]

pairwise: 0x8

group: 0x8

PSK (from passphrase) - hexdump(len=32): [REMOVED]

Priority group 0

id=0 ssid='OurNetwork'

Initializing interface (2) 'ath0'

EAPOL: SUPP_PAE entering state DISCONNECTED

EAPOL: KEY_RX entering state NO_KEY_RECEIVE

EAPOL: SUPP_BE entering state INITIALIZE

EAP: EAP entering state DISABLED

EAPOL: External notification - portEnabled=0

EAPOL: External notification - portValid=0

SIOCGIWRANGE: WE(compiled)=22 WE(source)=18 enc_capa=0xf

capabilities: key_mgmt 0xf enc 0xf

WEXT: Operstate: linkmode=1, operstate=5

Own MAC address: 00:1b:9e:ad:15:5f

wpa_driver_wext_set_wpa

wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0

wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0

wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0

wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0

wpa_driver_wext_set_countermeasures

wpa_driver_wext_set_drop_unencrypted

Setting scan request: 0 sec 100000 usec

Added interface ath0

RTM_NEWLINK: operstate=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])

Wireless event: cmd=0x8b06 len=8

RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])

RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added

RTM_NEWLINK: operstate=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])

RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added

State: DISCONNECTED -> SCANNING

Starting AP scan (broadcast SSID)

Trying to get current scan results first without requesting a new scan to speed up initial association

Received 1477 bytes of scan results (7 BSSes)

Scan results: 7

Selecting BSS from priority group 0

Try to find WPA-enabled AP

0: 00:1e:c7:1c:41:61 ssid='OurNetwork' wpa_ie_len=24 rsn_ie_len=0 caps=0x11

selected based on WPA IE

selected WPA AP 00:1e:c7:1c:41:61 ssid='OurNetwork'

Try to find non-WPA AP

Trying to associate with 00:1e:c7:1c:41:61 (SSID='OurNetwork' freq=2412 MHz)

Cancelling scan request

WPA: clearing own WPA/RSN IE

Automatic auth_alg selection: 0x1

WPA: using IEEE 802.11i/D3.0

WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1

WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02

WPA: clearing AP RSN IE

WPA: using GTK TKIP

WPA: using PTK TKIP

WPA: using KEY_MGMT WPA-PSK

WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02

No keys have been configured - skip key clearing

wpa_driver_wext_set_drop_unencrypted

State: SCANNING -> ASSOCIATING

wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)

WEXT: Operstate: linkmode=-1, operstate=5

wpa_driver_wext_associate

[kevdog]

No Im suggesting the ath5k driver rather than the ath_pci.

Something else -- after you type the command for wpa_supplicant -- does the output eventually stop?

[KC1117]

I'm novice enough to not know what you are suggesting regarding the driver.

I haven't let the command go long enough to find out. I will try this afternoon and report back. Thank you.

[kevdog]

Your current driver listed in lshw -C network is ath_pci otherwise known as madwifi. I believe you have either the Atheros 242x or 5007eg chipset (the two chipsets are the same -- not sure why they are referred to by different name). There is a new driver out for this particular chipset called ath5k --- its an alternative to ath_pci or the patched madwifi source.

As far as running wpa_supplicant in the terminal, it should not continuously report disconnected, try the handshaking process, fail, and repeat the process. It might try this a few times, but it should proceed forever -- more than a minute or so. If it does, the wpa authentication handshake is not working -- hence proceeding to the next step with the ifconfig statements is not going to work.

[KC1117]

...it should not continuously report disconnected, try the handshaking process, fail, and repeat the process. It might try this a few times, but it should proceed forever -- more than a minute or so. If it does, the wpa authentication handshake is not working...

It is taking more than 5 minutes.

[kevdog]

So the wpa handshake isn't working. That is what you are telling me.

There are many reasons for this -- all which are not entirely clear to me. Make sure your SSID is not broadcast, has no spaces or funky symbols in the name, and for now make sure its wpa(1) and not wpa2. If you have all these in place and still unsucessful, try another driver. ath5k would be my suggestion, although patched madwifi and ndiswrapper are other solutions as well.

[KC1117]

Before I try ath5k driver, does it matter that I have Hardy 8.04 kernel 2.6.24-23 (it was a different kernel before I reinstalled.

If I'm basically starting from scratch again, should I go ahead and install the latest Ubuntu, to Intrepid? or just stick with what I have?

I haven't reinstalled any of my personal settings or programs since starting over.

[kevdog]

Not sure about this one. I know the ath5k module is in the intrepid backports repository -- possibly in hardy's. Why don't you post another new thread in the Networking Section to see if someone can answer your question.

[KC1117]

Well, I went ahead and installed ath5k. I still have wireless through an unsecured server, but not to my wpa-personal.

I used these commands. At first I got the same type output as before,when I ran the wpa-supplicant it continued to run as before, but then I tried again and it gave me the output below. Maybe its got something in there that might help:

sudo ifconfig wlan0 down
sudo dhclient -r wlan0
sudo wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd

kelly@kelly-laptop:~$ gksu gedit /etc/wpa_supplicant.conf
kelly@kelly-laptop:~$ sudo wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ap_scan=1
ctrl_interface='/var/run/wpa_supplicant'
Line: 4 - start of a new network block
ssid - hexdump_ascii(len=10):
4f 75 72 4e 65 74 77 6f 72 6b OurNetwork
scan_ssid=0 (0x0)
proto: 0x1
key_mgmt: 0x2
PSK (ASCII passphrase) - hexdump_ascii(len=58): [REMOVED]
pairwise: 0x8
group: 0x8
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='OurNetwork'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1b:9e:ad:15:5f
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Using existing control interface directory.
ctrl_iface bind(PF_UNIX) failed: Address already in use
ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore
Failed to initialize control interface '/var/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.

Failed to add interface wlan0
State: DISCONNECTED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Cancelling scan request
Cancelling authentication timeout
WEXT: Operstate: linkmode=0, operstate=6
kelly@kelly-laptop:~$

[kevdog]

Not sure, but did you do what it said and remove the offending file:

sudo rm /var/run/wpa_supplicant/wlan0

[KC1117]

Not sure, but did you do what it said and remove the offending file:

Okay, will do that when I get home tonight.

[KC1117]

Not sure, but did you do what it said and remove the offending file:

sudo rm /var/run/wpa_supplicant/wlan0

I hope I'm not making this harder than it should be. Here are the results of this:
kelly@kelly-laptop:~$ sudo rm /var/run/wpa_supplicant/wlan0
rm: cannot remove `/var/run/wpa_supplicant/wlan0': No such file or directory
kelly@kelly-laptop:~$

I followed the path /var/run...and there is only a wpa_supplicant0 folder. I tried variations of the sudo rm command to see what happened and nothing did. Do I need to be in a different directory to try this?

[kevdog]

Inside /var/run, remove anything close to wpasupplicant, wpa_supplicant, or anything you think might be related.

[wieman01]

Dude, I tried to go through "/etc/network/interfaces" on Intrepid but couldn't get it to work. So I gave your tutorial a shot and it still works as advertised. Big thank you!

This is my configuration for WPA2:

ap_scan=1

network={
ssid="My SSID"
psk="My Key"
key_mgmt=WPA-PSK
proto=RSN
pairwise=CCMP
group=CCMP
}
Note that I had to remove "ctrl_interface=/var/run/wpa_supplicant" which caused a parsing error. Works just fine without it.

Good job!

EDIT:
I am using a static IP address as it lets me boot faster.

[kevdog]

Thanks for feedback -- I'll add a comment about the ctrl_interface -- not sure why that doesn't work. I think however that command is needed if you are going to be using a utility such as wpa_cli or wpa_gui. If not using these programs, I don't think you need a control interface -- however I could be wrong. I usually am using WICD most of the time, however tend to fall back to this method, when installing new versions, or things totally bomb -- which they do from time to time!

[gforeman]

This has solved a problem I have been having with a Netgear WG111v3 wireless device. Thank you very much.

[afeasfaerw23231233]

Hi, I have problem.
sudo wpa_supplicant -D<wext> -i<wlan0> -c/etc/wpa_supplicant.conf -dd
bash: wext: No such file or directory

what to do? thanks!

[kevdog]

Options preferenced with <> mean these are options you must fill in -- flags. If you want wext as the driver type -- which in most cases you do -- its
-Dwext
-i wlan0

Do not use <> explicitly.

[afeasfaerw23231233]

I have followed your instructions and trying to establish a WPA(1) but not success. My chip is Realtek 8187L and currently I'm using ndiswrapper with Realtek 8187L windows 98 driver to establish an unencrypted connection without big problems (but signal strength seems weaker than in win xp)

here's my lshw -C network


*-network
description: Ethernet interface
product: 191 Gigabit Ethernet Adapter
vendor: Silicon Integrated Systems [SiS]
physical id: 4
bus info: pci@0000:00:04.0
logical name: eth0
version: 02
serial: 00:03:0d:af:c3:b5
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=sis190 driverversion=1.2 latency=0 module=sis190 multicast=yes
*-network
description: Wireless interface
physical id: 2
logical name: wlan0
serial: 00:22:43:74:7b:05
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+netrtuw driverversion=1.53+Realtek Semiconductor Corp. multicast=yes wireless=IEEE 802.11g

Here's my /etc/wpa_supplicant.conf


ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="dlink"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk="A57B5675567A65D6765E675E76F51463E33A223A3A3A62B9E8 DD99E0138CEF"
pairwise=TKIP
group=TKIP
}



Here's the result from
sudo dhclient -r wlan0


There is already a pid file /var/run/dhclient.pid with pid 9088
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:22:43:74:7b:05
Sending on LPF/wlan0/00:22:43:74:7b:05
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.123.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.


Here's the result of

sudo wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd

Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ap_scan=1
ctrl_interface='/var/run/wpa_supplicant'
Line: 4 - start of a new network block
ssid - hexdump_ascii(len=5):
64 6c 69 6e 6b dlink
scan_ssid=0 (0x0)
proto: 0x1
key_mgmt: 0x2
PSK (ASCII passphrase) - hexdump_ascii(len=62): [REMOVED]
pairwise: 0x8
group: 0x8
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='dlink'
Initializing interface (2) 'wlan0'
SIOCGIWRANGE: WE(compiled)=22 WE(source)=18 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf flags 0x0
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:22:43:74:7b:05
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Added interface wlan0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b06 len=8
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 254 bytes of scan results (1 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:19:5b:df:63:da ssid='dlink' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
selected based on WPA IE
selected WPA AP 00:19:5b:df:63:da ssid='dlink'
Try to find non-WPA AP
Trying to associate with 00:19:5b:df:63:da (SSID='dlink' freq=2452 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_psk
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b04 len=12
EAPOL: disable timer tick
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8c07 len=55
AssocReq IE wireless event - hexdump(len=47): 00 05 64 6c 69 6e 6b 01 0c 82 84 8b 96 8c 12 98 24 b0 48 60 6c dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:19:5b:df:63:da
Association info event
req_ies - hexdump(len=47): 00 05 64 6c 69 6e 6b 01 0c 82 84 8b 96 8c 12 98 24 b0 48 60 6c dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: set own WPA/RSN IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:19:5b:df:63:da
No keys have been configured - skip key clearing
Associated with 00:19:5b:df:63:da
WPA: Association event - clear replay counter
WPA: Clear old PTK
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: enable timer tick
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RX EAPOL from 00:19:5b:df:63:da
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 0a 7f 7f c0 b4 89 35 a3 be 7d e8 a2 5f a0 a6 cd 5f 9d 42 09 d8 71 27 a8 66 fe 76 79 14 c2 c8 fb 5c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
EAPOL-Key type=254
key_info 0x89 (ver=1 keyidx=0 rsvd=0 Pairwise Ack)
key_length=32 key_data_length=0
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 0a
key_nonce - hexdump(len=32): 7f 7f c0 b4 89 35 a3 be 7d e8 a2 5f a0 a6 cd 5f 9d 42 09 d8 71 27 a8 66 fe 76 79 14 c2 c8 fb 5c
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 0a 7f 7f c0 b4 89 35 a3 be 7d e8 a2 5f a0 a6 cd 5f 9d 42 09 d8 71 27 a8 66 fe 76 79 14 c2 c8 fb 5c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:19:5b:df:63:da (ver=1)
WPA: Renewed SNonce - hexdump(len=32): 2a 68 8b 10 c9 db 15 f5 d3 a7 99 68 0d 29 de f4 14 a2 1e f4 5b a4 34 55 35 cd 65 87 87 99 d1 98
WPA: PTK derivation - A1=00:22:43:74:7b:05 A2=00:19:5b:df:63:da
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: WPA IE for msg 2/4 - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=125): 01 03 00 79 fe 01 09 00 20 00 00 00 00 00 00 00 0a 2a 68 8b 10 c9 db 15 f5 d3 a7 99 68 0d 29 de f4 14 a2 1e f4 5b a4 34 55 35 cd 65 87 87 99 d1 98 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 9d 89 29 a0 8b 09 e0 b8 fb 6c 73 10 7f db 42 43 00 1a dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
RX EAPOL from 00:19:5b:df:63:da
RX EAPOL - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 0b 7f 7f c0 b4 89 35 a3 be 7d e8 a2 5f a0 a6 cd 5f 9d 42 09 d8 71 27 a8 66 fe 76 79 14 c2 c8 fb 5c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 21 5f a8 c5 2d 6e 3c a0 8e 99 d2 0c a3 11 04 44 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
IEEE 802.1X RX: version=1 type=3 length=119
EAPOL-Key type=254
key_info 0x1c9 (ver=1 keyidx=0 rsvd=0 Pairwise Install Ack MIC)
key_length=32 key_data_length=24
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 0b
key_nonce - hexdump(len=32): 7f 7f c0 b4 89 35 a3 be 7d e8 a2 5f a0 a6 cd 5f 9d 42 09 d8 71 27 a8 66 fe 76 79 14 c2 c8 fb 5c
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 21 5f a8 c5 2d 6e 3c a0 8e 99 d2 0c a3 11 04 44
WPA: RX EAPOL-Key - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 0b 7f 7f c0 b4 89 35 a3 be 7d e8 a2 5f a0 a6 cd 5f 9d 42 09 d8 71 27 a8 66 fe 76 79 14 c2 c8 fb 5c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 21 5f a8 c5 2d 6e 3c a0 8e 99 d2 0c a3 11 04 44 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 3 of 4-Way Handshake from 00:19:5b:df:63:da (ver=1)
WPA: IE KeyData - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: Sending EAPOL-Key 4/4
WPA: TX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 01 09 00 20 00 00 00 00 00 00 00 0b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4d d1 16 7c 6c 9f b1 84 78 b5 d4 dc 16 48 d9 17 00 00
WPA: Installing PTK to the driver.
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_wext_set_key: alg=2 key_idx=0 set_tx=1 seq_len=6 key_len=32
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
EAPOL: startWhen --> 0
EAPOL: disable timer tick
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: enable timer tick
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
Added BSSID 00:19:5b:df:63:da into blacklist
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
State: GROUP_HANDSHAKE -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 5 seconds
Scan timeout - try to get results
Received 254 bytes of scan results (1 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:19:5b:df:63:da ssid='dlink' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
selected based on WPA IE
selected WPA AP 00:19:5b:df:63:da ssid='dlink'
Try to find non-WPA AP
Trying to associate with 00:19:5b:df:63:da (SSID='dlink' freq=2452 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_psk
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8c07 len=55
AssocReq IE wireless event - hexdump(len=47): 00 05 64 6c 69 6e 6b 01 0c 82 84 8b 96 8c 12 98 24 b0 48 60 6c dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:19:5b:df:63:da
Association info event
req_ies - hexdump(len=47): 00 05 64 6c 69 6e 6b 01 0c 82 84 8b 96 8c 12 98 24 b0 48 60 6c dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: set own WPA/RSN IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:19:5b:df:63:da
No keys have been configured - skip key clearing
Associated with 00:19:5b:df:63:da
WPA: Association event - clear replay counter
WPA: Clear old PTK
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RX EAPOL from 00:19:5b:df:63:da
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 0c 35 97 61 70 e2 6f 2d ea e0 8c e4 10 7f 74 a3 68 9a 2a a0 2c 8f 58 75 a5 0c ff 7e a8 1e b9 75 5b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
EAPOL-Key type=254
key_info 0x89 (ver=1 keyidx=0 rsvd=0 Pairwise Ack)
key_length=32 key_data_length=0
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 0c
key_nonce - hexdump(len=32): 35 97 61 70 e2 6f 2d ea e0 8c e4 10 7f 74 a3 68 9a 2a a0 2c 8f 58 75 a5 0c ff 7e a8 1e b9 75 5b
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 0c 35 97 61 70 e2 6f 2d ea e0 8c e4 10 7f 74 a3 68 9a 2a a0 2c 8f 58 75 a5 0c ff 7e a8 1e b9 75 5b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:19:5b:df:63:da (ver=1)
WPA: Renewed SNonce - hexdump(len=32): a3 cd e4 55 a9 fe 60 c3 99 e9 55 26 00 2e 52 92 87 76 f5 33 cc 71 f3 e0 b4 f9 49 69 f2 a4 83 67
WPA: PTK derivation - A1=00:22:43:74:7b:05 A2=00:19:5b:df:63:da
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: WPA IE for msg 2/4 - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=125): 01 03 00 79 fe 01 09 00 20 00 00 00 00 00 00 00 0c a3 cd e4 55 a9 fe 60 c3 99 e9 55 26 00 2e 52 92 87 76 f5 33 cc 71 f3 e0 b4 f9 49 69 f2 a4 83 67 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 27 98 a1 01 0b 80 fd e2 a3 54 2d bc 1b a3 a3 7d 00 1a dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
RX EAPOL from 00:19:5b:df:63:da
RX EAPOL - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 0d 35 97 61 70 e2 6f 2d ea e0 8c e4 10 7f 74 a3 68 9a 2a a0 2c 8f 58 75 a5 0c ff 7e a8 1e b9 75 5b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 12 68 83 09 99 fb 96 92 77 da cb d0 e6 53 79 ad 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
IEEE 802.1X RX: version=1 type=3 length=119
EAPOL-Key type=254
key_info 0x1c9 (ver=1 keyidx=0 rsvd=0 Pairwise Install Ack MIC)
key_length=32 key_data_length=24
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 0d
key_nonce - hexdump(len=32): 35 97 61 70 e2 6f 2d ea e0 8c e4 10 7f 74 a3 68 9a 2a a0 2c 8f 58 75 a5 0c ff 7e a8 1e b9 75 5b
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 12 68 83 09 99 fb 96 92 77 da cb d0 e6 53 79 ad
WPA: RX EAPOL-Key - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 0d 35 97 61 70 e2 6f 2d ea e0 8c e4 10 7f 74 a3 68 9a 2a a0 2c 8f 58 75 a5 0c ff 7e a8 1e b9 75 5b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 12 68 83 09 99 fb 96 92 77 da cb d0 e6 53 79 ad 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 3 of 4-Way Handshake from 00:19:5b:df:63:da (ver=1)
WPA: IE KeyData - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: Sending EAPOL-Key 4/4
WPA: TX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 01 09 00 20 00 00 00 00 00 00 00 0d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90 95 38 3c 76 88 cf 6d fa f4 a4 6a 41 b7 9d f1 00 00
WPA: Installing PTK to the driver.
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_wext_set_key: alg=2 key_idx=0 set_tx=1 seq_len=6 key_len=32
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
RX EAPOL from 00:19:5b:df:63:da
RX EAPOL - hexdump(len=131): 01 03 00 7f fe 03 91 00 20 00 00 00 00 00 00 00 0e 0c d1 81 07 98 0c db cc 4c 8b fe 5d 36 19 5e 80 1b 04 ce d7 d5 9f f0 61 2d 7b 6c 41 62 13 fd 64 1b 04 ce d7 d5 9f f0 61 2d 7b 6c 41 62 13 fd 66 2b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d8 32 9d d5 46 9e 3a 12 c4 66 c7 45 73 b3 8e c5 00 20 48 8b 9a 22 18 8a 80 24 67 7c 56 b2 69 89 52 f6 9f c6 b3 b2 c9 28 b6 7f cf b7 c0 1a fb 33 87 b8
IEEE 802.1X RX: version=1 type=3 length=127
EAPOL-Key type=254
key_info 0x391 (ver=1 keyidx=1 rsvd=0 Group Ack MIC Secure)
key_length=32 key_data_length=32
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 0e
key_nonce - hexdump(len=32): 0c d1 81 07 98 0c db cc 4c 8b fe 5d 36 19 5e 80 1b 04 ce d7 d5 9f f0 61 2d 7b 6c 41 62 13 fd 64
key_iv - hexdump(len=16): 1b 04 ce d7 d5 9f f0 61 2d 7b 6c 41 62 13 fd 66
key_rsc - hexdump(len=8): 2b 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): d8 32 9d d5 46 9e 3a 12 c4 66 c7 45 73 b3 8e c5
WPA: RX EAPOL-Key - hexdump(len=131): 01 03 00 7f fe 03 91 00 20 00 00 00 00 00 00 00 0e 0c d1 81 07 98 0c db cc 4c 8b fe 5d 36 19 5e 80 1b 04 ce d7 d5 9f f0 61 2d 7b 6c 41 62 13 fd 64 1b 04 ce d7 d5 9f f0 61 2d 7b 6c 41 62 13 fd 66 2b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d8 32 9d d5 46 9e 3a 12 c4 66 c7 45 73 b3 8e c5 00 20 48 8b 9a 22 18 8a 80 24 67 7c 56 b2 69 89 52 f6 9f c6 b3 b2 c9 28 b6 7f cf b7 c0 1a fb 33 87 b8
WPA: RX message 1 of Group Key Handshake from 00:19:5b:df:63:da (ver=1)
State: GROUP_HANDSHAKE -> GROUP_HANDSHAKE
WPA: Group Key - hexdump(len=32): [REMOVED]
WPA: Installing GTK to the driver (keyidx=1 tx=0 len=32).
WPA: RSC - hexdump(len=6): 2b 00 00 00 00 00
wpa_driver_wext_set_key: alg=2 key_idx=1 set_tx=0 seq_len=6 key_len=32
WPA: Sending EAPOL-Key 2/2
WPA: TX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 03 11 00 20 00 00 00 00 00 00 00 0e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 63 5f 31 77 05 d7 11 ec 37 d9 db f1 74 db 32 1d 00 00
WPA: Key negotiation completed with 00:19:5b:df:63:da [PTK=TKIP GTK=TKIP]
Cancelling authentication timeout
Removed BSSID 00:19:5b:df:63:da from blacklist
State: GROUP_HANDSHAKE -> COMPLETED
CTRL-EVENT-CONNECTED - Connection to 00:19:5b:df:63:da completed (auth) [id=0 id_str=]
wpa_driver_wext_set_operstate: operstate 0->1 (UP)
WEXT: Operstate: linkmode=-1, operstate=6
EAPOL: External notification - portValid=1
EAPOL: External notification - EAP success=1
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state SUCCESS
EAP: EAP entering state DISABLED
EAPOL: SUPP_PAE entering state AUTHENTICATED
EAPOL: SUPP_BE entering state IDLE
EAPOL authentication completed successfully
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RX EAPOL from 00:19:5b:df:63:da
RX EAPOL - hexdump(len=131): 01 03 00 7f fe 03 91 00 20 00 00 00 00 00 00 00 0e 0c d1 81 07 98 0c db cc 4c 8b fe 5d 36 19 5e 80 1b 04 ce d7 d5 9f f0 61 2d 7b 6c 41 62 13 fd 64 1b 04 ce d7 d5 9f f0 61 2d 7b 6c 41 62 13 fd 66 2b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d8 32 9d d5 46 9e 3a 12 c4 66 c7 45 73 b3 8e c5 00 20 48 8b 9a 22 18 8a 80 24 67 7c 56 b2 69 89 52 f6 9f c6 b3 b2 c9 28 b6 7f cf b7 c0 1a fb 33 87 b8
IEEE 802.1X RX: version=1 type=3 length=127
EAPOL-Key type=254
key_info 0x391 (ver=1 keyidx=1 rsvd=0 Group Ack MIC Secure)
key_length=32 key_data_length=32
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 0e
key_nonce - hexdump(len=32): 0c d1 81 07 98 0c db cc 4c 8b fe 5d 36 19 5e 80 1b 04 ce d7 d5 9f f0 61 2d 7b 6c 41 62 13 fd 64
key_iv - hexdump(len=16): 1b 04 ce d7 d5 9f f0 61 2d 7b 6c 41 62 13 fd 66
key_rsc - hexdump(len=8): 2b 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): d8 32 9d d5 46 9e 3a 12 c4 66 c7 45 73 b3 8e c5
WPA: RX EAPOL-Key - hexdump(len=131): 01 03 00 7f fe 03 91 00 20 00 00 00 00 00 00 00 0e 0c d1 81 07 98 0c db cc 4c 8b fe 5d 36 19 5e 80 1b 04 ce d7 d5 9f f0 61 2d 7b 6c 41 62 13 fd 64 1b 04 ce d7 d5 9f f0 61 2d 7b 6c 41 62 13 fd 66 2b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d8 32 9d d5 46 9e 3a 12 c4 66 c7 45 73 b3 8e c5 00 20 48 8b 9a 22 18 8a 80 24 67 7c 56 b2 69 89 52 f6 9f c6 b3 b2 c9 28 b6 7f cf b7 c0 1a fb 33 87 b8
WPA: EAPOL-Key Replay Counter did not increase - dropping packet
EAPOL: startWhen --> 0
EAPOL: disable timer tick
^CCTRL-EVENT-TERMINATING - signal 2 received
Removing interface wlan0
State: COMPLETED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 1->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_deauthenticate
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Cancelling scan request
Cancelling authentication timeout
WEXT: Operstate: linkmode=0, operstate=6

Here's the result of

sudo dhclient wlan0


Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:22:43:74:7b:05
Sending on LPF/wlan0/00:22:43:74:7b:05
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


In my router I choose WPA-PSK and TKIP.

Sorry for my long post. Thanks in advance!

[kevdog]

Just a follow up

psk="A57B5675567A65D6765E675E76F51463E33A223A3A3A62B9E8 DD99E0138CEF"

Is the password given above the hex key or the actual password? It looks like hex to me!

[sarel29]

Hi, thanks for that. I'm still having a problem with my connection though. When I type in sudo dhclient eth1, this is what I get

Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:0e:35:8a:8e:94
Sending on LPF/eth1/00:0e:35:8a:8e:94
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 225.225.225.225 port 67 interval 5
DHCPDISCOVER on eth1 to 225.225.225.225 port 67 interval 5
DHCPDISCOVER on eth1 to 225.225.225.225 port 67 interval 5
DHCPDISCOVER on eth1 to 225.225.225.225 port 67 interval 9
DHCPDISCOVER on eth1 to 225.225.225.225 port 67 interval 10
DHCPDISCOVER on eth1 to 225.225.225.225 port 67 interval 10
DHCPDISCOVER on eth1 to 225.225.225.225 port 67 interval 16
DHCPDISCOVER on eth1 to 225.225.225.225 port 67 interval 1
No DHCPOFFERS recieved.
No working leases in persistent database - sleeping.

Please tell me how I can wake it up?

Many thanks.

[afeasfaerw23231233]

Just a follow up

psk="A57B5675567A65D6765E675E76F51463E33A223A3A3A62B9E8 DD99E0138CEF"

Is the password given above the hex key or the actual password? It looks like hex to me!

I don't know if it is HEX or not. But I think it is the actual password. That long password was typed by me manually. This time I set the key as abcdefgh and set it again. Please have a look at my router setting page (see screenshots).


sudo dhclient -r wlan0
There is already a pid file /var/run/dhclient.pid with pid 6136
killed old client process, removed PID file

(Is this pid file having problem?)

Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:22:43:74:7b:05
Sending on LPF/wlan0/00:22:43:74:7b:05
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.123.1 port 67




sudo wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd
[sudo] password for coppen:
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ap_scan=1
ctrl_interface='/var/run/wpa_supplicant'
Line: 4 - start of a new network block
ssid - hexdump_ascii(len=5):
64 6c 69 6e 6b dlink
scan_ssid=0 (0x0)
proto: 0x1
key_mgmt: 0x2
PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED]
pairwise: 0x8
group: 0x8
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='dlink'
Initializing interface (2) 'wlan0'
SIOCGIWRANGE: WE(compiled)=22 WE(source)=18 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf flags 0x0
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:22:43:74:7b:05
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Added interface wlan0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b06 len=8
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 254 bytes of scan results (1 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:19:5b:df:63:da ssid='dlink' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
selected based on WPA IE
selected WPA AP 00:19:5b:df:63:da ssid='dlink'
Try to find non-WPA AP
Trying to associate with 00:19:5b:df:63:da (SSID='dlink' freq=2452 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_psk
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b04 len=12
EAPOL: disable timer tick
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8c07 len=55
AssocReq IE wireless event - hexdump(len=47): 00 05 64 6c 69 6e 6b 01 0c 82 84 8b 96 8c 12 98 24 b0 48 60 6c dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:19:5b:df:63:da
Association info event
req_ies - hexdump(len=47): 00 05 64 6c 69 6e 6b 01 0c 82 84 8b 96 8c 12 98 24 b0 48 60 6c dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: set own WPA/RSN IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:19:5b:df:63:da
No keys have been configured - skip key clearing
Associated with 00:19:5b:df:63:da
WPA: Association event - clear replay counter
WPA: Clear old PTK
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: enable timer tick
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RX EAPOL from 00:19:5b:df:63:da
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 0e 2a 61 4b dd c7 c0 1c b1 ec f5 5c 09 54 ea 08 a4 de ed 21 74 89 2b 6d 0d 75 40 1e ce b6 7a 0d 15 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
EAPOL-Key type=254
key_info 0x89 (ver=1 keyidx=0 rsvd=0 Pairwise Ack)
key_length=32 key_data_length=0
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 0e
key_nonce - hexdump(len=32): 2a 61 4b dd c7 c0 1c b1 ec f5 5c 09 54 ea 08 a4 de ed 21 74 89 2b 6d 0d 75 40 1e ce b6 7a 0d 15
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 0e 2a 61 4b dd c7 c0 1c b1 ec f5 5c 09 54 ea 08 a4 de ed 21 74 89 2b 6d 0d 75 40 1e ce b6 7a 0d 15 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:19:5b:df:63:da (ver=1)
WPA: Renewed SNonce - hexdump(len=32): 6e 18 89 40 ee b5 88 c9 96 ce 02 06 2a 08 02 52 6e b6 40 3f e4 14 06 03 8f a8 12 8b 50 fa 33 20
WPA: PTK derivation - A1=00:22:43:74:7b:05 A2=00:19:5b:df:63:da
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: WPA IE for msg 2/4 - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=125): 01 03 00 79 fe 01 09 00 20 00 00 00 00 00 00 00 0e 6e 18 89 40 ee b5 88 c9 96 ce 02 06 2a 08 02 52 6e b6 40 3f e4 14 06 03 8f a8 12 8b 50 fa 33 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 9b 7a e0 06 a4 28 79 e8 04 b3 c5 f2 7c e4 f6 26 00 1a dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
RX EAPOL from 00:19:5b:df:63:da
RX EAPOL - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 0f 2a 61 4b dd c7 c0 1c b1 ec f5 5c 09 54 ea 08 a4 de ed 21 74 89 2b 6d 0d 75 40 1e ce b6 7a 0d 15 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a7 42 dc 52 d9 60 30 e3 b9 2d 71 e2 14 1e b0 67 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
IEEE 802.1X RX: version=1 type=3 length=119
EAPOL-Key type=254
key_info 0x1c9 (ver=1 keyidx=0 rsvd=0 Pairwise Install Ack MIC)
key_length=32 key_data_length=24
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 0f
key_nonce - hexdump(len=32): 2a 61 4b dd c7 c0 1c b1 ec f5 5c 09 54 ea 08 a4 de ed 21 74 89 2b 6d 0d 75 40 1e ce b6 7a 0d 15
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): a7 42 dc 52 d9 60 30 e3 b9 2d 71 e2 14 1e b0 67
WPA: RX EAPOL-Key - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 0f 2a 61 4b dd c7 c0 1c b1 ec f5 5c 09 54 ea 08 a4 de ed 21 74 89 2b 6d 0d 75 40 1e ce b6 7a 0d 15 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a7 42 dc 52 d9 60 30 e3 b9 2d 71 e2 14 1e b0 67 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 3 of 4-Way Handshake from 00:19:5b:df:63:da (ver=1)
WPA: IE KeyData - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: Sending EAPOL-Key 4/4
WPA: TX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 01 09 00 20 00 00 00 00 00 00 00 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90 73 8f 15 89 0c 07 77 af 2f f1 32 4b 66 28 8e 00 00
WPA: Installing PTK to the driver.
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_wext_set_key: alg=2 key_idx=0 set_tx=1 seq_len=6 key_len=32
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
EAPOL: startWhen --> 0
EAPOL: disable timer tick
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: enable timer tick
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
Added BSSID 00:19:5b:df:63:da into blacklist
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
State: GROUP_HANDSHAKE -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 5 seconds
Scan timeout - try to get results
Received 254 bytes of scan results (1 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:19:5b:df:63:da ssid='dlink' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
selected based on WPA IE
selected WPA AP 00:19:5b:df:63:da ssid='dlink'
Try to find non-WPA AP
Trying to associate with 00:19:5b:df:63:da (SSID='dlink' freq=2452 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_psk
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8c07 len=55
AssocReq IE wireless event - hexdump(len=47): 00 05 64 6c 69 6e 6b 01 0c 82 84 8b 96 8c 12 98 24 b0 48 60 6c dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:19:5b:df:63:da
Association info event
req_ies - hexdump(len=47): 00 05 64 6c 69 6e 6b 01 0c 82 84 8b 96 8c 12 98 24 b0 48 60 6c dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: set own WPA/RSN IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:19:5b:df:63:da
No keys have been configured - skip key clearing
Associated with 00:19:5b:df:63:da
WPA: Association event - clear replay counter
WPA: Clear old PTK
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RX EAPOL from 00:19:5b:df:63:da
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 10 5c 48 33 8e 13 4b 2c 8a 2a 50 a6 48 b7 09 09 5a 7f 76 95 00 1e 14 a5 d4 09 ab 20 3b fa ac 65 51 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
EAPOL-Key type=254
key_info 0x89 (ver=1 keyidx=0 rsvd=0 Pairwise Ack)
key_length=32 key_data_length=0
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 10
key_nonce - hexdump(len=32): 5c 48 33 8e 13 4b 2c 8a 2a 50 a6 48 b7 09 09 5a 7f 76 95 00 1e 14 a5 d4 09 ab 20 3b fa ac 65 51
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 10 5c 48 33 8e 13 4b 2c 8a 2a 50 a6 48 b7 09 09 5a 7f 76 95 00 1e 14 a5 d4 09 ab 20 3b fa ac 65 51 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:19:5b:df:63:da (ver=1)
WPA: Renewed SNonce - hexdump(len=32): 2a ce 6f 3d 08 67 18 05 af b6 aa 6c 88 98 4e 11 df 30 7f f3 55 11 62 ea e9 e0 e9 00 2c c7 34 a5
WPA: PTK derivation - A1=00:22:43:74:7b:05 A2=00:19:5b:df:63:da
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: WPA IE for msg 2/4 - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=125): 01 03 00 79 fe 01 09 00 20 00 00 00 00 00 00 00 10 2a ce 6f 3d 08 67 18 05 af b6 aa 6c 88 98 4e 11 df 30 7f f3 55 11 62 ea e9 e0 e9 00 2c c7 34 a5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 67 81 48 a6 00 ac 25 32 28 91 e1 3e e0 a4 f3 79 00 1a dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
RX EAPOL from 00:19:5b:df:63:da
RX EAPOL - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 11 5c 48 33 8e 13 4b 2c 8a 2a 50 a6 48 b7 09 09 5a 7f 76 95 00 1e 14 a5 d4 09 ab 20 3b fa ac 65 51 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 61 33 1d 6a e3 6f e3 09 d3 02 28 cd 13 da 0b dd 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
IEEE 802.1X RX: version=1 type=3 length=119
EAPOL-Key type=254
key_info 0x1c9 (ver=1 keyidx=0 rsvd=0 Pairwise Install Ack MIC)
key_length=32 key_data_length=24
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 11
key_nonce - hexdump(len=32): 5c 48 33 8e 13 4b 2c 8a 2a 50 a6 48 b7 09 09 5a 7f 76 95 00 1e 14 a5 d4 09 ab 20 3b fa ac 65 51
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 61 33 1d 6a e3 6f e3 09 d3 02 28 cd 13 da 0b dd
WPA: RX EAPOL-Key - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 11 5c 48 33 8e 13 4b 2c 8a 2a 50 a6 48 b7 09 09 5a 7f 76 95 00 1e 14 a5 d4 09 ab 20 3b fa ac 65 51 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 61 33 1d 6a e3 6f e3 09 d3 02 28 cd 13 da 0b dd 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 3 of 4-Way Handshake from 00:19:5b:df:63:da (ver=1)
WPA: IE KeyData - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: Sending EAPOL-Key 4/4
WPA: TX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 01 09 00 20 00 00 00 00 00 00 00 11 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 97 c0 44 27 3b 4e 27 9f 5a 0f d2 9e 45 d5 82 e0 00 00
WPA: Installing PTK to the driver.
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_wext_set_key: alg=2 key_idx=0 set_tx=1 seq_len=6 key_len=32
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
RX EAPOL from 00:19:5b:df:63:da
RX EAPOL - hexdump(len=131): 01 03 00 7f fe 03 91 00 20 00 00 00 00 00 00 00 12 82 3d d6 ac 22 f5 aa 16 09 06 9c 88 eb c5 33 c6 ef 74 ae a4 04 5a c9 03 2b 03 4f f3 cc eb 0c 05 ef 74 ae a4 04 5a c9 03 2b 03 4f f3 cc eb 0c 07 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f1 b2 dc ec 7d ca 79 5a e1 f0 d5 11 a1 88 af 0f 00 20 af 76 06 32 84 ea 66 9c 91 e0 0a ef 00 7c 8a 3b 79 57 76 b9 9c f1 d5 e7 3c 4f 95 2d d1 6e 05 73
IEEE 802.1X RX: version=1 type=3 length=127
EAPOL-Key type=254
key_info 0x391 (ver=1 keyidx=1 rsvd=0 Group Ack MIC Secure)
key_length=32 key_data_length=32
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 12
key_nonce - hexdump(len=32): 82 3d d6 ac 22 f5 aa 16 09 06 9c 88 eb c5 33 c6 ef 74 ae a4 04 5a c9 03 2b 03 4f f3 cc eb 0c 05
key_iv - hexdump(len=16): ef 74 ae a4 04 5a c9 03 2b 03 4f f3 cc eb 0c 07
key_rsc - hexdump(len=8): 14 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): f1 b2 dc ec 7d ca 79 5a e1 f0 d5 11 a1 88 af 0f
WPA: RX EAPOL-Key - hexdump(len=131): 01 03 00 7f fe 03 91 00 20 00 00 00 00 00 00 00 12 82 3d d6 ac 22 f5 aa 16 09 06 9c 88 eb c5 33 c6 ef 74 ae a4 04 5a c9 03 2b 03 4f f3 cc eb 0c 05 ef 74 ae a4 04 5a c9 03 2b 03 4f f3 cc eb 0c 07 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f1 b2 dc ec 7d ca 79 5a e1 f0 d5 11 a1 88 af 0f 00 20 af 76 06 32 84 ea 66 9c 91 e0 0a ef 00 7c 8a 3b 79 57 76 b9 9c f1 d5 e7 3c 4f 95 2d d1 6e 05 73
WPA: RX message 1 of Group Key Handshake from 00:19:5b:df:63:da (ver=1)
State: GROUP_HANDSHAKE -> GROUP_HANDSHAKE
WPA: Group Key - hexdump(len=32): [REMOVED]
WPA: Installing GTK to the driver (keyidx=1 tx=0 len=32).
WPA: RSC - hexdump(len=6): 14 00 00 00 00 00
wpa_driver_wext_set_key: alg=2 key_idx=1 set_tx=0 seq_len=6 key_len=32
WPA: Sending EAPOL-Key 2/2
WPA: TX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 03 11 00 20 00 00 00 00 00 00 00 12 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3b 99 2c 35 31 ad d2 26 59 4b a9 c9 5b fb 69 e5 00 00
WPA: Key negotiation completed with 00:19:5b:df:63:da [PTK=TKIP GTK=TKIP]
Cancelling authentication timeout
Removed BSSID 00:19:5b:df:63:da from blacklist
State: GROUP_HANDSHAKE -> COMPLETED
CTRL-EVENT-CONNECTED - Connection to 00:19:5b:df:63:da completed (auth) [id=0 id_str=]
wpa_driver_wext_set_operstate: operstate 0->1 (UP)
WEXT: Operstate: linkmode=-1, operstate=6
EAPOL: External notification - portValid=1
EAPOL: External notification - EAP success=1
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state SUCCESS
EAP: EAP entering state DISABLED
EAPOL: SUPP_PAE entering state AUTHENTICATED
EAPOL: SUPP_BE entering state IDLE
EAPOL authentication completed successfully
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RX EAPOL from 00:19:5b:df:63:da
RX EAPOL - hexdump(len=131): 01 03 00 7f fe 03 91 00 20 00 00 00 00 00 00 00 12 82 3d d6 ac 22 f5 aa 16 09 06 9c 88 eb c5 33 c6 ef 74 ae a4 04 5a c9 03 2b 03 4f f3 cc eb 0c 05 ef 74 ae a4 04 5a c9 03 2b 03 4f f3 cc eb 0c 07 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f1 b2 dc ec 7d ca 79 5a e1 f0 d5 11 a1 88 af 0f 00 20 af 76 06 32 84 ea 66 9c 91 e0 0a ef 00 7c 8a 3b 79 57 76 b9 9c f1 d5 e7 3c 4f 95 2d d1 6e 05 73
IEEE 802.1X RX: version=1 type=3 length=127
EAPOL-Key type=254
key_info 0x391 (ver=1 keyidx=1 rsvd=0 Group Ack MIC Secure)
key_length=32 key_data_length=32
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 12
key_nonce - hexdump(len=32): 82 3d d6 ac 22 f5 aa 16 09 06 9c 88 eb c5 33 c6 ef 74 ae a4 04 5a c9 03 2b 03 4f f3 cc eb 0c 05
key_iv - hexdump(len=16): ef 74 ae a4 04 5a c9 03 2b 03 4f f3 cc eb 0c 07
key_rsc - hexdump(len=8): 14 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): f1 b2 dc ec 7d ca 79 5a e1 f0 d5 11 a1 88 af 0f
WPA: RX EAPOL-Key - hexdump(len=131): 01 03 00 7f fe 03 91 00 20 00 00 00 00 00 00 00 12 82 3d d6 ac 22 f5 aa 16 09 06 9c 88 eb c5 33 c6 ef 74 ae a4 04 5a c9 03 2b 03 4f f3 cc eb 0c 05 ef 74 ae a4 04 5a c9 03 2b 03 4f f3 cc eb 0c 07 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f1 b2 dc ec 7d ca 79 5a e1 f0 d5 11 a1 88 af 0f 00 20 af 76 06 32 84 ea 66 9c 91 e0 0a ef 00 7c 8a 3b 79 57 76 b9 9c f1 d5 e7 3c 4f 95 2d d1 6e 05 73
WPA: EAPOL-Key Replay Counter did not increase - dropping packet
EAPOL: startWhen --> 0
EAPOL: disable timer tick

It seemed stop here so I pressed Ctrl+C

^CCTRL-EVENT-TERMINATING - signal 2 received
Removing interface wlan0
State: COMPLETED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 1->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_deauthenticate
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Cancelling scan request
Cancelling authentication timeout
WEXT: Operstate: linkmode=0, operstate=6




sudo dhclient wlan0
[sudo] password for coppen:
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:22:43:74:7b:05
Sending on LPF/wlan0/00:22:43:74:7b:05
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


http://www.freeimagehosting.net/uploads/8fe7fc78dc.png (http://www.freeimagehosting.net/)

http://www.freeimagehosting.net/uploads/4745c3a475.png (http://www.freeimagehosting.net/)

[kevdog]

Run this command in one terminal:

sudo wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd

And this in another:

sudo dhclient wlan0

And just for testing purposes, try a simple password like fred or something. I want to make sure you are not having any transposition errors. Later on you can increase the numbers.

I have the same router as you -- and I can confirm this router should work with what you are trying to do!

[afeasfaerw23231233]

Run this command in one terminal:

sudo wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd

And this in another:

sudo dhclient wlan0

And just for testing purposes, try a simple password like fred or something. I want to make sure you are not having any transposition errors. Later on you can increase the numbers.

I have the same router as you -- and I can confirm this router should work with what you are trying to do!

This time I set it as fredfred as the router doesn't allow me to enter less than 8 characters.


cat /etc/wpa_supplicant.conf
ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="dlink"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk="fredfred"
pairwise=TKIP
group=TKIP
}






coppen@coppen-laptop:~$ sudo dhclient -r wlan0
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:22:43:74:7b:05
Sending on LPF/wlan0/00:22:43:74:7b:05
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.123.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
coppen@coppen-laptop:~$



this time
sudo wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd
is longer than before and some old lines disappear.


RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RX EAPOL from 00:19:5b:df:63:da
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 29 43 05 75 51 ed 21 dd 5a e6 e5 3f 4e 96 32 dc 80 21 e6 08 a2 39 a1 f5 0e 67 d9 3a 7e ea 34 43 41 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
EAPOL-Key type=254
key_info 0x89 (ver=1 keyidx=0 rsvd=0 Pairwise Ack)
key_length=32 key_data_length=0
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 29
key_nonce - hexdump(len=32): 43 05 75 51 ed 21 dd 5a e6 e5 3f 4e 96 32 dc 80 21 e6 08 a2 39 a1 f5 0e 67 d9 3a 7e ea 34 43 41
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 29 43 05 75 51 ed 21 dd 5a e6 e5 3f 4e 96 32 dc 80 21 e6 08 a2 39 a1 f5 0e 67 d9 3a 7e ea 34 43 41 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:19:5b:df:63:da (ver=1)
WPA: Renewed SNonce - hexdump(len=32): 0b d9 61 4e 5f bf 7d 3b 1a 01 86 32 2e 40 e0 87 d8 8f e7 25 98 93 a8 a9 aa ad 81 21 d2 47 47 19
WPA: PTK derivation - A1=00:22:43:74:7b:05 A2=00:19:5b:df:63:da
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: WPA IE for msg 2/4 - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=125): 01 03 00 79 fe 01 09 00 20 00 00 00 00 00 00 00 29 0b d9 61 4e 5f bf 7d 3b 1a 01 86 32 2e 40 e0 87 d8 8f e7 25 98 93 a8 a9 aa ad 81 21 d2 47 47 19 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 84 4a 25 32 d8 39 9c e3 a1 f4 38 f6 7f a0 43 db 00 1a dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
RX EAPOL from 00:19:5b:df:63:da
RX EAPOL - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 2a 43 05 75 51 ed 21 dd 5a e6 e5 3f 4e 96 32 dc 80 21 e6 08 a2 39 a1 f5 0e 67 d9 3a 7e ea 34 43 41 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f5 e0 aa 1f 1c 93 5f f4 42 09 cb 83 49 a9 3b ae 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
IEEE 802.1X RX: version=1 type=3 length=119
EAPOL-Key type=254
key_info 0x1c9 (ver=1 keyidx=0 rsvd=0 Pairwise Install Ack MIC)
key_length=32 key_data_length=24
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 2a
key_nonce - hexdump(len=32): 43 05 75 51 ed 21 dd 5a e6 e5 3f 4e 96 32 dc 80 21 e6 08 a2 39 a1 f5 0e 67 d9 3a 7e ea 34 43 41
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): f5 e0 aa 1f 1c 93 5f f4 42 09 cb 83 49 a9 3b ae
WPA: RX EAPOL-Key - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 2a 43 05 75 51 ed 21 dd 5a e6 e5 3f 4e 96 32 dc 80 21 e6 08 a2 39 a1 f5 0e 67 d9 3a 7e ea 34 43 41 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f5 e0 aa 1f 1c 93 5f f4 42 09 cb 83 49 a9 3b ae 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 3 of 4-Way Handshake from 00:19:5b:df:63:da (ver=1)
WPA: IE KeyData - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: Sending EAPOL-Key 4/4
WPA: TX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 01 09 00 20 00 00 00 00 00 00 00 2a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4a a0 77 aa fe de fa 91 ab 7b 00 58 1e da 9c 84 00 00
WPA: Installing PTK to the driver.
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_wext_set_key: alg=2 key_idx=0 set_tx=1 seq_len=6 key_len=32
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
EAPOL: startWhen --> 0
EAPOL: disable timer tick
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: enable timer tick
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
Added BSSID 00:19:5b:df:63:da into blacklist
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
State: GROUP_HANDSHAKE -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 5 seconds
Scan timeout - try to get results
Received 254 bytes of scan results (1 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:19:5b:df:63:da ssid='dlink' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
selected based on WPA IE
selected WPA AP 00:19:5b:df:63:da ssid='dlink'
Try to find non-WPA AP
Trying to associate with 00:19:5b:df:63:da (SSID='dlink' freq=2452 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_psk
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8c07 len=55
AssocReq IE wireless event - hexdump(len=47): 00 05 64 6c 69 6e 6b 01 0c 82 84 8b 96 8c 12 98 24 b0 48 60 6c dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:19:5b:df:63:da
Association info event
req_ies - hexdump(len=47): 00 05 64 6c 69 6e 6b 01 0c 82 84 8b 96 8c 12 98 24 b0 48 60 6c dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: set own WPA/RSN IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:19:5b:df:63:da
No keys have been configured - skip key clearing
Associated with 00:19:5b:df:63:da
WPA: Association event - clear replay counter
WPA: Clear old PTK
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RX EAPOL from 00:19:5b:df:63:da
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 2b 75 db d1 7f 4c 17 54 40 93 14 48 bf aa 46 2a ea 89 81 3f b1 35 b2 9f 08 d4 97 77 bd 8e f6 de 19 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
EAPOL-Key type=254
key_info 0x89 (ver=1 keyidx=0 rsvd=0 Pairwise Ack)
key_length=32 key_data_length=0
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 2b
key_nonce - hexdump(len=32): 75 db d1 7f 4c 17 54 40 93 14 48 bf aa 46 2a ea 89 81 3f b1 35 b2 9f 08 d4 97 77 bd 8e f6 de 19
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 2b 75 db d1 7f 4c 17 54 40 93 14 48 bf aa 46 2a ea 89 81 3f b1 35 b2 9f 08 d4 97 77 bd 8e f6 de 19 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:19:5b:df:63:da (ver=1)
WPA: Renewed SNonce - hexdump(len=32): 24 00 39 aa f3 ea 62 c6 e6 7d af 67 31 84 0a e0 8f a0 a3 f2 c3 8f 4f e8 07 c7 03 61 59 42 b0 cb
WPA: PTK derivation - A1=00:22:43:74:7b:05 A2=00:19:5b:df:63:da
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: WPA IE for msg 2/4 - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=125): 01 03 00 79 fe 01 09 00 20 00 00 00 00 00 00 00 2b 24 00 39 aa f3 ea 62 c6 e6 7d af 67 31 84 0a e0 8f a0 a3 f2 c3 8f 4f e8 07 c7 03 61 59 42 b0 cb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 39 a5 08 4d 72 a3 33 61 5a c3 4d 68 c3 cf 77 59 00 1a dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
RX EAPOL from 00:19:5b:df:63:da
RX EAPOL - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 2c 75 db d1 7f 4c 17 54 40 93 14 48 bf aa 46 2a ea 89 81 3f b1 35 b2 9f 08 d4 97 77 bd 8e f6 de 19 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 af 93 c5 54 72 54 70 5a f5 6e 6f 6e 29 12 a5 e0 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
IEEE 802.1X RX: version=1 type=3 length=119
EAPOL-Key type=254
key_info 0x1c9 (ver=1 keyidx=0 rsvd=0 Pairwise Install Ack MIC)
key_length=32 key_data_length=24
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 2c
key_nonce - hexdump(len=32): 75 db d1 7f 4c 17 54 40 93 14 48 bf aa 46 2a ea 89 81 3f b1 35 b2 9f 08 d4 97 77 bd 8e f6 de 19
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): af 93 c5 54 72 54 70 5a f5 6e 6f 6e 29 12 a5 e0
WPA: RX EAPOL-Key - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 2c 75 db d1 7f 4c 17 54 40 93 14 48 bf aa 46 2a ea 89 81 3f b1 35 b2 9f 08 d4 97 77 bd 8e f6 de 19 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 af 93 c5 54 72 54 70 5a f5 6e 6f 6e 29 12 a5 e0 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 3 of 4-Way Handshake from 00:19:5b:df:63:da (ver=1)
WPA: IE KeyData - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: Sending EAPOL-Key 4/4
WPA: TX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 01 09 00 20 00 00 00 00 00 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 7a 16 83 e7 ee f3 76 e6 5f 11 18 41 6b b3 08 f2 00 00
WPA: Installing PTK to the driver.
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_wext_set_key: alg=2 key_idx=0 set_tx=1 seq_len=6 key_len=32
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
EAPOL: startWhen --> 0
EAPOL: disable timer tick
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: enable timer tick
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
BSSID 00:19:5b:df:63:da blacklist count incremented to 2
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
State: GROUP_HANDSHAKE -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 5 seconds
Scan timeout - try to get results
Received 254 bytes of scan results (1 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:19:5b:df:63:da ssid='dlink' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
skip - blacklisted
Try to find non-WPA AP
0: 00:19:5b:df:63:da ssid='dlink' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
skip - blacklisted
No APs found - clear blacklist and try again
Removed BSSID 00:19:5b:df:63:da from blacklist (clear)
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:19:5b:df:63:da ssid='dlink' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
selected based on WPA IE
selected WPA AP 00:19:5b:df:63:da ssid='dlink'
Try to find non-WPA AP
Trying to associate with 00:19:5b:df:63:da (SSID='dlink' freq=2452 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_psk
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8c07 len=55
AssocReq IE wireless event - hexdump(len=47): 00 05 64 6c 69 6e 6b 01 0c 82 84 8b 96 8c 12 98 24 b0 48 60 6c dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:19:5b:df:63:da
Association info event
req_ies - hexdump(len=47): 00 05 64 6c 69 6e 6b 01 0c 82 84 8b 96 8c 12 98 24 b0 48 60 6c dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: set own WPA/RSN IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:19:5b:df:63:da
No keys have been configured - skip key clearing
Associated with 00:19:5b:df:63:da
WPA: Association event - clear replay counter
WPA: Clear old PTK
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RX EAPOL from 00:19:5b:df:63:da
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 2d 52 ad 00 7f 32 d3 9a aa 8f 81 15 30 e5 54 7b 2f e2 d0 95 ab 16 c9 46 7f 2f 2c 0a a5 39 a3 5e 2b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
EAPOL-Key type=254
key_info 0x89 (ver=1 keyidx=0 rsvd=0 Pairwise Ack)
key_length=32 key_data_length=0
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 2d
key_nonce - hexdump(len=32): 52 ad 00 7f 32 d3 9a aa 8f 81 15 30 e5 54 7b 2f e2 d0 95 ab 16 c9 46 7f 2f 2c 0a a5 39 a3 5e 2b
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 2d 52 ad 00 7f 32 d3 9a aa 8f 81 15 30 e5 54 7b 2f e2 d0 95 ab 16 c9 46 7f 2f 2c 0a a5 39 a3 5e 2b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:19:5b:df:63:da (ver=1)
WPA: Renewed SNonce - hexdump(len=32): f5 5a 07 24 64 aa fb b5 5d 63 23 09 c9 45 3c de 4d 9b 88 03 ee 81 af e7 10 ee a7 58 4d cd 9c 59
WPA: PTK derivation - A1=00:22:43:74:7b:05 A2=00:19:5b:df:63:da
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: WPA IE for msg 2/4 - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=125): 01 03 00 79 fe 01 09 00 20 00 00 00 00 00 00 00 2d f5 5a 07 24 64 aa fb b5 5d 63 23 09 c9 45 3c de 4d 9b 88 03 ee 81 af e7 10 ee a7 58 4d cd 9c 59 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30 0c c7 a5 96 12 6f ac f6 d6 9f c6 cb eb 20 f5 00 1a dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
RX EAPOL from 00:19:5b:df:63:da
RX EAPOL - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 2e 52 ad 00 7f 32 d3 9a aa 8f 81 15 30 e5 54 7b 2f e2 d0 95 ab 16 c9 46 7f 2f 2c 0a a5 39 a3 5e 2b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 63 54 e3 d3 dd d1 99 79 b3 e0 f0 ae fb ea 44 30 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
IEEE 802.1X RX: version=1 type=3 length=119
EAPOL-Key type=254
key_info 0x1c9 (ver=1 keyidx=0 rsvd=0 Pairwise Install Ack MIC)
key_length=32 key_data_length=24
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 2e
key_nonce - hexdump(len=32): 52 ad 00 7f 32 d3 9a aa 8f 81 15 30 e5 54 7b 2f e2 d0 95 ab 16 c9 46 7f 2f 2c 0a a5 39 a3 5e 2b
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 63 54 e3 d3 dd d1 99 79 b3 e0 f0 ae fb ea 44 30
WPA: RX EAPOL-Key - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 2e 52 ad 00 7f 32 d3 9a aa 8f 81 15 30 e5 54 7b 2f e2 d0 95 ab 16 c9 46 7f 2f 2c 0a a5 39 a3 5e 2b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 63 54 e3 d3 dd d1 99 79 b3 e0 f0 ae fb ea 44 30 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 3 of 4-Way Handshake from 00:19:5b:df:63:da (ver=1)
WPA: IE KeyData - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: Sending EAPOL-Key 4/4
WPA: TX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 01 09 00 20 00 00 00 00 00 00 00 2e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 18 e3 29 19 23 bb e3 09 c4 9c 77 84 f0 0a f0 09 00 00
WPA: Installing PTK to the driver.
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_wext_set_key: alg=2 key_idx=0 set_tx=1 seq_len=6 key_len=32
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
RX EAPOL from 00:19:5b:df:63:da
RX EAPOL - hexdump(len=131): 01 03 00 7f fe 03 91 00 20 00 00 00 00 00 00 00 2f a4 76 f1 d1 2f 35 55 8b 4c 37 ac 8d 83 0e bd 7c 83 a5 d8 f1 96 7f b9 4a 3e 28 1e 24 c9 08 1d 59 83 a5 d8 f1 96 7f b9 4a 3e 28 1e 24 c9 08 1d 5b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1c 89 11 10 fe 7a 0c f0 36 d1 f0 d6 e5 2b af ec 00 20 a1 2a 90 9c 9f 5b 3c 37 56 24 e7 fe f9 05 4a 63 21 3c 21 0c 92 3e 1c c3 aa 3a 33 4c c7 02 30 b4
IEEE 802.1X RX: version=1 type=3 length=127
EAPOL-Key type=254
key_info 0x391 (ver=1 keyidx=1 rsvd=0 Group Ack MIC Secure)
key_length=32 key_data_length=32
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 2f
key_nonce - hexdump(len=32): a4 76 f1 d1 2f 35 55 8b 4c 37 ac 8d 83 0e bd 7c 83 a5 d8 f1 96 7f b9 4a 3e 28 1e 24 c9 08 1d 59
key_iv - hexdump(len=16): 83 a5 d8 f1 96 7f b9 4a 3e 28 1e 24 c9 08 1d 5b
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 1c 89 11 10 fe 7a 0c f0 36 d1 f0 d6 e5 2b af ec
WPA: RX EAPOL-Key - hexdump(len=131): 01 03 00 7f fe 03 91 00 20 00 00 00 00 00 00 00 2f a4 76 f1 d1 2f 35 55 8b 4c 37 ac 8d 83 0e bd 7c 83 a5 d8 f1 96 7f b9 4a 3e 28 1e 24 c9 08 1d 59 83 a5 d8 f1 96 7f b9 4a 3e 28 1e 24 c9 08 1d 5b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1c 89 11 10 fe 7a 0c f0 36 d1 f0 d6 e5 2b af ec 00 20 a1 2a 90 9c 9f 5b 3c 37 56 24 e7 fe f9 05 4a 63 21 3c 21 0c 92 3e 1c c3 aa 3a 33 4c c7 02 30 b4
WPA: RX message 1 of Group Key Handshake from 00:19:5b:df:63:da (ver=1)
State: GROUP_HANDSHAKE -> GROUP_HANDSHAKE
WPA: Group Key - hexdump(len=32): [REMOVED]
WPA: Installing GTK to the driver (keyidx=1 tx=0 len=32).
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_wext_set_key: alg=2 key_idx=1 set_tx=0 seq_len=6 key_len=32
WPA: Sending EAPOL-Key 2/2
WPA: TX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 03 11 00 20 00 00 00 00 00 00 00 2f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ae bc 0d 67 91 be 47 4c 24 55 94 40 c6 53 6a f8 00 00
WPA: Key negotiation completed with 00:19:5b:df:63:da [PTK=TKIP GTK=TKIP]
Cancelling authentication timeout
State: GROUP_HANDSHAKE -> COMPLETED
CTRL-EVENT-CONNECTED - Connection to 00:19:5b:df:63:da completed (auth) [id=0 id_str=]
wpa_driver_wext_set_operstate: operstate 0->1 (UP)
WEXT: Operstate: linkmode=-1, operstate=6
EAPOL: External notification - portValid=1
EAPOL: External notification - EAP success=1
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state SUCCESS
EAP: EAP entering state DISABLED
EAPOL: SUPP_PAE entering state AUTHENTICATED
EAPOL: SUPP_BE entering state IDLE
EAPOL authentication completed successfully
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RX EAPOL from 00:19:5b:df:63:da
RX EAPOL - hexdump(len=131): 01 03 00 7f fe 03 91 00 20 00 00 00 00 00 00 00 2f a4 76 f1 d1 2f 35 55 8b 4c 37 ac 8d 83 0e bd 7c 83 a5 d8 f1 96 7f b9 4a 3e 28 1e 24 c9 08 1d 59 83 a5 d8 f1 96 7f b9 4a 3e 28 1e 24 c9 08 1d 5b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1c 89 11 10 fe 7a 0c f0 36 d1 f0 d6 e5 2b af ec 00 20 a1 2a 90 9c 9f 5b 3c 37 56 24 e7 fe f9 05 4a 63 21 3c 21 0c 92 3e 1c c3 aa 3a 33 4c c7 02 30 b4
IEEE 802.1X RX: version=1 type=3 length=127
EAPOL-Key type=254
key_info 0x391 (ver=1 keyidx=1 rsvd=0 Group Ack MIC Secure)
key_length=32 key_data_length=32
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 2f
key_nonce - hexdump(len=32): a4 76 f1 d1 2f 35 55 8b 4c 37 ac 8d 83 0e bd 7c 83 a5 d8 f1 96 7f b9 4a 3e 28 1e 24 c9 08 1d 59
key_iv - hexdump(len=16): 83 a5 d8 f1 96 7f b9 4a 3e 28 1e 24 c9 08 1d 5b
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 1c 89 11 10 fe 7a 0c f0 36 d1 f0 d6 e5 2b af ec
WPA: RX EAPOL-Key - hexdump(len=131): 01 03 00 7f fe 03 91 00 20 00 00 00 00 00 00 00 2f a4 76 f1 d1 2f 35 55 8b 4c 37 ac 8d 83 0e bd 7c 83 a5 d8 f1 96 7f b9 4a 3e 28 1e 24 c9 08 1d 59 83 a5 d8 f1 96 7f b9 4a 3e 28 1e 24 c9 08 1d 5b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1c 89 11 10 fe 7a 0c f0 36 d1 f0 d6 e5 2b af ec 00 20 a1 2a 90 9c 9f 5b 3c 37 56 24 e7 fe f9 05 4a 63 21 3c 21 0c 92 3e 1c c3 aa 3a 33 4c c7 02 30 b4
WPA: EAPOL-Key Replay Counter did not increase - dropping packet
EAPOL: startWhen --> 0
EAPOL: disable timer tick

it seems stop here again so i press ctrl+c

^CCTRL-EVENT-TERMINATING - signal 2 received
Removing interface wlan0
State: COMPLETED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 1->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_deauthenticate
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Cancelling scan request
Cancelling authentication timeout
WEXT: Operstate: linkmode=0, operstate=6
coppen@coppen-laptop:~$



coppen@coppen-laptop:~$ sudo dhclient wlan0
[sudo] password for coppen:
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:22:43:74:7b:05
Sending on LPF/wlan0/00:22:43:74:7b:05
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


p.s. thanks a lot for your patient!

[afeasfaerw23231233]

Now I have a doubt if my driver is working correctly. A few hours ago I booted into win xp and the wireless connection broken randomly. I search in website of the producer of my notebook and find out a new driver (the name is still realtek 8187 so I really don't know what version it is. But very likely it should be 8187B or 8187L). I reinstall it and it works great.

I compared the speed of copying big files in ubuntu and win xp by samba. I find out the speed in xp is around 2.6MB/s steady but in ubuntu it flutuates from 600KB to 2.2MB/s. That's a bit odd it keeps dropping to around 600KB/s for half a second and than goes up again. The signal strength in both OS is around 70%. And in both OS I notice no random disconnection. And WPA works well in xp too.

So should I reinstall the ndiswrapper driver? (The current driver in ubuntu is the windows 98 version as I mention in my previous post). Arrr... I am a noob and I forget the way how to get ndiswrapper work.. I need to search the forum again?

p.s. sorry for my bad english too

[kevdog]

it seems stop here again so i press ctrl+c

Why do you do this? Again, in one window do the wpa_supplicant thing, (do not stop it when it stops), and then in the other window do the dhclient command. You have to have wpa_supplicant running at all times (either in the foreground) or in the background (which can be done with use of the -B flag). However if you run it in the background you get no debugging output.

As far as the windows driver and things --- I don't know.

Lets try without ndiswrapper for now -- its the preferrable solution if it works!

[afeasfaerw23231233]

Sorry for my bad mistake. Now it works. Thanks a lot!

[kevdog]

Ok not to confuse you farther, however since you know it is working, you know longer need the -dd flag (this is a flag for double debugging output). I would now add the -B flag to send the process to the background. It would be something similar to this:

sudo wpa_supplicant -B -Dwext -iwlan0 -c/etc/wpa_supplicant.conf

Because the process is being run in the background, you can type the command and the dhclient command in the same terminal window.

[afeasfaerw23231233]

Hi, it's me again. since by notebook freeze randomly at boot up [actually I started another thread about this issue:http://ubuntuforums.org/showthread.php?t=1085758 ], I want to reinstall ndiswrapper again. I follow another guide by you about installing ndiswrapper http://ubuntuforums.org/showthread.php?t=574501&highlight=Kevdog&page=31
and I have problem while running this command:
sudo ndiswrapper -m

module configuration already contains alias directive

module configuration already contains alias directive

module configuration already contains alias directive

module configuration already contains alias directive

module configuration already contains alias directive

module configuration already contains alias directive

module configuration already contains alias directive

module configuration already contains alias directive




what should I do? thanks !

[kevdog]

Ignore the warning. ndiswrapper is probably listed in /etc/modules

[afeasfaerw23231233]

I want falling back to the native driver of realtek 8187 driver provided by Ubuntu by default because I doubt the ndiswrapper driver of win 98 version is the cause of freezing at "Loading manual drivers..." during bootup.

I clicked complete removal of ndisgtk, ndiswrapper-utils-1.9 and ndiswrapper-common in Synaptic. Then I run the following command according to your ndiswrapper howto http://ubuntuforums.org/showthread.php?t=574501&highlight=Kevdog in order to ensure a clean uninstallation:


sudo aptitude purge ndiswrapper
sudo rm /etc/modprobe.d/ndiswrapper
sudo sh -c "sed '/^ndiswrapper$/d' /etc/modules > /etc/modules.temp.rm; mv /etc/modules.temp.rm /etc/modules"
sudo rmmod ndiswrapper
sudo /lib/modules/`uname -r`/kernel/ubuntu/misc/ndiswrapper/ndiswrapper.ko
sudo rm -rf /etc/ndiswrapper
sudo rm /usr/sbin/ndiswrapper
sudo rm /sbin/loadndisdriver
sudo rm /lib/modules/`uname -r`/misc/ndiswrapper.ko

Then I check my /etc/modprobe.d/blacklist to ensure blacklist 818x and blacklisk 8187 are commented out. The extract of my /etc/modprobe.d/blacklist

# low-quality, just noise when being used for sound playback, causes
# hangs at desktop session start (Ubuntu: #246969)
blacklist snd_pcsp

#blacklist r818x
#blacklist r8187

then I run lshw -C network and the default driver seems not coming back. There is no driver installed for wlan realtek 8187?

lshw -C network
*-network
description: Wireless interface
physical id: 2
logical name: wlan0
serial: 00:22:43:74:7b:05
capabilities: ethernet physical wireless
configuration: broadcast=yes multicast=yes wireless=IEEE 802.11bg
Here's the result of lsmod|grep 818


lsmod|grep 818
rtl8187 53248 0
mac80211 216820 1 rtl8187
eeprom_93cx6 10240 1 rtl8187
cfg80211 32392 2 rtl8187,mac80211
usbcore 149360 7 rtl8187,usb_storage,libusual,usbhid,ehci_hcd,ohci_ hcd

Thanks!

edit: and when I run modprobe r818x and modprobe r8187

coppen@coppen-laptop:/etc/modprobe.d$ cd
coppen@coppen-laptop:~$ sudo modprobe r818x
[sudo] password for coppen:
FATAL: Module r818x not found.
coppen@coppen-laptop:~$ sudo modprobe r8187
FATAL: Module r8187 not found.

[kevdog]

I haven't kept abreast of the latest realtek drivers within the newer kernels since writing this guide. I am no longer certain they are called r8187 or r818x. They could possibly be called something else. You are going to have to look keeping your kernel version as a reference. This can be found with uname -r. Google might be your best fried here!

[afeasfaerw23231233]

Oh mine... I google around and cannot find any useful information. I think I have to go back to ndiswrapper.
I feel dizzy now...... :(

[afeasfaerw23231233]

Hi, I finally got the native driver rtl8187 installed. But this time I cannot connect even without encryption.

Here's the result:


coppen@coppen-laptop:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 No scan results

coppen@coppen-laptop:~$ sudo ifconfig wlan0 down
[sudo] password for coppen:
coppen@coppen-laptop:~$ sudo dhclient -r wlan0
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:22:43:74:7b:05
Sending on LPF/wlan0/00:22:43:74:7b:05
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.123.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
coppen@coppen-laptop:~$ sudo ifconfig wlan0 up
coppen@coppen-laptop:~$ sudo iwconfig wlan0 essid "homerouter269x"
coppen@coppen-laptop:~$ sudo iwconfig wlan0 mode Managed
coppen@coppen-laptop:~$ sudo dhclient wlan0
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:22:43:74:7b:05
Sending on LPF/wlan0/00:22:43:74:7b:05
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.



Then I tried install wicd and wicd connected immediately. But wicd suffered from random disconnection due to the lack of a suffix on ESSID as you mentioned on the first post.
Why this time I can't get dhclient work with the native driver?
Thanks!

EDIT: or is their any method to add a suffix for ESSID in wicd? Sorry that it is off-topic.

[timeOday]

This HowTo is excellent. However it is missing one important thing: if NetworkManager is installed (which it is by default, at least on Jaunty), you must first stop NetworkManager:

sudo /etc/init.d/NetworkManager stop

If you don't do this, and you're not running the NetworkManager applet (I run FVWM instead of gnome), then everything looks perfect in ifconfig and iwconfig, yet the wireless card will not associate with an access point.

[kevdog]

I'm not sure if what you are telling me is correct. Ive been able to make a manual connection with network manager connected and running in the background. I haven't used Jaunty yet, however I can confirm this statement based on all versions back to Feisty. Its possible the interface wasn't taken down correctly or something. Maybe I can confirm your statement later when Jaunty final is released and I actually install it!

[gleble]

I am using Intrepid running on an Acer 5735. My router is an Orange Livebox

I followed the WEP instructions and sudo dhclient wlan0 gave this


neil@neil-laptop:~$ sudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 17562
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:21:5d:74:69:f4
Sending on LPF/wlan0/00:21:5d:74:69:f4
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


What are the last two lines about
If I ifconfig eth0 down I get


There is already a pid file /var/run/dhclient.pid with pid 20547
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
can't create /var/lib/dhcp3/dhclient.leases: Permission denied
SIOCSIFADDR: Permission denied
SIOCSIFFLAGS: Permission denied
SIOCSIFFLAGS: Permission denied
wmaster0: unknown hardware address type 801
Open a socket for LPF: Operation not permitted

[gleble]

Solved, pressed button 2 on the Livebox and everything works so I must have got it configured right anyway.

[tonytraductor]

This was helpful.
I removed gnome-network-manager, and lost my connection, and couldn't bring it back up until I saw this.
Now, the question I have is, what to do if I don't know the essid?
I want the laptop to auto connect to wifi when I go to coffee shops, and stuff.
I suppose now that I have the connection up again, I could re apt-get gnome-network-manager, but I don't use gnome (prefer openbox).
I want to be able to connect from openbox, without gnome tools, and when I am roaming (unknown essid).
How do I do that?

[stansford]

kevdog,

I have an RT2500 pci wireless card that connects fine with the latest network manager applet in Jaunty using WPA....however any idea how to connect with WPA via a CLI only system?

You mention using iwconfig and iwpriv in your guide, but the in-built RT2x00 drivers in Jaunty don't allow you to inject a key via iwpriv any more, returning "no private ioctls" when tried.

Also I assume the serialmonkey route is now closed as they've dropped legacy support and it is their drivers that are built into the kernel.

So how do you connect a RT2500 wifi card via the CLI with WPA now? Thanks.

[kevdog]

TonyTraductor

To see the networks around you:

sudo iwlist scan

This will show you the essids of the networks around you, and then you can connect.

Its also possible to install and run wicd within openbox (Ive done this within e17). If you need a system tray app (trayer or docker), a wicd icon can be placed within the tray to give you feedback.

stansford:

Have you just tried the same old method as everyone else with the use of wpa supplicant?

[stansford]

TonyTraductor

stansford:

Have you just tried the same old method as everyone else with the use of wpa supplicant?


- Yes I'm trying that method but have a problem (or two!).
Don't know if you can help:

1. From the articles I've read etc there seems to be confusion about what config info to place where. Eg Do you need to put info into /etc/network/interfaces or is it sufficient to specify ssid, WPA key etc in wpa_supplicant.conf alone?

I'm not really clear about why you'd need both as it seems the information is duplicated if you put it in both files.

Anyway, here's my wpa_supplicant.conf file:

#--------
ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
ap_scan=1
fast_reauth=1
network={
ssid="my-ssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
psk=hex-key
priority=5
}

Here's my /etc/network/interfaces file:

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid my_essid
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk hex_key

I did a network restart:

#sudo /etc/init.d/networking restart

then bring up wlan0:

#iwconfig wlan0 essid my-ssid
-returns with no ouput

then the command:
#wpa_supplicant –iwlan0 –c~/wpa.conf -ddd
- this is where the problem starts.
- I don't seem to be able to associate with my router....I don't know why. I can see the message "no keys have been configured - skip keyring clearing" - then it times out and starts trying again.
Eventually I control-C to quit

I can attach the wpa_supplicant output if you want, but there is a lot of debugging stuff in there that I don't understand. However I see that wpa_supplicant does find my router and there's talk about WPA and wlan0 being up etc so it kinda feels like I'm not a million miles away and yet.....

I appreciate this may not be your thing, but any help, answers/suggestion gratefully received. Thanks

[kevdog]

Ok

Lets clear up a few misconceptions that run across these forums.

The /etc/network/interfaces file:

This file is read when the command "ifup" is executed. You can think of it as the configuration file when ifup is executed. Processess such as Network Manager that run ifup, read this file. Note that the ifup (interfaces up) command is a much higher level command than the more basic command "ifconfig <interface name -- ie wlan0> up". ifup not only calls the ifconfig command given the paramaters in the /etc/network/interfaces file, but it also tries to set the route statement. I know the differences between the ifup and ifconfig <interface name> up command seems confusing, however the man pages -- man ip and man ifconfig may help to clear up the confusion. Bottom line however ifconfig <interface> up is a more lower level command than ifup and using the ifconfig command means the /etc/network/interfaces file is never read. So hence you don't need this command at all -- and hence you never need to do a sudo /etc/init.d/networking restart command.

You wpa_supplicant.conf file is where you set your parameters that are read when you run the wpa_supplicant command. Ive noticed your wpa_supplicant.conf file is quite wordy. Meaning it seems to contain parameters that are excessive. I usually find a smaller wpa_supplicant.conf file to be more helpful than a larger one. I provided some examples in the instructions, and I would stick right now to using the format of the examples until things work. Adding a bunch of extra parameters -- although the man pages state you can do this -- in my experience usually messes up things.

I also don't understand this statment:

then bring up wlan0:

#iwconfig wlan0 essid my-ssid
-returns with no ouput


What exactly is your interface name? Is it wlan0 or eth1 or something else? Usually typing ifconfig at the command line will help you with this, or typing lshw -C network, and then examining the ouput will help

Bringing the interface up manually is usually like this:
sudo ifconfig <interface -- wlan0 for example> up

This activates the network card.

To scan for networks
sudo iwlist scan

You don't need specify a interface specifically with this command although you could -- sudo iwlist <interface> scan. Without the interface parameter, the command will be run on all interfaces and not just on the one designated interface.

[stansford]

Ok

Lets clear up a few misconceptions that run across these forums.

The /etc/network/interfaces file:

This file is read when the command "ifup" is executed. You can think of it as the configuration file when ifup is executed. Processess such as Network Manager that run ifup, read this file. Note that the ifup (interfaces up) command is a much higher level command than the more basic command "ifconfig <interface name -- ie wlan0> up". ifup not only calls the ifconfig command given the paramaters in the /etc/network/interfaces file, but it also tries to set the route statement. I know the differences between the ifup and ifconfig <interface name> up command seems confusing, however the man pages -- man ip and man ifconfig may help to clear up the confusion. Bottom line however ifconfig <interface> up is a more lower level command than ifup and using the ifconfig command means the /etc/network/interfaces file is never read. So hence you don't need this command at all -- and hence you never need to do a sudo /etc/init.d/networking restart command.

You wpa_supplicant.conf file is where you set your parameters that are read when you run the wpa_supplicant command. Ive noticed your wpa_supplicant.conf file is quite wordy. Meaning it seems to contain parameters that are excessive. I usually find a smaller wpa_supplicant.conf file to be more helpful than a larger one. I provided some examples in the instructions, and I would stick right now to using the format of the examples until things work. Adding a bunch of extra parameters -- although the man pages state you can do this -- in my experience usually messes up things.

I also don't understand this statment:

then bring up wlan0:

#iwconfig wlan0 essid my-ssid
-returns with no ouput


What exactly is your interface name? Is it wlan0 or eth1 or something else? Usually typing ifconfig at the command line will help you with this, or typing lshw -C network, and then examining the ouput will help

Bringing the interface up manually is usually like this:
sudo ifconfig <interface -- wlan0 for example> up

This activates the network card.

To scan for networks
sudo iwlist scan

You don't need specify a interface specifically with this command although you could -- sudo iwlist <interface> scan. Without the interface parameter, the command will be run on all interfaces and not just on the one designated interface.

Thanks for the reply.

my interface name is wlan0.
Yes sorry for the confusion over the command "iwconfig wlan0 essid my-ssid". It doesn't bring up the network, it just sets the essid parameter for wlan0 to "my-ssid"!

OK I will slim down the wpa.conf file as per your instructions.
Should I have anything in the /etc/network/interfaces file at this point?....the reason I ask is that Wieman's fantastic post
http://ubuntuforums.org/showthread.php?t=202834
seems to say: get your wifi up by having no wpa.conf file and instead putting all the config info into the /etc/network/ interfaces file....but then your thread says set up the wpa.conf file....

I'm confused! It maybe my lack of knowledge, but are these two approaches the same thing or are they mutually exclusive and you just try one then the other?

Many thanks for helping

[kevdog]

Wieman's post is great -- I talk to him frequently so don't get the idea that me and him are at war or something. His tutorial helped me out when I was a neophyte.

My post is just another way of making a network connection at the command line. Its much more lower level than his. You used to have to put a wpa_supplicant call within the /etc/network/interfaces file, but that was a long time ago. The method still works however its not necessary.

I find that manually specifying the commands for me at least to be more reliable than use of the interfaces file. I'm not a big fan of the ifup command.

sudo ifconfig wlan0 up (brings the network card up)
sudo iwconfig wlan0 essid "essid" (assigns the card to the specified essid)
...
...
...
sudo dhclient wlan0 (forces the wlan0 interface to ask for a dynamic ip address).

[stansford]

Wieman's post is great -- I talk to him frequently so don't get the idea that me and him are at war or something. His tutorial helped me out when I was a neophyte.

My post is just another way of making a network connection at the command line. Its much more lower level than his. You used to have to put a wpa_supplicant call within the /etc/network/interfaces file, but that was a long time ago. The method still works however its not necessary.

I find that manually specifying the commands for me at least to be more reliable than use of the interfaces file. I'm not a big fan of the ifup command.

sudo ifconfig wlan0 up (brings the network card up)
sudo iwconfig wlan0 essid "essid" (assigns the card to the specified essid)
...
...
...
sudo dhclient wlan0 (forces the wlan0 interface to ask for a dynamic ip address).


OK thanks for that. I will persevere with your way. I am still struggling to get an association. Sometimes I do, sometimes I don't and sometimes it comes and goes. I am using the RALINK RT2500 PCI wifi card and I wonder if this is still a source of trouble. I notice that you can't use the SerialMonkey drivers any more as they no longer compile though I admit I don't know why. I did see a post that said use the included drivers (rt2500pci) included in the kernel, but then you can't use the iwpriv method you mention in your how to.

Thanks for your help

[kevdog]

Forget about the serial monkey drivers for now.

Are you telling me sometimes you actually can connect via WPA, but sometimes it also doesn't work?

I'm not too sure if I can be of too much help to you if the connection is spotty!

[t0mppa]

Ok, so I have a Dell Truemobile 1400 minipci card on my friends laptop that has a Broadcom Corporation BCM4309 (rev 02) chip on it. Got it set up with NDISWrapper and it connects flawlessly with open networks. However, when I try to get into a WPA encrypted one, things go sour.

Tried the instructions given here and just can't figure out what's wrong. Wpa_supplicant says it gets associated with my routers MAC address, but dhclient finds no DHCP offers. Also checked NDISWrappers site and it said with this driver setup the card has been known to connect to open, WEP and WPA networks.

With the -dd option, the wpa_supplicant gives around 2k lines of output in the time space that it takes for dhclient to run through the different intervals, so if someone wants to read through all of that, I can supply the text file, but here should be one cycle of the debug info:


WPA: Installing PTK to the driver.
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_wext_set_key: alg=2 key_idx=0 set_tx=1 seq_len=6 key_len=32
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
EAPOL: startWhen --> 0
EAPOL: disable timer tick
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: enable timer tick
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8c07 len=85
AssocReq IE wireless event - hexdump(len=77): 00 06 54 6f 6d 70 70 61 01 08 82 84 0b 16 24 30 48 6c 21 02 08 0e 24 02 01 0e 32 04 0c 12 18 60 dd 06 00 40 96 01 01 00 dd 09 00 10 18 02 00 10 00 00 00 dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8c08 len=24
AssocResp IE wireless event - hexdump(len=16): 01 04 82 84 0b 16 32 08 0c 12 18 24 30 48 60 6c
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:1e:ab:00:e4:f1
Association info event
req_ies - hexdump(len=77): 00 06 54 6f 6d 70 70 61 01 08 82 84 0b 16 24 30 48 6c 21 02 08 0e 24 02 01 0e 32 04 0c 12 18 60 dd 06 00 40 96 01 01 00 dd 09 00 10 18 02 00 10 00 00 00 dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
resp_ies - hexdump(len=16): 01 04 82 84 0b 16 32 08 0c 12 18 24 30 48 60 6c
WPA: set own WPA/RSN IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
State: GROUP_HANDSHAKE -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated with 00:1e:ab:00:e4:f1
WPA: Association event - clear replay counter
WPA: Clear old PTK
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RX EAPOL from 00:1e:ab:00:e4:f1
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 01 29 62 48 f5 fa 1a 76 2c 8a 3c a7 e6 45 6e 60 23 a3 6a 01 c6 e1 02 50 1d ec 58 f4 8c e5 85 b6 75 85 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
EAPOL-Key type=254
key_info 0x89 (ver=1 keyidx=0 rsvd=0 Pairwise Ack)
key_length=32 key_data_length=0
replay_counter - hexdump(len=8): 00 00 00 00 00 00 01 29
key_nonce - hexdump(len=32): 62 48 f5 fa 1a 76 2c 8a 3c a7 e6 45 6e 60 23 a3 6a 01 c6 e1 02 50 1d ec 58 f4 8c e5 85 b6 75 85
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 01 29 62 48 f5 fa 1a 76 2c 8a 3c a7 e6 45 6e 60 23 a3 6a 01 c6 e1 02 50 1d ec 58 f4 8c e5 85 b6 75 85 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:1e:ab:00:e4:f1 (ver=1)
WPA: Renewed SNonce - hexdump(len=32): 70 13 a0 47 92 f0 5a 00 aa 5a 18 e6 78 e5 76 a9 cf e1 78 5f a6 2d ac d5 c0 14 56 f2 03 18 b3 e9
WPA: PTK derivation - A1=00:90:4b:66:b3:f2 A2=00:1e:ab:00:e4:f1
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: WPA IE for msg 2/4 - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=125): 01 03 00 79 fe 01 09 00 20 00 00 00 00 00 00 01 29 70 13 a0 47 92 f0 5a 00 aa 5a 18 e6 78 e5 76 a9 cf e1 78 5f a6 2d ac d5 c0 14 56 f2 03 18 b3 e9 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c6 2b f3 2d 21 e9 39 20 e3 d0 ac 5f 51 c2 fe ce 00 1a dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 0c 00
RX EAPOL from 00:1e:ab:00:e4:f1
RX EAPOL - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 01 2a 62 48 f5 fa 1a 76 2c 8a 3c a7 e6 45 6e 60 23 a3 6a 01 c6 e1 02 50 1d ec 58 f4 8c e5 85 b6 75 85 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2e 14 5e fd 0e 49 54 f6 4b 4f 86 97 16 58 28 e7 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
IEEE 802.1X RX: version=1 type=3 length=119
EAPOL-Key type=254
key_info 0x1c9 (ver=1 keyidx=0 rsvd=0 Pairwise Install Ack MIC)
key_length=32 key_data_length=24
replay_counter - hexdump(len=8): 00 00 00 00 00 00 01 2a
key_nonce - hexdump(len=32): 62 48 f5 fa 1a 76 2c 8a 3c a7 e6 45 6e 60 23 a3 6a 01 c6 e1 02 50 1d ec 58 f4 8c e5 85 b6 75 85
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 2e 14 5e fd 0e 49 54 f6 4b 4f 86 97 16 58 28 e7
WPA: RX EAPOL-Key - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 01 2a 62 48 f5 fa 1a 76 2c 8a 3c a7 e6 45 6e 60 23 a3 6a 01 c6 e1 02 50 1d ec 58 f4 8c e5 85 b6 75 85 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2e 14 5e fd 0e 49 54 f6 4b 4f 86 97 16 58 28 e7 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 3 of 4-Way Handshake from 00:1e:ab:00:e4:f1 (ver=1)
WPA: IE KeyData - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: Sending EAPOL-Key 4/4
WPA: TX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 01 09 00 20 00 00 00 00 00 00 01 2a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 cc 03 d2 35 4d 07 a8 28 30 a1 ba d9 36 a4 e9 00 00
WPA: Installing PTK to the driver.
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_wext_set_key: alg=2 key_idx=0 set_tx=1 seq_len=6 key_len=32
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
EAPOL: startWhen --> 0
EAPOL: disable timer tick
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: enable timer tick
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
^CCTRL-EVENT-TERMINATING - signal 2 received
Removing interface wlan0
State: GROUP_HANDSHAKE -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_deauthenticate
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Cancelling scan request
Cancelling authentication timeout
WEXT: Operstate: linkmode=0, operstate=6


So, any ideas what to do next?

[kevdog]

When wpa_supplicant associates, it stops scrolling. If it keeps scrolling its not being authenticated.

Is there a reason you are using ndiswrapper other than b43?

Have you tried WICD?

Can you post your wpa_supplicant.conf file?

[t0mppa]

Well, as you can see, it periodically does say "Associated with 00:1e:ab:00:e4:f1". So, it's just outputting that for kicks? :)

Couldn't get b43 to work actually, the proprietary driver on Hardware Drivers never does anything when I press enable and setting it up manually ran into various issues. And since there doesn't seem to be much motivation to get new drivers for this chip (neither the STA nor OpenFWWF support it), figured might as well go for NDISWrapper. If b43 is far superior though, I suppose I could have round #2 with it.

Yes, I have tried WICD, it's currently installed and it doesn't help much. Currently (that worked before I tried the manual route) it can't even establish a connection over open network though, something that even Network Manager managed to accomplish.


~$cat /etc/wpa_supplicant.conf
ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="my_essid"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk="my_password"
pairwise=TKIP
group=TKIP
}


And yes, I set my router to WPA Pre-Shared Key with TKIP, since the advice was to first get WPA working before trying WPA2.

EDIT: Now that you mentioned the NDISWrapper, dmesg says: [ 31.340935] wlan0: encryption modes supported: WEP; TKIP with WPA; AES/CCMP with WPA. So, I guess I'll have to have a go with b43 eventually anyway to get WPA2 support. It should work with WPA though.

[kevdog]

Does it work with just this:

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="my_essid"
proto=WPA
key_mgmt=WPA-PSK
psk="my_password"
pairwise=TKIP
group=TKIP
}

[t0mppa]

That will have to wait a while. Conveniently NDISwrapper just started producing kernel panics whenever I enable my wireless through the kill switch. Nothing is ever easy. ;)

[Icehuck]

I'm looking to ditch network manager and connect to a WPA secured wifi connection from the command line. Tried following your guide but I'm stuck. In case it matters, I'm running Jaunty.

lshw -C network lists my driver as.

driver=iwl3945

my wpa_supplicant.conf file looks like:

ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="xb332"
scan_ssid=1
proto=WPA
key_mgmt=WPA-PSK
psk="mykey"
pairwise=TKIP
group=TKIP
}

Then i run

sudo ifconfig wlan0 down
sudo dhclient -r wlan0
sudo wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -d
and it gives the following output and never goes any farther.


sudo ifconfig wlan0 down
sudo dhclient -r wlan0
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:1c:bf:0d:05:20
Sending on LPF/wlan0/00:1c:bf:0d:05:20
Sending on Socket/fallback

sudo wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -d
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ap_scan=1
ctrl_interface='/var/run/wpa_supplicant'
Priority group 0
id=0 ssid='xb332'
Initializing interface (2) 'wlan0'
Interface wlan0 set UP - waiting a second for the driver to complete initialization
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf flags 0x0
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1c:bf:0d:05:20
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Added interface wlan0
Ignore event for foreign ifindex 3
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b06 len=12
State: DISCONNECTED -> SCANNING
Trying to associate with SSID 'xb332'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: No WPA/RSN IE available from association info
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_psk
Setting authentication timeout: 60 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b06 len=12
EAPOL: disable timer tick
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b19 len=16
Received 788 bytes of scan results (2 BSSes)
CTRL-EVENT-SCAN-RESULTS

Any help would be appreciated.

[kevdog]

IceHuck

Just to confirm -- the terminal output stops -- correct?

This means you have been appropriately authenticated -- remember with the -d switch you are running this process in the foreground.

Just pop open another terminal window and type:
sudo dhclient wlan0

Once everything is up and working, the next time you want to connect, skip the -d flag and just use the -B flag which sends the process to the background without providing information. You can then request a dhcp address within the same terminal.

[Icehuck]

IceHuck

Just to confirm -- the terminal output stops -- correct?

This means you have been appropriately authenticated -- remember with the -d switch you are running this process in the foreground.

Just pop open another terminal window and type:
sudo dhclient wlan0

Once everything is up and working, the next time you want to connect, skip the -d flag and just use the -B flag which sends the process to the background without providing information. You can then request a dhcp address within the same terminal.

It was stopping after that line. However; after I turned my machine off and then started it up to try your suggestion I recieved a new error. This following output repeats for at least 10 minutes(that how long I left it going for). When I have ap_scan1 and scan_ssid=1 set that means my AP should be broadcasting it's SSID right?


Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ap_scan=1
ctrl_interface='/var/run/wpa_supplicant'
Priority group 0
id=0 ssid='xb332'
Initializing interface (2) 'wlan0'
Interface wlan0 set UP - waiting a second for the driver to complete initialization
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf flags 0x0
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1c:bf:0d:05:20
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Added interface wlan0
Ignore event for foreign ifindex 3
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b06 len=12
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=5):
78 62 33 33 32 xb332
Trying to get current scan results first without requesting a new scan to speed up initial association
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
Failed to get scan results
Failed to get scan results - try scanning again
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 5 seconds
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b19 len=16
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
Failed to get scan results
Failed to get scan results - try scanning again
Setting scan request: 1 sec 0 usec
EAPOL: disable timer tick
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=5):
78 62 33 33 32 xb332
Scan requested (ret=0) - scan timeout 30 seconds
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b19 len=16
Received 788 bytes of scan results (2 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:21:91:18:d4:2e ssid='xb332' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
selected based on WPA IE
selected WPA AP 00:21:91:18:d4:2e ssid='xb332'
Trying to associate with 00:21:91:18:d4:2e (SSID='xb332' freq=2462 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 24 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=28): dd 1a 00 50 f2 01 01 00 00 50 f2 02 02 00 00 50 f2 02 00 50 f2 04 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_psk
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b06 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b04 len=16
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8c02 len=216
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=24
Wireless event: new AP: 00:21:91:18:d4:2e
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:21:91:18:d4:2e
No keys have been configured - skip key clearing
Associated with 00:21:91:18:d4:2e
WPA: Association event - clear replay counter
WPA: Clear old PTK
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: enable timer tick
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=24
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
Added BSSID 00:21:91:18:d4:2e into blacklist
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such file or directory
Driver did not support SIOCSIWENCODEEXT
State: ASSOCIATED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 30 seconds
EAPOL: startWhen --> 0
EAPOL: disable timer tick
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:00:00:00:00:00 into blacklist
No keys have been configured - skip key clearing
State: SCANNING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=5):
78 62 33 33 32 xb332


BTW - Thanks for the quick response you gave on that.

[t0mppa]

@kevdog: I switched to b43 and it works now. Only the problem is that even though this is a a/b/g card, b43 recognizes it as a b card and puts b43legacy in control of it. That means a bit rate of 6 Mb/s instead of 54 Mb/s. But I guess that's the best possible solution for this card & Ubuntu, at least it's better than 0 Mb/s.

And it connects to WPA2 with no trouble on WICD, so thanks for your help and sorry about wasting your time with the NDISWrapper adventures.

[kevdog]

Icehuck

So yes the repetition you refer to means you are not being authenticated.

Try this:

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="xb332"
proto=WPA
key_mgmt=WPA-PSK
psk="mykey"
pairwise=TKIP
group=TKIP
}


Reading your output its weird since it states:
Associated to a new BSS: BSSID=00:21:91:18:d4:2e
No keys have been configured - skip key clearing
Associated with 00:21:91:18:d4:2e

Very strange on reviewing your post. It tells you that you are associated. Once you get this message and although the scrolling continues, can you try to request a dhcp address within another terminal window?

t0mppa
You may be right that your maximum rate may by 11 Mb/sec. You could try the following command to see if it makes a difference:

sudo iwconfig wlan0 rate 54M

or

sudo iwconfig wlan0 rate 11M

Typing ifconfig or iwconfig alone at the command line should give you the currently set rate.

[Icehuck]

Icehuck

So yes the repetition you refer to means you are not being authenticated.

Try this:

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="xb332"
proto=WPA
key_mgmt=WPA-PSK
psk="mykey"
pairwise=TKIP
group=TKIP
}


Reading your output its weird since it states:
Associated to a new BSS: BSSID=00:21:91:18:d4:2e
No keys have been configured - skip key clearing
Associated with 00:21:91:18:d4:2e

Very strange on reviewing your post. It tells you that you are associated. Once you get this message and although the scrolling continues, can you try to request a dhcp address within another terminal window?
.

Ok, I tried the different wpa_supplicant.conf but it still just scolls and goes from Associated > Disconnected. Also tried to do request a dhcp lease but it times out.

[kevdog]

IceHuck

Can you give me some ideas on the wireless driver you are using and can you post the exact commands you are typing at the command line!?

[Icehuck]

These are the commands I'm running inside from the CLI.

sudo ifconfig wlan0 down
sudo dhclient -r wlan0
sudo wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -d

I'm having wpa_supplicant use the wext driver to connect. Though I'm not sure if this is correct. When I do lshw -C network it tells me the wifi driver is iwl3945. I'll post my lshw -C network, wpa_supplicant.conf below.


lshw -C network


*-network
description: Wireless interface
product: PRO/Wireless 3945ABG [Golan] Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: wmaster0
version: 02
serial: 00:1c:bf:0d:05:20
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl3945 ip=192.168.0.197 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11abg


wpa_supplicant.conf



ctrl_interface=/var/run/wpa_supplicant

network={
ssid="xb332"
proto=WPA
key_mgmt=WPA-PSK
psk="brianne21"
pairwise=TKIP
group=TKIP
}

Having this setup gives me the output from the above post.

[kevdog]

Can you post

iwlist scan

Is your ssid broadcast or hidden? I would suggest for the time being to broadcast the ssid.

And lastly what if you just do this:

network={
ssid="xb332"
psk="brianne21"
}

Make sure there is a blank line at the end of the file.

[Icehuck]

Can you post

iwlist scan

Is your ssid broadcast or hidden? I would suggest for the time being to broadcast the ssid.

And lastly what if you just do this:

network={
ssid="xb332"
psk="brianne21"
}

Make sure there is a blank line at the end of the file.

My ssid is on broadcast. I will try changing my wpa_supplicant.conf to just those two lines. Before that, here is my iwlist scan.

iwlist scan


iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:21:91:18:D4:2E
ESSID:"xb332"
Mode:Master
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=74/100 Signal level:-60 dBm Noise level=-94 dBm
Encryption key:on
IE: Unknown: 00057862333332
IE: Unknown: 010482848B96
IE: Unknown: 03010B
IE: Unknown: 2A0100
IE: Unknown: 32080C1218243048606C
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F 00
IE: Unknown: 2D1A4E101BFFFF000000000000000000000000000000000000 000000
IE: Unknown: 3D160B071B0000000F000000000000000000000000000000
IE: Unknown: DD1E00904C336E101BFFFF0000000000000000000000000000 00000000000000
IE: Unknown: DD1A00904C340B07030000000F000000000000000000000000 000000
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=0000000be043d180
Extra: Last beacon: 52ms ago

pan0 Interface doesn't support scanning.

[Icehuck]

I made my config file say

network={
ssid="xb332"
psk="brianne21"
}

I still get this output that continuously repeats. I also added dmesg | tail blow this


Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
Priority group 0
id=0 ssid='xb332'
Initializing interface (2) 'wlan0'
Interface wlan0 set UP - waiting a second for the driver to complete initialization
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf flags 0x0
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1c:bf:0d:05:20
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Added interface wlan0
Ignore event for foreign ifindex 3
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b06 len=12
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 0 bytes of scan results (0 BSSes)
Cached scan results are empty - not posting
Selecting BSS from priority group 0
Try to find WPA-enabled AP
Try to find non-WPA AP
No suitable AP found.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 5 seconds
EAPOL: disable timer tick
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b19 len=16
Received 508 bytes of scan results (1 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:21:91:18:d4:2e ssid='xb332' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
selected based on WPA IE
selected WPA AP 00:21:91:18:d4:2e ssid='xb332'
Trying to associate with 00:21:91:18:d4:2e (SSID='xb332' freq=2462 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 24 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=28): dd 1a 00 50 f2 01 01 00 00 50 f2 02 02 00 00 50 f2 02 00 50 f2 04 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 04 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_psk
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b06 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b04 len=16
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8c02 len=216
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=24
Wireless event: new AP: 00:21:91:18:d4:2e
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:21:91:18:d4:2e
No keys have been configured - skip key clearing
Associated with 00:21:91:18:d4:2e
WPA: Association event - clear replay counter
WPA: Clear old PTK
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: enable timer tick
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=24
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
Added BSSID 00:21:91:18:d4:2e into blacklist
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such file or directory
Driver did not support SIOCSIWENCODEEXT
State: ASSOCIATED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 30 seconds
EAPOL: startWhen --> 0
EAPOL: disable timer tick
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:00:00:00:00:00 into blacklist
No keys have been configured - skip key clearing
State: SCANNING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 30 seconds
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b19 len=16
Received 506 bytes of scan results (1 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:21:91:18:d4:2e ssid='xb332' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
selected based on WPA IE
selected WPA AP 00:21:91:18:d4:2e ssid='xb332'
Trying to associate with 00:21:91:18:d4:2e (SSID='xb332' freq=2462 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 24 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=28): dd 1a 00 50 f2 01 01 00 00 50 f2 02 02 00 00 50 f2 02 00 50 f2 04 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 04 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_psk
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b06 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b04 len=16
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8c02 len=216
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=24
Wireless event: new AP: 00:21:91:18:d4:2e
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:21:91:18:d4:2e
No keys have been configured - skip key clearing
Associated with 00:21:91:18:d4:2e
WPA: Association event - clear replay counter
WPA: Clear old PTK
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: enable timer tick
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=24
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
BSSID 00:21:91:18:d4:2e blacklist count incremented to 2
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such file or directory
Driver did not support SIOCSIWENCODEEXT
State: ASSOCIATED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 30 seconds
EAPOL: startWhen --> 0
EAPOL: disable timer tick
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b19 len=16
Received 506 bytes of scan results (1 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:21:91:18:d4:2e ssid='xb332' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
skip - blacklisted
Try to find non-WPA AP
0: 00:21:91:18:d4:2e ssid='xb332' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
skip - blacklisted
No APs found - clear blacklist and try again
Removed BSSID 00:00:00:00:00:00 from blacklist (clear)
Removed BSSID 00:21:91:18:d4:2e from blacklist (clear)
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:21:91:18:d4:2e ssid='xb332' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
selected based on WPA IE
selected WPA AP 00:21:91:18:d4:2e ssid='xb332'
Trying to associate with 00:21:91:18:d4:2e (SSID='xb332' freq=2462 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 24 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=28): dd 1a 00 50 f2 01 01 00 00 50 f2 02 02 00 00 50 f2 02 00 50 f2 04 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 04 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_psk
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b06 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b04 len=16
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8c02 len=216
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=24
Wireless event: new AP: 00:21:91:18:d4:2e
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated with 00:00:00:00:00:00
WPA: Association event - clear replay counter
WPA: Clear old PTK
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: enable timer tick
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=24
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
Added BSSID 00:21:91:18:d4:2e into blacklist
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such file or directory
Driver did not support SIOCSIWENCODEEXT
State: ASSOCIATED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 30 seconds

dmesg | tail


[ 270.251568] wlan0: disassociating by local choice (reason=3)
[ 270.253370] wlan0: deauthenticated
[ 281.095600] wlan0: authenticate with AP 00:21:91:18:d4:2e
[ 281.098335] wlan0: authenticate with AP 00:21:91:18:d4:2e
[ 281.098351] wlan0: authenticated
[ 281.098355] wlan0: associate with AP 00:21:91:18:d4:2e
[ 281.106980] wlan0: RX ReassocResp from 00:21:91:18:d4:2e (capab=0x431 status=0 aid=1)
[ 281.106985] wlan0: associated
[ 281.110364] wlan0: disassociating by local choice (reason=3)
[ 281.112672] wlan0: deauthenticated

[kevdog]

This problem you are having is all over the place on the web

Its a conflict with the kernel and the ipw driver.

Ive seen one option recommend this:

It is to add the following line:

Code:

options iwl3945 disable_hw_scan=1

to the file:

Code:

/etc/modprobe.conf

You may have to create the file owned by root if it doesn't exist for you.

Another way to accomplish the above exact same thing is given here:
http://blog.dotkam.com/2008/11/17/configure-iwl3945-driver-on-ubuntu/

I hate intel chipsets because Ive found them to be quite buggy.
Another option for you is to reboot, and then selecting a different kernel at the grub menu. Its possibly a kernel problem and with the stock ubuntu install there are usually 2 different kernel versions included in the instal..

[Icehuck]

This problem you are having is all over the place on the web

Its a conflict with the kernel and the ipw driver.

Ive seen one option recommend this:

It is to add the following line:

Code:

options iwl3945 disable_hw_scan=1

to the file:

Code:

/etc/modprobe.conf

You may have to create the file owned by root if it doesn't exist for you.

Another way to accomplish the above exact same thing is given here:
http://blog.dotkam.com/2008/11/17/configure-iwl3945-driver-on-ubuntu/

I hate intel chipsets because Ive found them to be quite buggy.
Another option for you is to reboot, and then selecting a different kernel at the grub menu. Its possibly a kernel problem and with the stock ubuntu install there are usually 2 different kernel versions included in the instal..

Well those options didn't work. It's just kinda frustrating that I can connect just fine with network manager(which uses the iwl3945) but I can't do it from command line. Thanks for the help though, I appreciate the time you spent.

[kevdog]

Sorry those suggestions didn't work. I have no real experience with Intel Chipsets but likely will soon.

[stansford]

Sorry those suggestions didn't work. I have no real experience with Intel Chipsets but likely will soon.

Kevdog
Thanks for the help a week back. I have been away so wasn't able to reply to your post (#886).
Anyway wifi seems to be behaving at present with my realtek card so I'm happy.

One question though following on from your comment about not liking Intel chipsets....in your experience what type of chipset works the best in linux? Do you have a recommendation....or put it another way....what do you use?

thanks

[kerry_s]

for those that a want a friendlier way to set up networks without a network manger, you should try " network-config " it's in the repos.

i don't have my usb wifi plugged in so it's grayed out but you can still see the choices.

[kevdog]

stansford

I'm not certain if I can recommend one chipset over another. I can only tell you that I have a broadcom 4306 rev 03 wireless card, along with an atheros wireless card (can't remember number off the top of my head). Its hard for me however to recommend a broadcom or atheros because of the different revision numbers or revision chipsets each company makes. Some models or numbers do really well -- others not as well. Certain numbers take one driver, others taks a different driver. For example depending on your broadcom chipset revision number, you could use either a b43, wl/STA, bcm43xx, or ndiswrapper. Depending on the atheros chipset number you could use madwifi with the old HAL layer, the newer ath5k/ath9k modules that take advantage of the newer mac80211 networking stack within the kernel, or even ndiswrapper. Of course there are exceptions with some options requiring patching of sources etc. These exceptions are important to know for example if you need to put your wireless card into monitor mode to use it as an AP or use a tool such as Kismet or Aircrack-ng.

Chipset that I don't have a lot of experience with include ra chipsets, intel, and rtl. I'm not saying these chipsets are bad, but they all have their own set of nuances that only through experience and trial and error is it possible to master.

kerry_s
Ive never seen that utility before, however I should probably take a look. The purpose of this guide however was really however to avoid using a gui. This might be for example when your system crashes and all you have access to is a console app.

[stansford]

stansford

I'm not certain if I can recommend one chipset over another. I can only tell you that I have a broadcom 4306 rev 03 wireless card, along with an atheros wireless card (can't remember number off the top of my head). Its hard for me however to recommend a broadcom or atheros because of the different revision numbers or revision chipsets each company makes. Some models or numbers do really well -- others not as well. Certain numbers take one driver, others taks a different driver. For example depending on your broadcom chipset revision number, you could use either a b43, wl/STA, bcm43xx, or ndiswrapper. Depending on the atheros chipset number you could use madwifi with the old HAL layer, the newer ath5k/ath9k modules that take advantage of the newer mac80211 networking stack within the kernel, or even ndiswrapper. Of course there are exceptions with some options requiring patching of sources etc. These exceptions are important to know for example if you need to put your wireless card into monitor mode to use it as an AP or use a tool such as Kismet or Aircrack-ng.

Chipset that I don't have a lot of experience with include ra chipsets, intel, and rtl. I'm not saying these chipsets are bad, but they all have their own set of nuances that only through experience and trial and error is it possible to master.

kerry_s
Ive never seen that utility before, however I should probably take a look. The purpose of this guide however was really however to avoid using a gui. This might be for example when your system crashes and all you have access to is a console app.

Kevdog,
OK I kind of guessed that it was a real mixed bag re linux support and probably the most frustrating thing is that the way some support changes with the kernels. One time one method works and then another release comes out and it changes. That was my experience before getting the wpa_supplicant method to work anyway.

Anyway I now have 3 types of Realtek cards (2 PCI and 1 USB) and a Zydas based USB (3com) dongle all working pretty reliably via your method so as I said before I'm pretty happy.
Many thanks for your help.

[kerry_s]

kerry_s
Ive never seen that utility before, however I should probably take a look.


you should definitely give it a try, it's pretty sweet, uses the command line commands wrapped in gtk2-pearl.(see pic)



The purpose of this guide however was really however to avoid using a gui. This might be for example when your system crashes and all you have access to is a console app.


yeah, i was just throwing it out there, just in case. i wish someone had told me about it, i just came across it a couple of days ago.
i couldn't believe how absolutely simple it is.
you can have different profiles for different places.

it does have a few short comings, but there minor at best, example the "scan wifi networks" usually only shows the name and if it's protected.(see pic)
once you select and choose apply, you have to wait, the quit button is grayed out, you should be able to quit if it's taking to long, again it's a minor thing.
it's a manual thing, there's no auto about it. also minor, unless your one of those that get connection drops and have to keep clicking it to reapply. i'm not 1 of those. :)
on the plus side:
it has no running daemons, so very light
dead simple, to switch back and fourth between connections/setups/spots.

i forgot the pics for the main> preferences
here's those.

[Fischer]

Kevdog,

I have been trying to get your tutorial to work for the past few hours and I can make it work if I take the encryption off my network. Since that is not the most desirable way to communicate with my router, I've been trying to get my wireless card to connect via WPA-Personal encryption.

Im using a Ra-based chipset (I think)

when I type:

sudo iwpriv wlan0 set AuthMode=WPA-PSK

which returns: "Invalid command: set"
this happens with all the iwpriv commands.

please assist. this is for my little brothers computer and I am leaving on sunday ( i dont think they will be able to get it running without me)

also my network manager doesnt appear to work. when I connected to the unencrypted network, it didn't reflect it on the top right corner of the screen. it still had the red x.

Thanks

[kevdog]

Im no expert on ra chipsets, but why don't you try the standard way for now, meaning no iwpriv statements and then let me know what happens. The ra drivers have changed recently so some of the older techniques may not be applicable.

[Fischer]

Hey thanks for the response, I used the network-config app that someone suggested and it worked once i changed the specified driver to "wext". i guess the Ra method didnt work since the app incorporates wpa supplicant.

[kevdog]

Do to the way wpasupplicant is compiled in the newer kernels, only wext support is built into the compiled version. Please note this was not what it used to be. Its possible to compile the newer source code to include such specific driver support such as for ra, however it involves compiling, and also it seems that wext is a most suitable solution for almost everything.

[afeasfaerw23231233]

Hi, I'm running Ubuntu 9.04 32-bit. The internal USB wireless LAN card is Realtek 8187L. By following your great Howto I successfully established a WPA2 connection with my router. However the internal wireless card fail to start automatically during boot and I must press Fn+F10 to trigger on the wireless everytime.

How can I let the wireless card connect to the router automatically right after I press Fn+F10?

The following lines are for connecting to the router manually

sudo ifconfig wlan0 down
sudo dhclient -r wlan0
sudo wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B
sudo dhclient wlan0

Or, if it is possible to start the internal card automatically during boot? In XP the wifi is on automatically during boot. But in Ubuntu it is off unless I press Fn+F10 to trigger it on.

Many thanks!

[kevdog]

Im not sure if I can answer your question. Let me know if you find an answer.

[afeasfaerw23231233]

I find the solution by following this guide: http://ubuntuforums.org/showthread.php?t=202834
Now whenever I press Fn+F10 the wireless would auto connect.

[the_guv]

well, that was testing!

Kevdog .. thank you for your excellent guide. You are a star. Hi and lo, I had searched.

Maricaibo (http://ubuntuforums.org/member.php?u=458444) .. thank you too. You got me automated.

Kevdog .. you may consider amending your guide to include the rc whatnot details, for wifi startup. Or at least, they worked for me, WPA2 on Jaunty 64bit, on the HP Pavillion DV3500 Intel wifi adapter, using wicd (eventually .. I think wicd may just have an issue with a D-Link 635, cos it seems to leap on everything else.)

Superb tutorial and thread.

[kevdog]

the_guv

Can you tell me what you mean by the rc thing?

[De Baimbo]

thanks for the tutorial, I am trying to connect to my unprotected wireless network, wich works just fine with windows.
I am on Ubuntu 9.04



simo@simo-laptop:~$ sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 No scan results

pan0 Interface doesn't support scanning.

wmaster1 Interface doesn't support scanning.

wlan1 Scan completed :
Cell 01 - Address: 00:17:3F:60:E1:93
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=51/100 Signal level=51/100
Encryption key:off
ESSID:"belkin54g"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=00000016698570f4
Extra: Last beacon: 156ms ago
IE: Unknown: 000962656C6B696E353467
IE: Unknown: 010882848B962430486C
IE: Unknown: 03010B
IE: Unknown: 2A0100
IE: Unknown: 2F0100
IE: Unknown: 32040C121860
IE: Unknown: DD06001018020001

simo@simo-laptop:~$ sudo ifconfig wlan1 down
simo@simo-laptop:~$ sudo dhclient -r wlan1
There is already a pid file /var/run/dhclient.pid with pid 19379
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan1/00:02:72:57:a6:f1
Sending on LPF/wlan1/00:02:72:57:a6:f1
Sending on Socket/fallback
simo@simo-laptop:~$ sudo ifconfig wlan1 up
simo@simo-laptop:~$ sudo iwconfig wlan1 essid "belkin54g"
simo@simo-laptop:~$ sudo iwconfig wlan1 mode Managed
simo@simo-laptop:~$ sudo dhclient wlan1
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan1/00:02:72:57:a6:f1
Sending on LPF/wlan1/00:02:72:57:a6:f1
Sending on Socket/fallback
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 10
No DHCPOFFERS received.
No working leases in persistent database - sleeping


it sees the wi-fi network but it can't connect to it.
sometimes it actually gets connected if I try to connect clicking on the networkmanager icon, but it stays connected for maximum 5 minutes and then it disconnects

I am also sure it doesn't depend on my wireless card, because I also tried to connect via usb wireless cards and it shows the same behavior.

[kevdog]

That's a real hard one to debug -- it looks like you are doing everything correctly. The only one issue I am having is with the wlan1 interface. What do you have installed as wlan0? or pan0? What do these interfaces represent? Card type and driver please!

[De Baimbo]

wlan0 is my internal wireless card
wlan1 is my usb wireless card (I tried two of them, the system automatically recognises them and they work just fine in every other laptop with ubuntu 9.04, so I suppose they work fine here too)

[halalkebabhut]

Hi,

I'm trying to manually connect my wireless as Network manager interferes with my Jack Audio. I've followed the instructions for unsecured and WEP encryption but in both cases get the following situation ...




simonkatan@ubuntu:~$ sudo dhclient eth1
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:26:5e:11:0b:2d
Sending on LPF/eth1/00:26:5e:11:0b:2d
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

this is my network as at it appears in iwlist scan

eth1 Scan completed :
Cell 01 - Address: 00:19:E0:A3:35:94
ESSID:"TP-LINK"
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:5/5 Signal level:-46 dBm Noise level:-92 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s

am I doing something wrong ? please help

:(

[kevdog]

Please post your commands.

[halalkebabhut]

whoops sorry - I got it to work using

sudo iwconfig eth1 essid MYNETWORK (no quotes!)
sudo iwconfig eth1 key s:myweppassword
sudo dhclient eth1

seems simple enough - now trying to get it do this automatically on start-up

[kerry_s]

whoops sorry - I got it to work using

sudo iwconfig eth1 essid MYNETWORK (no quotes!)
sudo iwconfig eth1 key s:myweppassword
sudo dhclient eth1

seems simple enough - now trying to get it do this automatically on start-up

in /etc/network/interfaces:


auto eth1
iface eth1 inet dhcp
wireless-essid MYNETWORK
wireless-key s:xxxxxxxxxxxxx

[kerry_s]

i got a simple question, are you using a replacement applet for the network?
if so, which 1 ?

i been looking for a applet, so i know its connected.
currently i'm using "netspeed" which is okay, but maybe your using something nicer? :)

[kevdog]

I usually use WICD which provides an applet. The manual connection method is for troubleshooting or used when things just plain break or for experimenting with aircrack.

[kerry_s]

I usually use WICD which provides an applet. The manual connection method is for troubleshooting or used when things just plain break or for experimenting with aircrack.

i use the manual method all the time, it's just a lot faster. i've now switched to the "gnome-netstatus-applet", which gives pretty much the same look & if its not connected it has a red x.
i just installed the remix stuff late last night so i cut back to just the main applets.

[kevdog]

Where do you get that applet?

[kerry_s]

Where do you get that applet?

sudo apt-get install gnome-netstatus-applet

[pratiks19]

I've some problems connecting to my university wireless network.

plz check out my post:
http://ubuntuforums.org/showthread.php?p=7834638

[Scoobyhuw]

Thank you, thank you, thank you! You have ended a problem I get with every upgrade of my mum's laptop. Excellent stuff, Thank You!

[cailamaia]

Hi everyone, I have a question for y'all.

This morning, my wireless internet connection decided not to work. I have no idea why, as it was working fine yesterday evening. The wired connection is fine, and is how I am able to post this.

I just tried following this guide, but it didn't work for some reason. Here is the log of my terminal output:




selma@Horation:~$ sudo iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11abgn Mode:Managed Frequency:2.437 GHz
Access Point: Not-Associated Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

vboxnet0 no wireless extensions.

selma@Horation:~$ sudo ifconfig wlan0 down
selma@Horation:~$ sudo dhclient -r wlan0
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:16:ea:c3:52:28
Sending on LPF/wlan0/00:16:ea:c3:52:28
Sending on Socket/fallback
selma@Horation:~$ sudo ifconfig wlan0 up
selma@Horation:~$ sudo iwconfig wlan0 essid “gruetzi”
selma@Horation:~$ sudo iwconfig wlan0 key 8FD11DE0D267F9D3280046A674
selma@Horation:~$ sudo iwconfig wlan0 key restricted
selma@Horation:~$ sudo iwconfig wlan0 mode Managed
selma@Horation:~$ sudo dhclient wlan0
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:16:ea:c3:52:28
Sending on LPF/wlan0/00:16:ea:c3:52:28
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
* Reloading /etc/samba/smb.conf smbd only
...done.



As you can see, it didn't give me any errors, but I cannot connect despite that.

[drpaul]

What is the result of sudo iwconfig eth1 [or wlan0] after you have set the parameters? The initial result shows no connection.

Paul

[cailamaia]

This is what it returns:



selma@Horation:~$ sudo iwconfig wlan0
[sudo] password for selma:
wlan0 IEEE 802.11abgn Mode:Managed Frequency:2.437 GHz
Access Point: Not-Associated Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

[drpaul]

It's not showing the result of your iwconfig statements. Did you do the latest command after those?

If so, they aren't taking, and I don't know why.

Paul

[kevdog]

Yea for Longmont CO

You probably don't need these commands:
sudo iwconfig wlan0 key restricted
sudo iwconfig wlan0 mode Managed

What chipset are you using?

[drpaul]

kevdog-

I just installed 9.10 over 8.04, and wireless no longer works. The normal manual steps fail at the last step.

commands
sudo ifconfig wlan0 down
sudo dhclient -r wlan0
sudo ifconfig wlan0 up
sudo iwconfig wlan0 essid "cozycave"
sudo iwconfig wlan0 key xxxxxxxxxxxxxxxxxxxxxxxxxx
sudo iwconfig wlan0 mode Managed
sudo dhclient wlan0

results
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:18:de:1c:27:7e
Sending on LPF/wlan0/00:18:de:1c:27:7e
Sending on Socket/fallback
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:18:de:1c:27:7e
Sending on LPF/wlan0/00:18:de:1c:27:7e
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

NetworkManager will not start. Here is the result of NetworkManager --no-deamon

NetworkManager: <info> starting...
NetworkManager: <info> modem-manager is now available
NetworkManager: SCPlugin-Ifupdown: init!
NetworkManager: SCPlugin-Ifupdown: update_system_hostname
NetworkManager: SCPluginIfupdown: management mode: unmanaged
NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0/net/wlan0, iface: wlan0)
NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0/net/wlan0, iface: wlan0): no ifupdown configuration found.
NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0/net/wmaster0, iface: wmaster0)
NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0/net/wmaster0, iface: wmaster0): no ifupdown configuration found.
NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1e.0/0000:05:08.0/net/eth0, iface: eth0)
NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1e.0/0000:05:08.0/net/eth0, iface: eth0): no ifupdown configuration found.
NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/lo, iface: lo)
NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
NetworkManager: SCPlugin-Ifupdown: end _init.
NetworkManager: Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list.
NetworkManager: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
NetworkManager: <info> Found radio killswitch rfkill0 (at /sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0/ieee80211/phy0/rfkill0) (driver <unknown>)
NetworkManager: <WARN> nm_dbus_manager_start_service(): Could not acquire the NetworkManager service as it is already taken.
NetworkManager: <WARN> main(): Failed to start the dbus service.
NetworkManager: <info> exiting (error)

Any suggestions/pointers will be welcome.

Paul

[drpaul]

kevdog-

A word to the wary--

I installed wicd and dropped NetworkManager and my manual script connects just fine. My hardware is not weird.

I'll be happy to send you any info you want, but the standard distro looks bad to me.

Have a nice day.

Paul

[amandkumar]

Very good share.
I will try this out when my network manager dosnt work. Does this code will harm the computer by slowing down the process or some thing else.

[marseille]

:KS :KS :KS :KS :KS five star manual indeed.

this just worked like a charm on my acer apsire 10" netbook w/ 9.10 ubuntu netbook remix, using fluxbox as my default desktop.

i have been suffering from days of no internet after i tried to set-up windows for a class at school -- the dang thing tried to eat grub2 and sabotage my connection ;(

long story short... at first, i was able to ping the router but eventually the problem just pulled a 169.killed.the.net and left me w/ a PC icon w/an `X' instead of a graphed nm-applet.

this tutorial pulled through. i even went so far as happily removing gnome network manager (but opted to keep wifi-radar).

[marcopolo1981]

Hi and thank you for this well thought out tutorial!

I have an issue. I can connect wirelesly manually via CLI, but I can't get it to start at boot.

I have inserted ;


ifconfig eth0 down
ifconfig eth1 down
dhclient -r eth1
ifconfig eth1 up
iwconfig eth1 essid "linksys"
iwconfig eth1 mode Managed
dhclient eth1

exit 0

into the rc.local file. These are the commands I use to manually start the connection without problems. But it doesn't seem to execute this file at boot.

I have run chmod +x /etc/rc.local, so I am lost.

Any body have a clue what I am doing wrong?

[kevdog]

Sorry about the delay -- No rc.local file run at boot for you?? What version of Ubuntu are your using?

[marcopolo1981]

Hi.
Yeah, I am running plain old Ubuntu 9.10 X64.
Output from uname -a is

Linux ubuntu 2.6.31-20-generic #57-Ubuntu SMP Mon Feb 8 09:02:26 UTC 2010 x86_64 GNU/Linux


I can't get it to run at boot at all. But manually running those commands work perfectly.

[kerry_s]

i only use 3 commands in mine:


ifconfig wlan0 up &
iwconfig wlan0 essid hidden &
dhclient wlan0 &

i use "&" on the end to background it while it continues to boot.

[christer_f]

Hi Kevdog,
Thanks for a great tutorial.
I have the same problem as drpaul (#939 & #940). Is there a problem with NetworkManager and manual setup in Ubuntu 9.10?

In fact, my NetworkManager-applet connects with no problem (I use a 26 hex-digit WEP key).
However, I would like to be able to make the connections from a script that provides essid and key, and I followed the steps in your tutorial. Unfortunately with little luck.
With the ethernet physically disconnected and wireless network disconnetced (from the NetworkManager-applet), I run into the same problem as drpaul, with the dhclient not managing to get a lease:

After the unsuccessful

$ sudo dhclient wlan0

this is what I get from

$ sudo iwconfig




....
wlan0 IEEE 802.11bg ESSID:"LADIFREE"
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:7594-F110-2A4D-XXXX-1E66-61DA-F0
Power Management:on
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0(where I have replaced 4 hex characters in the key by "xxxx")


Can this be due to a conflict between iwconfig and the NetworkManager? Or doesn't iwconfig support 26 hex-digit keys?

-- christer

[aznguyphan]

Thanks a lot for this, helped me do a minimal Ubuntu install.

[Martin Anthony]

I have some problems with the script to work, first I run the lshw, see below.


martin@anthony-laptop:~$ lshw -c network
WARNING: you should run this program as super-user.
*-network:0
description: Wireless interface
product: PRO/Wireless 2200BG [Calexico2] Network Connection
vendor: Intel Corporation
physical id: 5
bus info: pci@0000:01:05.0
logical name: eth1
version: 05
serial: 00:0e:35:39:ad:fa
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ipw2200 driverversion=1.2.2kmprq firmware=ABG:9.0.5.27 (Dec 12 2007) ip=192.168.0.2 latency=64 maxlatency=24 mingnt=3 multicast=yes wireless=IEEE 802.11g
resources: irq:11 memory:cffff000-cfffffff
*-network:1
description: Ethernet interface
product: 82801DB PRO/100 VE (MOB) Ethernet Controller
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:01:08.0
logical name: eth0
version: 83
serial: 00:0e:7b:13:1c:14
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=e100 driverversion=3.5.24-k2-NAPI firmware=N/A latency=64 maxlatency=56 mingnt=8 multicast=yes
resources: irq:11 memory:cfffe000-cfffefff ioport:cf00(size=64)
martin@anthony-laptop:~$



And then I run this script:



#!/bin/bash
sudo ifconfig eth1 down
sudo dhclient -r eth1
sudo ifconfig eth1 up
sudo iwconfig eth1 essid "anthony"
sudo iwconfig eth1 key 1234567890
sudo iwconfig eth1 mode Managed
sudo dhclient eth1


And get this message:



martin@anthony-laptop:~$ ./wireless_3.sh
There is already a pid file /var/run/dhclient.pid with pid 2100
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:0e:35:39:ad:fa
Sending on LPF/eth1/00:0e:35:39:ad:fa
Sending on Socket/fallback
DHCPRELEASE on eth1 to 192.168.0.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:0e:35:39:ad:fa
Sending on LPF/eth1/00:0e:35:39:ad:fa
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
martin@anthony-laptop:~$





Can you see any thing wrong, with my script?

[drpaul]

I think that there may be a problem with what you are entering for your key. I realize that you you didn't want to put your real key in there, but it is expecting a hex format key as in this excerpt

sudo iwconfig eth1 key HEX_KEY <<<-------- If using ASCII Equivalent, this is s:ASCII_KEY (please make note of the prefix s:)

HTH

Paul

[MasMas]

Sorry for bothering, but every upgade of my Ubuntu brings network down... so I'm trying to find some help.
This time I had 9.04 and upgraded to 9.10... wireless stopped working.

I had an ASUS p5w deluxe with rtl8187 wireless card, I used the win98 drivers with ndiswrapper and uninstalled network manager and so.

I think the driver is still correcly installed, all as before.

an iwlist wlan0 scan finds my wireless network but my card seems not able to connect to it.

My iwconfig says:
wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:20 dBm Sensitivity=0/3
RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

If I put down and up the connection and try to associate to the AP it still remains unassociated...

Some peoples says me to use wicd, use another dirver and so, but I:
1. does not have an internet connection in the machine (so I cannot easilly download modules and such);
2. since before it functioned, I think something in the upgrade get in the way of a functionign installation.

So, has anyone a functioning ASUS P5W deluxe wifi connection with 9.10? In this case, what configuration are you using?

Alternatively, someone knows if 9.04 to 9.10 intorduces something that can ruin the wireless configuration?

Or can someune tell me some places to look to logs or so to understand why my connection cannot get its essid?

Thank you

[btindie]

I've been trying to do a minimal Ubuntu 9.10 wireless install using the mini.iso bootstrapping it via grub. After adding the required firmware to initrd.gz which in my case was rt73.bin it was able to use the wireless.

I did however have to mount and chroot into an existing installation to get access to the iwconfig command. In addition to the commands mentioned in the original post to get the wireless working correctly I did also have to do


iwconfig wlan0 channel 11

in addition, though I don't know if it was absolutely required, I manually set the key mode to open.

With the Lucid mini.iso I've found that all I've had to do is add the firmware to initrd.gz and it's been able to configure the wireless by itself.

EDIT:

I've had no end of problems trying to get my wireless connection to work using just the wireless-tools package for a mini install of Ubuntu, that's connecting via WEP. After adding the firmware to initrd the install went fine but after a reboot it stopped working. I've been trying to get it working via /etc/network/interfaces with wireless-* options. From that I've had some strange results.

The output of iwconfig wlan0 indicates that it's associated to the access point but when I run tcpdump along with dhclient I can see the requests going out but there's no reply from the access point. I have seen ARP requests coming in from the AP. Then for some reason after installing wpasupplicant and modifying /etc/network/interfaces to use the wpa-* options and restarting the network it all of a sudden comes to life!

[phaile]

You wee beauty :) This got me up and running in no time, thanks very much!

[menachem]

This is a great tutorial.

I didn't read all 69 pages of this thread, so I don't know if this was answered already.

Once you've configured and connected to the wireless network using the command line, how do you monitor it? I don't necessarily need real time updates, but what commands would I use to get information such as signal strength. Also, if I suspect there is something wrong with the connection and want to check it out.

[drpaul]

to the previous post:

sudo iwconfig

gives very useful info

HTH

Paul

[zebedeuzeu]

I don't really know if this has already been answered, but can you help me conecting to a wired network through the terminal? I've uninstalled network manager and I'm not being ale to install it again... (I don't have any kind of Internet conection on my Ubuntu pc, neither wired or wireless because of this situation) Also, can you talk a little something about what's Static IP? Ty!

[zebedeuzeu]

being able*

[Martin Anthony]

I don't really know if this has already been answered, but can you help me conecting to a wired network through the terminal? I've uninstalled network manager and I'm not being ale to install it again... (I don't have any kind of Internet conection on my Ubuntu pc, neither wired or wireless because of this situation) Also, can you talk a little something about what's Static IP? Ty!


Try to read page 1.

[hickorynutz]

Page one works for me, thanks! Ubuntu 10.10, belkin wireless router,
cable modem. Wicd, wifi-radar, net-applet all would lose connection
during downloads. Also worked on Ubuntu 10.04 and didn't lose connection
in the many downloads in upgrading to 10.10. Thanks again!

[bgmainx]

product: AR5001 Wireless Network Adapter
vendor: Atheros Communications Inc.

Trying to connect to WPA 1:

borimir@borimir-laptop:~$ gksu gedit /etc/wpa_supplicant.conf

ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="Mainx"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk="diablo0o"
pairwise=TKIP
group=TKIP
}




borimir@borimir-laptop:~$ gksu gedit /etc/wpa_supplicant.conf
borimir@borimir-laptop:~$ sudo ifconfig ath0 down
borimir@borimir-laptop:~$ sudo dhclient -r ath0
Internet Systems Consortium DHCP Client V3.1.3
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:1b:9e:52:5f:a8
Sending on LPF/ath0/00:1b:9e:52:5f:a8
Sending on Socket/fallbackAfter entering the "sudo wpa_supplicant -Dwext -iath0 -c/etc/wpa_supplicant.conf -dd" command I get :


Initializing interface 'ath0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ap_scan=1
ctrl_interface='/var/run/wpa_supplicant'
Line: 4 - start of a new network block
ssid - hexdump_ascii(len=5):
4d 61 69 6e 78 Mainx
scan_ssid=0 (0x0)
proto: 0x1
key_mgmt: 0x2
PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED]
pairwise: 0x8
group: 0x8
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='Mainx'
Interface ath0 set UP - waiting a second for the driver to complete initialization
SIOCGIWRANGE: WE(compiled)=22 WE(source)=18 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf flags 0x0
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1b:9e:52:5f:a8
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
WPS: UUID based on MAC address - hexdump(len=16): 8f 36 0a 69 4d 47 5b 93 b5 63 a2 c7 ca 84 23 56
WPS: Build Beacon and Probe Response IEs
WPS: * Version
WPS: * Wi-Fi Protected Setup State (0)
WPS: * Version
WPS: * Wi-Fi Protected Setup State (0)
WPS: * Response Type (2)
WPS: * UUID-E
WPS: * Manufacturer
WPS: * Model Name
WPS: * Model Number
WPS: * Serial Number
WPS: * Primary Device Type
WPS: * Device Name
WPS: * Config Methods (0)
WPS: * RF Bands (3)
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Added interface ath0
RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Ignore event for foreign ifindex 3
Ignore event for foreign ifindex 3
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Wireless event: cmd=0x8b06 len=8
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 2506 bytes of scan results (11 BSSes)
New scan results available
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:25:53:8f:54:06 ssid='Mainx' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
skip WPA IE - PTK cipher mismatch
1: 94:0c:6d:e8:88:6e ssid='marko' wpa_ie_len=0 rsn_ie_len=24 caps=0x11
skip - SSID mismatch
2: 00:1e:73:50:44:73 ssid='Mi6letata' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
3: 00:1f:33:41:c5:1e ssid='NETGEAR' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
skip - SSID mismatch
4: 38:22:9d:13:df:3a ssid='DEEPTHOUGHT' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
skip - SSID mismatch
5: 00:27:19:f9:b7:06 ssid='dorotea' wpa_ie_len=26 rsn_ie_len=24 caps=0x11
skip - SSID mismatch
6: 00:22:3f:83:67:b4 ssid='TODOROV' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
7: 00:1d:73:bb:0c:ec ssid='niko' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
8: 00:25:53:8f:54:07 ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
skip - no WPA/RSN IE
9: 00:1e:73:59:0e:ab ssid='BTC-ADSL' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
skip - no WPA/RSN IE
10: 38:22:9d:13:df:3b ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:25:53:8f:54:06 ssid='Mainx' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
skip - non-WPA network not allowed
1: 94:0c:6d:e8:88:6e ssid='marko' wpa_ie_len=0 rsn_ie_len=24 caps=0x11
skip - SSID mismatch
2: 00:1e:73:50:44:73 ssid='Mi6letata' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
3: 00:1f:33:41:c5:1e ssid='NETGEAR' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
skip - SSID mismatch
4: 38:22:9d:13:df:3a ssid='DEEPTHOUGHT' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
skip - SSID mismatch
5: 00:27:19:f9:b7:06 ssid='dorotea' wpa_ie_len=26 rsn_ie_len=24 caps=0x11
skip - SSID mismatch
6: 00:22:3f:83:67:b4 ssid='TODOROV' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
7: 00:1d:73:bb:0c:ec ssid='niko' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
8: 00:25:53:8f:54:07 ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
skip - SSID mismatch
9: 00:1e:73:59:0e:ab ssid='BTC-ADSL' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
skip - SSID mismatch
10: 38:22:9d:13:df:3b ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
skip - SSID mismatch
No suitable AP found.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 5 seconds
EAPOL: disable timer tick
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Wireless event: cmd=0x8b19 len=8
Received 2729 bytes of scan results (12 BSSes)
New scan results available
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:25:53:8f:54:06 ssid='Mainx' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
skip WPA IE - PTK cipher mismatch
1: 00:1e:73:50:44:73 ssid='Mi6letata' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
2: 94:0c:6d:e8:88:6e ssid='marko' wpa_ie_len=0 rsn_ie_len=24 caps=0x11
skip - SSID mismatch
3: 00:1f:33:41:c5:1e ssid='NETGEAR' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
skip - SSID mismatch
4: 38:22:9d:13:df:3a ssid='DEEPTHOUGHT' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
skip - SSID mismatch
5: 00:27:19:f9:b7:06 ssid='dorotea' wpa_ie_len=26 rsn_ie_len=24 caps=0x11
skip - SSID mismatch
6: 00:22:3f:83:67:b4 ssid='TODOROV' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
7: 00:1d:73:bb:0c:ec ssid='niko' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
8: 00:1d:0f:e8:99:34 ssid='Aok' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
9: 00:25:53:8f:54:07 ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
skip - no WPA/RSN IE
10: 00:1e:73:59:0e:ab ssid='BTC-ADSL' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
skip - no WPA/RSN IE
11: 38:22:9d:13:df:3b ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:25:53:8f:54:06 ssid='Mainx' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
skip - non-WPA network not allowed
1: 00:1e:73:50:44:73 ssid='Mi6letata' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
2: 94:0c:6d:e8:88:6e ssid='marko' wpa_ie_len=0 rsn_ie_len=24 caps=0x11
skip - SSID mismatch
3: 00:1f:33:41:c5:1e ssid='NETGEAR' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
skip - SSID mismatch
4: 38:22:9d:13:df:3a ssid='DEEPTHOUGHT' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
skip - SSID mismatch
5: 00:27:19:f9:b7:06 ssid='dorotea' wpa_ie_len=26 rsn_ie_len=24 caps=0x11
skip - SSID mismatch
6: 00:22:3f:83:67:b4 ssid='TODOROV' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
7: 00:1d:73:bb:0c:ec ssid='niko' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
8: 00:1d:0f:e8:99:34 ssid='Aok' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
9: 00:25:53:8f:54:07 ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
skip - SSID mismatch
10: 00:1e:73:59:0e:ab ssid='BTC-ADSL' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
skip - SSID mismatch
11: 38:22:9d:13:df:3b ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
skip - SSID mismatch
No suitable AP found... and keeps scanning for AP, until I hit CTRL+C.

Any ideas? : (

[jelly]

Thank you so much for this, it's allowed me to get my lucid server install on my eee 701 talking to the world.

[COKEDUDE]

The user settings will be stored here.


/home/userdirectory/.gconf/system/networking/connections

http://www.arachnoid.com/linux/NetworkManager/

The System settings will be stored here.



/etc/NetworkManager

/etc/NetworkManager/system-connections

[berserkpi]

Hi there, I was reading your manual but I have a problem to be started... It doesn't have a logical name assigned. Also the driver is not there (it is UNCLAIMED).. But ndiswrapper says the driver is installed... I've tried using winxp,winvista drivers... not a chance.

I'm using ubuntu 11.04 x64.

lshw -C network

*-network UNCLAIMED
description: Network controller
product: Realtek Semiconductor Co., Ltd.
vendor: Realtek Semiconductor Co., Ltd.
physical id: 2
bus info: pci@0000:03:02.0
version: 00
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration: latency=32 maxlatency=64 mingnt=32
resources: ioport:d000(size=256) memory:fe500000-fe500fff

lspci

00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation 2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 05)
00:1a.0 USB Controller: Intel Corporation 6 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series Chipset Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.3 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 4 (rev b5)
00:1d.0 USB Controller: Intel Corporation 6 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation H67 Express Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series Chipset Family 6 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series Chipset Family SMBus Controller (rev 05)
01:00.0 VGA compatible controller: ATI Technologies Inc Juniper [Radeon HD 5700 Series]
01:00.1 Audio device: ATI Technologies Inc Juniper HDMI Audio [Radeon HD 5700 Series]
02:00.0 PCI bridge: Integrated Technology Express, Inc. Device 8892 (rev 10)
03:02.0 Network controller: Realtek Semiconductor Co., Ltd. Device 8190
04:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03)

ndiswrapper -l

net819xp : driver installed
device (10EC:8190) present

[darko84]

hi all guys
i have ubuntu server and i have configured etc/network/interfaces to connect with an open network.
In the night this network go down and i have the possibility to connect with my network(wep protection).How can i connect with my network only on the night?Is it possibile to connect the same interface(wlan0) alternatively to the 2 wireless network?if yes,how?thank you very much!

[opodaniel]

I got problems connecting by wifi on my Intel 3945 abg. Here are the step that worked for me:
1 - to connect to wifi the ASCI (text) password won't work so I generate the password and add it to /etc/network/interfaces prior to any other changes
$sudo wpa_passphrase mywifinetwork secretwpa2key >> /etc/network/interfaces
this added
wpa-ssid homezone
# hexadecimal psk is encoded from a plaintext passphrase
wpa-psk 000102030405060708090a0b0c0d0e0f101112131415161718 191a1b1c1d1e1f
to interfaces

2- After doing this I added the following
$sudo nano /etc/network/interfaces


allow-hotplug wlan0
iface wlan0 inet dhcp
wpa-ssid homezone
# hexadecimal psk is encoded from a plaintext passphrase
wpa-psk 000102030405060708090a0b0c0d0e0f101112131415161718 191a1b1c1d1e1f

[kevdog]

I got problems connecting by wifi on my Intel 3945 abg. Here are the step that worked for me:
1 - to connect to wifi the ASCI (text) password won't work so I generate the password and add it to /etc/network/interfaces prior to any other changes
$sudo wpa_passphrase mywifinetwork secretwpa2key >> /etc/network/interfaces
this added
wpa-ssid homezone
# hexadecimal psk is encoded from a plaintext passphrase
wpa-psk 000102030405060708090a0b0c0d0e0f101112131415161718 191a1b1c1d1e1f
to interfaces

2- After doing this I added the following
$sudo nano /etc/network/interfaces

Great tip -- not sure I can incorporate this into the original guide - but nice find none-the-less!!

[vosnack]

I can't do it. My Wireless Network is simply DISABLED and whatever I try doesn't work. If someone could point me in the right direction I would be more than thankful. I try to install Belkin N Wireless USB Adapter F5D8053 on Ubuntu 10.04. I tried almost everything I could find on the internet. I found that drivers for this device should already be here so I've got rt2870 and rt2860, disabled rt2800usb(blacklist). Tried all the modprobe commands etc. But because my linux understanding is limited I don't really know the processes and I think some link is missing. Anyway the dongle's light doesn't turn on. Please help

[vosnack]

Some output:
for lshw -C network
*-network
description: Ethernet interface
product: NetXtreme BCM5751 Gigabit Ethernet PCI Express
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 01
serial: 00:11:43:ca:94:40
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=tg3 driverversion=3.102 firmware=5751-v3.29a ip=192.168.1.64 latency=0 multicast=yes
resources: irq:16 memory:dfcf0000-dfcfffff
*-network DISABLED
description: Wireless interface
physical id: 1
logical name: wlan0
serial: 94:44:52:44:0f:cf
capabilities: ethernet physical wireless
configuration: broadcast=yes multicast=yes wireless=802.11b/g

[vosnack]

km@km-desktop:~$ sudo lsmod | grep rt28*
[sudo] password for km:
rt2860sta 481561 0
rt2870sta 461811 0

[kevdog]

I don't know a lot about your device, only that the two kernel modules you have loaded rt2860sta, rt2870sta don't seem to be the correct drivers. Are you sure these are correct? Does dmesg give you any hint whats going on when the drivers are loaded either at boot or by hand with the modprobe statements?

[vosnack]

Hi. Thank you for your interest. You would have to walk me through it as I don't really know what you mean. As I mentioned I've got no idea how ubuntu works. how do I read the output? the problem i'm facing is that nothing happens even though i followed the exact instructions. At the moment I would need someone with the knowledge to help me as I tried few solutions and nothing. And I'm starting to wonder whether I didn't mess up something by following wrong instructions. The main problem is that there's no communication with dongle but usb can see it as 'belkin corporation' or something like that. I don't think it realizes it's a network card.

[vosnack]

Anyone willing to help me?

[nowifi]

Greetings - noticed rt2860 driver referred to - does

dmesg | grep RT2show something like?:

[ 35.973068] RtmpOSFileOpen(): Error 2 opening /etc/Wireless/RT2860STA/RT2860STA.dat
[ 35.973078] Open file "/etc/Wireless/RT2860STA/RT2860STA.dat" failed!
[ 36.297303] RtmpOSFileOpen(): Error 2 opening /etc/Wireless/RT2860STA/RT2860STA.dat
[ 36.297312] Open file "/etc/Wireless/RT2860STA/RT2860STA.dat" failed!
[ 200.006646] Read file "/etc/Wireless/RT2860STA/RT2860STA.dat" failed(errCode=0)!
[ 1894.184783] Read file "/etc/Wireless/RT2860STA/RT2860STA.dat" failed(errCode=0)!
[ 2373.659265] Read file "/etc/Wireless/RT2860STA/RT2860STA.dat" failed(errCode=0)!
[ 2405.543895] Read file "/etc/Wireless/RT2860STA/RT2860STA.dat" failed(errCode=0)!
[ 3581.869741] Read file "/etc/Wireless/RT2860STA/RT2860STA.dat" failed(errCode=0)!
[ 3635.055932] rt28xx_close call RT28xxPciAsicRadioOff fail !!
[ 3639.283087] Read file "/etc/Wireless/RT2860STA/RT2860STA.dat" failed(errCode=0)!
[ 3697.880831] Read file "/etc/Wireless/RT2860STA/RT2860STA.dat" failed(errCode=0)!A RT2860STA.dat file must be created and Network Manager restarted using:

sudo su
mkdir -p /etc/Wireless/RT2860STA
touch /etc/Wireless/RT2860STA/RT2860STA.dat
service network-manager restart
exitOOB, out of the box, the UNR 10.04 Live CD is missing the file (ie. it is a bug)
/etc/Wireless/RT2860STA/RT2860STA.dat which is required for the RT2860 driver as specified by the dmesg | grep RT messages.

The given script creates the file (with null content) so the driver "works".

---------------------------------------------------------------------------------------------------------------------------------
Another wrinkle (bug!) however is that it is exceedingly difficult to effect a connection with non-broadcasting SSID routers (the SSID is "hidden" but not the router service).

While this thread is about alternate (manual) methods to Network Manager the following process in this post will use NM with some "manual" labour to coerce such connections, because NM's Connect to Hidden Wireless Network ... left click menu option is ineffective.

Thus,
sudo iwconfig wlan0 essid <hidden SSID> key s:<ASCII password string> is needed while toggling the Enable Wireless right click function of Network Manager to make the wireless connection and then selecting the now visible SSID from NM's wireless service drop down menu list.


sudo iwlist scan can be used for monitoring: when the router's ESSID:<hidden SSID> is seen instead of ESSID:"" then the router will be seen (eventually, in ~ 20 or 30 sec.) in NM's drop down menu at which point it can be selected.

Is there a simple and short script to totally dispense with the need for NM? hmmm ... not this:

sudo su
ifconfig wlan0 up
dhclient -r wlan0
iwconfig wlan0 mode Managed essid <hidden SSID> key s:<ASCII password string>
dhclient wlan0
exit
ref:
Re: Ubuntu 10.04 using the Ralink RT2860 WiFi chipset (e.g. EeeBox B202) (http://ubuntuforums.org/showthread.php?p=11686653#post11686653)

[kevdog]

I can add this information to the original post, however did this solution work for you?

[nowifi]

yes - original post 971 (http://ubuntuforums.org/showpost.php?p=11686257&postcount=971) modified with more details

[vosnack]

dmesg | grep RT2 doesn't give me any results. Any idea why?

[nowifi]

GREP, Global Regular Expression Parser, did not find the r.e. (regular expression) RT2 (which evaluates literally to an RT2 character sequence) in the kernel ring buffer as piped, |, from dmesg, display or driver message, which exposes the buffer.

Presumably, dmesg by itself, does not fail, resulting in the revelation of the contents of the buffer where all the messages are without the character...s "RT2".
(sorry about the missing D and the malapropism of your mal-appropriated character's name R2... R2D2 ~ RTD2 sorry - a little inside cybernetic humour from one cybernaut, to another)

The RT2860 software suite of drivers and interface code is not required for the wireless hardware of all systems but when it is required, the posting 971 (http://ubuntuforums.org/showpost.php?p=11686257&postcount=971) shows that the Lucid UNR 10.04 LTS Live CD often succumbs to the wireless failure as noted.

The Belkin N Wireless USB Adapter F5D8053 presents a moving target for driver identificaton unless the exact version is known - caveat 1 below.
Do

lsusb | grep Belkin If this does not show a version use Belkin's method (http://en-us-support.belkin.com/app/answers/detail/a_id/6427).

============================== Caveat ================================
A cursory survey of anecdotal documentation for the Belkin N Wireless USB Adapter F5D8053 implies that as in 967 (http://ubuntuforums.org/showpost.php?p=11577931&postcount=967)


sudo lsmod | grep rt28*
rt2860sta 481561 0
rt2870sta 461811 0 does list modules correctly as required.
================================================== =================
The above may be incorrect.
Closer scrutiny now reveals the following observations:



Belkin's website (http://en-us-support.belkin.com/app/answers/detail/a_id/464/session/L3RpbWUvMTMyOTQwODM5My9zaWQvT0VvekdSUWs%3D) µsoft (aka mu ~ micro ...) support software is F5D8053 hardware version dependent (ref: Belkin driver link origin page (http://en-us-support.belkin.com/app/product/detail/p/210)) - implicating the possible Ubuntu complicity with these version complications as well.
This is confirmed in this link:
http://ubuntuforums.org/showthread.php?t=1673151&p=10486074&page=2
(which confirms a suspicion that in fact the rt2800usb is in fact the correct driver at least for V3) and
http://ubuntuforums.org/showthread.php?p=10458055&t=1673151 where V6 of the F5D8053 uses a driver for Realtek and NOT Ralink hardware:


lsusb | grep Belkin
Bus 001 Device 010: ID 050d:815f Belkin Components F5D8053 N Wireless USB Adapter v6000 [Realtek RTL8192SU]
modinfo r8192s_usb
filename: /lib/modules/2.6.32-21-generic/kernel/drivers/staging/rtl8192su/r8192s_usb.ko
description: Linux driver for Realtek RTL8192 USB WiFi cards
...
The rt2870 identifies with USB wireless devices but unless there is also another PCI wireless device, the rt2860 is NOT relevant
.
Ralink Linux drivers exist (http://www.ralink.com.tw/en/04_support/support.php?sn=501) with this specific one: RT2870USB(RT2870/RT2770 (http://www.ralink.com.tw/en/04_support/license.php?sn=5021) as the only RT28xx qualified w/ USB thus presumably distinct from any other RT2870 or RT28xx listed
.
The Ralink site has no matching RT2800 (or even RT280x) listing but UNR 10.04 does! Note that it identifies with the rt2870 firmware!

modinfo rt2800usb
filename: /lib/modules/2.6.32-21-generic/kernel/drivers/net/wireless/rt2x00/rt2800usb.ko
license: GPL
firmware: rt2870.bin
description: Ralink RT2800 USB Wireless LAN driver.
version: 2.3.0
author: http://rt2x00.serialmonkey.com
...
The Ralink site has distinct RT3070 and RT2870 listings but UNR 10.04 identifies them similarly:

modinfo rt2870sta
filename: /lib/modules/2.6.32-21-generic/kernel/drivers/staging/rt2870/rt2870sta.ko
alias: rt3070sta
version: 2.0.1.0
license: GPL
description: RTxx70 Wireless LAN Linux Driver
...


Possible remedial actions:


For Ubuntu 9.10 (karmic), this link http://ubuntuforums.org/showthread.php?t=1382798 details the manually labour intensive installation process which is explained in this link http://ubuntuforums.org/showthread.php?t=1515837&p=9503272 .

================================================== =================


Specific to your case 965 (http://ubuntuforums.org/showpost.php?p=11577925&postcount=965), check

dmesg | grep rt2(note that RT is now rt) for any other driver messages.
.
Assuming there is nothing extraordinary ...
Check ifconfig (interface configuration) to see if wlan0 is resident, it is on and confirm it is available

ifconfig -a
sudo ifconfig wlan0 up
ifconfig
Assuming that wlan0 is now on and has a HWaddr: 94:44:52:44:0f:cf from the previous step ...
Check the interface of the wireless configuration

iwconfig which, particularly this, should look similar to:

wlan0 RT2860 Wireless ESSID:"" Nickname:"RT2860STA"
Mode:Auto Frequency=2.412 GHz Access Point: Not-Associated
Bit Rate:1 Mb/s
RTS thr:off Fragment thr:off
Link Quality=100/100 Signal level:-49 dBm Noise level:-115 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
See ref: Re: Wireless disabled (http://ubuntuforums.org/showthread.php?p=11679119#post11679119) for other samples of output from this command with explanations.
.
If so, the wireless adapter is functioning and can be tested by using it to list the available proximal wireless services with:

sudo iwlist scan

For convenience of execution and brevity these commands are coalesced here, with a final dmesg check:

dmesg | grep rt2
ifconfig -a
sudo ifconfig wlan0 up
ifconfig
iwconfig
sudo iwlist scan
dmesg | grep RT2
Note: except for sudo ifconfig wlan0 up, which enables the hardware, these commands, as used here, are all passive and simply report the status of the operating environment.

[vosnack]

~$ dmesg | grep rt2
[ 18.328456] rt2870sta: module is from the staging directory, the quality is unknown, you have been warned.
[ 18.371455] usbcore: registered new interface driver rt2870
[ 18.561256] rt2860sta: module is from the staging directory, the quality is unknown, you have been warned.from dmesg |grep rt2

is there anything unusual?

[vosnack]

~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:11:43:ca:94:40
inet addr:193.178.2.74 Bcast:193.178.2.255 Mask:255.255.255.0
inet6 addr: fe80::211:43ff:feca:9440/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1541 errors:0 dropped:0 overruns:0 frame:0
TX packets:1451 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1331859 (1.3 MB) TX bytes:283192 (283.1 KB)
Interrupt:16

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:960 (960.0 B) TX bytes:960 (960.0 B)

[kevdog]

Everything looks ok so far, what does lshw -C network list (this won't help if this is a usb device however).

I don't have a rt device that uses this driver so hence I can't be of much help -- sorry!

[nowifi]

An excellent official refernce is the Debian Wifi USB Devices (http://wiki.debian.org/WiFi#USB_Devices) documentation.
Check
lsusb | grep Belkin
for V#
If this does not show a version (& more importantly "Ralink RT2870"," Realtek RTL8192SU" etc.) use Belkin's method (http://en-us-support.belkin.com/app/answers/detail/a_id/6427).

ie. (there seems to be no V2 - drivers colours: no modinfo in 10.04 : driver exists in 10.04 but may need manual persuasion to correct functionality)
V5 works w/ Realtek driver r8192u_usb details: debian.org page r8192u_usb (http://wiki.debian.org/rtl819x#r8192u_usb)
V6 works w/ Realtek driver r8192s_usb ( debian.org's r8192s_usb (http://wiki.debian.org/rtl819x#r8192s_usb) ) or r8712u ( debian.org's r8712u (http://wiki.debian.org/rtl819x#r8712u) )
V1/3/4 works w/ Ralink drivers rt2800usb (endorsed in debian.org's rt2800usb (http://wiki.debian.org/rt2800usb) ) or rt2870sta ( debian.org's rt2870sta (http://wiki.debian.org/rt2870sta) )

refs:
http://ubuntuforums.org/showpost.php?p=10458122&postcount=8

http://ubuntuforums.org/showpost.php?p=10486074&postcount=15

================================================== ======
ifconfig -a shows wlan0 is not bound (because it's missing) to a driver - the drivers rt28xx are loaded but not bound to the Belkin USB either because a different driver is needed or the drivers need repairing.

PS. the rt2860sta is for a PCI card and is totally irrelevant, unless there is another wireless interface that is a PCI card

(some) mutually exclusive possibilities are:

rt2870sta if needed the supplied one is probably incorrect - it can be rebuilt ... painfully

** r8192s_usb **
(ref:
http://wiki.debian.org/rtl819x#r8192s_usb
https://bugs.launchpad.net/ubuntu/.../+bug/492034/.../3 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/492034/comments/35)5 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/492034/comments/35))
requires

wget http://launchpadlibrarian.net/37387612/rtl8192sfw.bin.gz
gunzip rtl8192sfw.bin.gz
sudo mv rtl8192sfw.bin /lib/firmware/RTL8192SU/(for more info see http://alexsleat.co.uk/2011/02/15/realtek-rtl8191s-in-ubuntu-10-10/ )

rt2800usb no fixes needed

================================================== ========
Best ** bet ** if Belkin USB wireless is a recent acquisition, V6 is the latest version.

If it is V6 install and test via:


lsusb | grep Belkin
sudo mkdir /lib/firmware/RTL8192SU/
# cd /lib/firmware/RTL8192SU/
# sudo wget http://svn.debian.org/wsvn/kernel/dists/trunk/firmware-nonfree/realtek/RTL8192SU/rtl8192sfw.bin
# replaced the above, it may not be adequate, it is only 6K while below is ~66K
wget http://launchpadlibrarian.net/37387612/rtl8192sfw.bin.gz
gunzip rtl8192sfw.bin.gz
sudo mv rtl8192sfw.bin /lib/firmware/RTL8192SU/
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
modprobe -r rt2860sta rt2870sta
modprobe r8192s_usb
ifconfig -a
sudo ifconfig wlan0 up
ifconfig
iwconfig
sudo iwlist scan

[Azrael84]

I tried this but ran into issues, according to my router admin page I'm using `WPA-PSK[TKIP] + WPA2-PSK[AES]`


lshw -C network
*-network
description: Wireless interface
product: BCM4312 802.11b/g LP-PHY
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: eth1
version: 01
serial: c4:17:fe:65:51:f8
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=wl0 driverversion=5.100.82.38 latency=0 multicast=yes wireless=IEEE 802.11bg
resources: irq:17 memory:f0400000-f0403fff
*-network
description: Ethernet interface
product: RTL8101E/RTL8102E PCI Express Fast Ethernet controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:04:00.0
logical name: eth0
version: 02
serial: 00:26:b9:23:ce:df
size: 10Mbit/s
capacity: 100Mbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=N/A latency=0 link=no multicast=yes port=MII speed=10Mbit/s
resources: irq:41 ioport:2000(size=256) memory:f0810000-f0810fff memory:f0800000-f080ffff memory:f0820000-f083ffff
so edited
gksu gedit /etc/wpa_supplicant.conf to look like


ctrl_interface=/var/run/wpa_supplicant

network={
ssid="MYWIFI"
psk="MYKEY"
key_mgmt=WPA-PSK
proto=RSN WPA
pairwise=CCMP TKIP
group=CCMP TKIP
}

then

then I did
sudo ifconfig eth1 down
sudo dhclient -r eth1
Finally
wpa_supplicant -Dwext -ieth1 -c/etc/wpa_supplicant.conf -dd The result wasn't successful:


Initializing interface 'eth1' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
Line: 3 - start of a new network block
ssid - hexdump_ascii(len=15):
44 61 42 6c 75 65 43 68 65 65 7a 7a 7a 7a 65 DaBlueCheezzzze
PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED]
key_mgmt: 0x2
proto: 0x3
pairwise: 0x18
group: 0x18
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='MYWIFI'
SIOCGIWRANGE: WE(compiled)=22 WE(source)=19 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf flags 0x0
netlink: Operstate: linkmode=1, operstate=5
Own MAC address: c4:17:fe:65:51:f8
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=4 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=5 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
WPS: UUID based on MAC address - hexdump(len=16): 2f ee 0c d3 87 fc 56 b1 aa 78 95 f3 28 f1 ff de
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
Using existing control interface directory.
ctrl_iface bind(PF_UNIX) failed: Address already in use
ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/wpa_supplicant/eth1' manually if it is not used anymore
Failed to initialize control interface '/var/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.

Failed to add interface eth1
No keys have been configured - skip key clearing
State: DISCONNECTED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Cancelling scan request
Cancelling authentication timeout
netlink: Operstate: linkmode=0, operstate=6



What am I doing wrong here? thanks

[marionbates]

Just posting to say thank you for putting together this documentation...I never would've figured it out on my own!

Hardware: HP Mini 1120NR
Software: Open1to1.org September 2012 image (based on Ubuntu 12)

Contents of my wpa_supplicant.conf:

-------
ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="School Wifi"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk=longstringoflettersandnumbersgeneratedbywpa_pa ssphrasetool
pairwise=TKIP
group=TKIP
}
-------

Contents of my /etc/rc.local:

/sbin/ifconfig wlan0 down
/sbin/dhclient -r wlan0
/sbin/wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B
/bin/sleep 5
/sbin/ifconfig wlan0 up
/sbin/dhclient wlan0

This gets the wireless connection up and running before the student logs in, and I did apt-get remove network-manager so that they canNOT reveal the PSK that we use to connect them to the trusted network. Whether they can discern it from that hash is another matter, but at least now they have to work for it!

Thanks again.

-- MB