HOWTO: Wireless Security - WPA1, WPA2, LEAP, etc.

[Metallinut]

This runs S40WlanDown just before S40networking, so tidies up something in the wlan setup. Then S40networking runs ../init.d/networking which runs 'ifup -a' which successfully starts wlan0 and all other interfaces.


Sorry if this has been answered, but: What makes this run before S40networking? I mean...alphabetically S40WlanDown comes AFTER S40networking.

Also, I've done this on my machine, but have not yet tested. My adapter is eth1 instead of wlan0. I assume that I just need to use ifdown eth1 instead?

Thanks!

[tritohc]

I'm trying to set up a PCMCIA WPC11 v4 card on Xubuntu for use on a WAP secured ESSID broadcast network with PSK & TKIP

I imported the 8180.INF file and installed wpa_supplicant

I get some strange (probably wext related) errors when i restart networking



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

auto wlan0
iface wlan0 inet static
address 192.168.1.220
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1
dns-nameservers 205.171.2.65
wpa-driver wext
wpa-conf managed
wpa-ssid MYSSID
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA_PSK
wpa-psk h3xv4lu3

uname -a
Linux ubuntu 2.6.15-28-386

sudo /etc/init.d/networking restart
*Reconfiguring network interfaces...
ioctl[SIOSCIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH: Operation not supported
WEXT auth param 5 value 0x1 -

(this is where it hangs)


if any text is one off go ahead and comment on it but i had to copy this over manually from my laptop screen so assume that text errors are from the copy and NOT THE MAIN PROBLEM.

[wieman01]

I'm trying to set up a PCMCIA WPC11 v4 card on Xubuntu for use on a WAP secured ESSID broadcast network with PSK & TKIP

I imported the 8180.INF file and installed wpa_supplicant

I get some strange (probably wext related) errors when i restart networking

if any text is one off go ahead and comment on it but i had to copy this over manually from my laptop screen so assume that text errors are from the copy and NOT THE MAIN PROBLEM.
Question: Can you connect to unsecured networks without problem?

[wieman01]

I was wondering if someone could tell me whether I will be able to connect to my campus' secure network. I'm currently connected via the open wireless network, but with the secure one it requires some software to install:

https://wiki.brown.edu/confluence/display/CISDOC/Wireless+-+Connecting+to+the+Brown-Secure+Wireless+Network+with+Windows

There it says you need to download this software because our secure network is WPA1/TKIP/EAP, and it requires the SecureW2 client software from Alfa and Ariss Network Solutions. I found that it's a Windows-only program which I guess I could run through Wine, but I don't see how that's going to help me with connecting to the network. Anyway so I did more perusing and I found this one for Mac

https://wiki.brown.edu/confluence/display/CISDOC/Wireless+-+Connecting+to+the+Brown-Secure+Wireless+Network+with+a+Mac

and that talks about 802.1X which my iwlist scan returns when I look at the secure network.

Anyone have any ideas how I would go about connecting to this network?
Sorry for replying so late... Could your check this out? May be interesting for you. Post there if you need support.

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

[mackyman]

Really many thanks...
Read through this great howto and modified it a bit... And now I can atlast connect to my works wireless network!

Thanks!

[wieman01]

Really many thanks...
Read through this great howto and modified it a bit... And now I can atlast connect to my works wireless network!

Thanks!
Interesting... What wireless network are we talking about (e.g. PEAP, LEAP, etc.)? Just curious which script you may have used.

[mackyman]

Interesting... What wireless network are we talking about (e.g. PEAP, LEAP, etc.)? Just curious which script you may have used.

Well... I just read about the first post and didn't use any script.

And it was a WAP(1) network, wich I didn't know (as noone on the work knew anything about the network, they just use it in windows...).
All I did was change the parameters a bit and iflist scan:ed to find the network, and then adjusted the parameters to fit those last settings.

[johnnyxf]

Greetings.

My 2 cents:
Running Ubuntu 6.10 with a BT Voyager 1105 dongle, which uses the Broadcom4320 chipset. Using WPA-PSK with hidden SSID.

My interfaces file contains:
auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid <ESSID>
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <PASSPHRASE>
wireless-essid <ESSID>

I had the customary trouble with restart. After much fiddling about, I combined methods from posts #2 and #32.

In rcS.d, I inserted the symlinks:
S39wlandown->../init.d/wlandown containing 'ifdown wlan0'
S42wireless-restart->../init.d/wireless-restart containing '/etc/init.d/networking restart'

And this works [for me]. Many thanks to all who have contributed to this thread, especially wieman01 and David Tangye.

I have a couple of questions:
1. I put #! /bin/sh at the top of the shell script files, because it seemed sensible, and because the Debian policy document in init.d said to. Is this actually necessary, or will the system assume that anything in this directory is a shell script? I wondered if you guys assumed that anyone reading this thread would have the sense to do this as a matter of course - I didn't, until I did some learning.

2. What is the significance of 'restart' in the command "/etc/init.d/networking restart"? I have looked in my tutorials, and cannot find a reference to this. What is the distinction between that and simply running "/etc/init.d/networking"?

Thanks again, guys.

[wieman01]

I have a couple of questions:
1. I put #! /bin/sh at the top of the shell script files, because it seemed sensible, and because of the Debian policy document in init.d said to. Is this actually necessary, or will the system assume that anything in this directory is a shell script? I wondered if you guys assumed that anyone reading this thread would have the sense to do this as a matter of course - I didn't, until I did some learning.

2. What is the significance of 'restart' in the command "/etc/init.d/networking restart"? I have looked in my tutorials, and cannot find a reference to this. What is the distinction between that and simply running "/etc/init.d/networking"?
Hi there,

1. No, you don't have to add "#! /bin/sh". The script is recognized as such as soon as you put in the corresponding folder and make it "executable".
2. "/etc/init.d/networking" is a script which you can execute in 3 different manners:
a. start -> start network
b. stop -> stop network
c. restart -> restart network

"/etc/init.d/networking" is pretty much like doing "ifup" or "ifdown". Does this kind of answer your questions?

[johnnyxf]

Greetings wieman01.

Excellent, thanks very much. I have had a look at /etc/init.d/networking, have looked up a few things, and understand what you mean.

atb jxf

[tritohc]

Question: Can you connect to unsecured networks without problem?

i can connect using the wireless network manager application that comes with ubuntu on a WEP network

[mackyman]

Is it possible to make a bash script (or any type of script) that recognizes the network I'm in and change the config-file depending on wich network I am on...

I have 3 different config-files, one at home, one at work, and one by my gf's place. Feels quite unnecessary to start the computer without the wireless connection and start it afterwards with the right config-file

[wieman01]

i can connect using the wireless network manager application that comes with ubuntu on a WEP network
Assuming that there aren't any typos, could it be that you have not generated the PSK correctly? See PSK generation for more... Not sure what else could be wrong.

[wieman01]

Is it possible to make a bash script (or any type of script) that recognizes the network I'm in and change the config-file depending on wich network I am on...

I have 3 different config-files, one at home, one at work, and one by my gf's place. Feels quite unnecessary to start the computer without the wireless connection and start it afterwards with the right config-file
Not if you use this method I am afraid...

[cbrolin]

Do these instructions also work for Ubuntu 6.10 (Edgy)? And how does it relate to the Network Monitor, which also writes into the /etc/network/interfaces file?

By the way, I can't get it working without removing the encryption. I have tried both your instructions and just entering the hexadecimal key into the Network Monitor password field. I also don't understand the relation between wlani and ethj. My file looks like this when it is not encrypted:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

iface eth1 inet dhcp
wireless-essid <my-essid>

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

auto eth1

[Griffiss]

I've been trying to get my wireless to work for 3 days now (since installing Edgy with ASUS WL-138G card + ndiswrapper), and I'm now connected with WPA for the first time thanks to this HowTo!!:)

Nice one Wieman!

Griff

[wieman01]

Do these instructions also work for Ubuntu 6.10 (Edgy)? And how does it relate to the Network Monitor, which also writes into the /etc/network/interfaces file?

By the way, I can't get it working without removing the encryption. I have tried both your instructions and just entering the hexadecimal key into the Network Monitor password field. I also don't understand the relation between wlani and ethj. My file looks like this when it is not encrypted:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

iface eth1 inet dhcp
wireless-essid <my-essid>

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

auto eth1

Network Monitor is the standard networking tool for GNOME which does not support WPA, only WEP. If you need a graphical WPA tool, go for Gnome-Network-Manager. Otherwise give this HOWTO a go and follow the instruction to the T.

[mackyman]

Ok, thanks anyway for the answer. Now I atleast know it's not possible =P

[elamericano]

I think this is a great service to help people be more aware of their options regarding the security of their wireless networks. The only thing I'd add is that a hidden SSID provides no security at all unless you have no encryption on your network. Your router is beaconing just as much as when it's not hidden, and Aircrack will happily list it by MAC address until the client transmits the ssid. Any traffic captured between your client and router is just as captured - the ssid is irrelevant

If anyone is ever adversely affected by this, it would be you or guests to your network - not an attacker. You may have a non-security related reason to do this, but I wouldn't mislead people that it provides them with any security. :-$

[wieman01]

I think this is a great service to help people be more aware of their options regarding the security of their wireless networks. The only thing I'd add is that a hidden SSID provides no security at all unless you have no encryption on your network. Your router is beaconing just as much as when it's not hidden, and Aircrack will happily list it by MAC address until the client transmits the ssid. Any traffic captured between your client and router is just as captured - the ssid is irrelevant

If anyone is ever adversely affected by this, it would be you or guests to your network - not an attacker. You may have a non-security related reason to do this, but I wouldn't mislead people that it provides them with any security. :-$
Hi,

Thanks for the post. Of course hiding your ESSID does not provide any additional security at all under the circumstances as all other security options are turned on. But some people prefer it nonetheless and it "feels" it is safer somehow. I am not writing anywhere in the HOWTO that it adds any security to your network. Guess few people care anyway. Got your point though.

[tedrogers]

But of course, if your router will allow such an option, you could enable MAC address filtering to only allow MAC addresses that you know and trust. Anyone else would be locked out.

[compwiz18]

But of course, if your router will allow such an option, you could enable MAC address filtering to only allow MAC addresses that you know and trust. Anyone else would be locked out.
On the other hand, anyone can change their MAC address to match yours....

[wieman01]

I agree, guys. The only way to fully secure your wireless network is WPA2 with EAP. PSK is a good alternative though. I don't think anyone can compromise a WPA2-PSK secured network if the personal key has sufficient length (say 20 characters) in a reasonable amount of time.

This is my unqualified opinion though.

[wieman01]

But of course, if your router will allow such an option, you could enable MAC address filtering to only allow MAC addresses that you know and trust. Anyone else would be locked out.
MAC cloning is a piece of cake, I must agree with Compwiz18 here.

[tedrogers]

I had no idea it was so easy to clone a MAC address.

Lucky I'm using WPA2 with EAP and a huge random key then eh! ;)

[wieman01]

I had no idea it was so easy to clone a MAC address.

Lucky I'm using WPA2 with EAP and a huge random key then eh! ;)
Guess you are using PSK rather than EAP? :-)

WPA2-PSK is safe by all means.

[p51d78th]

I have a laptop that will disconnect from the router after sitting idle for a while. I can use

sudo /etc/init.d/networking restart

no problem but some people use the laptop that i don't want to give sudo rights. I tried making a ln to the /etc/init.d/wireless-network.sh on the desktop for the user but it doesn't work. Any ideas on how to make it so a non sudo user can reset the networking?

[wieman01]

I have a laptop that will disconnect from the router after sitting idle for a while. I can use

sudo /etc/init.d/networking restart

no problem but some people use the laptop that i don't want to give sudo rights. I tried making a ln to the /etc/init.d/wireless-network.sh on the desktop for the user but it doesn't work. Any ideas on how to make it so a non sudo user can reset the networking?
I don't think you can do this without root privileges.

However, I believe there is a problem with your router if your PC keeps disconnecting. What model do you use? I used to have the same issue with a Linksys WRT54G and it turned out that I had to change one setting (beacon interval from 100 to 20). That did the trick for me.

[cxterm]

I configured my destop using this tutorial. the wireless is connected. But it was disconnected randomly. may be several minutes, or may be several hours. My router is Belkin wireless G router(part #F5D7230-4) and the wireless pci cards is AirLink101 AWLH4030 super G wireless PCI. I use ndiswrapper. My computer is dual system and under windowsxp the wireless connection is good and didn't have the problem. I have searched this forum but didn't find a solution. Any ideas on solving this problem or how to configure the wireless reconnected automatically when it was disconected?

[wieman01]

I configured my destop using this tutorial. the wireless is connected. But it was disconnected randomly. may be several minutes, or may be several hours. My router is Belkin wireless G router(part #F5D7230-4) and the wireless pci cards is AirLink101 AWLH4030 super G wireless PCI. I use ndiswrapper. My computer is dual system and under windowsxp the wireless connection is good and didn't have the problem. I have searched this forum but didn't find a solution. Any ideas on solving this problem or how to configure the wireless reconnected automatically when it was disconected?
Hello,

Used to have the same problem. Take a look at the previous post (#278). I reckon you need to play around with the router's settings a bit.

[ubuntu_demon]

my /etc/network/interfaces :


#auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf


my /etc/wpa_supplicant/wpa_supplicant.conf :


ap_scan=2 # is more secure and first network block is tried first. sort your networks by amount of use

# my own (very secure) WPA2 personal network which also uses hidden essid and (whitelist) macfiltering :
network={
ssid="*****"
bssid=**:**:**:**:**:**
# I added the bssid of my router because I don't want to try to connect to other bssids which could have the same ssid
scan_ssid=1
proto=WPA2
pairwise=CCMP
group=CCMP
key_mgmt=WPA-PSK
#psk="******"
#wpa_passphrase **** ****
#wpa_passphrase wants ssid and plain psk and generates a big psk
psk=********************************************** **************************
}

ap_scan=1 # faster than ap_scan=2

#my university :
network={
ssid="****"
key_mgmt=IEEE8021X
wep_key0=************************
phase2="auth=MSCHAPV2"
identity="******"
password="******"
}



# now follow other networks ...

network={
ssid="typicalwep"
psk="*********"
}

network={
ssid="typicalwpa2"
proto=WPA2
key_mgmt=WPA-PSK
psk="*****"
}

network={
ssid="typicalwpa"
proto=WPA
key_mgmt=WPA-PSK
psk="********"
}



I'm a fan of this approach because it allows me to specify multiple networks and have complete control over the settings. Connecting to the available network is always simple by doing :

$sudo ifdown eth1 && sudo ifup eth1

[wieman01]

I'm a fan of this approach because it allows me to specify multiple networks and have complete control over the settings. Connecting to the available network is always simple by doing :

$sudo ifdown eth1 && sudo ifup eth1
Hi Ubuntu_Demon,

What card have you finally got? And what chipset does it use? Are you happy with it? I am asking because I am looking for a Atheros card at the moment because I want to do away with "ndiswrapper" and need support for injection... for audit reasons.

[ubuntu_demon]

Hi Ubuntu_Demon,

What card have you finally got? And what chipset does it use? Are you happy with it? I am asking because I am looking for a Atheros card at the moment because I want to do away with "ndiswrapper" and need support for injection... for audit reasons.
I recently bought a wg311T and it works perfectly. (I was busy with other stuff lately. I plan to blog about it tomorrow)

[wieman01]

I recently bought a wg311T and it works perfectly. (I was busy with other stuff lately. I plan to blog about it tomorrow)
Cool. Would be nice if you mentioned the Linux driver as well as the chipset.

[ubuntu_demon]

Cool. Would be nice if you mentioned the Linux driver as well as the chipset.
Netgear WG311T
chipset = atheros
linux driver = madwifi

detected out of the box in Dapper but you have to add it in your /etc/network/interfaces yourself.

[Synless]

I just wanted to give some well deserved kudos to all of you for contributing to this worthy cause. :) Also, wanted to post some info regarding LEAP and our environment in hopes it will help someone else out.

We're running Microsoft AD (radius), Cisco Secure ACS (MAC/LEAP/WEP) BSSID. Following your instructions to enable LEAP on an IBM R40 couldn't have been more simple. I am up and running! Thanks.

Syn.

[wieman01]

I just wanted to give some well deserved kudos to all of you for contributing to this worthy cause. :) Also, wanted to post some info regarding LEAP and our environment in hopes it will help someone else out.

We're running Microsoft AD (radius), Cisco Secure ACS (MAC/LEAP/WEP) BSSID. Following your instructions to enable LEAP on an IBM R40 couldn't have been more simple. I am up and running! Thanks.

Syn.
You're welcome. This is an interesting read concerning LEAP & its (low) level of security:

http://asleap.sourceforge.net/README

[Mujaheiden]

Hi,

Ive upgraded fro Dapper to Edgy, and I have the feeling that wireless support out of the box is really better in Edgy (Is this true, also for TKIP encrypted, etc?)

But for Dapper to come online on our encrypted WAN I changed all this wpa supplicant settings, boot up codes, and whatever, so now this laptop only works on the encrypted home network. Only when I put in the live disk it works on unencrypted networks, or allows other logins.

So now my question is: how can Iundo all the things I did before for setting up wireless? You would say that i would be the best to know, but as it is some months ago, and i really cant remember everything I did. So maybe there is a way to undo all the wireless settings? Thus make wpasupplicant shut up, undo startup scripts etc, or do i really have to look for everything i did, and how it should in the original state? I reckon thats gonna be a pretty difficult excercise...

So any tips? Thanx.

[wieman01]

Hi,

Ive upgraded fro Dapper to Edgy, and I have the feeling that wireless support out of the box is really better in Edgy (Is this true, also for TKIP encrypted, etc?)

But for Dapper to come online on our encrypted WAN I changed all this wpa supplicant settings, boot up codes, and whatever, so now this laptop only works on the encrypted home network. Only when I put in the live disk it works on unencrypted networks, or allows other logins.

So now my question is: how can Iundo all the things I did before for setting up wireless? You would say that i would be the best to know, but as it is some months ago, and i really cant remember everything I did. So maybe there is a way to undo all the wireless settings? Thus make wpasupplicant shut up, undo startup scripts etc, or do i really have to look for everything i did, and how it should in the original state? I reckon thats gonna be a pretty difficult excercise...

So any tips? Thanx.
All you have to do is open your "interfaces" file and remove the corresponding lines:
sudo gedit /etc/network/interfaces
Then only leave the first two lines of the section that relate to your interface, e.g.:
auto eth1
iface eth1 inet dhcp
Now uninstall wpa-supplicant if you don't need it (althought uninstalling it is not necessary... it won't start up after removing the respective lines from "interfaces" & rebooting):
sudo apt-get remove wpasupplicant
Does this help?

[3mbc]

A lot of info in this thread and my head is swimming, but I don't want to quit. Belkin F5D7010 (RA2500 out of the box) works fine with no security. Any ideas?

auto ra0
iface ra0 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid Blackhole
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 773e970a9915049c7d22a56671daa512c2fdbb9fc53374eef2 d9baf4d518739a


ra0 Scan completed :
Cell 01 - Address: **********************
Mode:Managed
ESSID:"Blackhole"
Encryption key:on
Channel:6
Quality:0/100 Signal level:-35 dBm Noise level:-192 dBm
Cell 02 - Address: **********************
Mode:Managed
ESSID:"default"
Encryption key:on
Channel:6
Quality:0/100 Signal level:-85 dBm Noise level:-194 dBm

[wieman01]

A lot of info in this thread and my head is swimming, but I don't want to quit. Belkin F5D7010 (RA2500 out of the box) works fine with no security. Any ideas?
I am not entirely sure if this tutorial works for Ralink... I replaced the Ralink driver for my card with "ndiswrapper" in order to get this to work. But I found this link for you:

http://pastebin.ca/408779

auto ra0
iface ra0 inet dhcp
pre-up iwconfig ra0 essid Blackhole
pre-up iwpriv ra0 set NetworkType=Infra
pre-up iwpriv ra0 set AuthMode=WPA2PSK
pre-up iwpriv ra0 set EncrypType=AES
pre-up iwpriv ra0 set WPAPSK="your_password"

[karachuonyo]

Thanks for this how-to wieman01. Even a newbie like me seems to understand the details. However i have been unable to connect with WPA encryption on my wifi pcmcia card under ubuntu. With WEP encryption it connects fine with the generic linux driver. I tried the how-to with wpa-tkip encryption with wext as driver but i get errors which seem to be related to the wext driver and my laptop really really slows down. When i use atmel as the driver then i still get errors claiming wpa_driver_atmel_set_drop_unencrypted and countermeasures not yet implemented. However the green light on the card is blinking showing that it's working ok (with the atmel driver, not wext). Is it possible the generic driver (wext) or atmel do not support wpa encryption. My wifi card is made by safecom with the texas instruments ACX 111 chipset. Any thoughts are welcome.

[wieman01]

Thanks for this how-to wieman01. Even a newbie like me seems to understand the details. However i have been unable to connect with WPA encryption on my wifi pcmcia card under ubuntu. With WEP encryption it connects fine with the generic linux driver. I tried the how-to with wpa-tkip encryption with wext as driver but i get errors which seem to be related to the wext driver and my laptop really really slows down. When i use atmel as the driver then i still get errors claiming wpa_driver_atmel_set_drop_unencrypted and countermeasures not yet implemented. However the green light on the card is blinking showing that it's working ok (with the atmel driver, not wext). Is it possible the generic driver (wext) or atmel do not support wpa encryption. My wifi card is made by safecom with the texas instruments ACX 111 chipset. Any thoughts are welcome.
It is possible that certain cards do not support WPA(2). I don't know your card well enough, but I'd suggest that you do some research on the web. It is certainly the case that some cards support WPA while others don't...

[3mbc]

I got it to work using RutILT: http://cbbk.free.fr/bonrom/

I had to back down to WPA versus WPA2 but it works - great job you guys are doing here.

[Esky]

Great thread and very helpful!

but...
my newbie *** is still stuck :(

I have a SMC SMCWPCI-G EU with RTL818? chip and a WPA2 AP (Siemens gigaset wlan repeater 108). This combo works under windows (dual boot).

some info on my system:
$ uname -a
Linux desktop 2.6.17-11-generic #2 SMP Thu Feb 1 18:03:05 UTC 2007 x86_64 GNU/Linux

$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:19:DB:5D:98:D8
inet addr:192.168.1.36 Bcast:192.168.1.255 Mask:255.255.255.0(works)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0(...)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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)

wlan0 Link encap:Ethernet HWaddr 00:13:F7:29:FF:55
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:356 dropped:25 overruns:0 frame:0
TX packets:3830 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:160312 (156.5 KiB)
Interrupt:225 Memory:ffffc20000052c00-ffffc20000052d00

$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0


$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 802.11b/g link.. ESSID:"PKS4U2"
Mode:Managed Frequency=2.437 GHz Access Point: Not-Associated
Bit Rate=11 Mb/s
Retry:on 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

sit0 no wireless extensions.

$ ifconfig
same as -a only without sit0

$ lsmod
Module Size Used by
arc4 3712 0
binfmt_misc 16012 1
rfcomm 51360 0
l2cap 31744 5 rfcomm
bluetooth 64644 4 rfcomm,l2cap
powernow_k8 16576 2
cpufreq_userspace 6560 0
cpufreq_stats 9312 0
freq_table 7104 2 powernow_k8,cpufreq_stats
cpufreq_powersave 3456 0
cpufreq_ondemand 10928 1
cpufreq_conservative 11272 0
video 22920 0
tc1100_wmi 10632 0
sbs 20928 0
sony_acpi 7704 0
pcc_acpi 19968 0
i2c_ec 7808 1 sbs
i2c_core 29312 1 i2c_ec
hotkey 14536 0
dev_acpi 17540 0
button 9888 0
battery 14088 0
container 6656 0
ac 8328 0
asus_acpi 21924 0
ipv6 334432 10
af_packet 29452 6
lp 16584 0
tsdev 11136 0
sg 44584 0
snd_hda_intel 23452 1
snd_hda_codec 219392 1 snd_hda_intel
usb_storage 89792 4
r818x 111632 0
snd_pcm_oss 57344 0
snd_mixer_oss 22784 1 snd_pcm_oss
libusual 21544 1 usb_storage
psmouse 51088 0
ieee80211_rtl 99728 1 r818x
pcspkr 5248 0
evdev 14592 1
r1000 20608 0
serio_raw 10244 0
parport_pc 43560 1
parport 49932 2 lp,parport_pc
snd_pcm 108168 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_timer 31112 1 snd_pcm
snd 79016 8 snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_timer
soundcore 14112 1 snd
snd_page_alloc 13200 2 snd_hda_intel,snd_pcm
shpchp 49068 0
pci_hotplug 38912 1 shpchp
ext3 164880 1
jbd 74024 1 ext3
ehci_hcd 40456 0
ohci_hcd 25988 0
usbcore 167840 5 usb_storage,libusual,ehci_hcd,ohci_hcd
ide_generic 2944 0
ide_disk 21248 3
ide_cd 39584 0
cdrom 43816 1 ide_cd
atiixp 9232 1
sd_mod 25728 12
generic 7940 0
ahci 24452 0
libata 88984 1 ahci
scsi_mod 181424 5 sg,usb_storage,sd_mod,ahci,libata
thermal 19472 0
processor 38280 2 powernow_k8,thermal
fan 7432 0
vesafb 11048 0
capability 7304 0
commoncap 10752 1 capability
vga16fb 16656 1
cfbcopyarea 5376 2 vesafb,vga16fb
vgastate 10368 1 vga16fb
cfbimgblt 4352 2 vesafb,vga16fb
cfbfillrect 6272 2 vesafb,vga16fb
fbcon 45824 72
tileblit 4736 1 fbcon
font 10240 1 fbcon
bitblit 8064 1 fbcon
softcursor 3968 1 bitblit


$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:01:E3:5E:0E:AA
ESSID:"NAME"
Protocol:IEEE 802.11bg
Mode:Master
Channel:6
Encryption key:on
Bit Rates:54 Mb/s
Extra: Rates (Mb/s): 1 2 5.5 9 11 6 12 18 24 36 48 54
Quality:0 Signal level:0 Noise level:158
Extra: Last beacon: 2ms ago

sit0 Interface doesn't support scanning.


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

auto eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid NAME
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
psk <HASH KEY GENERATED WITH SHELL COMMAND>

$ cat /etc/modprobe.d/ndiswrapper
cat: /etc/modprobe.d/ndiswrapper: No such file or directory

cat /etc/resolv.conf
nameserver 217.19.16.131
nameserver 217.19.16.132

dmesg after running network restart:
[ 3316.498198] rtl8180: bad CRC in monitor mode are accepted
[ 3316.498205] rtl8180: bad CRC in monitor mode are accepted
[ 3316.498234] rtl8180: bad CRC in monitor mode are accepted
[ 3316.498237] rtl8180: bad CRC in monitor mode are accepted
[ 3316.498240] rtl8180: bad CRC in monitor mode are accepted
[ 3320.936432] rtl8180: Bringing up iface
[ 3321.044637] rtl8180: Card successfully reset
[ 3321.504013] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3321.501498] rtl8180: Setting SW wep key
[ 3321.501578] rtl8180: Setting SW wep key
[ 3321.501791] rtl8180: Setting SW wep key
[ 3321.501952] rtl8180: Setting SW wep key

$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.eth0.pid with pid 8317
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/eth0/00:19:db:5d:98:d8
Sending on LPF/eth0/00:19:db:5d:98:d8
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.1.1 port 67
There is already a pid file /var/run/dhclient.wlan0.pid with pid 8378
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/wlan0/00:13:f7:29:ff:55
Sending on LPF/wlan0/00:13:f7:29:ff:55
Sending on Socket/fallback
There is already a pid file /var/run/dhclient.eth0.pid with pid 5798864
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/eth0/00:19:db:5d:98:d8
Sending on LPF/eth0/00:19:db:5d:98:d8
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
DHCPOFFER from 192.168.1.1
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.36 -- renewal in 119380 seconds.
ioctl[IEEE80211_IOCTL_DELKEY]: Operation not supported
ioctl[IEEE80211_IOCTL_DELKEY]: Operation not supported
ioctl[IEEE80211_IOCTL_DELKEY]: Operation not supported
ioctl[IEEE80211_IOCTL_DELKEY]: Operation not supported
There is already a pid file /var/run/dhclient.wlan0.pid with pid 5798864
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:13:f7:29:ff:55
Sending on LPF/wlan0/00:13:f7:29:ff:55
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 4
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 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

[wieman01]

The last line in "/etc/network/interfaces" looks a bit odd. It should read:
wpa-psk <HASH KEY GENERATED WITH SHELL COMMAND>
Can you connect to unsecured wireless networks? And are you sure your router runs WPA2 and not WEP?

What would be helpful as well are these commands:
sudo ifdown wlan0
sudo ifup -v wlan0
Please post the results of both commands.

[Esky]

okay edited the wpa-psk line must have mistyped that. :oops:

changed the AP to not use any security and edited /etc/network/interfaces and that works, but when I change it back to WPA2 or WPA or mixed mode it doesn work :(

Hereś the output you requested:

$ sudo ifdown wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 5798864
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:13:f7:29:ff:55
Sending on LPF/wlan0/00:13:f7:29:ff:55
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.1.1 port 67
$ sudo ifup -v wlan0
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...

ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "NAME" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise CCMP TKIP -- OK
wpa_supplicant: wpa-group CCMP TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto RSN WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 5798864
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:13:f7:29:ff:55
Sending on LPF/wlan0/00:13:f7:29:ff:55
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 21
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
Synchronizing clock to ntp.ubuntu.com...

[wieman01]

okay edited the wpa-psk line must have mistyped that. :oops:

changed the AP to not use any security and edited /etc/network/interfaces and that works, but when I change it back to WPA2 or WPA or mixed mode it doesn work :(

Hereś the output you requested:
It looks to me as if the current (Windows) driver does not support WPA2:
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
Have you used the latest driver? Your script is definitely ok.

[Forgott3n]

I am so lost its not even funny. I have tried virtually anything that I come across on the forums or google.

At this point its clear that I need some help...

Here is a dump of commands and their results:

justin@bullbox:~$ uname -a
Linux bullbox 2.6.17-10-generic #2 SMP Fri Oct 13 18:45:35 UTC 2006 i686 GNU/Linux
justin@bullbox:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:11:09:76:D3:F1
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:169 Base address:0x6000

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:20 errors:0 dropped:0 overruns:0 frame:0
TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1384 (1.3 KiB) TX bytes:1384 (1.3 KiB)

ra0 Link encap:Ethernet HWaddr 00:16:B6:57:46:9C
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:838 errors:70 dropped:70 overruns:0 carrier:0
collisions:191 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:27801 (27.1 KiB)
Interrupt:161 Base address:0x4000

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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)

justin@bullbox:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
justin@bullbox:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

ra0 RT2500 Wireless ESSID:"gray-network"
Mode:Managed Frequency=2.412 GHz Bit Rate:11 Mb/s Tx-Power:0 dBm
RTS thr:off Fragment thr:off
Link Quality=0/100 Signal level=-81 dBm Noise level:-192 dBm
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.

justin@bullbox:~$ 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:20 errors:0 dropped:0 overruns:0 frame:0
TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1384 (1.3 KiB) TX bytes:1384 (1.3 KiB)

justin@bullbox:~$ lsmod
Module Size Used by
nls_utf8 3200 1
nls_cp437 6912 1
vfat 14720 1
fat 56348 1 vfat
binfmt_misc 13448 1
ipv6 272288 8
rfcomm 42260 0
l2cap 27136 5 rfcomm
bluetooth 53476 4 rfcomm,l2cap
apm 23280 1
i915 21632 2
drm 74644 3 i915
speedstep_lib 5764 0
cpufreq_userspace 5408 0
cpufreq_stats 7744 0
freq_table 6048 1 cpufreq_stats
cpufreq_powersave 2944 0
cpufreq_ondemand 8876 0
cpufreq_conservative 8712 0
sg 37404 0
sr_mod 18212 0
sd_mod 22656 2
ndiswrapper 208656 0
lp 12964 0
af_packet 24584 2
8139cp 24832 0
rt2500 188004 0
tsdev 9152 0
8139too 29056 0
mii 6912 2 8139cp,8139too
usb_storage 75072 1
scsi_mod 144648 4 sg,sr_mod,sd_mod,usb_storage
snd_intel8x0 34844 1
snd_ac97_codec 97696 1 snd_intel8x0
snd_ac97_bus 3456 1 snd_ac97_codec
snd_pcm_oss 47360 0
snd_mixer_oss 19584 1 snd_pcm_oss
libusual 17040 1 usb_storage
usbhid 45152 0
snd_pcm 84612 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 25348 1 snd_pcm
evdev 11392 3
psmouse 41352 0
serio_raw 8452 0
shpchp 42144 0
pci_hotplug 32828 1 shpchp
snd 58372 8 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_timer
soundcore 11232 1 snd
snd_page_alloc 11400 2 snd_intel8x0,snd_pcm
parport_pc 37796 1
parport 39496 2 lp,parport_pc
i2c_i810 6276 0
pcspkr 4352 0
i2c_algo_bit 10376 1 i2c_i810
i2c_core 23424 1 i2c_algo_bit
intel_agp 26012 1
agpgart 34888 3 drm,intel_agp
ext3 142728 1
jbd 62228 1 ext3
ehci_hcd 34696 0
uhci_hcd 24968 0
usbcore 134912 7 ndiswrapper,usb_storage,libusual,usbhid,ehci_hcd,u hci_hcd
ide_generic 2432 0
ide_cd 33696 0
cdrom 38944 2 sr_mod,ide_cd
ide_disk 18560 3
piix 11780 1
generic 5764 0
processor 31560 0
fbcon 41504 0
tileblit 3840 1 fbcon
font 9344 1 fbcon
bitblit 7168 1 fbcon
softcursor 3328 1 bitblit
vesafb 9244 0
capability 5896 0
commoncap 8704 1 capability
justin@bullbox:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

ra0 Scan completed :
Cell 01 - Address: 00:40:10:10:00:03
Mode:Managed
ESSID:"gray-network"
Encryption key:on
Channel:11
Quality:0/100 Signal level:-65 dBm Noise level:-192 dBm

sit0 Interface doesn't support scanning.

justin@bullbox:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback


iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

auto ra0
iface ra0 inet dhcp
pre-up iwconfig ra0 essid gray-network
pre-up iwpriv ra0 set NetworkType=Infra
pre-up iwpriv ra0 set AuthMode=WPA2PSK
pre-up iwpriv ra0 set EncrypType=AES
pre-up iwpriv ra0 set WPAPSK="6049133380"
justin@bullbox:~$ cat /etc/modprobe.d/ndiswrapper
alias wlan0 ndiswrapper
justin@bullbox:~$ cat /etc/resolv.conf
justin@bullbox:~$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.eth1.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/

SIOCSIFADDR: No such device
eth1: ERROR while getting interface flags: No such device
eth1: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up eth1.
There is already a pid file /var/run/dhclient.eth2.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/

SIOCSIFADDR: No such device
eth2: ERROR while getting interface flags: No such device
eth2: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up eth2.
There is already a pid file /var/run/dhclient.ath0.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/

SIOCSIFADDR: No such device
ath0: ERROR while getting interface flags: No such device
ath0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up ath0.
There is already a pid file /var/run/dhclient.wlan0.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/

SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
wlan0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up wlan0.
Interface doesn't accept private ioctl...
set (8BE2): Invalid argument
Failed to bring up ra0.
[ ok ]
justin@bullbox:~$ sudo ifdown ra0
ifdown: interface ra0 not configured
justin@bullbox:~$ sudo ifup -v ra0
Configuring interface ra0=ra0 (inet)
iwconfig ra0 essid gray-network
iwpriv ra0 set NetworkType=Infra
iwpriv ra0 set AuthMode=WPA2PSK
Interface doesn't accept private ioctl...
set (8BE2): Invalid argument
Failed to bring up ra0.
justin@bullbox:~$




I'm really at my wits end here... and I noticed that last command returned (what appears to be) a syntax error... So I don't know why WPA2PSK isn't working...

This is a brandnew install of ubuntu 6.10 and a brandnew Linksys WMP54G PCI card (RT2500 - RaLink?) and I have a router that is Linksys WRT54G v5 (DD-WRT Firmware installed) with WPA2-PSK Mixed (legacy support of WPA-PSK) and TKIP+AES algorithms. So my router is set up for virtually anything.

I haven't been able to get this to work once, at all, for a moment. I have not tried connecting with out any encryption due to security. Any help, especially if it fixes the problem ;), is greatly, greatly, appreciated.

[Esky]

It looks to me as if the current (Windows) driver does not support WPA2:

Have you used the latest driver? Your script is definitely ok.

The AP doesn't seem to do plain WPA, only a mix WPA/WPA2 and that doesn't help :(

Downloaded the latest driver from the realtek site but that doesn't help :(

guess I've got to give up on linux till I buy a new wifi card :cry:

[elmar]

Hi Ubuntu_Demon,

What card have you finally got? And what chipset does it use? Are you happy with it? I am asking because I am looking for a Atheros card at the moment because I want to do away with "ndiswrapper" and need support for injection... for audit reasons.

Hi wieman01,

I´ve got the same problem as Jan Hrbacek: "NetworkManager works for hidden ssid but wpa_supplicant doesn't".

Unfortunately his (your) solution didn´t work on my computer (Celeron 600MHz, Ubuntu 6.10).

I´m using a TP-Link-Card with Atheros-Chipset, so this might be of interst to you.
I can connect with WPA using Network-Manager, but I don´t manage with wpa_supplicant.

I followed all steps (- at least I believe it -) described in your and Jan´s thread.

Some Output:

elmar@graue-kiste:~$ uname -a
Linux graue-kiste 2.6.17-11-generic #2 SMP Thu Feb 1 19:52:28 UTC 2007 i686 GNU/Linux


dmesg:

[17179603.556000] ath_hal: module license 'Proprietary' taints kernel.
[17179603.560000] ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
[17179603.616000] wlan: 0.8.4.2 (0.9.2.1)
[17179603.624000] ath_rate_sample: 1.2 (0.9.2.1)
[17179603.644000] ath_pci: 0.9.4.5 (0.9.2.1)
[17179603.648000] ACPI: PCI Interrupt 0000:01:04.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
[17179604.244000] wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
[17179604.244000] wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
[17179604.244000] wifi0: turboG rates: 6Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
[17179604.244000] wifi0: H/W encryption support: WEP AES AES_CCM TKIP
[17179604.244000] wifi0: mac 7.9 phy 4.5 radio 5.6
[17179604.244000] wifi0: Use hw queue 1 for WME_AC_BE traffic
[17179604.244000] wifi0: Use hw queue 0 for WME_AC_BK traffic
[17179604.244000] wifi0: Use hw queue 2 for WME_AC_VI traffic
[17179604.244000] wifi0: Use hw queue 3 for WME_AC_VO traffic
[17179604.244000] wifi0: Use hw queue 8 for CAB traffic
[17179604.244000] wifi0: Use hw queue 9 for beacons
[17179604.272000] wifi0: Atheros 5212: mem=0xd4000000, irq=11
...
[17179643.068000] NET: Registered protocol family 10
[17179643.068000] lo: Disabled Privacy Extensions
[17179643.068000] IPv6 over IPv4 tunneling driver
[17179653.584000] ath0: no IPv6 routers present
[17179655.496000] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[17179978.340000] ath0: no IPv6 routers present
[17180630.112000] ath0: no IPv6 routers present

iwlist scan

lo Interface doesn't support scanning.

wifi0 Interface doesn't support scanning.

ath0 Scan completed :
Cell 01 - Address: 00:15:0C:FD:F9:CC
ESSID:""
Mode:Master
Frequency:2.422 GHz (Channel 3)
Quality=23/94 Signal level=-72 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=100
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 02 - Address: 00:15:0C:84:AC:F7
ESSID:"Beaune"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=3/94 Signal level=-92 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=100
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 03 - Address: 00:15:0C:2E:4A:B4
ESSID:"FRITZ!Box Fon WLAN 7050"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=16/94 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; 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=100

sit0 Interface doesn't support scanning.

The first cell is probably mine...

elmar@graue-kiste:~$ lsmod
Module Size Used by
nls_cp437 6912 1
vfat 14720 1
fat 56348 1 vfat
ipv6 272288 8
binfmt_misc 13448 1
rfcomm 42260 0
l2cap 27136 5 rfcomm
bluetooth 53476 4 rfcomm,l2cap
cpufreq_userspace 5408 0
cpufreq_stats 7744 0
freq_table 6048 1 cpufreq_stats
cpufreq_powersave 2944 0
cpufreq_ondemand 8876 0
cpufreq_conservative 8712 0
video 17540 0
tc1100_wmi 8324 0
sbs 16804 0
sony_acpi 6412 0
pcc_acpi 14080 0
i2c_ec 6272 1 sbs
hotkey 11556 0
dev_acpi 12292 0
button 7952 0
sg 37404 0
battery 11652 0
container 5632 0
ac 6788 0
asus_acpi 17688 0
sd_mod 22656 2
nls_utf8 3200 2
ntfs 112116 1
lp 12964 0
af_packet 24584 4
tsdev 9152 0
usb_storage 75072 1
scsi_mod 144648 3 sg,sd_mod,usb_storage
libusual 17040 1 usb_storage
usbhid 45152 0
usblp 15488 0
irtty_sir 10112 0
sir_dev 18308 1 irtty_sir
evdev 11392 1
wlan_scan_sta 15744 1
ath_pci 100000 0
ath_rate_sample 16512 1 ath_pci
wlan 207708 4 wlan_scan_sta,ath_pci,ath_rate_sample
ath_hal 192976 3 ath_pci,ath_rate_sample
psmouse 41352 0
irda 214332 2 irtty_sir,sir_dev
crc_ccitt 3200 1 irda
serio_raw 8452 0
pcspkr 4352 0
analog 12960 0
gameport 17160 1 analog
snd_mpu401 9640 0
snd_mpu401_uart 10240 1 snd_mpu401
snd_rawmidi 27264 1 snd_mpu401_uart
snd_seq_device 9868 1 snd_rawmidi
parport_pc 37796 1
parport 39496 2 lp,parport_pc
floppy 63044 0
snd_intel8x0 34844 1
snd_ac97_codec 97696 1 snd_intel8x0
snd_ac97_bus 3456 1 snd_ac97_codec
snd_pcm_oss 47360 0
snd_mixer_oss 19584 1 snd_pcm_oss
snd_pcm 84612 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 25348 1 snd_pcm
snd 58372 12 snd_mpu401,snd_mpu401_uart,snd_rawmidi,snd_seq_dev ice,snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mi xer_oss,snd_pcm,snd_timer
soundcore 11232 1 snd
snd_page_alloc 11400 2 snd_intel8x0,snd_pcm
hw_random 7320 0
i2c_i810 6276 0
i2c_algo_bit 10376 1 i2c_i810
intel_agp 26012 1
agpgart 34888 2 intel_agp
i2c_core 23424 2 i2c_ec,i2c_algo_bit
shpchp 42144 0
pci_hotplug 32828 1 shpchp
ext3 142856 1
jbd 62228 1 ext3
ehci_hcd 34696 0
uhci_hcd 24968 0
ohci_hcd 22532 0
ide_generic 2432 0
usbcore 134912 8 usb_storage,libusual,usbhid,usblp,ehci_hcd,uhci_hc d,ohci_hcd
ide_disk 18560 4
ide_cd 33696 0
cdrom 38944 1 ide_cd
piix 11780 1
generic 6276 0
thermal 15624 0
processor 31560 1 thermal
fan 6020 0
fbcon 41504 0
tileblit 3840 1 fbcon
font 9344 1 fbcon
bitblit 7168 1 fbcon
softcursor 3328 1 bitblit
vesafb 9244 0
capability 5896 0
commoncap 8704 1 capability

In summary I´d guess, the madwifi-driver is properly installed.

Is set up my interfaces.conf as follows:


auto lo
iface lo inet loopback

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-conf managed
wpa-ssid ´hidden ssid name´
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-key-mgmt WPA-PSK
wpa-psk ´secret hex key´


But when I do sudo /etc/init.d/networking restart
I get:

* Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.ath0.pid with pid 4606
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/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:14:78:10:c1:af
Sending on LPF/ath0/00:14:78:10:c1:af
Sending on Socket/fallback
DHCPRELEASE on ath0 to 192.168.178.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
There is already a pid file /var/run/dhclient.ath0.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/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:14:78:10:c1:af
Sending on LPF/ath0/00:14:78:10:c1:af
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 7
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


A lot of information - I don´t see through it...

Where´s my mistake?

Thanks in advance!

[wieman01]

Hi wieman01,

I´ve got the same problem as Jan Hrbacek: "NetworkManager works for hidden ssid but wpa_supplicant doesn't".

Unfortunately his (your) solution didn´t work on my computer (Celeron 600MHz, Ubuntu 6.10).

I´m using a TP-Link-Card with Atheros-Chipset, so this might be of interst to you.
I can connect with WPA using Network-Manager, but I don´t manage with wpa_supplicant.

I followed all steps (- at least I believe it -) described in your and Jan´s thread.

A lot of information - I don´t see through it...

Where´s my mistake?

Thanks in advance!
Just in case you have not removed Wifi-Radar ("wifi0" ?) or Gnome-Network-Manager, please do so. I suppose that's the problem here. Post here if the problem persists.

[elmar]

No, Network-manager has been deinstalled by ´apt-get remove´ (as described in one of your threads). I never installed Wifi-Manager, and concerning the graphical ubuntu package manager it is not installed.

Any further suggestions?

Thanks,

Elmar

[wieman01]

No, Network-manager has been deinstalled by ´apt-get remove´ (as described in one of your threads). I never installed Wifi-Manager, and concerning the graphical ubuntu package manager it is not installed.

Any further suggestions?

Thanks,

Elmar
What does "wifi0" refer to in your opinion? Trying to figure out what that error message is about.

[che-hai]

Hi,
I don't know much but I can tell that my ath0 is disconnected from the wifi router when proto is wpa2-psk(aes). I succeded in connecting it using wpa-psk proto but trying wpa2 i got this trouble. Analyzing your thread it seems that my config is ok...
In brief, here's the output of: sudo wpa_supplicant -Dmadwifi -iath0 -c/etc/wpa_supplicant/wpa_supplicant.conf -dd

bla bla...

RSN: encrypted key data - hexdump(len=76): /* bla/bla - the encrypted keys - end bla/bla */
WPA: Unsupported AES-WRAP len 76
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface ath0
State: 4WAY_HANDSHAKE -> DISCONNECTED
wpa_driver_madwifi_deauthenticate

...end bla bla

If you have any ideas why this is not working please let me know. Thanks.

[GoBieN]

I am having trouble connecting to my WPA2 (personal AES) secured wifi network at home.
I al running Ubuntu 7.04 but i think its pretty much the same.

My wireless interface was recognized during install and is using the bmwcutter(?) linux driver, so not ndiswrapper.

I followed the steps mentioned, please help me what can i do further ?

stan@laptop-ubuntu:~$ uname -a
Linux laptop-ubuntu 2.6.20-13-generic #2 SMP Sat Mar 24 23:12:02 UTC 2007 x86_64 GNU/Linux
stan@laptop-ubuntu:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:16:36:93:8E:7E
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:10 Base address:0xc000

eth1 Link encap:Ethernet HWaddr 00:14:A5:F3:64:F2
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:255

eth0:avah Link encap:Ethernet HWaddr 00:16:36:93:8E:7E
inet addr:169.254.6.234 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:10 Base address:0xc000

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:45 errors:0 dropped:0 overruns:0 frame:0
TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4117 (4.0 KiB) TX bytes:4117 (4.0 KiB)

stan@laptop-ubuntu:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 eth0
stan@laptop-ubuntu:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11b/g ESSID:off/any Nickname:"Broadcom 4311"
Mode:Managed Access Point: Invalid
RTS thr:off Fragment thr:off
Link Quality=0/100 Signal level=-256 dBm Noise level=-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

stan@laptop-ubuntu:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:36:93:8E:7E
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:10 Base address:0xc000

eth0:avah Link encap:Ethernet HWaddr 00:16:36:93:8E:7E
inet addr:169.254.6.234 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:10 Base address:0xc000

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:45 errors:0 dropped:0 overruns:0 frame:0
TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4117 (4.0 KiB) TX bytes:4117 (4.0 KiB)

stan@laptop-ubuntu:~$ lsmod
Module Size Used by
binfmt_misc 14604 1
rfcomm 45352 0
l2cap 28160 5 rfcomm
bluetooth 62340 4 rfcomm,l2cap
ppdev 11272 0
powernow_k8 16480 1
cpufreq_stats 8416 0
cpufreq_userspace 6176 0
cpufreq_conservative 9736 0
cpufreq_powersave 3072 0
cpufreq_ondemand 10640 1
freq_table 6336 3 powernow_k8,cpufreq_stats,cpufreq_ondemand
sony_acpi 7064 0
dev_acpi 17028 0
tc1100_wmi 9224 0
pcc_acpi 15616 0
sbs 17856 0
i2c_ec 6784 1 sbs
dock 11992 0
button 10016 0
container 6144 0
asus_acpi 19756 0
backlight 8448 1 asus_acpi
video 19080 0
ac 6920 0
battery 12040 0
nls_utf8 3456 2
ntfs 101960 2
sbp2 26628 0
parport_pc 40104 0
lp 15048 0
parport 43404 3 ppdev,parport_pc,lp
snd_hda_intel 24224 1
snd_hda_codec 261888 1 snd_hda_intel
snd_pcm_oss 49536 0
snd_mixer_oss 19840 1 snd_pcm_oss
snd_pcm 92808 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_dummy 5380 0
joydev 12928 0
snd_seq_oss 36608 0
snd_seq_midi 11008 0
snd_rawmidi 29696 1 snd_seq_midi
snd_seq_midi_event 9856 2 snd_seq_oss,snd_seq_midi
bcm43xx 135828 0
snd_seq 61856 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
snd_timer 26632 2 snd_pcm,snd_seq
snd_seq_device 10260 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
nvidia 7761432 22
sdhci 20748 0
ieee80211softmac 34688 1 bcm43xx
serio_raw 9092 0
ieee80211 37064 2 bcm43xx,ieee80211softmac
ieee80211_crypt 8064 1 ieee80211
ide_cd 35104 0
psmouse 43536 0
mmc_core 31624 1 sdhci
pcspkr 4736 0
cdrom 40744 1 ide_cd
snd 68904 12 snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_ti mer,snd_seq_device
soundcore 10272 1 snd
k8temp 7552 0
shpchp 37404 0
pci_hotplug 36228 1 shpchp
snd_page_alloc 11792 2 snd_hda_intel,snd_pcm
i2c_nforce2 7680 0
i2c_core 26624 3 i2c_ec,nvidia,i2c_nforce2
af_packet 27020 6
tsdev 10112 0
evdev 13056 5
ext3 143760 2
jbd 68208 1 ext3
mbcache 11400 1 ext3
sg 40616 0
sd_mod 25092 6
amd74xx 16944 0 [permanent]
generic 6532 0 [permanent]
usbhid 29088 0
hid 34048 1 usbhid
sata_nv 24580 5
ohci_hcd 24196 0
forcedeth 48776 0
ata_generic 10628 0
ehci_hcd 37004 0
libata 130728 2 sata_nv,ata_generic
scsi_mod 166968 4 sbp2,sg,sd_mod,libata
ohci1394 38088 0
ieee1394 369784 2 sbp2,ohci1394
usbcore 154416 4 usbhid,ohci_hcd,ehci_hcd
thermal 16912 0
processor 34952 2 powernow_k8,thermal
fan 6536 0
fbcon 44416 0
tileblit 4096 1 fbcon
font 9856 1 fbcon
bitblit 7296 1 fbcon
softcursor 3712 1 bitblit
vesafb 10376 0
cfbcopyarea 5120 1 vesafb
cfbimgblt 4096 1 vesafb
cfbfillrect 5632 1 vesafb
capability 7048 0
commoncap 9472 1 capability
stan@laptop-ubuntu:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 No scan results

stan@laptop-ubuntu:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid dd-wrt
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 7b7e32e6e56a29edb1f5348d94c8aaf22b34e2acc967092d03 3663172f6475ce

stan@laptop-ubuntu:~$ cat /etc/modprobe.d/ndiswrapper
cat: /etc/modprobe.d/ndiswrapper: No such file or directory

stan@laptop-ubuntu:~$ cat /etc/resolv.conf
# generated by NetworkManager, do not edit!

search gobien.local


nameserver 192.168.1.254


stan@laptop-ubuntu:~$

[GoBieN]

Nevermind my previous post.

It seems I had to get some firmware for my adapter for the wlan would actually be activated. After a reboot i saw the blue light come on. After login i did not have an IP adress but after issuing a sudo dhclient eth1 i got my IP just fine :D

Only one thing dough, i am at 11 mb/sec while my adapter and my router are both 54g.

[wieman01]

Hi,
I don't know much but I can tell that my ath0 is disconnected from the wifi router when proto is wpa2-psk(aes). I succeded in connecting it using wpa-psk proto but trying wpa2 i got this trouble. Analyzing your thread it seems that my config is ok...
In brief, here's the output of: sudo wpa_supplicant -Dmadwifi -iath0 -c/etc/wpa_supplicant/wpa_supplicant.conf -dd

bla bla...

RSN: encrypted key data - hexdump(len=76): /* bla/bla - the encrypted keys - end bla/bla */
WPA: Unsupported AES-WRAP len 76
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface ath0
State: 4WAY_HANDSHAKE -> DISCONNECTED
wpa_driver_madwifi_deauthenticate

...end bla bla

If you have any ideas why this is not working please let me know. Thanks.
Perhaps your card/driver does not support WPA2. What driver are you using?

[elmar]

What does "wifi0" refer to in your opinion? Trying to figure out what that error message is about.

I found out that wifi0 is added by the madwifi driver:

madwifi.org/wiki/UserDocs/UsersGuide (http://madwifi.org/wiki/UserDocs/UsersGuide)

Every Linux network device consists of a prefix followed by a number indicating the device number of the network device. For instance, the ethernet devices are named eth0, eth1, eth2, etc. Each VAP which is created is also registered as a Linux network device. The value VAP can be either a prefix name of the Linux network device, or it can be the entire device name. For instance, specifying VAP as ath lets the Linux kernel add the network device as the next device with the prefix ath. Thus, the Linux kernel appends the proper number to the end to form the full device name, e.g., ath1 if ath0 already exists. However, the full device name can also be specified. For instance, VAP can also be ath2. In this case, the network device ath2 is registered, regardless of whether ath1 exists.

The Base Device is the underlying wireless network device name created when the driver is loaded. The MadWifi driver creates wifi0, wifi1, etc. as the underlying devices. By specifying the Base Device, the VAP is created with the Base Device as the parent device. The mode is the operating mode of the VAP. The operating mode of the VAP cannot be changed once it is created. In special cases, the operating mode of the VAP can be different from the operating mode of the underlying parent device. The first VAP which is created sets the operating mode of the underlying device. If the first VAP is deleted and a new VAP is created with a different operating mode than the original VAP, then the operating mode of the underlying device is changed to the new operating mode. The valid operating modes and their descriptions are given in Table 1.

I must admit I don´t really understand what a "virtual" AP is and why a "Base device" is needed and exspecially what all this means for me... maybe I would save time and sweat by drilling holes and pulling a cable through my house...

[che-hai]

Perhaps your card/driver does not support WPA2. What driver are you using?

I'm sorry, I do not know how to get the version of the driver (is there any command that I should know?). You refeer to madwifi or there are also another drivers implied in the stack? Sorry but I did not faced such deep problems.

The hardware that I got is working ok with wpa2-psk(aes) on another operating system.

[wieman01]

I found out that wifi0 is added by the madwifi driver:

I must admit I don´t really understand what a "virtual" AP is and why a "Base device" is needed and exspecially what all this means for me... maybe I would save time and sweat by drilling holes and pulling a cable through my house...
Perhaps "wifi0" does not play a role after all. That said, I do remember that another guy I helped a while ago mentioned that his device did not support WPA2, only WPA-TKIP. Can you try to connect to an WPA-TKIP secured network? Just change your router's settings and give it a go.

[wieman01]

I'm sorry, I do not know how to get the version of the driver (is there any command that I should know?). You refeer to madwifi or there are also another drivers implied in the stack? Sorry but I did not faced such deep problems.

The hardware that I got is working ok with wpa2-psk(aes) on another operating system.
Maybe the current Linux driver does not support WPA2... I am not entirely sure. See previous post.

Can you at least connect to WPA-TKIP secured networks?

[che-hai]

Maybe the current Linux driver does not support WPA2... I am not entirely sure. See previous post.

Can you at least connect to WPA-TKIP secured networks?

Yes, I am able to connect using wpa-tkip. I think the driver supports wpa2 since the error that I get "Unsupported AES-WRAP len 76" (please see the previous post) is returned after the protocol startup is established between ath0 and router and two keys - 2 out of 4- (or something like that - I need to look over the output again) were already exchanged. In fact the error message itself denotes that the driver supports AES (AES is specific to WPA2, isn't it?) - . When disconnected state is entered (please see the previos post indicating the output) it is stated that a 4 way handshake protocol is implied - so there is a known protocol.
All I know is that the linux-restricted-modules-2.6.15-28-386 is installed, I think that this comprise the madwifi but I do not know any command to list the driver's version.

[Kizilbas]

Wow, very nice tutorial thanks.

[elmar]

Perhaps "wifi0" does not play a role after all. That said, I do remember that another guy I helped a while ago mentioned that his device did not support WPA2, only WPA-TKIP. Can you try to connect to an WPA-TKIP secured network? Just change your router's settings and give it a go.

I´m using WPA-TKIP (see my interfaces file). Nonetheless ist does´nt work.

Elmar

[Sporkmaster]

This isn't working for me. Every time I put in my interfaces file, the computer lags to a Windows degree and the net don't work

non hidden SSID
WPA TKIP security
Yes, the PSK is hex
It's a Linksys wireless G router... I hate said router anyway

auto eth0
iface eth0 inet static
# wireless-* options are implemented by the wireless-tools package
address 192.168.1.103
netmask 255.255.255.0
network 192.168.1.1
broadcast 192.168.1.255
gateway 192.168.1.1
dns-nameservers 192.168.1.1
wpa-driver wext
wpa-conf managed
wpa-ssid ****************************
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk ****************************

This is what iwconfig turned up
eth0 IEEE 802.11g ESSID:"NETGEAR"
Mode:Managed Frequency:2.462 GHz Access Point: 00:0F:B5:5F:C3:C6
Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr: off Fragment thr: off
Power Management: off
Link Quality=61/100 Signal level=-64 dBm Noise level=-79 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries 0 Invalid misc:0 Missed beacon:18

Also, I installed Network-Manager-Gnome but it doesn't appear in my sys tray

[wieman01]

This isn't working for me. Every time I put in my interfaces file, the computer lags to a Windows degree and the net don't work

non hidden SSID
WPA TKIP security
Yes, the PSK is hex
It's a Linksys wireless G router... I hate said router anyway

Also, I installed Network-Manager-Gnome but it doesn't appear in my sys tray
Can you try a...
iwlist scan
...and post the results?

Also what card are you using? Is "eth0" the right interface? "Normally" this refers to your Ethernet connection and not wireless. But that could be different on your PC.

[fdhenard]

WPA is not working. It's an old pc that I'm trying to get Ubuntu to work on. I'm a newbie. Before I found this how-to, I was able to get internet working by turning off WPA on my router. However, I would prefer to use WPA encryption.

Adapter: Linksys WUSB11 ver 2.6 - pretty old - will it work with WPA?
I'm surprised (and happy) that Ubuntu recognized my adapter without installing drivers. Windows XP didn't do that!

Router: Fairly new Linksys W54???G - I'm not at home at the moment. I can update later if needed.

#uname -a
Linux fdhenard-desktop 2.6.15-26-386 #1 PREEMPT Thu Aug 3 02:52:00 UTC 2006 i586 GNU/Linux


# ifconfig -a
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:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:672 (672.0 b) TX bytes:672 (672.0 b)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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)

wlan0 Link encap:Ethernet HWaddr 00:06:25:26:BB:D9
UP BROADCAST 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)


# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface

#iwconfig
lo no wireless extensions.

wlan0 IEEE 802.11-DS ESSID:"okuwlan" Nickname:"okuwlan"
Mode:Managed Frequency:2.457 GHz Access Point: Not-Associated
Bit Rate:11 Mb/s Tx-Power=15 dBm
Retry limit:8 RTS thr=1536 B Fragment thr=1536 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

sit0 no wireless extensions.


# 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:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:672 (672.0 b) TX bytes:672 (672.0 b)

wlan0 Link encap:Ethernet HWaddr 00:06:25:26:BB:D9
UP BROADCAST 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)


#lsmod
Module Size Used by
ipv6 265728 6
rfcomm 40216 0
l2cap 26244 5 rfcomm
bluetooth 49892 4 rfcomm,l2cap
ppdev 9220 0
cpufreq_userspace 4696 0
cpufreq_stats 5636 0
freq_table 4740 1 cpufreq_stats
cpufreq_powersave 1920 0
cpufreq_ondemand 6428 0
cpufreq_conservative 7332 0
video 16260 0
tc1100_wmi 6916 0
sony_acpi 5644 0
pcc_acpi 12416 0
hotkey 11556 0
dev_acpi 11140 0
container 4608 0
button 6672 0
acpi_sbs 19980 0
battery 9988 1 acpi_sbs
i2c_acpi_ec 5120 1 acpi_sbs
ac 5252 1 acpi_sbs
af_packet 22920 6
dm_mod 58936 1
md_mod 72532 0
lp 11844 0
at76c503_rfmd 5260 0
at76c503 88544 1 at76c503_rfmd
at76_usbdfu 5764 1 at76c503
tsdev 8000 0
snd_cmipci 34336 1
gameport 15496 1 snd_cmipci
snd_pcm_oss 53664 0
snd_mixer_oss 18688 1 snd_pcm_oss
snd_pcm 89864 2 snd_cmipci,snd_pcm_oss
snd_page_alloc 10632 1 snd_pcm
snd_opl3_lib 10624 1 snd_cmipci
snd_timer 25220 2 snd_pcm,snd_opl3_lib
snd_hwdep 9376 1 snd_opl3_lib
snd_mpu401_uart 7808 1 snd_cmipci
snd_rawmidi 25504 1 snd_mpu401_uart
snd_seq_device 8716 2 snd_opl3_lib,snd_rawmidi
floppy 62148 0
parport_pc 35780 1
parport 36296 3 ppdev,lp,parport_pc
snd 55268 12 snd_cmipci,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_o pl3_lib,snd_timer,snd_hwdep,snd_mpu401_uart,snd_ra wmidi,snd_seq_device
pcspkr 2180 0
i2c_via 4484 0
i2c_algo_bit 9608 1 i2c_via
i2c_core 21904 2 i2c_acpi_ec,i2c_algo_bit
soundcore 10208 1 snd
psmouse 36100 0
serio_raw 7300 0
rtc 13492 0
shpchp 45632 0
pci_hotplug 29236 1 shpchp
via_agp 9856 1
agpgart 34888 1 via_agp
evdev 9856 1
ext3 135688 1
jbd 58772 1 ext3
ide_generic 1536 0
uhci_hcd 33680 0
usbcore 130692 5 at76c503_rfmd,at76c503,at76_usbdfu,uhci_hcd
ide_cd 33028 0
cdrom 38560 1 ide_cd
ide_disk 17664 3
via82cxxx 9988 0 [permanent]
generic 5124 0
thermal 13576 0
processor 23360 1 thermal
fan 4868 0
capability 5000 0
commoncap 7296 1 capability
vga16fb 13704 1
vgastate 10368 1 vga16fb
fbcon 42784 72
tileblit 2816 1 fbcon
font 8320 1 fbcon
bitblit 6272 1 fbcon
softcursor 2304 1 bitblit


# iwlist scan
lo Interface doesn't support scanning.

wlan0 Failed to read scan data : Resource temporarily unavailable

sit0 Interface doesn't support scanning.


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

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid ballparkfh
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 523ee409XXXXREMOVEDXXXXXXXX4817e764721903286261580 c

# cat /etc/modprobe.d/ndiswrapper
cat: /etc/modprobe.d/ndiswrapper: No such file or directory

# cat /etc/resolve.conf
search myhome.westell.com
nameserver 192.168.1.1

[GoBieN]

Is there a place somewhere where I would need to specify the speed of the wireless network ?

iwconfig says i'm at 11mb/s while my router and onboard adapter (pavilion dv6000, broadcom 43xx) are both capable of 54mb/s ?


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

eth0 no wireless extensions.

eth1 IEEE 802.11b/g ESSID:"dd-wrt" Nickname:"Broadcom 4311"
Mode:Managed Frequency=2.437 GHz Access Point: 00:40:10:10:00:03
Bit Rate=11 Mb/s Tx-Power=18 dBm
RTS thr:off Fragment thr:off
Link Quality=83/100 Signal level=-48 dBm Noise level=-71 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

stan@laptop-ubuntu:~$
stan@laptop-ubuntu:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wireless-essid dd-wrt
wpa-driver wext
wpa-conf /etc/wpa_supplicant.conf
stan@laptop-ubuntu:~$
stan@laptop-ubuntu:~$ sudo cat /etc/wpa_supplicant.conf
Password:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
network={
ssid="dd-wrt"
scan_ssid=1
psk="suXXXXXag"
}
stan@laptop-ubuntu:~$

Using native linux driver (the cutter thing) with firmware downloaded from internet by cutter script.

Please tell me how to get on 54mb/s ! Thank you

[fdhenard]

deleted

[wieman01]

WPA is not working. It's an old pc that I'm trying to get Ubuntu to work on. I'm a newbie. Before I found this how-to, I was able to get internet working by turning off WPA on my router. However, I would prefer to use WPA encryption.

Adapter: Linksys WUSB11 ver 2.6 - pretty old - will it work with WPA?
I'm surprised (and happy) that Ubuntu recognized my adapter without installing drivers. Windows XP didn't do that!
Depending on the (Windows) driver that you use, it either supports WPA or it doesn't. Can you download the latest driver from Linksys' website and deploy it? I doubt it will support WPA2, but WPA1 should not be a big issue.

[wieman01]

Is there a place somewhere where I would need to specify the speed of the wireless network ?

iwconfig says i'm at 11mb/s while my router and onboard adapter (pavilion dv6000, broadcom 43xx) are both capable of 54mb/s ?

Using native linux driver (the cutter thing) with firmware downloaded from internet by cutter script.

Please tell me how to get on 54mb/s ! Thank you
This is not quite the place to ask that question, but you could try:
iwconfig --help
This will list all the options for "iwconfig". Nonetheless here is a link to the "man" pages:

http://www.die.net/doc/linux/man/man8/iwconfig.8.html

[Staudie]

Wieman01,

Great guide, I'm not sure what I wold have done with out it. I do have one item that is giving me grief. I'm using a Netgear WG111T and it times out during boot. I followed "Post 2" to set up the script and set it to "S40". Could it be since this is a USB device I need to use a different timing? Once the system is up and running "sudo /etc/init.d/networking restart" works with out a hitch. Do you have any ideas? By the way I'm running Feisty.

Thanks in advance,
-Staudie

[wieman01]

Wieman01,

Great guide, I'm not sure what I wold have done with out it. I do have one item that is giving me grief. I'm using a Netgear WG111T and it times out during boot. I followed "Post 2" to set up the script and set it to "S40". Could it be since this is a USB device I need to use a different timing? Once the system is up and running "sudo /etc/init.d/networking restart" works with out a hitch. Do you have any ideas? By the way I'm running Feisty.

Thanks in advance,
-Staudie
A lot of other users have experienced the same problem (timeout) and one user proposed that this must be due to a bug which I cannot really explain.

As for the timing ("S40") I am using a USB device as well (Linksys wusb54g v4). The sequence has more to do with certain services that need to be initialized at certain stages while the system boots. "S40" seems appropriate.

If you want to shorten boot times and avoid a DHCP timeout, use Static IP instead which causes virtually no delay.

[gen_x]

Dude you are the wiseman! You rock man! :guitar: Literally 2 minutes and I'm on. Struggled form several hours.

Specs:
Acer 5670 Intel 3945ABG
Ubuntu Edy Eft

Note: Didn't have to install anything! Just follow this tutorial, it's so simple!

******interfaces*********

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid test
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <don't forget to generate your hex key>

******iwlist scan**********

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:00:00:00:00:00
ESSID:"test"
Protocol:IEEE 802.11bg
Mode:Master
Channel:6
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
Quality=96/100 Signal level=-30 dBm Noise level=-30 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 4ms ago

sit0 Interface doesn't support scanning.

*******iwconfig*******
lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11g ESSID:"test"
Mode:Managed Frequency:2.437 GHz Access Point: 00:00:00:00:00:00
Bit Rate:54 Mb/s Tx-Power:15 dBm
Retry limit:15 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=96/100 Signal level=-31 dBm Noise level=-32 dBm
Rx invalid nwid:0 Rx invalid crypt:1 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:133 Missed beacon:0

sit0 no wireless extensions.


Again great how to! Many thanks! :)

[sefs]

Tell me where I am going wrong...

I had this previously working in edgy, but since moving to Feisty the old ndiswrapper would not compile and I had to go with there newest version. ver 1.42

WPA no longer works and have had to fall back to WEP.

I want to get WPA working again. I've followed the HOWTO as before.

my /etc/network/interfaces looks like


# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
mapping hotplug
script grep
map wlan0

# The wireless network interface
iface wlan0 inet static

# General settings
#------------------------------
address 192.168.1.55
netmask 255.255.255.0
network 192.168.1.0
gateway 192.168.1.1
dns-nameservers 205.214.192.201 205.214.192.202 208.67.222.222 208.67.220.220 192.168.254.254

# WPA settings
#------------------------------
wpa-driver wext
wpa-ssid fshome
wpa-conf managed
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise AES
wpa-group AES
wpa-key-mgmt WPA-PSK
wpa-psk xxxx

auto wlan0


The errors i am getting when restarting the network (i have rebooted, shut right off and restarted) are


funkycold@funkycold:~$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces...
wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-down.d/wpasupplicant exited with return code 1
wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-post-down.d/wpasupplicant exited with return code 1
wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-up.d/wpasupplicant exited with return code 1
[ OK ]



what can i do to rectify.

Thanks.

[wieman01]

Sefs,

The settings for WPA1 are...
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
And WPA2...
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
Your code does not look right.
wpa-ap-scan 2
...suggests that you have your ESSID broadcast disabled. Is that correct?

[corax]

Hi all !

I have exactly the same problem ... I have upgraded (reinstalled) to feisty and I can't connect to WPA (WEP works fine). I have two cards one intel ipw2200 and a netgear wg511T (atheros with madwifi) both of them worked with WPA under edgy. None of them works with WPA now :) I have the same /etc/network/interfaces file (backed up) and I have no idea what is the problem :(

Can someone help me ? :)

THX

------------------------------------------------------
EDIT:

sorry it happens me all time ... :( I post a question after 2 hours of searching then I find the solution myself 10 minutes later :(

so

my /etc/network/interfaces was :

iface lo inet loopback
auto lo

#iface eth0 inet dhcp
#auto eth0

iface eth1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid sssssiiiiiddddd
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk keykeykey............
auto eth1

and this above said when i entered
sudo ifup eth1

wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
There is already a pid file /var/run/dhclient.eth1.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/
....

and I was unable to connect ...

The solution was to delete the line "wpa-conf managed" from /etc/network interfaces

so it is like

iface lo inet loopback
auto lo

#iface eth0 inet dhcp
#auto eth0

iface eth1 inet dhcp
wpa-driver wext
wpa-ssid sssssiiiiiddddd
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk keykeykey............
auto eth1

It works now as I see ... Can someone tell me what is "wpa-conf managed" for ?

Thanks !

[wieman01]

It works now as I see ... Can someone tell me what is "wpa-conf managed" for ?

Thanks !
I could not find any documentation on "wpa-conf". I will remove this line from my script as it does not appear to serve any purpose any longer. Thanks for highlighting it.

[sefs]

Hi again.

Weeima01 I want to confirm that WPA1 with AES works. Here is why.

I have a wrt54gl. the ssid broadcast is set to enabled. But I am as confused as you as to why wpa-ap-scan 2 works and wpa-ap-scan 1 does not ... when wpa-ap-scan 1 I cannot connect to the network but when I go wpa-ap-scan 2 I am able to connect. This is very very weird.

I also want to know what "wpa-conf managed" is for. I followed corax's suggestion and commented it out. And what would you know...after restarting the network ... I was back in business again using WPA-Personal which I assume is WPA1 and with AES encryption.

My /etc/network/interfaces now looks like this...

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
mapping hotplug
script grep
map wlan0

# The wireless network interface
iface wlan0 inet static

# General settings
#------------------------------
address 192.168.1.55
netmask 255.255.255.0
network 192.168.1.0
gateway 192.168.1.1
dns-nameservers 205.214.192.201 205.214.192.202 208.67.222.222 208.67.220.220 192.168.254.254

# WPA settings
#------------------------------
wpa-driver wext
wpa-ssid xxxxx
#wpa-conf managed
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise AES
wpa-group AES
wpa-key-mgmt WPA-PSK
wpa-psk xxxxxxxxxxxxxxxxxxx

auto wlan0


Can you shed some light on why it would wpa-ap-scan 2 works with ssid broadcast enabled and not wpa-ap-scan 1.

Can you also let us know whats this wpa-conf.

and how can I specify infrastructure mode.

While researching wpa_supplicant I saw ppl using the wpa-conf line to specify the path to /etc/wpa_supplicant.conf.

At one point i went this rout and made better progress where it detected the network but could not connect.

Thanks very much.


UPDATE:

I've tried WPA2 Personal on the WRT54GL with these settings ...


# WPA settings
#------------------------------
wpa-driver wext
wpa-ssid xxxxx
#wpa-conf managed
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk xxxxxx


now the wpa-ap-scan works when both set to 1 or 2.

So now I'm able to use WPA2 with AES.

Discussions on WPA+AES and WPA2+AES ect... it sounds rather confusing (AES was apprently added to WPA1 as an afterthought?)
http://www.dslreports.com/forum/remark,12691890
http://forums.practicallynetworked.com/showthread.php?t=7119

[wieman01]

Hi Sef:

I will update my tutorial immediately and remove the line in question (wpa-conf). Not sure why your version of wpa-supplicant works the way it does, however, it used to be the case that wpa-ap-scan would control the scanning logic of your wireless card (ESSID broadcast enabled vs. disabled).

Again, I'll remove the line from my scripts. I have not found any documentation on it so far.

[wieman01]

I have updated the HOWTO. Really appreciated your feedback as I have not tried Feisty yet. Still on Dapper which I plan to change soon. :-) So I really depend on your input. Sorry I have not found anything on the "wpa-conf" issues yet, but I will check it out over the weekend or so.

[sefs]

Just in case you were wondering its the wpa-supplicant that comes with a default upgrade to feisty.

Hi Sef:

I will update my tutorial immediately and remove the line in question (wpa-conf). Not sure why your version of wpa-supplicant works the way it does, however, it used to be the case that wpa-ap-scan would control the scanning logic of your wireless card (ESSID broadcast enabled vs. disabled).

Again, I'll remove the line from my scripts. I have not found any documentation on it so far.

[wieman01]

Just in case you were wondering its the wpa-supplicant that comes with a default upgrade to feisty.
Cool. Got it. Hope things will work out for Feisty users from now on. Thanks for your help.

EDIT:
One more question: Why would Feisty users still requires this HOWTO at all? I thought Feisty comes with enhanced wireless support including the support for Static IP and WPA? Just curious... Does the standard install not work for you?

[corax]

Hi all !

I think this howto is great. You should update it sometimes like remove the wpa-conf thing ... I think it is much cleaner (you don't need an additional program) and more straight than the network manager. And you can't configure WPA in NM as much as here in /etc/network/interfaces. And the NM works about 90 % of all cases because you can't setup everything in GUI. (extreme cases like WPA1 + WPA2 (mixed) + hidden essid + RADIUS. I don't think you can do it with network manager).

This is my opinion :)

[mr_delphi]

it works !!!
Removed "managed"
and put 2 in wpa-ap-scan 2

another thing is that for my router, AES does not work, WPA personal =tkip here

thanks everybody here


Hi again.

Weeima01 I want to confirm that WPA1 with AES works. Here is why.

I have a wrt54gl. the ssid broadcast is set to enabled. But I am as confused as you as to why wpa-ap-scan 2 works and wpa-ap-scan 1 does not ... when wpa-ap-scan 1 I cannot connect to the network but when I go wpa-ap-scan 2 I am able to connect. This is very very weird.

I also want to know what "wpa-conf managed" is for. I followed corax's suggestion and commented it out. And what would you know...after restarting the network ... I was back in business again using WPA-Personal which I assume is WPA1 and with AES encryption.

My /etc/network/interfaces now looks like this...

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
mapping hotplug
script grep
map wlan0

# The wireless network interface
iface wlan0 inet static

# General settings
#------------------------------
address 192.168.1.55
netmask 255.255.255.0
network 192.168.1.0
gateway 192.168.1.1
dns-nameservers 205.214.192.201 205.214.192.202 208.67.222.222 208.67.220.220 192.168.254.254

# WPA settings
#------------------------------
wpa-driver wext
wpa-ssid xxxxx
#wpa-conf managed
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise AES
wpa-group AES
wpa-key-mgmt WPA-PSK
wpa-psk xxxxxxxxxxxxxxxxxxx

auto wlan0


Can you shed some light on why it would wpa-ap-scan 2 works with ssid broadcast enabled and not wpa-ap-scan 1.

Can you also let us know whats this wpa-conf.

and how can I specify infrastructure mode.

While researching wpa_supplicant I saw ppl using the wpa-conf line to specify the path to /etc/wpa_supplicant.conf.

At one point i went this rout and made better progress where it detected the network but could not connect.

Thanks very much.


UPDATE:

I've tried WPA2 Personal on the WRT54GL with these settings ...


# WPA settings
#------------------------------
wpa-driver wext
wpa-ssid xxxxx
#wpa-conf managed
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk xxxxxx


now the wpa-ap-scan works when both set to 1 or 2.

So now I'm able to use WPA2 with AES.

Discussions on WPA+AES and WPA2+AES ect... it sounds rather confusing (AES was apprently added to WPA1 as an afterthought?)
http://www.dslreports.com/forum/remark,12691890
http://forums.practicallynetworked.com/showthread.php?t=7119

[sefs]

I wasn't aware of that. I will have to investigate that and see. I took a cursory glance at NM after upgrading to feisty immediately looking for the static IP support but I must have missed it so I removed it immediately to go back to what I knew was working (this tutorial). I'll have to reinstall NM to take a closer look.


Cool. Got it. Hope things will work out for Feisty users from now on. Thanks for your help.

EDIT:
One more question: Why would Feisty users still requires this HOWTO at all? I thought Feisty comes with enhanced wireless support including the support for Static IP and WPA? Just curious... Does the standard install not work for you?

[wieman01]

Hi all !

I think this howto is great. You should update it sometimes like remove the wpa-conf thing ... I think it is much cleaner (you don't need an additional program) and more straight than the network manager. And you can't configure WPA in NM as much as here in /etc/network/interfaces. And the NM works about 90 % of all cases because you can't setup everything in GUI. (extreme cases like WPA1 + WPA2 (mixed) + hidden essid + RADIUS. I don't think you can do it with network manager).

This is my opinion :)
If you have suggestions as to how we can improve this thread, you are welcome to post them here. It will be nice to keep this thread alive. I have removed that "wpa-conf" stanza in the meantime.

[wieman01]

Well, I have just tried Feisty Kubuntu (actually I am writing this while running the LiveCD) and I must say it is beautiful. More than that I had no problems whatsoever connecting to my local wireless network (Static IP, ESSID broadcast disabled) without installing any additional software packages. I am impressed... Having said that the new version of Ubuntu pretty much renders this thread unnecessary. Eventually!

EDIT:
On a Sony Vaio with Intel IPW2200 B/G that is.

[mabelrxu]

For WPA1 my example would look like this:

I have never bothered to setup wpa_supplicant outside of "interfaces" because I don't think it is nice. So I cannot give you any advice there. However, I am having a similar issue as you whereby I need to initialize my wireless network at startup, then immediately bring it down & restart it. For some reason the network would remain disconnected if I did not restart it.

So my advice is to follow post #2 and restart the network during the boot process. Not sure if this is a bug but I have not found a solution ever since.

actually, here's how you create your /etc/wpa_supplicant.conf file:


wpa_passphrase <network essid> <network password>


then some text comes up that's like

network={
ssid="ssid"
#psk="password"
psk=q45kl3j45;l3kj45h345lkj34h5;l2k3j45k3j4l5;h34j 5
}


so, you copy that psk, then do

sudo gedit /etc/wpa_supplicant.conf

and type (copy & paste) this:

ctrl_interface=/var/run/wpa_supplicant
ap_scan=1

network={
ssid="yourNetworkSsid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP
group=CCMP
psk=blah-;kljl23j4h2l3kj4h2l34h23lk4j23hl4h-blah
}


i have wpa2 with ipw2200 and wext, so you might need to change ap_scan, proto, pairwise, and group to match your network settings ... hope this helps!

[KiwiPete]

Hi there

I'm running Xubuntu 6.10 and need help getting my wireless PCI card recognised.
I'm using a LinkSys Wireless-G router.

Read your original post and followed all the instructions, but no joy.
Here are the results for running the various terminal commands you suggested.
-----------------------------------------------------------
uname -a
Linux ubuntu 2.6.17-11-generic #2 SMP Thu Feb 1 19:52:28 UTC 2007 i686 GNU/Linux

ifconfig -a
ath0 Link encap:Ethernet HWaddr 00:19:E0:83:24:D5
inet6 addr: fe80::219:e0ff:fe83:24d5/64 Scope:LinkOn,
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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth0 Link encap:Ethernet HWaddr 00:05:1C:19:DE:45
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:7871 errors:0 dropped:0 overruns:0 frame:0
TX packets:7579 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4741783 (4.5 MiB) TX bytes:672194 (656.4 KiB)
Interrupt:3 Base address:0xc00

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:306 errors:0 dropped:0 overruns:0 frame:0
TX packets:306 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:15300 (14.9 KiB) TX bytes:15300 (14.9 KiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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-19-E0-83-24-D5-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3288 errors:0 dropped:0 overruns:0 frame:33430
TX packets:7692 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:289523 (282.7 KiB) TX bytes:353932 (345.6 KiB)
Interrupt:11 Memory:d0920000-d0930000

route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface

iwconfig
lo no wireless extensions.

wifi0 no wireless extensions.

ath0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.467 GHz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:18 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=0/94 Signal level=-95 dBm Noise level=-95 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 no wireless extensions.

sit0 no wireless extensions.

ifconfig
ath0 Link encap:Ethernet HWaddr 00:19:E0:83:24:D5
inet6 addr: fe80::219:e0ff:fe83:24d5/64 Scope:Link
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:0
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:696 errors:0 dropped:0 overruns:0 frame:0
TX packets:696 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:34800 (33.9 KiB) TX bytes:34800 (33.9 KiB)

wifi0 Link encap:UNSPEC HWaddr 00-19-E0-83-24-D5-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3288 errors:0 dropped:0 overruns:0 frame:33430
TX packets:8680 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:289523 (282.7 KiB) TX bytes:399380 (390.0 KiB)
Interrupt:11 Memory:d0920000-d0930000

lsmod
Module Size Used by
ipv6 272288 8
apm 23280 1
cpufreq_userspace 5408 0
cpufreq_stats 7744 0
freq_table 6048 1 cpufreq_stats
cpufreq_powersave 2944 0
cpufreq_ondemand 8876 0
cpufreq_conservative 8712 0
nls_iso8859_1 5248 1
nls_cp437 6912 1
vfat 14720 1
fat 56348 1 vfat
lp 12964 0
af_packet 24584 4
snd_ens1371 28704 1
gameport 17160 1 snd_ens1371
snd_rawmidi 27264 1 snd_ens1371
snd_seq_device 9868 1 snd_rawmidi
snd_ac97_codec 97696 1 snd_ens1371
snd_ac97_bus 3456 1 snd_ac97_codec
snd_pcm_oss 47360 0
snd_mixer_oss 19584 1 snd_pcm_oss
snd_pcm 84612 3 snd_ens1371,snd_ac97_codec,snd_pcm_oss
snd_timer 25348 1 snd_pcm
tsdev 9152 0
parport_pc 37796 1
parport 39496 2 lp,parport_pc
snd 58372 10 snd_ens1371,snd_rawmidi,snd_seq_device,snd_ac97_co dec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 11232 1 snd
floppy 63044 0
i2c_i810 6276 0
snd_page_alloc 11400 1 snd_pcm
serio_raw 8452 0
8139cp 24832 0
8139too 29056 0
mii 6912 2 8139cp,8139too
evdev 11392 1
wlan_scan_sta 15744 1
psmouse 41352 0
i2c_algo_bit 10376 1 i2c_i810
ath_pci 100000 0
ath_rate_sample 16512 1 ath_pci
wlan 207708 4 wlan_scan_sta,ath_pci,ath_rate_sample
ath_hal 192976 3 ath_pci,ath_rate_sample
i2c_core 23424 1 i2c_algo_bit
intel_agp 26012 1
agpgart 34888 2 intel_agp
hw_random 7320 0
pcspkr 4352 0
shpchp 42144 0
pci_hotplug 32828 1 shpchp
ext3 142856 1
jbd 62228 1 ext3
uhci_hcd 24968 0
ide_generic 2432 0
usbcore 134912 2 uhci_hcd
ide_cd 33696 0
cdrom 38944 1 ide_cd
ide_disk 18560 4
piix 11780 1
generic 6276 0
processor 31560 0
fbcon 41504 0
tileblit 3840 1 fbcon
font 9344 1 fbcon
bitblit 7168 1 fbcon
softcursor 3328 1 bitblit
vesafb 9244 0
capability 5896 0
commoncap 8704 1 capability

iwlist scan
lo Interface doesn't support scanning.
wifi0 Interface doesn't support scanning.
ath0 No scan results
eth0 Interface doesn't support scanning.
sit0 Interface doesn't support scanning.

cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-essid linksys
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 8d796ee354033e76a823bbab3996249c1e4e9c0af571a252de aec99fff1b537d

cat /etc/modprobe.d/ndiswrapper
cat: /etc/modprobe.d/ndiswrapper: No such file or directory

cat /etc/resolv.conf
nameserver 203.96.152.4
nameserver 203.96.152.12
-----------------------------------------------------------
Any suggestions on what I should try next?
Thanks
KiwiPete

[wieman01]

If I were you, I'd to connect up to unsecure networks first. As you have said, your card does not seem to work, therefore this thread won't help you much.

Sorry I cannot say more, but this thread is meant for wireless security rather than hardware problems. I will try to help you though, if you send me a link by PM.

[mills]

maybe i should have come here first

http://ubuntuforums.org/showthread.php?p=2517527#post2517527

](*,)

[gamerteck]

I can confirm that removing wpa-conf managed fixed my LEAP authentication issue.
It worked before, in 6.10, I upgrade to 7.04


My interface config for WPA on eth1 looked as so:

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid <something>
wpa-eap LEAP
wpa-key-mgmt IEEE8021X
wpa-identity <user>
wpa-password <password>



When I restarted networking I would gett the same error:

wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
There is already a pid file /var/run/dhclient.eth1.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/


Removed the wpa-conf manager from my interfaces WPA config paramaters and it worked like a charm...
Thanks corax for squashing this issue! :guitar:

[chevkoch]

Some users reported (including myself) that the network has to be restarted every time after startup... Apparently this is a bug.
...quote from post #2
Why is this bug still there in Feisty? It's been two new releases since then!!!! Sometimes I doubt open source works.

[wieman01]

...quote from post #2
Why is this bug still there in Feisty? It's been two new releases since then!!!! Sometimes I doubt open source works.
No idea... I have not reported anything on launchpad, maybe I should do that.

EDIT:
This has nothing to do with Open Source though...

[chevkoch]

No idea... I have not reported anything on launchpad, maybe I should do that.


yeah you should do it

[sdjkfhk123j4h2jk]

I agree with removing "wpa-conf managed" to make it work. From the man page, the wpa-conf option is for choosing an wpasupplicant.conf file, so if you don't have a file called "managed" it will give an error.

[nab]

Hi,
I'm having problems with my wlan ;-(

Yesterday I switched from dapper to feisty. According to this howto I installed and configured my wlan and everything worked fine.

After rebooting I can't connect anymore to the wlan. The Network-Manager I see only LAN and manual configuratio no wlan.

My wlan card is an IPW 2200.
In the Network Administration Tool wlan is switched to roaming.

with iwconfig I get:

eth1 IEEE 802.11g ESSID:"GDP"
Mode:Managed Frequency:2.462 GHz Access Point: 00:03:C9:B3:13:75
Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=92/100 Signal level=-35 dBm Noise level=-85 dBm
Rx invalid nwid:0 Rx invalid crypt:128 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


with iwlist scan I get:
Cell 02 - Address: 00:03:C9:B3:13:75
ESSID:"GDP"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
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
Quality=93/100 Signal level=-34 dBm
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 1428ms ago


My /etc/network/interfaces looks like:


auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid GDP
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk ####...###


on sudo /etc/init.d/networking restart I get:

* Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.eth0.pid with pid 8225
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/eth0/00:0f:b0:57:18:25
Sending on LPF/eth0/00:0f:b0:57:18:25
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.2.1 port 67
There is already a pid file /var/run/dhclient.eth1.pid with pid 8250
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:0e:35:bd:b2:b7
Sending on LPF/eth1/00:0e:35:bd:b2:b7
Sending on Socket/fallback
DHCPRELEASE on eth1 to 192.168.2.1 port 67
There is already a pid file /var/run/dhclient.eth0.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/eth0/00:0f:b0:57:18:25
Sending on LPF/eth0/00:0f:b0:57:18:25
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 192.168.2.1
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.2.1
bound to 192.168.2.32 -- renewal in 138107 seconds.
There is already a pid file /var/run/dhclient.eth1.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/eth1/00:0e:35:bd:b2:b7
Sending on LPF/eth1/00:0e:35:bd:b2:b7
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 192.168.2.1
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPACK from 192.168.2.1
bound to 192.168.2.33 -- renewal in 130447 seconds.
RTNETLINK answers: File exists
run-parts: /etc/network/if-up.d/avahi-autoipd exited with return code 2
eth2: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.eth2.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/

SIOCSIFADDR: No such device
eth2: ERROR while getting interface flags: No such device
eth2: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up eth2.
ath0: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.ath0.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/

SIOCSIFADDR: No such device
ath0: ERROR while getting interface flags: No such device
ath0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up ath0.
wlan0: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.wlan0.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/

SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
wlan0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up wlan0.


Well ...
What can I do to get my wlan working?

Any help or link is welcome!

TIA
Nikolaus

[wieman01]

Hi,
I'm having problems with my wlan ;-(

Yesterday I switched from dapper to feisty. According to this howto I installed and configured my wlan and everything worked fine.

After rebooting I can't connect anymore to the wlan. The Network-Manager I see only LAN and manual configuratio no wlan.
Well, that"s what I have mentioned under "Common stumbling blocks"... You cannot manually configure your wireless network using WPA and have NetworkManager running at the same time. Surprises me it did work after upgrading to Feisty. Weird.

Have you got Firestarter installed? What is the result of:
route

[imekon]

I tried the following with my D-Link DWL-G650 PCMCIA card:


auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
# wpa-conf managed
wpa-ssid <your_essid>
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <your_wpa_psk>


it worked once I rebooted, and restarted the network with /etc/init.d/networking/restart. :)

This morning, it no longer works! :confused:

DHCP tries to get and address continuously then gives up.

The card flashed both lights continuously when it worked - when it doesn't work they flash alternately as they did this morning. It's almost as if the card hasn't been configured right.

(This is on Ubuntu desktop 7.04)

[wieman01]

I tried the following with my D-Link DWL-G650 PCMCIA card:

This morning, it no longer works! :confused:

DHCP tries to get and address continuously then gives up.

The card flashed both lights continuously when it worked - when it doesn't work they flash alternately as they did this morning. It's almost as if the card hasn't been configured right.

(This is on Ubuntu desktop 7.04)
Please try to disable all security settings and connect to an unsecured network, just to see if card cards works fine. When you scan for your network ("iwlist scan") do you get any results?

[imekon]

Well it did connect last night, now today it doesn't. I haven't changed any settings either end, so this is a bit strange?

[wieman01]

Well it did connect last night, now today it doesn't. I haven't changed any settings either end, so this is a bit strange?
Definitely is. Does restarting the network right after restarting your computer do any good? Does scanning yield any results? Odd...

[nab]

Hi wieman01,

I haven't installed any firewall, because I'm sitting behind a router.

with route I get:

Kernel IP Routentabelle
Ziel Router Genmask Flags Metric Ref Use Iface
172.16.145.0 * 255.255.255.0 U 0 0 0 vmnet8
192.168.2.0 * 255.255.255.0 U 0 0 0 eth0
192.168.252.0 * 255.255.255.0 U 0 0 0 vmnet1
link-local * 255.255.0.0 U 0 0 0 eth1
link-local * 255.255.0.0 U 1000 0 0 eth0
default 192.168.2.1 0.0.0.0 UG 0 0 0 eth0
default * 0.0.0.0 U 1000 0 0 eth1


Well, I'm not sure I understand you right (being non-native in English)

I didn't configure my wlan card in Network Administration Tool. The setting there is roaming. I never changed that.

What I don't understand is that I see the wlan-router with iwconfig and iwlist scan, but that I don't have the menu point wlan in nm-applet listed (There are only the menu points: LAN and "manual configuration", which brings me to the Network Administration Tool.)

On the first installation the wlan-router was listed in the menu.

Repeating the installation steps -including restarting the network and rebooting didn't help me to connect with the wlan.

Well, I hope I was able to clarify what I did.

TIA,
Nikolaus

[wieman01]

Hi wieman01,

I haven't installed any firewall, because I'm sitting behind a router.

Well, I'm not sure I understand you right (being non-native in English)

Well, I hope I was able to clarify what I did.

TIA,
Nikolaus
No prob. :-)

I couldn't quite figure out what method you have used to connect to your wireless network... manually editing "/etc/network/interfaces" or using the Network-Manager applet?

Nevertheless "route" seems to suggest that you are connected. Please trying to ping your router and see if you get a response:
ping 192.168.2.1
And ensure that your Ethernet cable is not connected to your computer while you are attempting to connect via wireless. Feel free to PM me if there are any other problems.

[d3dtn01]

I upgrade to Feisty last week and it blew away my wireless card drivers. Having gone through the whole ndiswrapper process and such, I now have wireless working. However, I'm only able to connect to a neighbor's unprotected network, not my WPA protected network. I used this HowTO in the past (before the upgrade) and it worked great. This time, I can't seem to connect. Here's the output I get when I run sudo /etc/init.d/networking restart:

* Reconfiguring network interfaces... wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-down.d/wpasupplicant exited with return code 1
There is already a pid file /var/run/dhclient.wlan0.pid with pid 6789
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/wlan0/00:14:a5:4f:36:1a
Sending on LPF/wlan0/00:14:a5:4f:36:1a
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.1.1 port 67
wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-post-down.d/wpasupplicant exited with return code 1
RTNETLINK answers: No such process
There is already a pid file /var/run/dhclient.eth0.pid with pid 6857
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/eth0/00:14:22:9a:89:92
Sending on LPF/eth0/00:14:22:9a:89:92
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.1.1 port 67
wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
There is already a pid file /var/run/dhclient.wlan0.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:14:a5:4f:36:1a
Sending on LPF/wlan0/00:14:a5:4f:36:1a
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
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.142 -- renewal in 82167 seconds.
wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-up.d/wpasupplicant exited with return code 1
There is already a pid file /var/run/dhclient.eth0.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/eth0/00:14:22:9a:89:92
Sending on LPF/eth0/00:14:22:9a:89:92
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 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


What should I make of this?

[wieman01]

I upgrade to Feisty last week and it blew away my wireless card drivers. Having gone through the whole ndiswrapper process and such, I now have wireless working. However, I'm only able to connect to a neighbor's unprotected network, not my WPA protected network. I used this HowTO in the past (before the upgrade) and it worked great. This time, I can't seem to connect. Here's the output I get when I run sudo /etc/init.d/networking restart:

What should I make of this?
Simply remove this line from your interfaces config files:
wpa-conf managed
Then restart the network or your computer.

[reauthor]

Hy guys!
First,I wish to thanks for this great HOWTO..it works perfectly for me on Feisty.
I have a laptop whit Intel wireless card 2200BG.For encryption I using WPA2 and radius server for authentication,shortly WPA2 AES Enterprise.
Like I said,thanks one more time.

[wieman01]

Hy guys!
First,I wish to thanks for this great HOWTO..it works perfectly for me on Feisty.
I have a laptop whit Intel wireless card 2200BG.For encryption I using WPA2 and radius server for authentication,shortly WPA2 AES Enterprise.
Like I said,thanks one more time.
Great stuff. Would you mind sharing your script with us so that I can update the HOWTO and change the status from "not tested" to "sample configuration"? Would be nice... Thanks.

[d3dtn01]

I followed wieman01's suggestion

Simply remove this line from your interfaces config files: "wpa-conf managed".

I saved the interfaces file then I rebooted. Still doesn't work. New suggestions?

[reauthor]

Great stuff. Would you mind sharing your script with us so that I can update the HOWTO and change the status from "not tested" to "sample configuration"? Would be nice... Thanks.

Yes,ofcourse,Iam glad I can help. Maybe I have a little confused network configuration but just point to eth1 interface.
Before I made some changes first I disabled roaming mode in System->Administration->Network for wireless interface
#My interfaces configuration.

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid my_ssid
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-eap PEAP
wpa-key-mgmt WPA-EAP
wpa-identity my_username
wpa-password my_password

auto eth1:0
iface eth1:0 inet static
address 10.x.x.x
netmask 255.255.255.0

#my static routes
up /sbin/route add -net 10.x.x.x/24 gw 10.x.x.x dev eth1
down /sbin/route del -net 10.x.x.x/24 gw 10.x.x.x dev eth1

up /sbin/route add -net 10.x.x.x/24 gw 10.x.x.x dev eth1
down /sbin/route del -net 10.x.x.x/24 gw 10.0.x.x.x dev eth1

up /sbin/route add -net 10.x.x.x/24 gw 10.x.x.x dev eth1
down /sbin/route del -net 10.x.x.x/24 gw 10.x.x.x dev eth1

up /sbin/route add -net 10.x.x.x/24 gw 10.x.x.x dev eth1
down /sbin/route del -net 10.x.x.x/24 gw 10.x.x.x dev eth1

After I made this configuration I added few lines from tedrogers post (post #50)where I replaced wlano whit eth1.
echo 'ifdown eth1' >/etc/init.d/WlanDown
ln -s ../init.d/WlanDown /etc/rcS.d/S40WlanDown
chmod +x /etc/init.d/WlanDown


Sorry for my english,it isnt my native language.

[wieman01]

Yes,ofcourse,Iam glad I can help. Maybe I have a little confused network configuration but just point to eth1 interface.
Before I made some changes first I disabled roaming mode in System->Administration->Network for wireless interface

Sorry for my english,it isnt my native language.
Excellent, buddy. Thank you.

[wieman01]

I followed wieman01's suggestion

I saved the interfaces file then I rebooted. Still doesn't work. New suggestions?
Guess it's worth taking a look at you configuration once again. Could you post it? Also including the output after restarting the network. No idea yet what is going on.

[d3dtn01]

OK, here's the content of my interfaces file:

auto lo
iface lo inet loopback
iface eth0 inet dhcp

iface wlan0 inet dhcp
wpa-driver wext
# wpa-conf managed
wpa-ssid habibi
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk c1cc29f9151cedb15d292d1607e4aba74e8680cda61986f122 5702668b818873

auto eth0

When I restart my network, I get the following output:

* Reconfiguring network interfaces... RTNETLINK answers: No such process
There is already a pid file /var/run/dhclient.eth0.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/eth0/00:14:22:9a:89:92
Sending on LPF/eth0/00:14:22:9a:89:92
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.1.1 port 67
There is already a pid file /var/run/dhclient.eth0.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/eth0/00:14:22:9a:89:92
Sending on LPF/eth0/00:14:22:9a:89:92
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


See anything wrong here? Thanks for the help.

[reauthor]

OK, here's the content of my interfaces file:

auto lo
iface lo inet loopback
iface eth0 inet dhcp

iface wlan0 inet dhcp
wpa-driver wext
# wpa-conf managed
wpa-ssid habibi
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk c1cc29f9151cedb15d292d1607e4aba74e8680cda61986f122 5702668b818873

auto eth0

When I restart my network, I get the following output:

* Reconfiguring network interfaces... RTNETLINK answers: No such process
There is already a pid file /var/run/dhclient.eth0.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/eth0/00:14:22:9a:89:92
Sending on LPF/eth0/00:14:22:9a:89:92
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.1.1 port 67
There is already a pid file /var/run/dhclient.eth0.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/eth0/00:14:22:9a:89:92
Sending on LPF/eth0/00:14:22:9a:89:92
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


See anything wrong here? Thanks for the help.

Hy d3dtn01.

Did you unchecked roaming mode in network-manager(System->Adminstration->Network)
If you do so,can you please put your iwconfig output here.
Dont worry,we will try to make your wifi on:)

[GuruX]

Before upgrading to Feisty Fawn I had WPA running very nicely with this type of config. nm-applet was used to connect to different APs.

Inetfaces file

auto lo
iface lo inet loopback
;auto ath0
;iface ath0 inet dhcp
wpa-driver madwifi
wpa-conf /etc/wpa_supplicant.conf


iface ppp0 inet ppp
provider ppp0


I'm no expert, so I guess there is some junk in it.


And the wpa_supplicant.conf looked like this.


network={
ssid="My SSID"
proto=WPA
key_mgmt=WPA-PSK
#psk="my key in ascii"
psk=my key in hex
}

Worked really fine. I could connect to my own AP with WPA encryption, and to other WEP encrypted APs. But now after upgrading to Feisty, it doesn't work. I really haven't found out why.

[wieman01]

Before upgrading to Feisty Fawn I had WPA running very nicely with this type of config. nm-applet was used to connect to different APs.

Inetfaces file

auto lo
iface lo inet loopback
;auto ath0
;iface ath0 inet dhcp
wpa-driver madwifi
wpa-conf /etc/wpa_supplicant.conf


iface ppp0 inet ppp
provider ppp0


I'm no expert, so I guess there is some junk in it.


And the wpa_supplicant.conf looked like this.


network={
ssid="My SSID"
proto=WPA
key_mgmt=WPA-PSK
#psk="my key in ascii"
psk=my key in hex
}

Worked really fine. I could connect to my own AP with WPA encryption, and to other WEP encrypted APs. But now after upgrading to Feisty, it doesn't work. I really haven't found out why.
Try our approach then. I cannot give you advice. But I reckon you will find an answer here:

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

[wieman01]

OK, here's the content of my interfaces file:

auto lo
iface lo inet loopback
iface eth0 inet dhcp

iface wlan0 inet dhcp
wpa-driver wext
# wpa-conf managed
wpa-ssid habibi
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk c1cc29f9151cedb15d292d1607e4aba74e8680cda61986f122 5702668b818873

auto eth0

When I restart my network, I get the following output:

* Reconfiguring network interfaces... RTNETLINK answers: No such process
There is already a pid file /var/run/dhclient.eth0.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/eth0/00:14:22:9a:89:92
Sending on LPF/eth0/00:14:22:9a:89:92
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.1.1 port 67
There is already a pid file /var/run/dhclient.eth0.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/eth0/00:14:22:9a:89:92
Sending on LPF/eth0/00:14:22:9a:89:92
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


See anything wrong here? Thanks for the help.
Looks to me as if you have not pulled your Ethernet cable. You cannot have a wireless and wired connection at the same time as far as I remember. Pull the plug and restart the network.

If this does not help, please follow Reauthor's suggestion.

[GuruX]

Try our approach then. I cannot give you advice. But I reckon you will find an answer here:

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

Yeah, that's pretty much what I did last time. And tried again this time. But it didn't work.

Anyway, I came to the solution now. The problem was obviously patched madwifi drivers for aircrack-ng. I compiled and installed the unpatched madwifi, and the compiled wpa_supplicant towards the unpatched madwifi. And now my setup is working again. I'll try to install the patched drivers again, that might work.


edit:
Yeah that worked. So, if you want to run wpa with the patched madwifi drivers. The installation order must be this.
1. Compile/install madwifi
2. Compile/install wpa_supplicant (towards unpatched madwifi)
3. Compile/install patched madwifi

[Forgott3n]

Hello,

I am using the D-Link WDA-1320 card (Atheros) and it uses the restricted drivers (as said in Feisty).

I have followed the directions precisely but with no luck.

I also noticed with the d-link card I have ath0, eth2, and wlan0 (eth1 is my wired connection) So I added the static configuration to all of them.

I have removed NetworkManager and NetworkManager-Gnome, I have WPA_Supplicant, and I'm running Feisty Fawn 7.04


Any help would be greatly appreciated.


[Edit] Here's what I get when I restart, what iwconfig dumps, and what I have in /etc/networking/interfaces

justin@bullbox:~$ sudo /etc/init.d/networking restart
Password:
* Reconfiguring network interfaces... SIOCDELRT: No such process
eth1: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.eth1.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/

wifi0: unknown hardware address type 801
SIOCSIFADDR: No such device
eth1: ERROR while getting interface flags: No such device
eth1: ERROR while getting interface flags: No such device
wifi0: unknown hardware address type 801
Bind socket to interface: No such device
Failed to bring up eth1.
eth2: ERROR while getting interface flags: No such device
ioctl[SIOCSIWPMKSA]: No such device
ioctl[SIOCSIWMODE]: No such device
Could not configure driver to use managed mode
ioctl[SIOCGIFFLAGS]: No such device
Could not set interface 'eth2' UP
ioctl[SIOCGIWRANGE]: No such device
ioctl[IEEE80211_IOCTL_SETPARAM]: No such device
ioctl[SIOCSIWAP]: No such device
ioctl[SIOCGIFFLAGS]: No such device
Failed to initialize driver interface
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
SIOCSIFADDR: No such device
eth2: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
eth2: ERROR while getting interface flags: No such device
Failed to bring up eth2.
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
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
RTNETLINK answers: File exists
run-parts: /etc/network/if-up.d/avahi-autoipd exited with return code 2
wlan0: ERROR while getting interface flags: No such device
ioctl[SIOCSIWPMKSA]: No such device
ioctl[SIOCSIWMODE]: No such device
Could not configure driver to use managed mode
ioctl[SIOCGIFFLAGS]: No such device
Could not set interface 'wlan0' UP
ioctl[SIOCGIWRANGE]: No such device
ioctl[IEEE80211_IOCTL_SETPARAM]: No such device
ioctl[SIOCSIWAP]: No such device
ioctl[SIOCGIFFLAGS]: No such device
Failed to initialize driver interface
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
There is already a pid file /var/run/dhclient.wlan0.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/

wifi0: 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
wifi0: unknown hardware address type 801
Bind socket to interface: No such device
Failed to bring up wlan0.
[ OK ]
justin@bullbox:~$


=======

justin@bullbox:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wifi0 no wireless extensions.

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

justin@bullbox:~$

=======

auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet static
address 192.168.1.127
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver madwifi
wpa-ssid gray-network
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 9783db4dfeaf61f96982d0791f15534ea0d9d98d55267bdf2b a750501f98a80d

auto ath0
iface ath0 inet static
address 192.168.1.127
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver madwifi
wpa-ssid gray-network
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 9783db4dfeaf61f96982d0791f15534ea0d9d98d55267bdf2b a750501f98a80d

auto wifi0
iface wifi0 inet static
address 192.168.1.127
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver madwifi
wpa-ssid gray-network
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 9783db4dfeaf61f96982d0791f15534ea0d9d98d55267bdf2b a750501f98a80d

auto wlan0
iface wlan0 inet dhcp
wpa-driver madwifi
wpa-ssid gray-network
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 9783db4dfeaf61f96982d0791f15534ea0d9d98d55267bdf2b a750501f98a80d



Note: I added wifi0 into the mix because on first attempt I noticed that the restart was complaining about a wifi0.

[wieman01]

Hello,

I am using the D-Link WDA-1320 card (Atheros) and it uses the restricted drivers (as said in Feisty).

I have followed the directions precisely but with no luck.

I also noticed with the d-link card I have ath0, eth2, and wlan0 (eth1 is my wired connection) So I added the static configuration to all of them.

I have removed NetworkManager and NetworkManager-Gnome, I have WPA_Supplicant, and I'm running Feisty Fawn 7.04


Any help would be greatly appreciated.
Two quesiton before we proceed... Have you scanned for your network yet & does it yield any results?
iwlist scan
Second, have you been able to connect to unsecured networks yet? That is particularly important because I need to now if you card is working or not.

Lastly, some card do not support WPA2 (RSN-CCMP) but only WPA1 (WPA-TKIP). Please try both options.

[Forgott3n]

Two quesiton before we proceed... Have you scanned for your network yet & does it yield any results?

Second, have you been able to connect to unsecured networks yet? That is particularly important because I need to now if you card is working or not.

Lastly, some card do not support WPA2 (RSN-CCMP) but only WPA1 (WPA-TKIP). Please try both options.


Ahh yes, forgot to mention. I was able to connect to my secured AP and unsecured APs via NetworkManager prior to attempting to make my system static. Here is the iwlist scan

justin@bullbox:~$ 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:40:10:10:00:03
ESSID:"gray-network"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=31/94 Signal level=-64 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: 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 (2) : CCMP TKIP
Authentication Suites (1) : PSK
Cell 02 - Address: 00:13:46:87:0F:74
ESSID:"default"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=1/94 Signal level=-94 dBm Noise level=-95 dBm
Encryption key:off
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:ath_ie=dd0900037f01010020ff7f
Cell 03 - Address: 00:0C:41:B3:06:C0
ESSID:"linksys"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=10/94 Signal level=-85 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 - Address: 00:0F:3D:5B:23:BA
ESSID:"ottis"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=2/94 Signal level=-93 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
Extra:ath_ie=dd0900037f010100170000

[wieman01]

Ahh yes, forgot to mention. I was able to connect to my secured AP and unsecured APs via NetworkManager prior to attempting to make my system static. Here is the iwlist scan:
I see... Please try WPA1 (TKIP) instead (sample script on first page), I don't know if the Madwifi driver supports WPA with CCMP (AES). Any better now?

[Forgott3n]

I see... Please try WPA1 (TKIP) instead (sample script on first page), I don't know if the Madwifi driver supports WPA with CCMP (AES). Any better now?

Thank you! It works perfectly.

[wieman01]

Thank you! It works perfectly.
It's the driver then. I should mention that in the tutorial. No all adapters/drivers support WPA2. :-)

[Forgott3n]

It's the driver then. I should mention that in the tutorial. No all adapters/drivers support WPA2. :-)

WPA2 worked alright, but its the encryption method (AES). Once I switched to TKIP it worked just fine.

A little side note: after boot up I have to restart the /etc/init.d/networking in order for it to work. I guess thats what the scripts are for on the tutorial page.

Thanks again!

[d3dtn01]

Wieman01,

Thanks for the suggestion about taking the "enable roaming" off. I deactivated that and now I'm connected to my network. Thanks for the great help!

[wieman01]

Wieman01,

Thanks for the suggestion about taking the "enable roaming" off. I deactivated that and now I'm connected to my network. Thanks for the great help!
That was Reauthor's idea. But anyway, good to hear it worked for you. :-)

[Forgott3n]

Interesting... For some reason, every once in a while I have to restart the networking because the server will stop staying connected.

Can a script be written to restart the networking if the server cannot ping google?

[wieman01]

Interesting... For some reason, every once in a while I have to restart the networking because the server will stop staying connected.

Can a script be written to restart the networking if the server cannot ping google?
I suppose one could do that altough I can't. But if you don't stay connected wouldn't it be easier if you played around with the settings of your physical network e.g. RTS threshold, beacon interval, channel, etc.? I am sure the problem lies there. The wireless channel is a usual suspect for instance as your network might interfer with others around you.

[pleurastic]

Thanks for the note of removing the "wpa_conf managed". Solved the fiesty upgrade failure in 2 minutes. My ath0 device was working but not connecting and I'd never have thought to remove the line you suggested.

[50ftrobot]

Hi there,

I'm a bit of a noob so please be patient!

I previously had my mum's pc setup with Ubuntu installed and working fine on our wireless network so I know the wireless card and drivers etc work.

The problem I've got is that I upgraded our home wireless network to WPA from WEP and followed a guide online to setup WPA in Ubuntu. This then [i think] broke everything and I couldn't connect to wireless at all even when the network was set back to WEP. This also resulted ina very slow boot up as I think the networking config was broken.

I followed this guide which which seems to have sorted the boot-up problem as the system is now quick and responsive again, however, when I restart the network it says 'Couldn't read interfaces file'

I know the network is fine because my mac and pc connect without an issue on WEP and WPA.

Any suggestions on how I can solve my problem would be much appreciated.

Many Thanks

[reauthor]

Hi there,

I'm a bit of a noob so please be patient!

I previously had my mum's pc setup with Ubuntu installed and working fine on our wireless network so I know the wireless card and drivers etc work.

The problem I've got is that I upgraded our home wireless network to WPA from WEP and followed a guide online to setup WPA in Ubuntu. This then [i think] broke everything and I couldn't connect to wireless at all even when the network was set back to WEP. This also resulted ina very slow boot up as I think the networking config was broken.

I followed this guide which which seems to have sorted the boot-up problem as the system is now quick and responsive again, however, when I restart the network it says 'Couldn't read interfaces file'

I know the network is fine because my mac and pc connect without an issue on WEP and WPA.

Any suggestions on how I can solve my problem would be much appreciated.

Many Thanks

Which version of Ubuntu you using?

[50ftrobot]

Hi,

Thanks for getting back to me.!

I installed theversion before [i can't remember the name] but then it got upgraded to the current one Edgy Eft [that's the version it states in the about Ubuntu Version info]

Thanks,

Chris

[wieman01]

Hi,

Thanks for getting back to me.!

I installed theversion before [i can't remember the name] but then it got upgraded to the current one Edgy Eft [that's the version it states in the about Ubuntu Version info]

Thanks,

Chris
More importantly what wireless network card have you got? And could you also post the contents of "/etc/network/interfaces" please? Simply connect your computer via Ethernet, that should do.

Reauthor and I can only help you if you provide a little more information. Actually, please provide as much as possible...

[50ftrobot]

Hi,

Thanks for getting back to me - I've got the details of all the things you ask for in the thread [i think]

I apologise in advance for any schoolboy errors you spot....

uname
Linux maggie-desktop 2.6.17-11-generic #2 SMP Thu Feb 1 19:52:28 UTC 2007 i686 GNU/Linux

route:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface

lsmod:
Module Size Used by
nls_utf8 3200 1
nls_cp437 6912 1
vfat 14720 1
fat 56348 1 vfat
binfmt_misc 13448 1
ipv6 272288 8
rfcomm 42260 0
l2cap 27136 5 rfcomm
bluetooth 53476 4 rfcomm,l2cap
i915 21632 2
drm 74644 3 i915
sg 37404 0
sd_mod 22656 2
speedstep_lib 5764 0
cpufreq_userspace 5408 0
cpufreq_stats 7744 0
freq_table 6048 1 cpufreq_stats
cpufreq_powersave 2944 0
cpufreq_ondemand 8876 0
cpufreq_conservative 8712 0
video 17540 0
tc1100_wmi 8324 0
sbs 16804 0
sony_acpi 6412 0
pcc_acpi 14080 0
i2c_ec 6272 1 sbs
hotkey 11556 0
dev_acpi 12292 0
button 7952 0
battery 11652 0
container 5632 0
ac 6788 0
asus_acpi 17688 0
lp 12964 0
8139cp 24832 0
tsdev 9152 0
8139too 29056 0
mii 6912 2 8139cp,8139too
usb_storage 75072 1
scsi_mod 144648 3 sg,sd_mod,usb_storage
usblp 15488 0
acx 102540 0
libusual 17040 1 usb_storage
snd_intel8x0 34844 1
snd_ac97_codec 97696 1 snd_intel8x0
snd_ac97_bus 3456 1 snd_ac97_codec
snd_pcm_oss 47360 0
snd_mixer_oss 19584 1 snd_pcm_oss
evdev 11392 1
i2c_i810 6276 0
i2c_algo_bit 10376 1 i2c_i810
pcspkr 4352 0
psmouse 41352 0
serio_raw 8452 0
parport_pc 37796 1
parport 39496 2 lp,parport_pc
snd_pcm 84612 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 25348 1 snd_pcm
floppy 63044 0
i2c_core 23424 2 i2c_ec,i2c_algo_bit
snd 58372 8 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_timer
soundcore 11232 1 snd
snd_page_alloc 11400 2 snd_intel8x0,snd_pcm
shpchp 42144 0
pci_hotplug 32828 1 shpchp
intel_agp 26012 1
agpgart 34888 3 drm,intel_agp
ext3 142856 1
jbd 62228 1 ext3
ehci_hcd 34696 0
uhci_hcd 24968 0
usbcore 134912 7 usb_storage,usblp,acx,libusual,ehci_hcd,uhci_hcd
ide_generic 2432 0
ide_cd 33696 0
cdrom 38944 1 ide_cd
ide_disk 18560 3
piix 11780 1
generic 6276 0
thermal 15624 0
processor 31560 1 thermal
fan 6020 0
fbcon 41504 0
tileblit 3840 1 fbcon
font 9344 1 fbcon
bitblit 7168 1 fbcon
softcursor 3328 1 bitblit
vesafb 9244 0
capability 5896 0
commoncap 8704 1 capability

iwlist scan:
lo Interface doesn't support scanning.

iwconfig:
lo no wireless extensions.

wlan0 IEEE 802.11b+/g+ ESSID:"STAD7D5D3" Nickname:"acx v0.3.21"
Mode:Managed Channel:1 Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power=15 dBm Sensitivity=1/3
Retry min limit:7 RTS 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

eth0 no wireless extensions.

sit0 no wireless extensions.

interfaces:
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet sdhcp
wpa-driver wext
wpa-ssid skelligs
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk da56438a0c62b1bbd02a48789c5b5f650a009275a5b85bdb42 f2e42b88cd8a88

ifconfig:
eth0 Link encap:Ethernet HWaddr 00:01:6C:30:59:7B
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:209 Base address:0x4000

lo Link encap:Local Loopback
LOOPBACK 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)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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)

wlan0 Link encap:Ethernet HWaddr 00:C0:49:D7:D5:D3
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:169


cat resolve:
cat: /etc/resolve.conf: No such file or directory

cat network:
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet sdhcp
wpa-driver wext
wpa-ssid skelligs
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk da56438a0c62b1bbd02a48789c5b5f650a009275a5b85bdb42 f2e42b88cd8a88

cat modprobe
cat: /etc/modprobe.d/ndiswrapper: No such file or directory

let me know if you need to see anything else [though you might need to supply the terminal command as I'm not clued up on this but can follow instructions easily]

Thanks!

[wieman01]

50ftrobot:

Are your sure "iwlist scan" does not yield any results with regard to your wireless interface ("wlan0")? Have you installed "ndiswrapper"?

One thing I saw immediately although I am not sure if it is a typo:
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet sdhcp
wpa-driver wext
wpa-ssid skelligs
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk da56438a0c62b1bbd02a48789c5b5f650a009275a5b85bdb42 f2e42b88cd8a88
The line in red should read:
iface wlan0 inet dhcp
It would be helpful to know what your wireless interface is referred to normally (e.g. eth1, wlan0, etc.). Any idea?

[50ftrobot]

I changed the line to read dhcp but it's not helped.

I don't think ndiswrapper is installed, but I didn't need it before I had this problem so would I still need it as I thought that is just for the driver for the wireless card [the card was working on WEP]?

no results on iwlist scan

Thanks

[wieman01]

I changed the line to read dhcp but it's not helped.

I don't think ndiswrapper is installed, but I didn't need it before I had this problem so would I still need it as I thought that is just for the driver for the wireless card [the card was working on WEP]?

no results on iwlist scan

Thanks
No results? Then your card is not working... Have you switched it off (physical switch) perhaps?

[50ftrobot]

No results? Then your card is not working... Have you switched it off (physical switch) perhaps?
i don't think it has an actual physical switch on it - it just has an antenna on it sticking out the back of the pc. I'm not sure if following a guide elsewhere has broken the settings for it [or perhaps I did unknowingly which is just as likely].

Is there a terminal command you could suggest which would determine whether the card was working or not?

[wieman01]

i don't think it has an actual physical switch on it - it just has an antenna on it sticking out the back of the pc. I'm not sure if following a guide elsewhere has broken the settings for it [or perhaps I did unknowingly which is just as likely].

Is there a terminal command you could suggest which would determine whether the card was working or not?
It is a PCI card, isn't it? So you should try this:
lspci
Please open a new thread, however... Apparently you have got a problem with your wireless card... I would not try to configure wireless security unless you get it working.

[reauthor]

Hy,can you give me output of this command.

iwlist wlan0 scan

[jago25_98]

I'm stumped. It was working before? -using knetworkmanager but that has stopped listing networks.

iwconfig truncates the 64character key to 32characters so I'm trying WPA instead.

I can't even get to my router to see what it's setup as because I don't know what the IP is anymore.

Linux r40 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux
eth0 Link encap:Ethernet HWaddr 00:06:1B:DA:41:F9
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::206:1bff:feda:41f9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3327 errors:0 dropped:0 overruns:0 frame:0
TX packets:3334 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2147076 (2.0 MiB) TX bytes:619149 (604.6 KiB)

eth2 Link encap:Ethernet HWaddr 00:0E:35:FA:80:8B
inet6 addr: fe80::20e:35ff:fefa:808b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18 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:490 (490.0 b) TX bytes:1348 (1.3 KiB)
Interrupt:11 Base address:0x6000 Memory:d0200000-d0200fff

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:170 errors:0 dropped:0 overruns:0 frame:0
TX packets:170 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:15417 (15.0 KiB) TX bytes:15417 (15.0 KiB)

Kernel IP routeing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0
0.0.0.0 192.168.1.10 0.0.0.0 UG 0 0 0 eth0
eth2 IEEE 802.11g ESSID:"hillpark"
Mode:Managed Frequency:2.412 GHz Access Point: 00:0E:A6:CE:E2:37
Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:1CA5-BD93-FAF3-5945-A096-BD17-3F Security mode:restricted
Power Management:off
Link Quality=73/100 Signal level=-55 dBm Noise level=-92 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 Link encap:Ethernet HWaddr 00:06:1B:DA:41:F9
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::206:1bff:feda:41f9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3327 errors:0 dropped:0 overruns:0 frame:0
TX packets:3334 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2147076 (2.0 MiB) TX bytes:619149 (604.6 KiB)

eth2 Link encap:Ethernet HWaddr 00:0E:35:FA:80:8B
inet6 addr: fe80::20e:35ff:fefa:808b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18 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:490 (490.0 b) TX bytes:1348 (1.3 KiB)
Interrupt:11 Base address:0x6000 Memory:d0200000-d0200fff

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:170 errors:0 dropped:0 overruns:0 frame:0
TX packets:170 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:15417 (15.0 KiB) TX bytes:15417 (15.0 KiB)

Module Size Used by
michael_mic 3584 2
ieee80211_crypt_tkip 12032 1
ipv6 268704 8
binfmt_misc 12680 1
rfcomm 40856 2
l2cap 25728 5 rfcomm
bluetooth 55908 4 rfcomm,l2cap
nvram 9992 1
uinput 10240 1
radeon 124576 2
drm 81044 3 radeon
ppdev 10116 0
speedstep_ich 6288 0
speedstep_lib 6148 1 speedstep_ich
cpufreq_ondemand 9228 1
cpufreq_conservative 8200 0
cpufreq_stats 7360 0
cpufreq_powersave 2688 0
cpufreq_userspace 5408 0
freq_table 5792 3 speedstep_ich,cpufreq_ondemand,cpufreq_stats
dev_acpi 12292 0
pcc_acpi 13184 0
tc1100_wmi 8068 0
sony_acpi 6284 0
ibm_acpi 31512 0
sbs 15652 0
container 5248 0
i2c_ec 5888 1 sbs
i2c_core 22784 1 i2c_ec
ac 6020 0
dock 10268 0
battery 10756 0
asus_acpi 17308 0
backlight 7040 2 ibm_acpi,asus_acpi
button 8720 0
video 16388 0
nls_iso8859_1 5120 1
nls_cp437 6784 1
vfat 14208 1
fat 53916 1 vfat
lp 12452 0
fuse 46612 0
snd_intel8x0 34204 2
snd_ac97_codec 98336 1 snd_intel8x0
ac97_bus 3200 1 snd_ac97_codec
arc4 2944 4
ecb 4480 4
blkcipher 6784 1 ecb
joydev 10816 0
snd_pcm_oss 44544 0
snd_mixer_oss 17408 1 snd_pcm_oss
irtty_sir 9600 0
sir_dev 17156 1 irtty_sir
ieee80211_crypt_wep 6144 1
snd_pcm 79876 4 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
pcmcia 39212 0
irda 201276 2 irtty_sir,sir_dev
snd_seq_dummy 4740 0
snd_seq_oss 32896 0
crc_ccitt 3072 1 irda
ipw2200 148040 0
snd_seq_midi 9600 0
snd_rawmidi 25472 1 snd_seq_midi
snd_seq_midi_event 8448 2 snd_seq_oss,snd_seq_midi
snd_seq 52592 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
snd_timer 23684 3 snd_pcm,snd_seq
snd_seq_device 9100 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
parport_pc 36388 1
psmouse 38920 0
ieee80211 34760 1 ipw2200
ieee80211_crypt 7040 3 ieee80211_crypt_tkip,ieee80211_crypt_wep,ieee80211
parport 36936 3 ppdev,lp,parport_pc
yenta_socket 27532 1
rsrc_nonstatic 14080 1 yenta_socket
pcmcia_core 40852 3 pcmcia,yenta_socket,rsrc_nonstatic
pcspkr 4224 0
snd 54020 12 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_ti mer,snd_seq_device
serio_raw 7940 0
soundcore 8672 1 snd
snd_page_alloc 10888 2 snd_intel8x0,snd_pcm
shpchp 34324 0
pci_hotplug 32576 1 shpchp
intel_agp 25116 1
agpgart 35400 2 drm,intel_agp
iTCO_wdt 11812 0
iTCO_vendor_support 4868 1 iTCO_wdt
af_packet 23816 12
evdev 11008 5
tsdev 8768 0
ext3 133128 1
jbd 59816 1 ext3
mbcache 9604 1 ext3
sg 36252 0
sr_mod 17060 0
cdrom 37664 1 sr_mod
sd_mod 23428 4
generic 5124 0 [permanent]
ata_generic 9092 0
floppy 59524 0
ehci_hcd 34188 0
e100 36232 0
mii 6528 1 e100
ata_piix 15492 3
libata 125720 2 ata_generic,ata_piix
scsi_mod 142348 4 sg,sr_mod,sd_mod,libata
uhci_hcd 25360 0
usbcore 134280 3 ehci_hcd,uhci_hcd
thermal 14856 0
processor 31048 1 thermal
fan 5636 0
fbcon 42656 0
tileblit 3584 1 fbcon
font 9216 1 fbcon
bitblit 6912 1 fbcon
softcursor 3200 1 bitblit
vesafb 9220 0
capability 5896 0
commoncap 8192 1 capability
eth2 Scan completed :
Cell 01 - Address: 00:0E:A6:CE:E2:37
ESSID:"hillpark"
Protocol:IEEE 802.11bg
Mode:Master
Channel:1
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
Quality=71/100 Signal level=-57 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 136ms ago

auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

auto eth0
iface eth0 inet dhcp

auto eth2
iface eth2 inet dhcp
wpa-ssid hillpark
wpa-key-mgmt WPA-PSK
wpa-psk <64character,256bit-wep-key-censored)
wireless-essid hillpark# generated by NetworkManager, do not edit!



nameserver 192.168.1.10

[reauthor]

hy everybody...

I have a one suggestion..It is much easier and faster for me and I belive for other members to give help if I we have some information. So,I suggest that everybody who needs a help follow this protocol.

Example:

Hy,I using_________(Edgy,Feisty)and can not connect to my AP/wireless router.
Roaming mode in Network Manager is disabled(only if using Feisty).

My iwconfig

My /etc/network/interfaces

My iwlist ________(eth1,wlanO,ath0)scan

So,like I said,this is suggestion,if somebody have better idea....

[KiwiPete]

Thank you Wieman01

Having finally got my wireless card working (with no security) I have now followed the instructions in your original post (at top of this thread) and got the wireless enabled successfully with WPA1.

The only extra question I have is that I using a wireless card with Atheros chipset, but I just used 'driver wext' in my interfaces file - and it seems to work fine.
Should I change it to 'driver madwifi' to get better performance??

KiwiPete

[wieman01]

Thank you Wieman01

Having finally got my wireless card working (with no security) I have now followed the instructions in your original post (at top of this thread) and got the wireless enabled successfully with WPA1.

The only extra question I have is that I using a wireless card with Atheros chipset, but I just used 'driver wext' in my interfaces file - and it seems to work fine.
Should I change it to 'driver madwifi' to get better performance??

KiwiPete
Hello,

Glad to hear it. I don't know if the driver makes any difference at all in terms of performance. Use whatever works for you. :-)

[wieman01]

hy everybody...

I have a one suggestion..It is much easier and faster for me and I belive for other members to give help if I we have some information. So,I suggest that everybody who needs a help follow this protocol.

Example:

Hy,I using_________(Edgy,Feisty)and can not connect to my AP/wireless router.
Roaming mode in Network Manager is disabled(only if using Feisty).

My iwconfig

My /etc/network/interfaces

My iwlist ________(eth1,wlanO,ath0)scan

So,like I said,this is suggestion,if somebody have better idea....
That's a good idea actually. I'll try to update my thread over the weekend, Reauthor. Could make the whole procedure a bit smoother.

[jago25_98]

I got mine working in the end when knetworkmanager started working again. The trick was to enter the 256 WEP key as WPA.

[smiley1962]

hy i'm using feisty and can not connect to my AP/wireless router.
Roaming mode in Network Manager is disabled

My iwconfig

eth1 IEEE 802.11b ESSID:"smiley2" Nickname:"Broadcom 4301"
Mode:Managed Frequency=2.472 GHz Access Point: 00:01:E3:D9:C7:C2
Bit Rate=1 Mb/s Tx-Power=16 dBm
RTS thr:off Fragment thr:off
Encryption key:off
Link Quality=0/100 Signal level=-256 dBm Noise level=-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

My /etc/network/interfaces

auto lo
iface lo inet loopback

auto eth1
iface eth1 inet static
address 192.168.2.2
gateway 192.168.2.1
dns-nameservers 195.121.1.34
netmask 255.255.255.0
wpa-driver wext
wpa-ssid smiley2
wpa-ap-scan 2
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 898e115c50e2a053ea04a161cb95aa7a1e9f40f8971373117e 228fda2d50201a

iface eth0 inet static
address 192.168.2.2
netmask 255.255.255.0
gateway 192.168.2.1

auto eth0

My iwlist eth1 scan

eth1 Scan completed :
Cell 01 - Address: 00:01:E3:D9:C7:C2
ESSID:"smiley2"
Protocol:IEEE 802.11bg
Mode:Master
Channel:13
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 9 Mb/s; 11 Mb/s
6 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=80/100 Signal level=-55 dBm Noise level=-43 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
Preauthentication Supported
Extra: Last beacon: 32ms ago

I have tried almost every howto on the net but can't get it working.
about the wpa_supplicant.conf; it does not exist

Ihope you guys can help me:)

[wieman01]

Smiley1962:

First, what wireless card have you got?

Second this line needs to be changed as ESSID broadcast is enabled in your case:
wpa-ap-scan 1
Third, can you connect to unsecured networks?

EDIT:
This is the right place for you. So stay with us, I am sure we will be able to get you connected in the end.

[smiley1962]

First, what wireless card have you got?
a broadcom 4303 (with the linux driver)

second this line needs to be changed as ESSID broadcast is enabled in your case:

ok i wil change the 2 into a 1

Third, can you connect to unsecured networks?

Tried that but unsuccesfull

[wieman01]

First, what wireless card have you got?
a broadcom 4303 (with the linux driver)

second this line needs to be changed as ESSID broadcast is enabled in your case:

ok i wil change the 2 into a 1

Third, can you connect to unsecured networks?

Tried that but unsuccesfull
Ok... I would not proceed here before you have not been able to establish a connection in unsecured mode if you know what I mean. WPA will make things even more complicated. Post your problem in the forums, there should be people who are able to help.

[smiley1962]

ok thanks anyway

[reauthor]

Hy smiley1962..
Can you setup your AP whitout encryption and put this configuration in your interfaces

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wireless-essid smiley2

than save your configuration and restart network whit sudo /etc/init.d/networking restart

Please tell me if this work for you...

[reech]

I have recently decided to switch to wpa - I'm having problems with my fiesty box - it's been using wep with no problems. I can use the WPA AP with my laptop no problem (winXP)

I'm using a netgear ma101 usb card (at76_usb) -

I get the following output when attempting to start networking...


root@reech-desktop:/home/reech# /etc/init.d/networking restart
* Reconfiguring network interfaces... wpa_driver_atmel_set_wpa wlan0
ioctl[ATMEL_WPA_IOCTL_PARAM]: Operation not supported
ioctl[ATMEL_WPA_IOCTL_PARAM]: Operation not supported
ioctl[ATMEL_WPA_IOCTL]: Argument list too long
Failed to set encryption.
ioctl[ATMEL_WPA_IOCTL]: Argument list too long
Failed to set encryption.
ioctl[ATMEL_WPA_IOCTL]: Argument list too long
Failed to set encryption.
ioctl[ATMEL_WPA_IOCTL]: Argument list too long
Failed to set encryption.
wpa_driver_atmel_set_countermeasures - not yet implemented
wpa_driver_atmel_set_drop_unencrypted - not yet implemented


here is the output from the syslog:


May 8 00:09:08 reech-desktop kernel: [ 4673.260000] ubuntu/wireless/at76/at76c503.c: 2492: assertion dev->istate == SCANNING failed
May 8 00:09:35 reech-desktop ntpdate[9080]: can't find host ntp.ubuntu.com
May 8 00:09:35 reech-desktop ntpdate[9080]: no servers can be used, exiting
May 8 00:11:35 reech-desktop kernel: [ 4820.756000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 8 00:11:37 reech-desktop kernel: [ 4822.864000] ubuntu/wireless/at76/at76c503.c: 2522: assertion dev->istate == INIT failed
May 8 00:11:38 reech-desktop kernel: [ 4823.592000] ubuntu/wireless/at76/at76c503.c: 2492: assertion dev->istate == SCANNING failed
May 8 00:12:05 reech-desktop ntpdate[9226]: can't find host ntp.ubuntu.com
May 8 00:12:05 reech-desktop ntpdate[9226]: no servers can be used, exiting


below is my interfaces file:


auto wlan0
iface wlan0 inet static
address 192.168.0.12
netmask 255.255.255.0
gateway 192.168.0.1
wpa-driver atmel
##wpa-conf managed
wpa-ssid reechy
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 495c57eed85a88a04d2a1567b1db83bf188caff9929be64445 a0fb8a066c9bd4


...seems fine no?

I'm running kernel 2.6.20-15-generic

Is this a driver problem? I'm at my wit's end.

](*,)

[wieman01]

Is this a driver problem? I'm at my wit's end.
Looks like it is a driver problem indeed. Have you downloaded the latest Windows driver for your adapter? If not, please do so and deploy it using "ndiswrapper".

Before you do so, please try another wpa-driver (i.e. wext) which should be the right one in your case ("ndiswrapper"):
wpa-driver wext
Also ensure that ESSID broadcast is disabled as that's what this line says:
wpa-ap-scan 2
If you want to enable broadcast it should read:
wpa-ap-scan 1

[reech]

Thank you for the reply - although I had hoped to get it working without resorting to ndiswrapper.

I had thought it would be supported with the kernel module driver as the at_76 module is loaded and working:

I had tried wext with no joy.


hostap = Host AP driver (Intersil Prism2/2.5/3)
atmel = ATMEL AT76C5XXx (USB, PCMCIA)
wext = Linux wireless extensions (generic)
madwifi = Atheros
wired = wpa_supplicant wired Ethernet driver

[wieman01]

Thank you for the reply - although I had hoped to get it working without resorting to ndiswrapper.

I had thought it would be supported with the kernel module driver as the at_76 module is loaded and working:

I had tried wext with no joy.
Well, the interface name "wlan0" suggests you are using "ndiswrapper" already... Are you sure you are referring to the right interface then?

What does a scan yield?
iwlist scan

[reech]

scan finds my AP

I think the wlan0 label is legacy as I think I was using ndiswrapper with edgy, and fiesty seems to have decided to use the kernel module (after upgrading).

[wieman01]

scan finds my AP

I think the wlan0 label is legacy as I think I was using ndiswrapper with edgy, and fiesty seems to have decided to use the kernel module (after upgrading).
Alright then. Then give 'wext' a go please. If that does not yield any good results, then I am afraid the Linux driver does not support WPA after all. At least that's how I interpret the error message.

Can you connect to unsecured networks at all?

[reech]

Thanks for your patience wieman01 - I can connect fine at the moment using wep and the current kernel module - so I assume an unsecured network will be fine.

I have tried WEXT with similar results - but of course the ndiswrapper module is not loaded.

[wieman01]

Thanks for your patience wieman01 - I can connect fine at the moment using wep and the current kernel module - so I assume an unsecured network will be fine.

I have tried WEXT with similar results - but of course the ndiswrapper module is not loaded.
No problem.

I would do some more research concerning your adapter and WPA support. I can't tell for sure, but it appears to me that the current driver does not really support WPA. That said "ndiswrapper" may be worth a short after all. The latest driver for Windows will certainly support WPA(2).

[deevus]

This worked for me, but Im only connected at 1mbit/s .. Im using a Broadcom 4306 on a PPC, capable of 54mbit. What can I do to speed it up?

[reech]

I would do some more research concerning your adapter and WPA support. I can't tell for sure, but it appears to me that the current driver does not really support WPA. That said "ndiswrapper" may be worth a short after all. The latest driver for Windows will certainly support WPA(2).

Indeed - ndiswrapper is looking like my only option - thanks again.:)

[Zoufiax]

I can't get my wireless connection to work when using WPA1 security, I have tried the suggestions of the first post of this topic. However, I do get it working using WEP security, this reply was sent using it actually.

I wanted to post all results here of the commands we had to enter when "stumped", but when I try, the forum gives me an error that I'm using too many pictures, which is not correct. If anyone needs specific information please let me know, as well as how I can retrieve it as I'm a Linux newbie.

[wieman01]

I can't get my wireless connection to work when using WPA1 security, I have tried the suggestions of the first post of this topic. However, I do get it working using WEP security, this reply was sent using it actually.

I wanted to post all results here of the commands we had to enter when "stumped", but when I try, the forum gives me an error that I'm using too many pictures, which is not correct. If anyone needs specific information please let me know, as well as how I can retrieve it as I'm a Linux newbie.
What card have you got and what driver is in use? The issue could be that either card or driver does not support WPA.

[Zoufiax]

I'm using Speedtouch 121g, and it does support WPA1, for previously I was using Windows on my laptop, and WPA was working fine. But now I have installed Ubuntu Fiesty Fawn and can't get it working. I'm using ndiswrapper with the Windows drivers for the 121g, and that works fine for I can get online when using WEP-security. Also I can get my passphrase (64 characters), and I see all wireless networks in the neighborhood, so it has to do something with my Linux-WPA-configuration. Too bad Ubuntu doesn't support WPA as it supports WEP yet.

[wieman01]

I'm using Speedtouch 121g, and it does support WPA1, for previously I was using Windows on my laptop, and WPA was working fine. But now I have installed Ubuntu Fiesty Fawn and can't get it working. I'm using ndiswrapper with the Windows drivers for the 121g, and that works fine for I can get online when using WEP-security. Also I can get my passphrase (64 characters), and I see all wireless networks in the neighborhood, so it has to do something with my Linux-WPA-configuration. Too bad Ubuntu doesn't support WPA as it supports WEP yet.
Alright. Then I would ask you to post the contents of "/etc/network/interfaces". That's shed some light on the issue.

[mazz]

Hi,I using Feisty and can not connect to my AP/wireless router.
Roaming mode in Network Manager is disabled(only if using Feisty).

My iwconfig:

lo no wireless extensions.



eth0 no wireless extensions.



ra0 RT2500 Wireless ESSID:""

Mode:Managed Frequency=2.412 GHz Bit Rate:11 Mb/s Tx-Power:0 dBm

RTS thr:off Fragment thr:off

Link Quality=0/100 Signal level=-120 dBm Noise level:-192 dBm

Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0

Tx excessive retries:0 Invalid misc:0 Missed beacon:0


My /etc/network/interfaces:

auto lo

iface lo inet loopback



auto eth0

iface eth0 inet dhcp



auto eth1

iface eth1 inet dhcp



auto eth2

iface eth2 inet dhcp



auto ath0

iface ath0 inet dhcp



auto wlan0

iface wlan0 inet dhcp



address 192.168.168.0.3

gateway 192.168.0.255

dns-nameservers 192.168.0.1

netmask 255.255.255.0

wpa-driver wext

wpa-ssid <MyNetwork>

wpa-ap-scan 1

wpa-proto WPA

wpa-pairwise TKIP

wpa-group CCMP

wpa-key-mgmt WPA-PSK

wpa-psk <ccdc167d0597b7acb5336dfd8a3bc598da8472fed4c2cf7084 18a27d35c20080>


My iwlist scan:
Usage: iwlist [interface] scanning

[interface] frequency

[interface] channel

[interface] bitrate

[interface] rate

[interface] encryption

[interface] key

[interface] power

[interface] txpower

[interface] retry

[interface] ap

[interface] accesspoints

[interface] peers

[interface] event


I have tried both WAP 1 and WAP 2. stil cant get it to work.
My wireless card is a Linksys Wmp54G v4. I am trying to connect to a Netgear router.
See if something is wrong with my info.

[Zoufiax]

Alright. Then I would ask you to post the contents of "/etc/network/interfaces". That's shed some light on the issue.
Here it is:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

# auto eth1
# iface eth1 inet dhcp
#
# auto eth2
# iface eth2 inet dhcp
#
# auto ath0
# iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wireless-essid SpeedTouch3C153D
wireless-key [secret hexadecimal string]
wpa-driver wext
wpa-ssid SpeedTouch3C153D
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk [secret hexadecimal string consisting of 64 characters (lower case, does that matter?)]

If there is some more information you need please let me know.

[venky80]

@Weiman
Hi It seems you have been helping people here for quite a long time.
I have intel pro wireless 3945ABG in my toshiba laptop
my wireless device is eth01
iwlist scan
shows my wireless
with IE WPA version 1
group chiper as WEP-40
pairwise chipher WEP-40
authentication suites PSK
IE IEEE 802.11i/WPA2 version 1
group chiper as WEP-40
pairwise chipher WEP-40
authentication suites PSK

I have put the necessary lines in interfaces but iam not able to connect
do i need to do something to my wpa_supplicant?
thanks for any help

[wieman01]

Here it is:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

# auto eth1
# iface eth1 inet dhcp
#
# auto eth2
# iface eth2 inet dhcp
#
# auto ath0
# iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wireless-essid SpeedTouch3C153D
wireless-key [secret hexadecimal string]
wpa-driver wext
wpa-ssid SpeedTouch3C153D
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk [secret hexadecimal string consisting of 64 characters (lower case, does that matter?)]

If there is some more information you need please let me know.
Looks a bit different from mine. Please try this instead:
auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid SpeedTouch3C153D
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key>
I have removed 2 lines (wireless-essid, wireless-key) which refer to WEP security.

Please restart the computer and restart the network right after that:
sudo ifdown -v wlan0
sudo ifup -v wlan0
If possible post the output.

[wieman01]

@Weiman
Hi It seems you have been helping people here for quite a long time.
I have intel pro wireless 3945ABG in my toshiba laptop
my wireless device is eth01
iwlist scan
shows my wireless
with IE WPA version 1
group chiper as WEP-40
pairwise chipher WEP-40
authentication suites PSK
IE IEEE 802.11i/WPA2 version 1
group chiper as WEP-40
pairwise chipher WEP-40
authentication suites PSK

I have put the necessary lines in interfaces but iam not able to connect
do i need to do something to my wpa_supplicant?
thanks for any help
WPA-Supplicant won't help you there as you use WEP, not WPA. Ubuntu supports WEP security out of the box. Just use the default networking tool for wireless.

[nab]

well,

I solved my problem.

It seems that the manual configuration in /etc/network/interfaces and nm-applet broke my system, because after removing all edits from /etc/network/interfaces my wlan works fine again.

Thanks for the help.
Niko

[Zoufiax]

Looks a bit different from mine. Please try this instead:

I have removed 2 lines (wireless-essid, wireless-key) which refer to WEP security.

Please restart the computer and restart the network right after that:

If possible post the output.

If have changed my /etc/network/interfaces according to your suggestions, and restarted the computer and after that the network (sudo ifdown -v wlan0, and: sudo ifup -v wlan0), but it still doesn't work. The output of these ifdown and ifup commands was as follows:

zoufiax@zoufiax-laptop:~$ sudo ifdown -v wlan0
Password:
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
RTNETLINK answers: No such process
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 3984
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/wlan0/00:12:bf:08:59:49
Sending on LPF/wlan0/00:12:bf:08:59:49
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 10.0.0.138 port 67
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 3913).

zoufiax@zoufiax-laptop:~$ sudo ifup -v wlan0
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 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "SpeedTouch3C153D" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP -- OK
wpa_supplicant: wpa-group TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.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:bf:08:59:49
Sending on LPF/wlan0/00:12:bf:08:59:49
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 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
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.
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
zoufiax@zoufiax-laptop:~$

[venky80]

WPA-Supplicant won't help you there as you use WEP, not WPA. Ubuntu supports WEP security out of the box. Just use the default networking tool for wireless.

I think you misunderstood my router is setup for WPA-PSK
here are the details

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

eth0 no wireless extensions.

eth1 unassociated ESSID:off/any
Mode:Managed Frequency=nan kHz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:16 dBm
Retry limit:15 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:80 Missed beacon:0

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

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:13:46:3F:99:A2
ESSID:"nyf"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 9 Mb/s; 11 Mb/s
6 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=61/100 Signal level=-71 dBm Noise level=-71 dBm
Extra: Last beacon: 84ms ago
Cell 02 - Address: 00:0C:E5:4E:88:2F
ESSID:"wastintime"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
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
Quality=97/100 Signal level=-29 dBm Noise level=-29 dBm
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
Extra: Last beacon: 140ms ago


My Interfaces file according to the tutorial (hopefully I made no mistakes)
Is it necessary to get rid of knetworkmanager?

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid wastintime
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wap-psk <my key>

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

Thanks

[wieman01]

If have changed my /etc/network/interfaces according to your suggestions, and restarted the computer and after that the network (sudo ifdown -v wlan0, and: sudo ifup -v wlan0), but it still doesn't work. The output of these ifdown and ifup commands was as follows:

zoufiax@zoufiax-laptop:~$ sudo ifdown -v wlan0
Password:
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
RTNETLINK answers: No such process
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 3984
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/wlan0/00:12:bf:08:59:49
Sending on LPF/wlan0/00:12:bf:08:59:49
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 10.0.0.138 port 67
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 3913).

zoufiax@zoufiax-laptop:~$ sudo ifup -v wlan0
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 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "SpeedTouch3C153D" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP -- OK
wpa_supplicant: wpa-group TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.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:bf:08:59:49
Sending on LPF/wlan0/00:12:bf:08:59:49
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 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
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.
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
zoufiax@zoufiax-laptop:~$
A few more questions:

a. MAC filtering is disabled (router settings)?
b. Is your firewall up (using Firestarter for instance)?

Can you check your router's log-files? What do they say?

The authentication/encryption bit seems ok, we need to figure out why you cannot connect via DHCP. Has this worked before on unsecured networks?

[wieman01]

I think you misunderstood my router is setup for WPA-PSK
here are the details

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

eth0 no wireless extensions.

eth1 unassociated ESSID:off/any
Mode:Managed Frequency=nan kHz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:16 dBm
Retry limit:15 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:80 Missed beacon:0

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

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:13:46:3F:99:A2
ESSID:"nyf"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 9 Mb/s; 11 Mb/s
6 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=61/100 Signal level=-71 dBm Noise level=-71 dBm
Extra: Last beacon: 84ms ago
Cell 02 - Address: 00:0C:E5:4E:88:2F
ESSID:"wastintime"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
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
Quality=97/100 Signal level=-29 dBm Noise level=-29 dBm
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
Extra: Last beacon: 140ms ago


My Interfaces file according to the tutorial (hopefully I made no mistakes)
Is it necessary to get rid of knetworkmanager?

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid wastintime
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wap-psk <my key>

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

Thanks
What confuses me is the fact that the scan says that your router is set to use "WEP-40" as cipher which is referring to WEP, not WPA. WPA supports both TKIP and AES, but certainly not WEP-40 which would defeat the purpose of WPA i.e. enhanced security.

Now... Would you mind changing the cipher from WEP-40 to TKIP on the router? Your client script mentions TKIP ("wpa-pairwise TKIP") so the easiest way from here is to tell your router to use TKIP (WPA) instead of WEP-40.

EDIT:
If you don't have access to the router because it isn't yours, let me know. Then we'll change your script although that's not my preferred solution as WEP-40 is not part of the WPA suite.

[Zoufiax]

A few more questions:

a. MAC filtering is disabled (router settings)?
b. Is your firewall up (using Firestarter for instance)?

Can you check your router's log-files? What do they say?

The authentication/encryption bit seems ok, we need to figure out why you cannot connect via DHCP. Has this worked before on unsecured networks?
a. I don't know what MAC filtering is. I have a Speedtouch 580 router and don't know if it supports MAC filtering. Should it be on or off? By the way, before Ubuntu I used Windows XP, and had no problem connecting to the wireless network using WPA so I guess it has to do with the setup of Ubuntu rather then my router.
b. I am not using a firewall on my Ubuntu laptop as far as I know.

I don't think my router has any log files as it is not a computer.

[VorDesigns]

Hi,

Used this document after trying others, still no joy. This is one of the reason I can't get business users to switch to Linux but I'm still trying.

I have tried excluding the eth0 device in the interfaces to no avail. This will work with some tweaking using WEP, been there, done that.
Current status is card show connected briefly then disconnected, cycle and repeat.

This is a fresh install/patch.
----------------------
tanuki@pikunikubasukitu:~$ uname -a
Linux pikunikubasukitu 2.6.15-28-386 #1 PREEMPT Tue Mar 13 20:49:31 UTC 2007 i686 GNU/Linux
tanuki@pikunikubasukitu:~$ ifconfig -a
ath0 Link encap:Ethernet HWaddr 99:99:99:99:99:99
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:703 errors:1707 dropped:0 overruns:0 frame:1707
TX packets:742 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:200
RX bytes:79439 (77.5 KiB) TX bytes:104109 (101.6 KiB)
Interrupt:11 Memory:d8a40000-d8a50000

eth0 Link encap:Ethernet HWaddr 99:99:99:99:99:99
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2282 (2.2 KiB) TX bytes:1791 (1.7 KiB)

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:15 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:772 (772.0 b) TX bytes:772 (772.0 b)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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)

tanuki@pikunikubasukitu:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
tanuki@pikunikubasukitu:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

ath0 IEEE 802.11g ESSID:"too_ishi_o_ishi_ashi"
Mode:Managed Frequency:2.452 GHz Access Point: 99:99:99:99:99:99
Bit Rate:36 Mb/s Tx-Power:18 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=28/94 Signal level=-67 dBm Noise level=-95 dBm
Rx invalid nwid:57 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

sit0 no wireless extensions.

tanuki@pikunikubasukitu:~$ ifconfig
ath0 Link encap:Ethernet HWaddr 99:99:99:99:99:99
inet6 addr: fe80::20d:88ff:feaa:a1a6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:742 errors:1753 dropped:0 overruns:0 frame:1753
TX packets:789 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:200
RX bytes:83846 (81.8 KiB) TX bytes:110876 (108.2 KiB)
Interrupt:11 Memory:d8a40000-d8a50000

eth0 Link encap:Ethernet HWaddr 99:99:99:99:99:99
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2282 (2.2 KiB) TX bytes:1791 (1.7 KiB)

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:15 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:772 (772.0 b) TX bytes:772 (772.0 b)

tanuki@pikunikubasukitu:~$ lsmod
Module Size Used by
rfcomm 40216 0
l2cap 26244 5 rfcomm
bluetooth 50020 4 rfcomm,l2cap
ppdev 9220 0
ipv6 265856 6
speedstep_smi 5904 0
speedstep_lib 4484 1 speedstep_smi
cpufreq_userspace 4696 1
cpufreq_stats 5636 0
freq_table 4740 2 speedstep_smi,cpufreq_stats
cpufreq_powersave 1920 0
cpufreq_ondemand 6428 0
cpufreq_conservative 7332 0
video 16260 0
tc1100_wmi 6916 0
sony_acpi 5644 0
pcc_acpi 12416 0
hotkey 11556 0
dev_acpi 11140 0
container 4608 0
button 6672 0
acpi_sbs 19980 0
battery 9988 1 acpi_sbs
ac 5252 1 acpi_sbs
i2c_acpi_ec 5120 1 acpi_sbs
dm_mod 58936 1
md_mod 72532 0
lp 11844 0
af_packet 22920 6
joydev 10048 0
e100 40580 0
ath_pci 80540 0
ath_rate_sample 17160 1 ath_pci
ltserial 11056 0
ltmodem 566638 1 ltserial
mii 5888 1 e100
wlan 144924 3 ath_pci,ath_rate_sample
ath_hal 148816 3 ath_pci,ath_rate_sample
tsdev 8000 0
pcspkr 2180 0
floppy 62148 0
rtc 13492 0
pcmcia 40508 0
parport_pc 35780 1
parport 36296 3 ppdev,lp,parport_pc
psmouse 36100 0
snd_maestro3 25380 1
snd_ac97_codec 93216 1 snd_maestro3
snd_ac97_bus 2304 1 snd_ac97_codec
serio_raw 7300 0
snd_pcm_oss 53664 0
snd_mixer_oss 18688 1 snd_pcm_oss
snd_pcm 89864 3 snd_maestro3,snd_ac97_codec,snd_pcm_oss
snd_timer 25220 1 snd_pcm
snd_page_alloc 10632 1 snd_pcm
snd 55268 8 snd_maestro3,snd_ac97_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_timer
i2c_piix4 9104 0
soundcore 10208 1 snd
i2c_core 21904 2 i2c_acpi_ec,i2c_piix4
yenta_socket 28428 3
rsrc_nonstatic 13440 1 yenta_socket
shpchp 45632 0
pci_hotplug 29236 1 shpchp
pcmcia_core 42640 3 pcmcia,yenta_socket,rsrc_nonstatic
intel_agp 22940 1
agpgart 34888 1 intel_agp
evdev 9856 2
ext3 135944 1
jbd 58772 1 ext3
ide_generic 1536 0
uhci_hcd 33808 0
usbcore 130820 2 uhci_hcd
ide_cd 33028 0
cdrom 38560 1 ide_cd
ide_disk 17664 3
piix 11012 1
generic 5124 0
thermal 13576 0
processor 23360 1 thermal
fan 4868 0
capability 5000 0
commoncap 7296 1 capability
vga16fb 13704 1
vgastate 10368 1 vga16fb
fbcon 42784 72
tileblit 2816 1 fbcon
font 8320 1 fbcon
bitblit 6272 1 fbcon
softcursor 2304 1 bitblit
tanuki@pikunikubasukitu:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

ath0 Scan completed :
Cell 01 - Address: 99:99:99:99:99:99
ESSID:"too_ishi_o_ishi_ashi"
Mode:Master
Frequency:2.452 GHz (Channel 9)
Quality=27/94 Signal level=-68 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 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:wpa_ie=dd180050f20101000050f20201000050f2020 1000050f2020000
Cell 02 - Address: 00:00:00:00:00:00
ESSID:"some_other_ap_not_mine"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=2/94 Signal level=-93 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 22 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=100

sit0 Interface doesn't support scanning.

tanuki@pikunikubasukitu:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-ssid too_ishi_o_ishi_ashi
wpa-ap-scan 1
# wpa-conf managed
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <reallylongjumbleofnumbersbasedonmyapkeywhichworkso nwindowsfine>

# auto wlan0
# iface wlan0 inet dhcp
tanuki@pikunikubasukitu:~$ cat /et/modprobe.d/ndiswrapper
cat: /et/modprobe.d/ndiswrapper: No such file or directory
<probably no data hear because I have an atheros based card>
tanuki@pikunikubasukitu:~$ cat /etc/resolv.conf
search vordesigns.net
nameserver retained from eth0 last connection
nameserver retained from eth0 last connection
tanuki@pikunikubasukitu:~$

tanuki@pikunikubasukitu:~$ sudo ifdown -v ath0
Configuring interface ath0=ath0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/wpasupplicant
wpa_supplicant: ctrl_interface=/var/run/wpa_supplicant
dhclient3 -r -pf /var/run/dhclient.ath0.pid -lf /var/lib/dhcp3/dhclient.ath0.leases ath0
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/ath0/00:0d:88:aa:a1:a6
Sending on LPF/ath0/00:0d:88:aa:a1:a6
Sending on Socket/fallback
ifconfig ath0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: ctrl_interface=/var/run/wpa_supplicant
wpa_supplicant: terminating wpa_supplicant daemon
Stopped wpa_supplicant (pid 7694).
tanuki@pikunikubasukitu:~$ sudo ifup -v ath0
Configuring interface ath0=ath0 (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: ctrl_interface=/var/run/wpa_supplicant
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.ath0.pid -i ath0 -C /var/run/wpa_supplicant -D madwifi
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/ath0
wpa_supplicant: wpa-ap-scan : OK
wpa_supplicant: configuring new network block "0"wpa_supplicant: wpa-ssid : OK
wpa_supplicant: wpa-psk : OK
wpa_supplicant: wpa-pairwise : OK
wpa_supplicant: wpa-group : OK
wpa_supplicant: wpa-key-mgmt : OK
wpa_supplicant: wpa-proto : OK
wpa_supplicant: enabling network 0 : OK

dhclient3 -pf /var/run/dhclient.ath0.pid -lf /var/lib/dhcp3/dhclient.ath0.leases ath0
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/ath0/00:0d:88:aa:a1:a6
Sending on LPF/ath0/00:0d:88:aa:a1:a6
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 7
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
Synchronizing clock to ntp.ubuntu.com...
tanuki@pikunikubasukitu:~$

[venky80]

What confuses me is the fact that the scan says that your router is set to use "WEP-40" as cipher which is referring to WEP, not WPA. WPA supports both TKIP and AES, but certainly not WEP-40 which would defeat the purpose of WPA i.e. enhanced security.

Now... Would you mind changing the cipher from WEP-40 to TKIP on the router? Your client script mentions TKIP ("wpa-pairwise TKIP") so the easiest way from here is to tell your router to use TKIP (WPA) instead of WEP-40.

EDIT:
If you don't have access to the router because it isn't yours, let me know. Then we'll change your script although that's not my preferred solution as WEP-40 is not part of the WPA suite.

I Checked my router settings it is WPA-PSK TKIP
I am attaching the screenshot maybe you might see something I missed
Also I am on Gutsy (yes I know it is supposed to break and yes I know it is for developers and yes I am prepared for data loss) and knetworkmanager is broken so I am trying to connect using good old interfaces
Meanwhile my other laptop which runs feisty shows
iwlist scan as TKIP so it might be a Gutsy bug...well then I really dont know what to do unless u have some tricks
Thanks for all the help

[wieman01]

a. I don't know what MAC filtering is. I have a Speedtouch 580 router and don't know if it supports MAC filtering. Should it be on or off? By the way, before Ubuntu I used Windows XP, and had no problem connecting to the wireless network using WPA so I guess it has to do with the setup of Ubuntu rather then my router.
b. I am not using a firewall on my Ubuntu laptop as far as I know.

I don't think my router has any log files as it is not a computer.
Using the same network interface and turning off security on the router (while commenting the corresponding lines in "interfaces") can you connect to your network using DHCP? WPA handshake seems ok, but for some reason the router does not assign an IP via DHCP.

Please try the unsecured method once again, if that fails would you mind assigning a static IP for a minute? Just for the sake of testing.

[wieman01]

Hi,

Used this document after trying others, still no joy. This is one of the reason I can't get business users to switch to Linux but I'm still trying.

I have tried excluding the eth0 device in the interfaces to no avail. This will work with some tweaking using WEP, been there, done that.
Current status is card show connected briefly then disconnected, cycle and repeat.

This is a fresh install/patch.
Same to you, can you assign a static IP and try once again? Are you sure your wireless card and driver do support WPA? And do router settings match those of your PC?

Sorry for asking these simple questions, but we need to start somewhere. :-)

[wieman01]

I Checked my router settings it is WPA-PSK TKIP
I am attaching the screenshot maybe you might see something I missed
Also I am on Gutsy (yes I know it is supposed to break and yes I know it is for developers and yes I am prepared for data loss) and knetworkmanager is broken so I am trying to connect using good old interfaces
Meanwhile my other laptop which runs feisty shows
iwlist scan as TKIP so it might be a Gutsy bug...well then I really dont know what to do unless u have some tricks
Thanks for all the help
Could you please set WPA to "Enabled" and scan once again? Try various settings there until scanning shows something along these lines:
Cell 01 - Address: 00:13:10:41:A8:E5
ESSID:"<hidden>"
Protocol:IEEE 802.11bg
Mode:Master
Channel:6
Encryption key:on
Bit Rates:54 Mb/s
Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54
Quality=93/100 Signal level=-35 dBm
IE: IEEE 802.11i/WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 1996ms ago

Your router settings are incorrect as it expects WEP-40 rather than TKIP.

[VorDesigns]

Same to you, can you assign a static IP and try once again? Are you sure your wireless card and driver do support WPA? And do router settings match those of your PC?

Sorry for asking these simple questions, but we need to start somewhere. :-)

No problem, I won't treat you like I would an MS, CA, Infor, or Intuit grunt reading a script and thank you for the help.
--
Cllient Wireless NIC
================================================== ===========
DWL-G650
version B4
reported as compatible with madwifi
http://madwifi.org/wiki/Compatibility/D-Link-
D-Link asserts that this card supports
- 64 bit and 128 WEP
- 802.1x
- WPA Wi-Fi Protected Access
- WPA PSK (Pre-Shared Key)
http://www.dlink.com/products/resource.asp?pid=11&rid=34&sec=0
-

Access Point Wireless to wired host
================================================== ===========
Linksys WRT54GL
Firmware version v4.30.5, Apr. 27, 2006
Security Mode: WPA Personal
WPA Algoritims: TKIP
================================================== ===========
Set client to static: Fails connectivity.
Air Snare running on Windows client connected to AP showed
intermittent reports of wireless intruder. <edit> I unregistered the MAC address of the D-Link card so
that Air Snare would let me know. <edit>
Visual monitoring of the DWL-G650 card shows intermittent
connection to the AP, LED's flash in unison, of about two seconds and then returns
to unconnected state, LED's cycle.
================================================== ===========
<edit>
This system/card configuration worked great with WEP.
I am using an internal DHCP server not the Linksys WRT54GL and it is leasing IP addresses successfully
to two Windows systems running on the same WRT54GL router.<edit>

[venky80]

Could you please set WPA to "Enabled" and scan once again? Try various settings there until scanning shows something along these lines:

Your router settings are incorrect as it expects WEP-40 rather than TKIP.

well that is what is puzzling coz I have a laptop with feisty which connects to the same wireless router and the one I am trying to fix is running gutsy

the gutsy gibbon laptop iwlist scan shows for my wireless as

Address: 00:0C:E5:4E:88:2F
ESSID:"wastintime"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
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
Quality=98/100 Signal level=-26 dBm Noise level=-26 dBm
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
Extra: Last beacon: 256ms ago

but for the same wireless connection my feisty laptop shows this

Address: 00:0C:E5:4E:88:2F
ESSID:"wastintime"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
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
Quality:96 Signal level:0 Noise level:0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

[WhiteHorse]

Hi I tried this and about 40 other things to no avail. I tried the wpa_supplicant stuff(all versions), I tried the /etc/network/interfaces stuff(all versions), I downloaded beta drivers, recompiled modules, tried RAconfig2500 or whatever it's called, tried latest CVS drivers, rebooted about 20 times, reinstalled ubuntu, etc(oh yeah and the ndiswrapper). It's been 28 hours of work and now I've given up.

Here's what works:
I can connect with WEP(oh joy) through System->Amin->Network and I disable roaming and set my wep key in there. It works flawlessly.

iwconfig shows:
ra0 RT2500 Wireless ESSID:"myessid"
Mode:Managed Frequency=2.412 GHz Access Point: 00:14:BF:0F:CE:27
Bit Rate=54 Mb/s Tx-Power:0 dBm
RTS thr:off Fragment thr:off
Link Quality=63/100 Signal level=-65 dBm Noise level:-192 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

my dmesg output shows:
[ 37.794864] rt2500 1.1.0 BETA4 2006/06/18 http://rt2x00.serialmonkey.com
[ 37.912497] rt2500 EEPROM: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Channel
[ 37.912505] rt2500 EEPROM: 4 4 4 4 4 4 3 3 3 3 3 3 3 3 dBm Maximum
[ 51.609223] ra0: no IPv6 routers present

lspci shows:
02:09.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)

lsmod shows:
rt2500 202088 1

/etc/network/interfaces shows:
auto lo
iface lo inet loopback

iface ra0 inet dhcp
wireless-essid myessid
wireless-key myweakasswepkey

auto ra0

Here's what doesn't work:
WPA/WPA2 and nm-applet. When I try to use the nm-applet( for n00biez:the computer icon in the task bar) I can connect to a network only if it is broadcasting it's network ssid and has no wep(eg open). otherwise, if wep is enabled, it asks for the key and then just hangs and says "Waiting for network key". There is no option to select anything other than wep.

My Configuration:
Feisty(7.04)
amd64(MS-1029 aka megabook 635)
minipci Ralink rt2500

Summary:
I know the card supports it because I can use wpa on windows. The access point is a standard OpenWRT Linksys WRT54G. I read some bug reports and it appears this may be a known bug with network manager, something to do with wireless extensions that network manager uses aren't compatible with the extensions available on the rt2500 driver. I have read as many posts and how-to's as I could and I just wound up with a really screwed up system and no WPA.

To be honest, the 28 hours I lost on this could have been better spent on the other open source projects I contribute to and has(according to other posts) cost a lot of other people time wasted as well. Can't we just PUSH A GODDAM UPDATE THAT FIXES THIS CRAP???? I mean make 2 developers waste one day rather than 2000 users/developers/testers/potential devs waste 3 days each? Not to flame anybody but hopefully I can spark some response on the part of the Ubuntu team to get this fixed. Any suggestions at this point would be great, thanks. I have 8 wireless networks in proximity and I'm sure someone has sniffed my passwords and arp poisoned me already. I'll just keep changing my wep key every day and never send passwords in the clear on my wireless or my lan until something comes along.

](*,) :-x :cry:

[wieman01]

No problem, I won't treat you like I would an MS, CA, Infor, or Intuit grunt reading a script and thank you for the help.
--
Cllient Wireless NIC
================================================== ===========
DWL-G650
version B4
reported as compatible with madwifi
http://madwifi.org/wiki/Compatibility/D-Link-
D-Link asserts that this card supports
- 64 bit and 128 WEP
- 802.1x
- WPA Wi-Fi Protected Access
- WPA PSK (Pre-Shared Key)
http://www.dlink.com/products/resource.asp?pid=11&rid=34&sec=0
-

Access Point Wireless to wired host
================================================== ===========
Linksys WRT54GL
Firmware version v4.30.5, Apr. 27, 2006
Security Mode: WPA Personal
WPA Algoritims: TKIP
================================================== ===========
Set client to static: Fails connectivity.
Air Snare running on Windows client connected to AP showed
intermittent reports of wireless intruder. <edit> I unregistered the MAC address of the D-Link card so
that Air Snare would let me know. <edit>
Visual monitoring of the DWL-G650 card shows intermittent
connection to the AP, LED's flash in unison, of about two seconds and then returns
to unconnected state, LED's cycle.
================================================== ===========
<edit>
This system/card configuration worked great with WEP.
I am using an internal DHCP server not the Linksys WRT54GL and it is leasing IP addresses successfully
to two Windows systems running on the same WRT54GL router.<edit>
Looks ok to me. Would you mind trying static IP instead of DHCP?

Another idea would be (as mentioned by another user in earlier posts) to disable "roaming" using the networking applet.

[wieman01]

well that is what is puzzling coz I have a laptop with feisty which connects to the same wireless router and the one I am trying to fix is running gutsy

the gutsy gibbon laptop iwlist scan shows for my wireless as

Address: 00:0C:E5:4E:88:2F
ESSID:"wastintime"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
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
Quality=98/100 Signal level=-26 dBm Noise level=-26 dBm
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
Extra: Last beacon: 256ms ago

but for the same wireless connection my feisty laptop shows this

Address: 00:0C:E5:4E:88:2F
ESSID:"wastintime"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
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
Quality:96 Signal level:0 Noise level:0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
That is indeed odd. Perhaps something IS wrong with Gutsy at this stage... No idea how I can help you there.

[wieman01]

Hi I tried this and about 40 other things to no avail. I tried the wpa_supplicant stuff(all versions), I tried the /etc/network/interfaces stuff(all versions), I downloaded beta drivers, recompiled modules, tried RAconfig2500 or whatever it's called, tried latest CVS drivers, rebooted about 20 times, reinstalled ubuntu, etc(oh yeah and the ndiswrapper). It's been 28 hours of work and now I've given up.
RT2500 (Ralink) is a bit of a headache as Serialmonkey's driver does not quite work the way others do. As a consequence wpa-supplicant won't help you and you need to do some extra work. Check this out:

http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?p=21546&sid=c5e02ed97dde07681fb564639e9f50c5

I'll update my HOWTO and mention this issue like I used to in the past. Install "ndiswrapper" if you prefer to do it our way. That's all I can say... I have a RT25700 as well and I only got this working after deploying the Windows driver.

EDIT:
You find stuff here as well:

http://ubuntuforums.org/showthread.php?t=202834&page=30

[mksec]

Nå. I have a headache with this. I'm sue something really obvious is missing but i can't figure it out. I'm posting all my config info from the stumped part of your excellent tutorial. So close yet so far.

I can see my network. I have the card working. But can't seem to connect to it. Ideas most appreciated.

uname -a
Linux laptop 2.6.20-15-386 #2 Sun Apr 15 07:34:00 UTC 2007 i686 GNU/Linux

ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:08:02:D9:8E:E5
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

eth1 Link encap:Ethernet HWaddr 00:07:40:DC:28:08
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:21 overruns:0 frame:0
TX packets:35538 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:1564168 (1.4 MiB)
Interrupt:10 Base address:0x8000

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:110 errors:0 dropped:0 overruns:0 frame:0
TX packets:110 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9760 (9.5 KiB) TX bytes:9760 (9.5 KiB)

vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01
inet addr:172.16.210.1 Bcast:172.16.210.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

vmnet8 Link encap:Ethernet HWaddr 00:50:56:C0:00:08
inet addr:192.168.63.1 Bcast:192.168.63.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)


route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
172.16.210.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet1
192.168.63.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet8


iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11b/g ESSID:"MKSEC" Nickname:"MKSEC"
Mode:Managed Frequency=2.484 GHz Access Point: Invalid
Bit Rate=1 Mb/s Tx-Power=15 dBm
RTS thr:off Fragment thr:off
Link Quality=0/100 Signal level=-256 dBm Noise level=-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

vmnet1 no wireless extensions.

vmnet8 no wireless extensions.


[B]ifconfig
eth0 Link encap:Ethernet HWaddr 00:08:02:D9:8E:E5
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

eth1 Link encap:Ethernet HWaddr 00:07:40:DC:28:08
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:21 overruns:0 frame:0
TX packets:36034 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:1586984 (1.5 MiB)
Interrupt:10 Base address:0x8000

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:110 errors:0 dropped:0 overruns:0 frame:0
TX packets:110 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9760 (9.5 KiB) TX bytes:9760 (9.5 KiB)

vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01
inet addr:172.16.210.1 Bcast:172.16.210.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

vmnet8 Link encap:Ethernet HWaddr 00:50:56:C0:00:08
inet addr:192.168.63.1 Bcast:192.168.63.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

lsmod
Module Size Used by
nls_iso8859_1 4224 0
nls_cp437 5888 0
vfat 12800 0
fat 52380 1 vfat
ipv6 252512 8
binfmt_misc 11272 1
rfcomm 37660 0
l2cap 22276 5 rfcomm
bluetooth 51300 4 rfcomm,l2cap
vmnet 36388 13
vmmon 111244 0
ppdev 9220 0
radeon 123680 3
drm 79380 4 radeon
speedstep_centrino 8072 0
cpufreq_userspace 4116 0
cpufreq_stats 5508 0
cpufreq_powersave 1792 0
cpufreq_ondemand 7676 1
freq_table 4740 3 speedstep_centrino,cpufreq_stats,cpufreq_ondemand
cpufreq_conservative 6560 0
tc1100_wmi 7172 0
pcc_acpi 12160 0
dev_acpi 11140 0
sony_acpi 5388 0
video 15492 0
sbs 14752 0
i2c_ec 4992 1 sbs
i2c_core 21776 1 i2c_ec
dock 9216 0
button 7696 0
battery 9860 0
container 4352 0
ac 5124 0
asus_acpi 16412 0
backlight 6016 1 asus_acpi
fuse 44436 1
lp 11332 0
bcm43xx 123924 0
joydev 9920 0
snd_intel8x0 32796 1
snd_ac97_codec 97184 1 snd_intel8x0
ac97_bus 2304 1 snd_ac97_codec
snd_pcm_oss 43264 0
snd_mixer_oss 16512 1 snd_pcm_oss
snd_pcm 76680 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
ieee80211softmac 30720 1 bcm43xx
ieee80211 33608 2 bcm43xx,ieee80211softmac
ieee80211_crypt 6144 1 ieee80211
snd_seq_dummy 3844 0
snd_seq_oss 31616 0
irtty_sir 8448 0
sir_dev 15748 1 irtty_sir
pcmcia 38316 0
snd_seq_midi 8576 0
snd_rawmidi 24448 1 snd_seq_midi
snd_seq_midi_event 7424 2 snd_seq_oss,snd_seq_midi
snd_seq 49648 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
snd_timer 22276 2 snd_pcm,snd_seq
snd_seq_device 8204 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
irda 191036 2 irtty_sir,sir_dev
snd 51716 12 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_ti mer,snd_seq_device
rtc 13104 0
pcspkr 3072 0
parport_pc 34980 1
parport 35272 3 ppdev,lp,parport_pc
crc_ccitt 2176 1 irda
soundcore 7520 1 snd
psmouse 37640 0
serio_raw 6916 0
yenta_socket 26636 3
rsrc_nonstatic 13184 1 yenta_socket
pcmcia_core 39696 3 pcmcia,yenta_socket,rsrc_nonstatic
snd_page_alloc 9992 2 snd_intel8x0,snd_pcm
intel_agp 24220 1
agpgart 34096 2 drm,intel_agp
iTCO_wdt 10656 0
iTCO_vendor_support 3972 1 iTCO_wdt
af_packet 20872 6
shpchp 33300 0
pci_hotplug 31160 1 shpchp
evdev 10112 4
tsdev 7872 0
ext3 129288 1
jbd 53032 1 ext3
mbcache 8196 1 ext3
sg 35484 0
sr_mod 15908 0
cdrom 36512 1 sr_mod
sd_mod 22292 4
usb_storage 70976 1
libusual 17040 1 usb_storage
ata_piix 14596 4
ata_generic 8196 0
libata 125208 2 ata_piix,ata_generic
scsi_mod 141580 5 sg,sr_mod,sd_mod,usb_storage,libata
floppy 58020 0
tg3 107396 0
generic 4228 0 [permanent]
ehci_hcd 32780 0
uhci_hcd 23952 0
usbcore 131480 5 usb_storage,libusual,ehci_hcd,uhci_hcd
raid10 24704 0
raid456 123408 0
xor 15752 1 raid456
raid1 23936 0
raid0 8704 0
multipath 8832 0
linear 6400 0
md_mod 77076 7 raid10,raid456,raid1,raid0,multipath,linear
thermal 13832 0
processor 22956 1 thermal
fan 4740 0
dm_mod 57164 5
fbcon 41760 0
tileblit 2688 1 fbcon
font 8320 1 fbcon
bitblit 6016 1 fbcon
softcursor 2304 1 bitblit
vesafb 8196 0
capability 5000 0
commoncap 7296 1 capability

iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:A0:C5:63:80:1E
ESSID:"neighbourtotheleftofme"
Protocol:IEEE 802.11b
Mode:Master
Channel:6
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Quality=79/100 Signal level=-71 dBm Noise level=-71 dBm
Extra: Last beacon: 3260ms ago
Cell 02 - Address: 00:13:49:CE:88:2D
ESSID:"jokertotheright"
Protocol:IEEE 802.11bg
Mode:Master
Channel:6
Encryption key:off
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; 22 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Quality=72/100 Signal level=-77 dBm Noise level=-71 dBm
Extra: Last beacon: 3256ms ago
Cell 03 - Address: 00:14:85:0D:C7:76
ESSID:"MKSEC"
Protocol:IEEE 802.11bg
Mode:Master
Channel:1
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 9 Mb/s; 11 Mb/s
6 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=88/100 Signal level=-60 dBm Noise level=-71 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
Preauthentication Supported
Extra: Last beacon: 3336ms ago

vmnet1 Interface doesn't support scanning.

vmnet8 Interface doesn't support scanning.


cat /etc/network/interfaces

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.


# The primary network interface


auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid MKSEC
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk HEXKEY as stated in tutorial

sudo cat /etc/modprobe.d/ndiswrapper
alias wlan0 ndiswrapper

cat /etc/resolv.conf
# generated by NetworkManager, do not edit!

search opasia.dk


nameserver 192.168.2.1

[wieman01]

Nå. I have a headache with this. I'm sue something really obvious is missing but i can't figure it out. I'm posting all my config info from the stumped part of your excellent tutorial. So close yet so far.
I have made slight changes as I don't know if your card supports WPA2. Please try this one first and let me know if this works for you:
auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid MKSEC
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise CCMP TKIP
wpa-group CCMP TKIP
wpa-key-mgmt WPA-PSK
wpa-psk HEXKEY as stated in tutorial
Then restart the network:
sudo /etc/init.d/networking restart
Please post the results.

And by the way... please state what card you have got. IPW2200 by chance?

[mksec]

whatcha know!!! It worked. Thanks alot. I knew it was something obvious.

Card is a Buffalo WLI-CB-G54Awith a broadcom chipset. I installed it using bcm43xx-fwcutter.


Thanks again.

[venky80]

That is indeed odd. Perhaps something IS wrong with Gutsy at this stage... No idea how I can help you there.

How can I report a bug. I mean I dont even know how to point out this problem

[wieman01]

How can I report a bug. I mean I dont even know how to point out this problem
You can file bugs here (https://launchpad.net/ubuntu). Let me know if you need a hand.

[VorDesigns]

Hi,

I gave up on using the interfaces and went to trying nm-applet; post the headscratching and commenting out almost everything in the interfaces file as directed, I was able to get the nm-applet to function.
I still couldn't connect.
So, I decided that I must have introduced an operator error into the process based on Windows laxity; I was correct. While I entered the psk in lower case on the Windows systems, the key itself is displayed in upper case on the router. I reentered the key substituting upper-case for all the alpha key characters and was prompted for a key-ring password.
I stopped to thank you for your assistance using my now functional connection prior to reactivating the eth0 device.
Again, thank you for your help.
I am debating whether to go back and put everything into the interfaces file but, having a functional nm-applet gives my the ability to roam a little more simply.

[venky80]

You can file bugs here (https://launchpad.net/ubuntu). Let me know if you need a hand.
yes definitely so that i can make an impact with the submission
Thanks

[Skolem45]

Thank you!!! It worked. After two days of bashing my head against the table, I finally have working WPA. Its just WPA1, that's all that my router will support, but still. My card is Airlink101 AWLH3026T; I'm using ndiswrapper.

:)

[Zoufiax]

Using the same network interface and turning off security on the router (while commenting the corresponding lines in "interfaces") can you connect to your network using DHCP? WPA handshake seems ok, but for some reason the router does not assign an IP via DHCP.

Please try the unsecured method once again, if that fails would you mind assigning a static IP for a minute? Just for the sake of testing.

What do you mean with turning security off on the router? Setting it to WEP or no encryption / protection? When I set it to WEP I can connect to my router. Also when I had Windows XP installed on my laptop, I could connect with WPA security.

Also I do want to assign a static IP to my laptop, but please tell me how to do that. And with WPA or WEP security or something else? I hope you don't mind my ignorance...

[wieman01]

What do you mean with turning security off on the router? Setting it to WEP or no encryption / protection? When I set it to WEP I can connect to my router. Also when I had Windows XP installed on my laptop, I could connect with WPA security.

Also I do want to assign a static IP to my laptop, but please tell me how to do that. And with WPA or WEP security or something else? I hope you don't mind my ignorance...
Let's configure your PC to use static IP then:
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet static
address 192.168.1.xxx
gateway 192.168.1.xxx
dns-nameservers 192.168.1.xxx
netmask 255.255.255.0
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key>
Please replace the blue bits with your networks IP range and desired client IP. If you don't know what I am referring to, please post your router's IP address. I will give you a hand.

Please use upper case for the the hex key (I assume you have generated the key the way I have suggested in my tutorial). Then restart the network:
sudo /etc/init.d/networking restart
Post the contents of "interfaces", etc. after that.

[waylow]

hey thanks for the helpful thread

I have managed to get my wireless internet working - the only thing that didn't work was trying to get it automated

I created the sh file and followed the instructions but it gave a DCHP -sleeping message

I then had to delete the .sh file and sybolic link (whatever that is) to get it able to work again


what did I do worng when I made the .sh file?


thanks

[wieman01]

hey thanks for the helpful thread

I have managed to get my wireless internet working - the only thing that didn't work was trying to get it automated

I created the sh file and followed the instructions but it gave a DCHP -sleeping message

I then had to delete the .sh file and sybolic link (whatever that is) to get it able to work again


what did I do worng when I made the .sh file?


thanks
Not sure what you did in the first place. :-)

Seriously, static IP will resolve your problem with having to restart the network. Want to try that instead?

[waylow]

Not sure what you did in the first place. :-)

neither am I - going to try it again and see how it goes


Seriously, static IP will resolve your problem with having to restart the network. Want to try that instead?
I can't because it isn't my network - just moved into my brothers house and thats the way he wants it to stay

the network does seem to stop working and I have to restart it again

but sometimes that doesn't work and I need to reboot then restart

I'm assuming that has to do with the dhcp renewal
bound to 192.168.0.3 -- renewal in 41716 seconds

anything I can do (apart from convince my brother to change it to static)??

[wieman01]

neither am I - going to try it again and see how it goes


I can't because it isn't my network - just moved into my brothers house and thats the way he wants it to stay

the network does seem to stop working and I have to restart it again

but sometimes that doesn't work and I need to reboot then restart

I'm assuming that has to do with the dhcp renewal
bound to 192.168.0.3 -- renewal in 41716 seconds

anything I can do (apart from convince my brother to change it to static)??
Actually you could use a static IP configuration anytime you want. Just use the IP address that you were assigned before and use 192.168.0.3 as DNS and gateway. That's all you need to do. Then restart the network and there you go. :-) There won't be any sort of conflict with DHCP of course.

[waylow]

Actually you could use a static IP configuration anytime you want. Just use the IP address that you were assigned before and use 192.168.0.3 as DNS and gateway. That's all you need to do. Then restart the network and there you go. :-) There won't be any sort of conflict with DHCP of course.

GREAT!!:) I don't know exactly how to do that but you have given me enough to go on

thanks heaps :KS

-waylow
-over

[wieman01]

GREAT!!:) I don't know exactly how to do that but you have given me enough to go on

thanks heaps :KS

-waylow
-over
Just follow the steps on page 1 of this thread. That should do. If you still have problems, just post here, buddy. :-)

[waylow]

Yep still seem to be having trouble trying to change it to static
I am confused a bit about making it static

Actually you could use a static IP configuration anytime you want. Just use the IP address that you were assigned before and use 192.168.0.3 as DNS and gateway. That's all you need to do. Then restart the network and there you go. :-) There won't be any sort of conflict with DHCP of course.

I am confused as to what address I should use

here is my /etc/network/interfaces file


auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
#iface wlan0 inet dchp

#not sure what addresses are correct and which are wrong
#I comment out the next bit and switch the comment
#on the dchp line above to the static one and
#the internet sometimes connects - for about 3 - 4 minutes

address 192.168.0.1
gateway 192.168.0.3
dns-nameservers 192.168.0.3
netmask 255.255.255.0

wpa-driver wext
wpa-ssid Megadeth
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk (really long hex PSK Key)


am I mental in the brain?

[wieman01]

Yep still seem to be having trouble trying to change it to static
I am confused a bit about making it static



I am confused as to what address I should use

here is my /etc/network/interfaces file


auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
#iface wlan0 inet dchp

#not sure what addresses are correct and which are wrong
#I comment out the next bit and switch the comment
#on the dchp line above to the static one and
#the internet sometimes connects - for about 3 - 4 minutes

address 192.168.0.1
gateway 192.168.0.3
dns-nameservers 192.168.0.3
netmask 255.255.255.0

wpa-driver wext
wpa-ssid Megadeth
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk (really long hex PSK Key)


am I mental in the brain?
You are not. :-) Your configuration looks actually quite correct. The only thing that you need to find out about is what "address" you should actually use:
address 192.168.0.xxx
The problem is that the router reserves certain IP ranges for its clients. So you must pick one that is within that range (e.g. address 192.168.0.4 - address 192.168.0.10).

What IP address were you assigned while you used DHCP? You could use that one. Or ask you brother what IP range he is using, so that you could pick one. Just make sure you pick an address that does not conflict with one that the router assign's to your bother's PC, if you know what I mean. IPs are unique.

[waylow]

just a quick update

I have changed my interfaces file back to:

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dchp


then I restarted the network and it seemed to work fine - I tested it for about 30mins or so and the internet was working the whole time (that's the longest it has managed to work)

then I rebooted and it doesn't want to work - even after trying to restart the network several times
-it says it's sleeping

WAKE UP DAMMIT

any ideas??

[waylow]

You are not. :-) Your configuration looks actually quite correct. The only thing that you need to find out about is what "address" you should actually use:

The problem is that the router reserves certain IP ranges for its clients. So you must pick one that is within that range (e.g. address 192.168.0.4 - address 192.168.0.10).

What IP address were you assigned while you used DHCP? You could use that one. Or ask you brother what IP range he is using, so that you could pick one. Just make sure you pick an address that does not conflict with one that the router assign's to your bother's PC, if you know what I mean. IPs are unique.

OK so I have uncommented the bits that I need to (changing back to static)

the IP that I have managed to connect on is alway 192.168.0.3

Is this the one I use for the
address
gateway
or dns

Thanks for your help too - by the way

it has been greatly appreciated

waylow

[waylow]

YAY! I seem to have figured it out

tried it a few different combo's and got it to work with a static address

The only thing now is to get it to happen on boot
but I will sort that out tommorrow

Thanks A LOT for your help
(hopefully I won't need it again for this wireless problem - touch wood)

I have only been using Linux for less than a week now but I feel like I have had a crash course

TA
Have a Good Week end:):)

-waylow

[wieman01]

YAY! I seem to have figured it out

tried it a few different combo's and got it to work with a static address

The only thing now is to get it to happen on boot
but I will sort that out tommorrow

Thanks A LOT for your help
(hopefully I won't need it again for this wireless problem - touch wood)

I have only been using Linux for less than a week now but I feel like I have had a crash course

TA
Have a Good Week end:):)

-waylow
Have a nice weekend too. :-)

As for your boot problem, see post #2 of this thread. I am sure you will be able to fix it. If not, you know where you find me.

[waylow]

I am having trouble with the instructions for post #2

can't get it to restart the network at boot

I have created the .sh script - changed the permission - then created the symbolic link

you mention that you might need to change the number of the boot sequence from S40

well on my system there was S40networking (I'm not sure if this is the thing that we are trying to restart so I tried 2 things)
I have tried changing this the S40wireless-network file to S41 and S39 - both end up with me still having to restart the network manually

drawing a blank now:confused:

[wieman01]

I am having trouble with the instructions for post #2

can't get it to restart the network at boot

I have created the .sh script - changed the permission - then created the symbolic link

you mention that you might need to change the number of the boot sequence from S40

well on my system there was S40networking (I'm not sure if this is the thing that we are trying to restart so I tried 2 things)
I have tried changing this the S40wireless-network file to S41 and S39 - both end up with me still having to restart the network manually

drawing a blank now:confused:
What happens when you execute the script?
sudo /etc/init.d/wireless-network.sh
Does that restart the network? And what about:
sudo /etc/rcS.d/S40wireless-network

[waylow]

What happens when you execute the script?

Does that restart the network? And what about:

yep they both restart the network


aahh crap now I'm having trouble connecting at all
-I haven't changed any setting to when it worked for over 30mins

[waylow]

OK managed to get it back up

but I had to change the static address in the interfaces file from 192.168.0.3 to 192.168.0.4

does this mean that I haven't got the interfaces file setup correctly?

(trying to re-do the auto restart at boot again)

[wieman01]

OK managed to get it back up

but I had to change the static address in the interfaces file from 192.168.0.3 to 192.168.0.4

does this mean that I haven't got the interfaces file setup correctly?

(trying to re-do the auto restart at boot again)
192.168.0.3 is your router? Perhaps it is best if you posted the contents of your "interfaces" file once again for reference.

EDIT:
Also post the results of this one please:
route

[waylow]

my router is 192.168.0.1 - the .3 was the only IP I manged to get connected on before

anyway here is my interfaces - (typed by hand - don't know how to share drives with windows (yet) and I am getting my removable media fixed ie. my iRiver is getting fixed so I can't just pop it into a text file and transfer it across)

interfaces

auto lo
iface lo inet loopback

auto wlan0
iface wlan inet static

address 192.168.0.3
gateway 192.168.0.1
dns-nameserver192.168.0.3
netmask 255.255.255.0

wpa-driver wext
wpa-ssid Megadeth
wpa-ap scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk MY PSK


route

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 wlan0
link-local * 255.255.0.0 U 1000 0 0 wlan0
default 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0



does it look wrong (except for the formatting - sorry :( stupid broken iRiver)

[wieman01]

my router is 192.168.0.1 - the .3 was the only IP I manged to get connected on before

anyway here is my interfaces - (typed by hand - don't know how to share drives with windows (yet) and I am getting my removable media fixed ie. my iRiver is getting fixed so I can't just pop it into a text file and transfer it across)

interfaces

auto lo
iface lo inet loopback

auto wlan0
iface wlan inet static

address 192.168.0.3
gateway 192.168.0.1
dns-nameserver192.168.0.3
netmask 255.255.255.0

wpa-driver wext
wpa-ssid Megadeth
wpa-ap scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk MY PSK

"dns-nameserver" and "gateway" should both point to your router, hence the IP address should be 192.168.0.3:
auto lo
iface lo inet loopback

auto wlan0
iface wlan inet static

address 192.168.0.3
gateway 192.168.0.1
dns-nameserver 192.168.0.1
netmask 255.255.255.0

wpa-driver wext
wpa-ssid Megadeth
wpa-ap scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk MY PSK
But this might be a typo. Otherwise you would not have been able to browse the web.

Your scripts look actually fine, your network should restart automatically while your system is booting. So it surprises me you need to do another manual restart after logging on to your system. I am running out of ideas here to be honest.

Another thing is that you need to have a chat with your system admin... The reason is that your manually assigned IP address may conflict with other PC clients on your network. DHCP assigns IP address within a certain range e.g. 192.168.0.2 to 192.168.0.10 and the more clients there are, the more likely it is that one client is assigned the same address as you. To avoid this from happening you should pick an IP address outside that range reserved for DHCP.

[waylow]

yeah I found out why I was getting kicked off
the other flatmate also uses the network (which I didn't know) - so when he turns on his laptop - he was getting assigned the .3 address and kicking me off

I have changed it to .200 so I shouldn't have any problems now (I hope - well not so far anyway)

no that wasn't a typo

I know that the DNS and gateway should be the same (192.168.0.1 - but it hasn't been working)

it seems to work when it's the same my my computers IP address - I am confused too

I wiil try and change it again and see how I go


with the startup script - I give up
I have come to the sad realization that I will probably have to restart it manually every time i boot

It doesn't really bother me that much - at least I will be reminded daily of the help you have given me wieman01 :)

Thanks a bunch -
(I know where to find you if I have spoken too soon)

waylow
over

[wieman01]

yeah I found out why I was getting kicked off
the other flatmate also uses the network (which I didn't know) - so when he turns on his laptop - he was getting assigned the .3 address and kicking me off

I have changed it to .200 so I shouldn't have any problems now (I hope - well not so far anyway)

no that wasn't a typo

I know that the DNS and gateway should be the same (192.168.0.1 - but it hasn't been working)

it seems to work when it's the same my my computers IP address - I am confused too

I wiil try and change it again and see how I go


with the startup script - I give up
I have come to the sad realization that I will probably have to restart it manually every time i boot

It doesn't really bother me that much - at least I will be reminded daily of the help you have given me wieman01 :)

Thanks a bunch -
(I know where to find you if I have spoken too soon)

waylow
over
No problem then. Nice talking to you anyway.

One last word concerning the DNS setting... You PC should actually synchronize your interfaces file and this one:
sudo gedit /etc/resolv.conf
Occasinally the system would not update the file for a reason unknown to me, therefore it's worth taking a look at it. It should contain your router's / gateway's IP address i.e. 192.168.0.1. I suspect it does not at the moment.

Good luck, mate!

[waylow]

yeah I managed to fix that one on my lonesome :)


No problem then. Nice talking to you anyway.

ditto!!

I will have another go at the script when I learn more about Linux - been about 4 days so far (proper dual boot - virtual machine about 2 weeks) and my head is about to explode

[gatoruss]

I recently upgrade to ubuntu 7.4. Prior to upgrade, I had wi running fine...and as best I can recall, I got it to run following instructions at the top of this tutorial for wpa1/broadcast.

After installation of 7.4, I no loinger have connection. I tried reconfiguring with the tutorial, but it is not working. I have tried both wlan0 and ra0. IN the case of the former, when I run restart I am told that there is no such device. When I used ra0 I am told it is "sleeping."

Here are some of the settings/results I am getting.

I would greatly appreciate any help.

My iface:

iface auto lo
iface lo inet loopback

auto ra0
iface ra0 inet dhcp
wpa-driver wext
wpa-ssid linksys_SES_4032
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk ***********************

Restart:

* Reconfiguring network interfaces...
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - 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/ra0/00:18:f8:28:ee:bf
Sending on LPF/ra0/00:18:f8:28:ee:bf
Sending on Socket/fallback
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

ifconfig:

eth0 Link encap:Ethernet HWaddr 00:01:80:52:62:F9
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:0x6000
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:122 errors:0 dropped:0 overruns:0 frame:0
TX packets:122 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:11350 (11.0 KiB) TX bytes:11350 (11.0 KiB)

ra0 Link encap:Ethernet HWaddr 00:18:F8:28:EE:BF
inet6 addr: fe80::218:f8ff:fe28:eebf/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:2586 errors:0 dropped:0 overruns:0 frame:0
TX packets:11159 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:297100 (290.1 KiB) TX bytes:0 (0.0 b)
Interrupt:19

ra0:avahi Link encap:Ethernet HWaddr 00:18:F8:28:EE:BF
inet addr:169.254.9.244 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:19

iwlist scan:

lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
ra0 Failed to read scan data : Device or resource busy

Someone suggested that since I had a linksys I should try item #6 under "Common stumbling blocks":

6. RTxxx (Ralink) drivers do not support this approach. Either install "ndiswrapper" replacing Serialmonkey's driver or visit this site.

I followed the link and wrote the script, but have no idea what to do with it! :-)

[wieman01]

I followed the link and wrote the script, but have no idea what to do with it! :-)
Ralink is a different story as you have found out. Do this:
sudo gedit /etc/network/interfaces
And probably paste this:
auto ra0
iface ra0 inet dhcp
pre-up iwconfig ra0 essid Blackhole
pre-up iwpriv ra0 set NetworkType=Infra
pre-up iwpriv ra0 set AuthMode=WPA2PSK
pre-up iwpriv ra0 set EncrypType=AES
pre-up iwpriv ra0 set WPAPSK="your_password"
Then restart the network and see how it goes:
sudo /etc/init.d/networking restart
If you can't restart the network successfully reboot the PC please.

I have not tried this myself though...

EDIT:
You'd probably would want to install "ndiswrapper" and use the latest Windows driver for your card. Personally I find the RTxxxx drivers quite troublesome.

[gatoruss]

Alas....that did not work. When I run restart (even after reboot), no wifi.

When I restart I get this:

* Reconfiguring network interfaces...
RTNETLINK answers: No such process
There is already a pid file /var/run/dhclient.ra0.pid with pid 5610
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/ra0/00:18:f8:28:ee:bf
Sending on LPF/ra0/00:18:f8:28:ee:bf
Sending on Socket/fallback
Interface doesn't accept private ioctl...
set (8BE2): Invalid argument
Failed to bring up ra0.

Strange thing is that before upgrade it worked fine.

You'd probably would want to install "ndiswrapper" and use the latest Windows driver for your card. Personally I find the RTxxxx drivers quite troublesome.

How do I do this? I have no internet connection for my ubuntu box. I suppose I have download ndiswrapper from my xp machine (PC I am using for this post) and copy it over on a thumb drive? I have never loaded anything on my ubuntu machine without using syanaptic?

[wieman01]

How do I do this? I have no internet connection for my ubuntu box. I suppose I have download ndiswrapper from my xp machine (PC I am using for this post) and copy it over on a thumb drive? I have never loaded anything on my ubuntu machine without using syanaptic?
You could use Synaptic to install "ndiswrapper" but you need to tell Synaptic that it is supposed to install from CD, no through the Internet. I am not in front of my own computer right now, so I can't tell you exactly how to do it, but it is possible.

[myidbe]

Hi forum: I'm having a similar problem. Switching to Ubuntu 7.04 has been nice, but I'm still having trouble getting wireless working.

After following the instructions at the beginning of this thread, I still couldn't connect (to the WPA1 network here). I used eth1 instead of wlan0. I use a Sony PCG-V505EX Laptop with an Intel Pro-Wireless 2100 integrated wireless LAN. Here are the outputs from my machine (network cable was unplugged and network-manager was switched off during all this - also after I went through the procedure, my cable internet no longer functioned..):

uname -a

malcolm@malcolm-laptop:~$ uname -a
Linux malcolm-laptop 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux


ifconfig -a

malcolm@malcolm-laptop:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 08:00:46:CD:1A:01
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:268898 errors:0 dropped:0 overruns:0 frame:0
TX packets:200518 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:263632148 (251.4 MiB) TX bytes:25486778 (24.3 MiB)

eth1 Link encap:Ethernet HWaddr 00:0E:35:03:2B:01
inet6 addr: fe80::20e:35ff:fe03:2b01/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:4 errors:0 dropped:68 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:1000
RX bytes:295156 (288.2 KiB) TX bytes:496768 (485.1 KiB)
Interrupt:9 Base address:0x6000 Memory:d0201000-d0201fff

eth0:avah Link encap:Ethernet HWaddr 08:00:46:CD:1A:01
inet addr:169.254.3.97 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1

eth1:avah Link encap:Ethernet HWaddr 00:0E:35:03:2B:01
inet addr:169.254.1.51 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:9 Base address:0x6000 Memory:d0201000-d0201fff

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:18733 errors:0 dropped:0 overruns:0 frame:0
TX packets:18733 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1087245 (1.0 MiB) TX bytes:1087245 (1.0 MiB)



route -n

malcolm@malcolm-laptop:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 eth0


iwconfig

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

eth0 no wireless extensions.

eth1 IEEE 802.11g ESSID:"HieglW"
Mode:Managed Frequency:2.412 GHz Access Point: 00:15:0C:D3:EE:C5
Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=67/100 Signal level=-56 dBm Noise level=-87 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:68 Missed beacon:0


ifconfig

malcolm@malcolm-laptop:~$ ifconfigeth0 Link encap:Ethernet HWaddr 08:00:46:CD:1A:01
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:268898 errors:0 dropped:0 overruns:0 frame:0
TX packets:200518 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:263632148 (251.4 MiB) TX bytes:25486778 (24.3 MiB)

eth1 Link encap:Ethernet HWaddr 00:0E:35:03:2B:01
inet6 addr: fe80::20e:35ff:fe03:2b01/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:68 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:1000
RX bytes:310637 (303.3 KiB) TX bytes:524762 (512.4 KiB)
Interrupt:9 Base address:0x6000 Memory:d0201000-d0201fff

eth0:avah Link encap:Ethernet HWaddr 08:00:46:CD:1A:01
inet addr:169.254.3.97 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1

eth1:avah Link encap:Ethernet HWaddr 00:0E:35:03:2B:01
inet addr:169.254.1.51 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:9 Base address:0x6000 Memory:d0201000-d0201fff

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:18756 errors:0 dropped:0 overruns:0 frame:0
TX packets:18756 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1089284 (1.0 MiB) TX bytes:1089284 (1.0 MiB)


lsmod

malcolm@malcolm-laptop:~$ lsmodModule Size Used by
nls_iso8859_1 5120 0
nls_cp437 6784 0
vfat 14208 0
fat 53916 1 vfat
binfmt_misc 12680 1
rfcomm 40856 0
l2cap 25728 5 rfcomm
bluetooth 55908 4 rfcomm,l2cap
sonypi 23196 0
ppdev 10116 0
radeon 124576 2
drm 81044 3 radeon
speedstep_centrino 9920 0
cpufreq_conservative 8200 0
cpufreq_stats 7360 0
cpufreq_ondemand 9228 1
cpufreq_powersave 2688 0
freq_table 5792 3 speedstep_centrino,cpufreq_stats,cpufreq_ondemand
cpufreq_userspace 5408 0
sony_acpi 6284 0
dev_acpi 12292 0
tc1100_wmi 8068 0
pcc_acpi 13184 0
button 8720 0
container 5248 0
ac 6020 0
video 16388 0
battery 10756 0
asus_acpi 17308 0
backlight 7040 1 asus_acpi
dock 10268 0
sbs 15652 0
i2c_ec 5888 1 sbs
i2c_core 22784 1 i2c_ec
ipv6 268704 8
sbp2 23812 0
parport_pc 36388 0
lp 12452 0
parport 36936 3 ppdev,parport_pc,lp
fuse 46612 0
pcmcia 39212 0
joydev 10816 0
snd_intel8x0 34204 1
snd_ac97_codec 98336 1 snd_intel8x0
ac97_bus 3200 1 snd_ac97_codec
snd_pcm_oss 44544 0
snd_mixer_oss 17408 1 snd_pcm_oss
snd_pcm 79876 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
yenta_socket 27532 1
rsrc_nonstatic 14080 1 yenta_socket
ipw2200 148040 0
snd_seq_dummy 4740 0
snd_seq_oss 32896 0
serio_raw 7940 0
snd_seq_midi 9600 0
snd_rawmidi 25472 1 snd_seq_midi
snd_seq_midi_event 8448 2 snd_seq_oss,snd_seq_midi
ieee80211 34760 1 ipw2200
ieee80211_crypt 7040 1 ieee80211
pcmcia_core 40852 3 pcmcia,yenta_socket,rsrc_nonstatic
snd_seq 52592 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
snd_timer 23684 2 snd_pcm,snd_seq
snd_seq_device 9100 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
psmouse 38920 0
snd 54020 12 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_ti mer,snd_seq_device
soundcore 8672 1 snd
snd_page_alloc 10888 2 snd_intel8x0,snd_pcm
shpchp 34324 0
pci_hotplug 32576 1 shpchp
intel_agp 25116 1
agpgart 35400 2 drm,intel_agp
iTCO_wdt 11812 0
iTCO_vendor_support 4868 1 iTCO_wdt
af_packet 23816 18
evdev 11008 3
tsdev 8768 0
ext3 133128 1
jbd 59816 1 ext3
mbcache 9604 1 ext3
sg 36252 0
sr_mod 17060 0
cdrom 37664 1 sr_mod
sd_mod 23428 3
usb_storage 72256 0
libusual 17936 1 usb_storage
ata_piix 15492 2
ata_generic 9092 0
libata 125720 2 ata_piix,ata_generic
scsi_mod 142348 6 sbp2,sg,sr_mod,sd_mod,usb_storage,libata
e100 36232 0
mii 6528 1 e100
ohci1394 36528 0
ieee1394 299448 2 sbp2,ohci1394
generic 5124 0 [permanent]
ehci_hcd 34188 0
uhci_hcd 25360 0
usbcore 134280 5 usb_storage,libusual,ehci_hcd,uhci_hcd
thermal 14856 0
processor 31048 1 thermal
fan 5636 0
fbcon 42656 0
tileblit 3584 1 fbcon
font 9216 1 fbcon
bitblit 6912 1 fbcon
softcursor 3200 1 bitblit
vesafb 9220 0
capability 5896 0
commoncap 8192 1 capability


iwlist scan

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

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:15:0C:D3:EE:C5
ESSID:"HieglW"
Protocol:IEEE 802.11bg
Mode:Master
Channel:1
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
Quality=95/100 Signal level=-30 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 2696ms ago
Cell 02 - Address: 00:03:C9:8B:4C:52
ESSID:"WLAN"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
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
Quality=33/100 Signal level=-80 dBm
Extra: Last beacon: 2536ms ago


cat /etc/network/interfaces

malcolm@malcolm-laptop:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid XXXXXX
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk LotsOfNumbersAndLettersHere0123456789

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp


cat /etc/modprobe.d/ndiswrapper

malcolm@malcolm-laptop:~$ cat /etc/modprobe.d/ndiswrapper
cat: /etc/modprobe.d/ndiswrapper: No such file or directory


cat /etc/resolv.conf

malcolm@malcolm-laptop:~$ cat /etc/resolv.conf
# generated by NetworkManager, do not edit!



nameserver 192.168.178.1




sudo /etc/init.d/networking restart

malcolm@malcolm-laptop:~$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces... RTNETLINK answers: No such process
There is already a pid file /var/run/dhclient.eth0.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/eth0/08:00:46:cd:1a:01
Sending on LPF/eth0/08:00:46:cd:1a:01
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.178.1 port 67
There is already a pid file /var/run/dhclient.eth1.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/eth1/00:0e:35:03:2b:01
Sending on LPF/eth1/00:0e:35:03:2b:01
Sending on Socket/fallback
There is already a pid file /var/run/dhclient.eth0.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/eth0/08:00:46:cd:1a:01
Sending on LPF/eth0/08:00:46:cd:1a:01
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
There is already a pid file /var/run/dhclient.eth1.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/eth1/00:0e:35:03:2b:01
Sending on LPF/eth1/00:0e:35:03:2b:01
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 12
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
eth2: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.eth2.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/

SIOCSIFADDR: No such device
eth2: ERROR while getting interface flags: No such device
eth2: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up eth2.
ath0: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.ath0.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/

SIOCSIFADDR: No such device
ath0: ERROR while getting interface flags: No such device
ath0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up ath0.
wlan0: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.wlan0.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/

SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
wlan0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up wlan0.


This seems to have gotten pretty long...btw, this is my very first post in the Ubuntu forums....

Best,
Van

[wieman01]

This seems to have gotten pretty long...btw, this is my very first post in the Ubuntu forums....

Best,
Van
No problem. Feisty installs NetworkManager by default. Why don't you use it instead? Unless you uninstall it, this thread won't help you. And if you do not require static IP, stick with NetworkManager for the sake of convenience...

[gatoruss]

You could use Synaptic to install "ndiswrapper" but you need to tell Synaptic that it is supposed to install from CD, no through the Internet. I am not in front of my own computer right now, so I can't tell you exactly how to do it, but it is possible.

I got "ndiswrapper" installed, but cannot find the windows driver....

Followed directions at "ndiswrapper" (http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,installation/), and install seems successfule; but I hit a wall with trying to find the drivers. Per this site, I have tried a all the things it suggests...

On my XP box where a similar card is installed: i cannot find the .inf file.

This site has window drivers (http://www.ralinktech.com/ralink/Home/Support/Windows.html) that can be installed, but when you unpack it, it is a setup.exe file (no .sys or .inf files).

This site says it has linux drivers (http://www.ralinktech.com/ralink/Home/Support/Linux.html) but when you unpack it there are 3 bin files. Again, no .sys or .inf files.

This really should not be this hard....it is very frustrating.:(

[wieman01]

I got "ndiswrapper" installed, but cannot find the windows driver....

Followed directions at "ndiswrapper" (http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,installation/), and install seems successfule; but I hit a wall with trying to find the drivers. Per this site, I have tried a all the things it suggests...

On my XP box where a similar card is installed: i cannot find the .inf file.

This site has window drivers (http://www.ralinktech.com/ralink/Home/Support/Windows.html) that can be installed, but when you unpack it, it is a setup.exe file (no .sys or .inf files).

This site says it has linux drivers (http://www.ralinktech.com/ralink/Home/Support/Linux.html) but when you unpack it there are 3 bin files. Again, no .sys or .inf files.

This really should not be this hard....it is very frustrating.:(
The .exe file could be a ZIP archive. Try to open it with any ZIP tool that you have got. It is possible that it contains all the files you need.

[gatoruss]

The .exe file could be a ZIP archive. Try to open it with any ZIP tool that you have got. It is possible that it contains all the files you need.


When you unzip the windows file, it is a .exe fiel that is an install application. When you run it on XP, it allempts to install on the machine (which alraedy had functioning wifi). When you try to run it on Ubuntu, you get a message that there is no app that can run it.

I am about to the point of giving up, on this ubuntu experiment and going back to XP. I was really enjoying playing around on ubuntu, but w/out wifi there is not much point. And the search for wifi has become too consuming without results.

Very frustrated....:(

On the plus side, I do appreciate your help.

[wieman01]

When you unzip the windows file, it is a .exe fiel that is an install application. When you run it on XP, it allempts to install on the machine (which alraedy had functioning wifi). When you try to run it on Ubuntu, you get a message that there is no app that can run it.

I am about to the point of giving up, on this ubuntu experiment and going back to XP. I was really enjoying playing around on ubuntu, but w/out wifi there is not much point. And the search for wifi has become too consuming without results.

Very frustrated....:(

On the plus side, I do appreciate your help.
Try to unzip the executable (= install application) then. It should contain more files.

[gerdt]

Hello,
I've been looking, but I can't find the answer, so I thought this might be the correct place to place my question:

I have a (lspci):
05:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card (rev 01)

I use Feisty on my laptop (Dell Inspiron 1501)

Thanks to your HOWTO, I have wireless internet at my university, but...
Every some minutes, the connections goes down, and I have to restart the network. Most often it's less than 10 minutes, but my max has not been more than 30 minutes.
I was wondering what I could do about this?

Another thing which annoys me is that with my newly adapted /etc/network/interfaces, I can't use my NetworkManager (see image below). Therefore, each time I leave university and go home, I have to restore the original interfaces file in order to get my NetworkManager up and running properly, so that I can use my home-wlan-connection.

/etc/network/interfaces :
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid XXXXXXXXXX
wpa-ap-scan 1
wpa-eap TTLS
wpa-key-mgmt IEEE8021X
wpa-anonymous-identity YYYYYYYYYY
wpa-identity YYYYYYYYYY
wpa-password ZZZZZZZZZZ
wpa-phase2 auth=PAP


This is how my Network-Manager looks like when using the above interfaces-file. As you can see, it doesn't show anything concerning WLAN. Just to be clear, this is the image of my network-manager when I am at university using WLAN.

http://www.graas.org/ubuntu/network-manager.jpg

Conclusion:
I would like to fix:
1) stop the network from going down every few minutes.
2) use my network-manager whithout having the restore the "normal" interfaces every time I leave university.

Note: These two problems I have described, I only encounter when using the above interfaces, i.e. only when I want to use the WLAN at my university. When I restore the original interfaces file, I can use any other "simple" WLAN and i can use my network manager without any problems.

Original /etc/network/interfaces :
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp


Image of my Network-Manager when using the "simple" interfaces-file:
http://www.graas.org/ubuntu/network-manager2.jpg

I hope that some of you can help me out!
Thanx in advace,
Gerdt

[wieman01]

@gerdt:

1) Unless you have admin access to your university's network, I can't help you there, mate.
2) I would think that the latest version of NetworkManager supports TTLS? Unless that isn't possible, there is no way you can avoid it at this stage.

Question: Are you using DHCP both at home and on the campus? I have got something in mind...

EDIT:
If you are willing to help me test a few things, we could try to work it out together. What kind of network are you using back home? WPA, WEP, DHCP, etc.?

[gerdt]

@wieman:

At home I use a WLAN with:
DHCP & WPA Personal & TKIP & MAC address filter
But for that to work I don't adjust the interfaces file, it can be done graphically through Network Manager. I haven't tried Wifi-Radar yet, though I would prefer to try everything first with NetworkManager.

About my university problem:
Isn't there someway to detect that the network has gone down, so that it can automatically restart the network?

About the tests, yes, I am willing to help you. If it can resolve my (and/or other) problems, I would be glad to help you.

EDIT:
Question: Are you using DHCP both at home and on the campus? I have got something in mind...
Yes, at university I also use DHCP.

Thanx,
Gerdt

[wieman01]

@wieman:

At home I use a WLAN with:
DHCP & WPA Personal & TKIP & MAC address filter
But for that to work I don't adjust the interfaces file, it can be done graphically through Network Manager. I haven't tried Wifi-Radar yet, though I would prefer to try everything first with NetworkManager.

About my university problem:
Isn't there someway to detect that the network has gone down, so that it can automatically restart the network?

About the tests, yes, I am willing to help you. If it can resolve my (and/or other) problems, I would be glad to help you.

EDIT:

Yes, at university I also use DHCP.

Thanx,
Gerdt
What I was thinking of is putting both configurations in one single file which - I believe - should work. Would you mind give it a try? You have to configure your interfaces file once, that's it. Your PC would connect to either network as soon as one of them is in range.

Here we go...
auto eth1
iface eth1 inet dhcp
wpa-driver wext
# Home network
wpa-ssid <home_essid>
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key>
# University network
wpa-ssid XXXXXXXXXX
wpa-ap-scan 1
wpa-eap TTLS
wpa-key-mgmt IEEE8021X
wpa-anonymous-identity YYYYYYYYYY
wpa-identity YYYYYYYYYY
wpa-password ZZZZZZZZZZ
wpa-phase2 auth=PAP
Please take a look at the "key generation" section in the HOWTO for your home network. I also assume that ESSID broadcast is enabled ("wpa-ap-scan 1").

This should get you hooked up. No matter where you start your computer from now on, it should connect to the right network immediately. So that's the theory... can you test it for me please?

[gerdt]

@wieman:
Yes, at home the ESSID is also being broadcasted

This the interfaces-file I just tested (without succes :( ):
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
# Home network
wpa-ssid XXXXXXXXXX
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk ZZZZZZZZZZ
# University network
wpa-ssid XXXXXXXXXX
wpa-ap-scan 1
wpa-eap TTLS
wpa-key-mgmt IEEE8021X
wpa-anonymous-identity YYYYYYYYYY
wpa-identity YYYYYYYYYY
wpa-password ZZZZZZZZZZ
wpa-phase2 auth=PAP

This is the error when I try to restart the network after having modified the settings:
> sudo ./wireless-network.sh
* Reconfiguring network interfaces... /etc/network/interfaces:19: duplicate option
ifdown: couldn't read interfaces file "/etc/network/interfaces"
/etc/network/interfaces:19: duplicate option
ifup: couldn't read interfaces file "/etc/network/interfaces"


Just out of curiosity, what does the lo in interfaces means? Is it some kind of virtual network card?

Another question:
Is it possible to include a certain IF clause into /etc/network/interfaces?
Something like:
IF ("iwlist scan" includes HOME_SSID) THEN intefaces-configuration-home
ELSEIF ("iwlist scan" includes UNIVERSITY_SSID) THEN interfaces-configuration-university
ELSE standard-interfaces-configuration

[wieman01]

@wieman:
Yes, at home the ESSID is also being broadcasted

This the interfaces-file I just tested (without succes :( ):
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
# Home network
wpa-ssid XXXXXXXXXX
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk ZZZZZZZZZZ
# University network
wpa-ssid XXXXXXXXXX
wpa-ap-scan 1
wpa-eap TTLS
wpa-key-mgmt IEEE8021X
wpa-anonymous-identity YYYYYYYYYY
wpa-identity YYYYYYYYYY
wpa-password ZZZZZZZZZZ
wpa-phase2 auth=PAP

This is the error when I try to restart the network after having modified the settings:
> sudo ./wireless-network.sh
* Reconfiguring network interfaces... /etc/network/interfaces:19: duplicate option
ifdown: couldn't read interfaces file "/etc/network/interfaces"
/etc/network/interfaces:19: duplicate option
ifup: couldn't read interfaces file "/etc/network/interfaces"


Just out of curiosity, what does the lo in interfaces means? Is it some kind of virtual network card?

Another question:
Is it possible to include a certain IF clause into /etc/network/interfaces?
Something like:
IF ("iwlist scan" includes HOME_SSID) THEN intefaces-configuration-home
ELSEIF ("iwlist scan" includes UNIVERSITY_SSID) THEN interfaces-configuration-university
ELSE standard-interfaces-configuration
The first two lines refer to the loopback interface which enables your computer to recognize (e.g. ping) itself.

I don't think you can include any sort of scripting in the file.

What about this then:
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
# Home network
wpa-priority 1
wpa-ssid XXXXXXXXXX
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk ZZZZZZZZZZ
# University network
wpa-priority 2
wpa-ssid XXXXXXXXXX
wpa-ap-scan 1
wpa-eap TTLS
wpa-key-mgmt IEEE8021X
wpa-anonymous-identity YYYYYYYYYY
wpa-identity YYYYYYYYYY
wpa-password ZZZZZZZZZZ
wpa-phase2 auth=PAP


EDIT:
Added "wpa-priority"...

[gerdt]

I'm sorry, I get the same error:
ifdown: couldn't read interfaces file "/etc/network/interfaces"
/etc/network/interfaces:17: duplicate option
ifup: couldn't read interfaces file "/etc/network/interfaces"
[fail]

[yamad]

Hi,

I'm trying to get a Netgear WG121 USB adapter to connect up with a Netgear WGT624 router in Ubuntu 7.04 (Feisty). The router is set for WPA1 and broadcasts the SSID. The set-up works fine in Windows, but won't take in Ubuntu. If I turn off WPA protection it connects fine. I've set aside a static IP for the computer.

The most frustrating part is that it has actually connected up twice for about a minute each. Both times were coincident with installing NetworkManager, but stopped working soon after. I have uninstalled NetworkManager as per the instructions.

My /etc/network/interfaces file:

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
address 192.168.0.200
netmask 255.255.255.0
dns-nameserver 192.168.0.1
gateway 192.168.0.1
wpa-driver wext
wpa-ssid <SSID>
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <phrase_from_wpa_passphrase>


My /etc/wpa_supplicant.conf (I realize that this shouldn't matter):

network={
pairwise=TKIP
group=TKIP
ssid="<SSID>"
proto=WPA
key_mgmt=WPA-PSK
psk=<phrase_from_wpa_passphrase>
}


If there's any other file/log I should provide please let me know. Thanks for your help. I'm really really ready to get this working after two days trying!

[wieman01]

I'm sorry, I get the same error:
ifdown: couldn't read interfaces file "/etc/network/interfaces"
/etc/network/interfaces:17: duplicate option
ifup: couldn't read interfaces file "/etc/network/interfaces"
[fail]

Bad news then... Was worth it anyway.

[wieman01]

My /etc/network/interfaces file:

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
address 192.168.0.200
netmask 255.255.255.0
dns-nameserver 192.168.0.1
gateway 192.168.0.1
wpa-driver wext
wpa-ssid <SSID>
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <phrase_from_wpa_passphrase>

This looks actually quite neat. The results of a few more commands would be helpful indeed:
iwlist scan
route
iwconfig
sudo ifdown -v wlan0
sudo ifup -v wlan0
If your network keeps disconnecting, then this might be due to the "physical" settings of your network. But let's look at that later on.

EDIT;
Indeed you don't require "/etc/wpa_supplicant.conf".

[AZzKikR]

Alright, I've been browsing through this thread for quite some time, trying for some hints about my problem.

I have a nice connection to my router with the following properties:

I have a Linksys Wireless PCI card, which is based on the Ralink Rt2500 chipset;
Router has WPA/PSK TKIP
I am using SerialMonkey's drivers
I used this wiki post (https://help.ubuntu.com/community/WifiDocs/Driver/RalinkRT2500#WPA) to enable WPA/PSK TKIP


I have been noticing however, that sometimes my connection just get very laggy (i.e. pinging my router often results in 40% - 60% packet loss). After a short while, my connection just plain drops. Rebooting does not help and I have to let this effect 'wear out': after some time it works normally.

The other 4 windows based laptops and computers in my house all have a perfect wireless connection, so my router is just functioning fine. I am thinking it's the driver which is just plain crap.

Anyone else has something like this? I am thinking about using ndiswrapper.

[wieman01]

Alright, I've been browsing through this thread for quite some time, trying for some hints about my problem.

I have a nice connection to my router with the following properties:

I have a Linksys Wireless PCI card, which is based on the Ralink Rt2500 chipset;
Router has WPA/PSK TKIP
I am using SerialMonkey's drivers
I used this wiki post (https://help.ubuntu.com/community/WifiDocs/Driver/RalinkRT2500#WPA) to enable WPA/PSK TKIP


I have been noticing however, that sometimes my connection just get very laggy (i.e. pinging my router often results in 40% - 60% packet loss). After a short while, my connection just plain drops. Rebooting does not help and I have to let this effect 'wear out': after some time it works normally.

The other 4 windows based laptops and computers in my house all have a perfect wireless connection, so my router is just functioning fine. I am thinking it's the driver which is just plain crap.

Anyone else has something like this? I am thinking about using ndiswrapper.
I had the same issues (connection dropping) usind "ndiswrapper" and the latest Windows driver (RT2570). Changing a few (wireless) settings did the job for me eventually (beacon interval, etc.). Not sure if this is an option for you, but I would play around with those router settings.

EDIT:
I didn't enjoy Serialmonkey's driver either, believe me. So I dropped it.

[yamad]

Thanks for your help.

If your network keeps disconnecting, then this might be due to the "physical" settings of your network. But let's look at that later on.

I see what you are saying, but I wouldn't characterize the network as disconnecting. Rather, one or twice it connected for a brief period (probably some command got fired while starting up NetworkManager). Also, when I turned off WPA everything worked.

Here are the logs.

iwconfig

lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"<SSID>"
Mode:Managed Frequency:2.437 GHz Access Point: 00:09:5B:86:B0:B4
Bit Rate=54 Mb/s
RTS thr=2432 B Fragment thr=2432 B
Power Management:off
Link Quality:64/100 Signal level:-55 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


iwlist scan

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:09:5B:86:B0:B4
ESSID:"<SSID>"
Protocol:IEEE 802.11b
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; 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=1
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 02 - Address: 00:E0:98:D3:D4:4A
ESSID:"<some other guy's SSID>"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:21/100 Signal level:-82 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=200
Extra:atim=2
Cell 03 - Address: 00:0F:B5:64:A2:3E
ESSID:"<another other guy's SSID>"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:17/100 Signal level:-85 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=1



route:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 wlan0
link-local * 255.255.0.0 U 1000 0 0 wlan0
default 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0



ifdown -v wlan0:

Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
route del default gw 192.168.0.1 wlan0
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 7120)


ifup -v wlan0

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 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "<SSID>" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP -- OK
wpa_supplicant: wpa-group TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

ifconfig wlan0 192.168.0.200 netmask 255.255.255.0 up
route add default gw 192.168.0.1 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


a note on MAC addresses... my router uses them and I had to enter the one from ifconfig wlan0 when I was setting aside the IP (I set aside the IP because I thought it might work better than dhcp after trying it with dhcp for a while). not sure if that it MAC filtering or not. unfortunately, i don't know if i can turn it off if it is (i assume that must be done on the router side).

Thanks for all your help. Seriously.

[wieman01]

@yamad:

What happens if you ping your router:
ping 192.168.0.1
Or Google:
ping www.google.com

[yamad]

yeah, pinging is how i usually check whether i'm connected or not.


ping 162.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 192.168.0.200 icmp_seq=2 Destination Host Unreachable
and so on...



ping www.google.com
ping: unknown host www.google.com


thanks!

[wieman01]

Ah... You have changed your second post in the meantime ("ifup -v wlan0") which confirms that authentication is not the issue.

I suspect that this has to do with...

a) either MAC filtering
b) the IP you have chosen.

Could you connect to the network using this very PC when you were running Windows? If that is so, MAC filtering is ruled out. Is the IP address valid? Well, enable DHCP once again and see what IP address you are assigned. That is the IP address you should use for testing Static IP.

We'll get there... we're fairly close. WPA is not our problem. :-)

[yamad]

hmmm... i can't get an ip from dhcp. lots of DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval X errors. this is why i had tried to switch to static ip. the ip i chose was random, but within the range of assignable IPs (i think). the same hardware (same computer) running windows worked fine.

dmesg has these two following errors that may be relevant:

wlan0: no IPv6 routers present
ADDRCONF(NETDEV_UP): wlan0: link is not ready


thanks