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

[wieman01]

Any good cardbus cards?
None that I know of. But you could check here:

https://help.ubuntu.com/community/WifiDocs/WirelessCardsSupported

[emmir]

I'm back!!!
Took me about 2 hours to set the whole thing up but now I'm the proud owner of a working Wifi with static IP.:):):) Thank you, thank you very much.

A last question: is it normal for "network manager" to give me only the "manual configuration" option and no wifi indication at all (you know those vertical increasing in size blue lines) ? And if so, is there a way to have a graphical indication for it?

Again, thank you

Besides that why must I give " sudo ifdown -v eth1" and "sudo ifup -v eth1" every time I turn my pc on? Isn't there a way to avoid this?

[wieman01]

Besides that why must I give " sudo ifdown -v eth1" and "sudo ifup -v eth1" every time I turn my pc on? Isn't there a way to avoid this?
This is a bug that others have confirmed as well. See post #2 for a workaround.

[airstrike]

this is an awesome guide. it worked perfectly well. congrats and thanks on writing such a good how-to!

[Maelgwyn]

route -n
Destination Gateway Genmask Flags Metric Ref Use Iface
10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 ra0
0.0.0.0 10.1.1.1 0.0.0.0 UG 0 0 0 ra0
iwconfig

ra0 RT2500 Wireless ESSID "DLINK_WIRELESS" //This is wrong - should be "This Binary Universe"


cat /etc/network/interfaces
// usual stuff here

# The primary network interface
auto ra0
iface ra0 inet static
address 10.1.1.12
gateway 10.1.1.1
dns-nameservers 10.1.1.1
netmask 255.0.0.0
wpa-driver wext
wpa-ssid This Binary Universe
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk bf0d97141d75a8bda5a4f307d766547c2dbeec388401f08fa8 54db8d13d85c2c

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

cat /etc/resolv.conf
nameserver 10.1.1.1

If it's of any use - the wireless router is 10.1.1.2 and it's connected via cat6 to the broadband router which is 10.1.1.1. I can get this going on my boyfriends' XP laptop, but I can't get it going on my Ubuntu server + fluxbox desktop =(

I want my computer to have interweb capabilities!!! *cry*

[wieman01]

route -n
Destination Gateway Genmask Flags Metric Ref Use Iface
10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 ra0
0.0.0.0 10.1.1.1 0.0.0.0 UG 0 0 0 ra0
iwconfig

ra0 RT2500 Wireless ESSID "DLINK_WIRELESS" //This is wrong - should be "This Binary Universe"


cat /etc/network/interfaces
// usual stuff here

# The primary network interface
auto ra0
iface ra0 inet static
address 10.1.1.12
gateway 10.1.1.1
dns-nameservers 10.1.1.1
netmask 255.0.0.0
wpa-driver wext
wpa-ssid This Binary Universe
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk bf0d97141d75a8bda5a4f307d766547c2dbeec388401f08fa8 54db8d13d85c2c

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

cat /etc/resolv.conf
nameserver 10.1.1.1

If it's of any use - the wireless router is 10.1.1.2 and it's connected via cat6 to the broadband router which is 10.1.1.1. I can get this going on my boyfriends' XP laptop, but I can't get it going on my Ubuntu server + fluxbox desktop =(

I want my computer to have interweb capabilities!!! *cry*
Sorry, it's a Ralink. Mentioned in post #1, you'll have to replace the driver with "ndiswrapper" if you want to follow thiw HOWTO. Ralink does not work.

[Maelgwyn]

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

This means I don't have ndiswrapper installed eh? Is it as simple as apt-get install ndiswrapper?

[wieman01]

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

This means I don't have ndiswrapper installed eh? Is it as simple as apt-get install ndiswrapper?
It's not as simple, but you find tons of HOWTOs around here. If you need help, post your issues and send me the link by PM. :-)

[Megatog615]

How can I get this manual connection to show network status such as signal strength with knetworkmanager?

I got a new card by the way. It's a Ralink chipset but how am I to know(damn vendors don't supply chipset info on the box)?

Using ndiswrapper for now until open source drivers for it can handle WPA2 without locking the system.

[wieman01]

How can I get this manual connection to show network status such as signal strength with knetworkmanager?
You can't.

Enable DHCP on the router and use KNetworkManager instead. Only follow this tutorial if you need a static IP. I also recommend the use of "ndiswrapper" as the Ralink driver for Linux is a hassle.

[foxy123]

Hi, thanks a lot for the howto. It is great. However I still has a problem. Even after creating a script for network restart I still have to do it manually again (without the script I had to do it twice). I tried to add the same line in the script but it does not seem to work. Any advice?

$ sudo /etc/init.d/networking restart
Password:
* Reconfiguring network interfaces... RTNETLINK answers: File exists
run-parts: /etc/network/if-up.d/avahi-autoipd exited with return code 2
[ OK ]

[wieman01]

Hi, thanks a lot for the howto. It is great. However I still has a problem. Even after creating a script for network restart I still have to do it manually again (without the script I had to do it twice). I tried to add the same line in the script but it does not seem to work. Any advice?

$ sudo /etc/init.d/networking restart
Password:
* Reconfiguring network interfaces... RTNETLINK answers: File exists
run-parts: /etc/network/if-up.d/avahi-autoipd exited with return code 2
[ OK ]

What wireless adapter have you got? An are you running Firestarter?

No idea yet... Let's see if we find a solution together.

[foxy123]

What wireless adapter have you got? An are you running Firestarter?

No idea yet... Let's see if we find a solution together.

I am running BCM4306 chip with ndiswrapper. No I am not running Firestarter.

[Paris Heng]

Can I do like this in my Linux Atheros Wifi? I want to have both AP mode and Ad-hoc mode in my laptop. It is possible?

#wlanconfig ath0 create wlandev wifi0 wlanmode ap
#wlanconfig ath1 create wlandev wifi0 wlanmode adhoc

Please assist. Thank you.

[wieman01]

I am running BCM4306 chip with ndiswrapper. No I am not running Firestarter.
There was another user with a similar problem. Tried to find the relevant posts but in vain. I remember that we had no success in the end and a manual restart was still necessary. Sorry I cannot say more.

[wieman01]

Can I do like this in my Linux Atheros Wifi? I want to have both AP mode and Ad-hoc mode in my laptop. It is possible?

#wlanconfig ath0 create wlandev wifi0 wlanmode ap
#wlanconfig ath1 create wlandev wifi0 wlanmode adhoc

Please assist. Thank you.
I am afraid I cannot follow you. Can you explain what this is about? I may have nothing to do with this thread... Anyway, let us know.

[Paris Heng]

I am afraid I cannot follow you. Can you explain what this is about? I may have nothing to do with this thread... Anyway, let us know.

You are using Madwifi _ Madwifi-tools rights? I believe you have encounter this type of configuration to make the Wifi card become station, ad-hoc, and AP ..etc.

[wieman01]

You are using Madwifi _ Madwifi-tools rights? I believe you have encounter this type of configuration to make the Wifi card become station, ad-hoc, and AP ..etc.
I see... No, I don't use Madwifi right now. Somehow yes, there is mention of a Madwifi driver in the HOWTO, but I have never heard of such a tool.

[Paris Heng]

I see... No, I don't use Madwifi right now. Somehow yes, there is mention of a Madwifi driver in the HOWTO, but I have never heard of such a tool.

Anyway thanx, are you 'Zhong guo Ren'? Your side is very useful.

[emmir]

What wireless adapter have you got? An are you running Firestarter?


I have the same problem. Even though I followed your 2nd post so I don't have to restart networking after reboot it didn't work. What about Firestarter? Is there something you have to configure in order to have wifi upon restart?

[wieman01]

I have the same problem. Even though I followed your 2nd post so I don't have to restart networking after reboot it didn't work. What about Firestarter? Is there something you have to configure in order to have wifi upon restart?
Actually no. It just happens that occasionally there is an issue with DHCP and Firestarter. So that's why I thought turning it off would be a remedy. Just to test it.

What adapter have you got?

[foxy123]

There was another user with a similar problem. Tried to find the relevant posts but in vain. I remember that we had no success in the end and a manual restart was still necessary. Sorry I cannot say more.

Thanks anyway. Possibly it's a bug in Ubuntu's basic networking script. It is really quite inconvenient that it cannot be done automatic.

[wieman01]

Thanks anyway. Possibly it's a bug in Ubuntu's basic networking script. It is really quite inconvenient that it cannot be done automatic.
All we can do it file bug reports at Launchpad...

[foxy123]

All we can do it file bug reports at Launchpad...

yes, but I do not know against what package. And also it is not clear what is wrong.

[Dark Star]

Very nice How to will help me soon :)

[emmir]

Actually no. It just happens that occasionally there is an issue with DHCP and Firestarter. So that's why I thought turning it off would be a remedy. Just to test it.

What adapter have you got?

USR Maxg 5417A, and a USR 9108 wifi Router.

I don't use DHCP. How can I be sure its disabled?

[wieman01]

yes, but I do not know against what package. And also it is not clear what is wrong.
Ok, I'll see what I can do. Should have done that long ago. I'll report back.

[wieman01]

USR Maxg 5417A, and a USR 9108 wifi Router.

I don't use DHCP. How can I be sure its disabled?
Firestarter is not installed by default so don't worry about it if you have not installed it yourself.

As for the reconnection issue... Launchpad is all I can suggest.

[emmir]

Firestarter is not installed by default so don't worry about it if you have not installed it yourself.

As for the reconnection issue... Launchpad is all I can suggest.

ok thank you...
For the record:
I have installed Firestarter, (since I'm using Azureus). I also have kind of "reverse" followed your second post in order to get rid of the initially created files and links, and create them again. Since then wifi connection (or re-connection if you like) at startup works at will!!! Imagine my surprise when immediatly after reboot I opened Firefox and I saw my start page loading rapidly, (and not from the cache since I configured firefox to delete everything when I close the program) and then when I tried to load another page... there was no connection!!
Anyway I'm still trying to figure thinks out. When I have any news I'll get back to you.
Thank you again for your valuable help...

[wieman01]

ok thank you...
For the record:
I have installed Firestarter, (since I'm using Azureus). I also have kind of "reverse" followed your second post in order to get rid of the initially created files and links, and create them again. Since then wifi connection (or re-connection if you like) at startup works at will!!! Imagine my surprise when immediatly after reboot I opened Firefox and I saw my start page loading rapidly, (and not from the cache since I configured firefox to delete everything when I close the program) and then when I tried to load another page... there was no connection!!
Anyway I'm still trying to figure thinks out. When I have any news I'll get back to you.
Thank you again for your valuable help...
Interesting finding, mate.

You use the 'madwifi' driver as part of your script. Does replacing it with 'wext' make a difference?

[Trash_Gordon]

Hi,
I've been trying to bring up Wireless Lan on my Ubuntu system for months now, and I finally have the feeling that I'm *that* close to succeeding. However, there is an obstacle left which I couldn't figure out.
I'm using a Fritz! WLAN USB Stick with native Linux drivers which is working fine. I've set up wpa_supplicant according to your howto, but then I get this:

RTNETLINK answers: File exists
run-parts: /etc/network/if-up.d/avahi-autoipd exited with return code 2

full ifup -v wlan0 (http://pastebin.com/f6d254f04)
I've been looking around and couldn't find relief. Hope you can help me. Here some additional information:
root@adrian:/home/adrian# 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-ssid FRITZ!Box Fon WLAN 7141
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <censored>


root@adrian:/home/adrian# iwonfig
bash: iwonfig: command not found
root@adrian:/home/adrian# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11b/g ESSID:"FRITZ!Box Fon WLAN 7141"
Mode:Managed Channel:6 Access Point: 00:04:0E:F8:9D:E6
Encryption key:3131-3131-3131-3131-3131-3131-31 Security mode:open
Link Signal level=-62 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


root@adrian:/home/adrian# ifconfig wlan0
wlan0 Protokoll:Ethernet Hardware Adresse 00:04:0E:CB:81:CE
inet Adresse:192.168.178.20 Bcast:192.168.178.255 Maske:255.255.255.0
inet6 Adresse: fe80::204:eff:fecb:81ce/64 Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:267 errors:0 dropped:0 overruns:0 frame:0
TX packets:182 errors:12 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:48598 (47.4 KiB) TX bytes:19272 (18.8 KiB)

[wieman01]

full ifup -v wlan0
It looks like the adapter has been able to connect. What happens when you do this (please post the output):
route
ping 192.168.178.1

[Trash_Gordon]

Well, the problem solved itself. After rebooting, it works fine. Thanks for your awesome walkthrough.

[Ken101]

I can connect with my WG111 (no encryption) and have tried to set up WPA-PSK. I must have some wrong setting but I don't know how to proceed. Xubuntu 6.06 - assistance is appreciated - thx

wlan0 Scan completed :
Cell 01 - Address: 00:09:5B:71:3D:B8
ESSID:"PCD"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.457 GHz (Channel 10)
Quality:0/100 Signal level:-78 dBm Noise level:-256 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

[wieman01]

I can connect with my WG111 (no encryption) and have tried to set up WPA-PSK. I must have some wrong setting but I don't know how to proceed. Xubuntu 6.06 - assistance is appreciated - thx

wlan0 Scan completed :
Cell 01 - Address: 00:09:5B:71:3D:B8
ESSID:"PCD"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.457 GHz (Channel 10)
Quality:0/100 Signal level:-78 dBm Noise level:-256 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
Please also post the contents of "/etc/network/interfaces".

[Ken101]

Thx for quick reply!
Here is /etc/network/interfaces - i'm sure it's wrong but i'm clueless

auto lo
iface lo inet loopback


iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp


iface eth2 inet dhcp
wireless-essid PCD
wireless-key randburg

auto ath0
iface ath0 inet dhcp
wpa-driver wext
wpa-ssid "PCD"
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk "c0fc780681eda01aa2dc10dc39cda62373e7cc25cc43bc639d ec5f69ab41d203"






auto eth2





iface wlan0 inet dhcp
wireless-essid PCD
wireless-key s:













auto wlan0

auto eth0

[wieman01]

Thx for quick reply!
Here is /etc/network/interfaces - i'm sure it's wrong but i'm clueless

auto lo
iface lo inet loopback

iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

iface eth2 inet dhcp
wireless-essid PCD
wireless-key randburg

auto ath0
iface ath0 inet dhcp
wpa-driver wext
wpa-ssid "PCD"
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk "c0fc780681eda01aa2dc10dc39cda62373e7cc25cc43bc639d ec5f69ab41d203"

auto eth2

iface wlan0 inet dhcp
wireless-essid PCD
wireless-key s:

auto wlan0

auto eth0
Ok, let's try this instead. Please replace the contents with this (no "" please):
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid PCD
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk c0fc780681eda01aa2dc10dc39cda62373e7cc25cc43bc639 dec5f69ab41d203
Then restart the computer. That done, restart the network manually and post the output:
sudo ifdown -v wlan0
sudo ifup -v wlan0
route

[Ken101]

ken@ken-laptop:~$ sudo ifdown -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
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 4803
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:0f:b5:dc:74:be
Sending on LPF/wlan0/00:0f:b5:dc:74:be
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.0.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
ifconfig wlan0 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: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 4779).
ken@ken-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 "PCD" -- OK
wpa_supplicant: wpa-psk ***** -- FAIL
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:0f:b5:dc:74:be
Sending on LPF/wlan0/00:0f:b5:dc:74:be
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
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...
Error : Temporary failure in name resolution
ken@ken-laptop:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
ken@ken-laptop:~$

[wieman01]

It's obvious... you have not generated the PSK correctly:
wpa_supplicant: wpa-psk ***** -- FAIL
How did you do it? Please remove all apostrophes ("") when you generate it? There should not be any "" in /etc/network/interfaces.

[Ken101]

I entered it & wireless worked briefly.
Is there any application that can do the wireless configuration job instead of manually entering it?

[wieman01]

I entered it & wireless worked briefly.
Is there any application that can do the wireless configuration job instead of manually entering it?
There is. Network Manager which comes with the default install of Feisty Fawn. What version of Ubuntu are you on?

[Ken101]

:guitar:I'm connected!
I installed Wicd (http://wicd.sourceforge.net/) and got it working with not too much trouble.

I recommend anyone to use this program - it worked for me!

[tech9]

sweet... I will check this out

[delta2]

wieman01 thank you success!

[prosonik]

After many hours of frustration, I have the WL-138g and a dell gx280 working with the console based instructions..
I'm using the latest and greatest Ndiswrapper.. I had to uninstall all network managers..
WICD did not 'see' my card. even when i configured it (wlan0).. I'm not sure why. I have used wicd before, and it seemed to work well...

If people are having problems not getting a dhcp offer, go back and check your essid and wpa password.. That was part of my problem.. as well ensure your ndis is working.. (ndiswrapper -v) and (ndisrwrapper -l)

pro

[merlin666]

Thank you, I managed to get my router connected on the first try even with ESSID disabled and MAC filtering in place. However, after a few minutes I lost the connection and I don't know how to re-connect. My router still shows up when I type iwlist scan.

How do I re-establish the connection?

Update: I restarted the network connection. Now there is wlan0 without Interface information in Network Tools, and also wlan0:avahi that shows the correct MAC address - this is also listed in the router log. It looks like wlan0:avahi is not doing anything.

[wieman01]

Thank you, I managed to get my router connected on the first try even with ESSID disabled and MAC filtering in place. However, after a few minutes I lost the connection and I don't know how to re-connect. My router still shows up when I type iwlist scan.

How do I re-establish the connection?

Update: I restarted the network connection. Now there is wlan0 without Interface information in Network Tools, and also wlan0:avahi that shows the correct MAC address - this is also listed in the router log. It looks like wlan0:avahi is not doing anything.
No idea what "wlan0:avahi" is. Could you post the output?

As for the issue with the dropping connection, that must have something to do with the router & the wireless adapter. Is the router on "mixed mode"?

[merlin666]

Thank you for the response and how-to. The connection was re-established after I did a re-boot.

A re-boot seems to solve about 85% of the problems I may have had when changing something in Ubuntu.

[wieman01]

Thank you for the response and how-to. The connection was re-established after I did a re-boot.

A re-boot seems to solve about 85% of the problems I may have had when changing something in Ubuntu.
Haha... Yes, indeed. :-)

[merlin666]

No idea what "wlan0:avahi" is. Could you post the output?

As for the issue with the dropping connection, that must have something to do with the router & the wireless adapter. Is the router on "mixed mode"?

I started up ubuntu again today and faced the same problem. What kind of diagnostic output would be useful here?

Oh and another question: I finally managed to get network manager into the notification area and it is dead - only works with the wired connection. Is this a result of the security configuration?

[wieman01]

I started up ubuntu again today and faced the same problem. What kind of diagnostic output would be useful here?
You could try post #2 in the thread. If that doesn't help, you need to post the contents of your boot log files. The most relevant one is this one:
gedit /var/log/boot
Oh and another question: I finally managed to get network manager into the notification area and it is dead - only works with the wired connection. Is this a result of the security configuration?
Yes, it is.

[emmir]

Hi again...

I had to reinstall and decided to upgrade to 2.6.22.11 (it suppose to solve the "harsh" shutdown problem). Trying to apply your method I get this:
myron@Pelion:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

Warning: Driver for device eth1 has been compiled with version 22
of Wireless Extension, while this program supports up to version 20.
Some things may be broken...

eth1 No scan results


Ignoring this and proceeding with the next steps I get this:

myron@Pelion:~$ sudo ifup -v eth1
Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
SIOCSIFFLAGS: No such file or directory
Error for wireless request "Set Encode" (8B2A) :
invalid argument "935818082004%%".
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.eth1.pid
Stopped /sbin/wpa_supplicant (pid 8687).
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.eth1.pid -i eth1 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
SIOCSIFFLAGS: No such file or directory
Could not set interface 'eth1' UP
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/eth1
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "MMSDH" -- 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

ifconfig eth1 192.168.72.70 netmask 255.255.255.0 broadcast 192.168.72.255 up
SIOCSIFFLAGS: No such file or directory
SIOCSIFFLAGS: No such file or directory
Failed to bring up eth1.

Is there a way to work around this?

[wieman01]

@emmir:

Oh, man. Beats me. The only thing I could suggest is that you upgrade to the latest version of "ndiswrapper" as well.

If that does not work, I could help you with the shutdown issue. This is what fixed it for me after I had installed Feisty:

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

[exz]

thanks worked like a charm. tried the wpa-driver ipw3945 at first (got it from some random internet forum) but without success.. it worked with the wext driver thought.. thanks!

[wieman01]

thanks worked like a charm. tried the wpa-driver ipw3945 at first (got it from some random internet forum) but without success.. it worked with the wext driver thought.. thanks!
Did Network Manager not work for you? Just curious.

[Depressed Man]

Do you have any idea why it would stop working? I have a laptop with ipw3945. I didn't have to download any additional drivers or do anything that you described in your guide. It just worked after my install with my wireless settings after I inputed them in (WPA Personal, passphrase, and cipher type).

However, recently it doesn't work anymore. It can't connect to my wireless network unless I turn off the protection (it works fine in Vista with the protection as well).

Any idea why this changed recently? And how to fix it?

[wieman01]

Do you have any idea why it would stop working? I have a laptop with ipw3945. I didn't have to download any additional drivers or do anything that you described in your guide. It just worked after my install with my wireless settings after I inputed them in (WPA Personal, passphrase, and cipher type).

However, recently it doesn't work anymore. It can't connect to my wireless network unless I turn off the protection (it works fine in Vista with the protection as well).

Any idea why this changed recently? And how to fix it?
Beats me. I have not noticed any change at all, but that is because I have turned off automatic updates (with security updates being the exception).

[Depressed Man]

And now it works again.. ugh.

[mail5253680]

OK -- DId the stuff in the parent post, but problems remain:

I have Dlink wireless PCI card in a desktop system. When I first boot up, the system brings up the card and connects to the wireless router, then asks for an IP address via DHCP. This last step fails and continues to fail.

After bootup however, I go to the command line and issue the commands:

sudo ifdown ath0
sudo ifup ath0

At the last command, I see the interface starting up again, DHCP asking for an IP address, which works!

What could be the problem with bringing up the interface the first time?

Why would a simple ifdown/ifup make it work?

What can I do to make it work automatically at boot?

[wieman01]

OK -- DId the stuff in the parent post, but problems remain:

I have Dlink wireless PCI card in a desktop system. When I first boot up, the system brings up the card and connects to the wireless router, then asks for an IP address via DHCP. This last step fails and continues to fail.

After bootup however, I go to the command line and issue the commands:

sudo ifdown ath0
sudo ifup ath0

At the last command, I see the interface starting up again, DHCP asking for an IP address, which works!

What could be the problem with bringing up the interface the first time?

Why would a simple ifdown/ifup make it work?

What can I do to make it work automatically at boot?
It's a known bug (nature knows where). Please see post #2 for a workaround.

[neptho]

This has been a bit of a pain, but it actually works for mapping multiple 'known' points in your /etc/network/interfaces file. I've got some ideas from here (http://www.lazy8.nu/delld180/DebianLinuxOnDellLattitude810laptop.html), which helped me fix the mapping problems I was having when I was using my own script. His information is for WEP, but this will also work for WPA, as you will see below.

First, you'll want to create /etc/network/wlan-scanning.sh:
#!/bin/sh
#
# Written by Thomas Dilts 20060719, Trivial fixups by Shawn Holwegner.
# This script is designed to be run by the "interfaces" system to find which
# wireless networks are present and return the first found interface.
#
#We must run as root (id -u returns then 0) and we must have the interface name as input
if [ `id -u` -ne "0" ] || [ "$1" = "" ]; then exit 1; fi

iface="$1"
which=""
# With this method, You only need one scan, instead of scanning for each SSID until you find the AP.
FOUNDAPS=`/sbin/iwlist "$iface" scanning | grep ESSID`
while read searchstring returnvalue ; do
if [ "$which" ]; then continue; fi
echo " Trying to find wlan $searchstring" >&2
if echo "$FOUNDAPS" | /bin/grep -c "$searchstring" >/dev/null2>&1
then
which="$returnvalue" ;
echo " found $searchstring and now starting $which" >&2
fi
done

if [ "$which" ]; then echo $which; exit 0; fi
exit 1

Remember to chmod it 775 so it can run.

Now, edit your mappings in /etc/network/interfaces as so:

auto eth1
mapping eth1
script /etc/network/wlan-scanning.sh
map HomeSSID HOME
map WorkSSID WORK
map key:off TRAVELING

iface HOME inet dhcp
wpa-ssid HomeSSID
wpa-psk wpa_key_generated_with_wpa_passphrase_here
...

iface WORK inet dhcp
wpa-ssid WorkSSID
wpa-psk wpa_key_generated_with_wpa_passphrase_here
...

#This is the open system setup that works at hotels and airports.
iface TRAVELING inet dhcp
iface eth1 inet dhcp

It's actually pretty simple to use, once you have it setup. It will scan for any of the 'known' SSIDs in your mapping, and execute wpa_supplicant with the correct data. Priorly, I had been using a custom ifup interface and a cobbled together wpa_supplicant.conf that set priorities for different SSIDs. It also took about 5 seconds to bring the interface up. Now? About 2.

I hope this helps others, many thanks to Thomas Dilts for a functional mapping script.

If you run it manually, it will tell you what it's looking for, and what it finds. Using the '-v' flag coupled with ifup will give useful debugging information.

%sudo ifup eth1
Trying to find wlan HomeSSID
Trying to find wlan WorkSSID
Found WorkSSID and now starting WORK

[st33med]

I am having problems with my wireless on startup. It does not always connect on startup, it drops connections randomly, and Network Manager does not cooperate with my setup.

route -n:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 wlan0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0
iwconfig:
lo no wireless extensions.

eth0 no wireless extensions.

Warning: Driver for device wlan0 has been compiled with version 22
of Wireless Extension, while this program supports up to version 20.
Some things may be broken...

wlan0 IEEE 802.11g ESSID:"mason"
Mode:Managed Frequency:2.422 GHz Access Point: 00:13:10:C8:97:8D
Bit Rate=36 Mb/s Tx-Power:32 dBm
RTS thr=2347 B Fragment thr=2346 B
Power Management:off
Link Quality:62/100 Signal level:-56 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

ifconfig:
eth0 Link encap:Ethernet HWaddr 00:15:C5:B7:17:A9
inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:22

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

wlan0 Link encap:Ethernet HWaddr 00:18:F3:57:D5:3D
inet addr:192.168.1.102 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::218:f3ff:fe57:d53d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3320 errors:0 dropped:0 overruns:0 frame:0
TX packets:2334 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2547642 (2.4 MiB) TX bytes:331565 (323.7 KiB)
Interrupt:16 Memory:efdfc000-efe00000

route:
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 * 255.255.255.0 U 0 0 0 eth0
192.168.1.0 * 255.255.255.0 U 0 0 0 wlan0
link-local * 255.255.0.0 U 1000 0 0 wlan0
default 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0

cat /etc/network/interfaces:
#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-ssid ***** #censored!
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 1072992ef365767275eb91331246b79ceb8175e359df3dfbc1 8f01704ac001fe

cat /etc/modprobe.d/ndiswrapper:
alias wlan0 ndiswrapper
cat /etc/resolv.conf:
nameserver 68.87.73.242
nameserver 68.87.71.226

[wieman01]

I am having problems with my wireless on startup. It does not always connect on startup, it drops connections randomly, and Network Manager does not cooperate with my setup.
It's close to impossible to judge from here what could be going on. Network Manager usually does a better job at reconnecting, however, under the circumstances it is no option I guess.

What wireless adapter have you got?

WICD might be an alternative for you if everything else fails. If reconnecting after boot is the issue, then see post #2.

[gladstone]

I followed these steps (after trying ALOT of other methods) but couldnt get it to work. I decided to test if it would work after a reboot, instead I was given the gnome-settings-daemon error.

Initially having no idea what had happened (I couldn't login), I managed to pin-point it back to the /etc/network/interfaces file I just edited.

The bug has been discussed here:

https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/61381

and more specifically:

https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/61381/comments/43

https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/61381/comments/23

However, during that time, my wireless was working!

Is there anything I can try? I can remember another guide adding something like DISABLED=1 to /etc/wpa_supplicant.conf (I saw it mentioned in the Launchpad thread)... Is that the correct command?

[Target2019]

I have a Belkin 54g PC card, and it is connected to a Netgear WGR614v7 using WEP. I have SSID broadcast OFF, and the key is 128bit Hex.

I'm using WEP for now, as I have another notebook with a wireless B card. In time I'll find another great deal on a G card, and go to WPA-PSK.

Until then, I'm using WEP, and securing it as best I can. I start the notebook (or after it wakes from hibernate) and then have to enter the network manager > connect to other wireless manager. I enter the information, and connect. Can I save this information in some way, and streamline the process. I'd like to keep things simple, as I take this notebook to other locations, and do not want to complicate things going forward.

Here is iwconfig

iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"STATIONID"
Mode:Managed Frequency:2.427 GHz Access Point: 00:1B:2F:55:C0:32
Bit Rate=54 Mb/s Tx-Power:32 dBm
RTS thr=2347 B Fragment thr=2346 B
Power Management:off
Link Quality:48/100 Signal level:-65 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:

iwlist scan

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1B:2F:55:C0:32
ESSID:"STATIONID"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.427 GHz (Channel 4)
Quality:51/100 Signal level:-63 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0

Finally, my network interface config:

sudo gedit /etc/network/interfaces

auto lo
iface lo inet loopback


I've read some posts in this thread, and I'm looking for some help to alter my config, so that I can connect to my home wireless with as few steps as possible.

Thanks.

[lorenmcc]

I have experienced that I have to restart networking multiple times to get connected. Is there a more reliable method to get connected?

[wieman01]

I followed these steps (after trying ALOT of other methods) but couldnt get it to work. I decided to test if it would work after a reboot, instead I was given the gnome-settings-daemon error.

Initially having no idea what had happened (I couldn't login), I managed to pin-point it back to the /etc/network/interfaces file I just edited.

The bug has been discussed here:

https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/61381

and more specifically:

https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/61381/comments/43

https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/61381/comments/23

However, during that time, my wireless was working!

Is there anything I can try? I can remember another guide adding something like DISABLED=1 to /etc/wpa_supplicant.conf (I saw it mentioned in the Launchpad thread)... Is that the correct command?
If you posted the contents of "/etc/network/interfaces" it would help a lot. I don't know if "DISABLED=1" is the right command at the moment.

[wieman01]

I have experienced that I have to restart networking multiple times to get connected. Is there a more reliable method to get connected?
Have you noticed post #2? It might be the solution.

[wieman01]

I have a Belkin 54g PC card, and it is connected to a Netgear WGR614v7 using WEP. I have SSID broadcast OFF, and the key is 128bit Hex.

I'm using WEP for now, as I have another notebook with a wireless B card. In time I'll find another great deal on a G card, and go to WPA-PSK.

Until then, I'm using WEP, and securing it as best I can. I start the notebook (or after it wakes from hibernate) and then have to enter the network manager > connect to other wireless manager. I enter the information, and connect. Can I save this information in some way, and streamline the process. I'd like to keep things simple, as I take this notebook to other locations, and do not want to complicate things going forward.

Here is iwconfig

iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"STATIONID"
Mode:Managed Frequency:2.427 GHz Access Point: 00:1B:2F:55:C0:32
Bit Rate=54 Mb/s Tx-Power:32 dBm
RTS thr=2347 B Fragment thr=2346 B
Power Management:off
Link Quality:48/100 Signal level:-65 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:

iwlist scan

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1B:2F:55:C0:32
ESSID:"STATIONID"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.427 GHz (Channel 4)
Quality:51/100 Signal level:-63 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0

Finally, my network interface config:

sudo gedit /etc/network/interfaces

auto lo
iface lo inet loopback


I've read some posts in this thread, and I'm looking for some help to alter my config, so that I can connect to my home wireless with as few steps as possible.

Thanks.
Well, you could follow this tutorial which should make it as simple as possible for you. If you encounter problems you could just post here.

Another solution for you might be WICD:

http://wicd.sourceforge.net/

[Target2019]

Well, you could follow this tutorial which should make it as simple as possible for you. If you encounter problems you could just post here.

Another solution for you might be WICD:

http://wicd.sourceforge.net/

Thanks for the link to WICD. I'll check that out.

Assuming by tutorial, you mean the first post or two, I have read that. I did not find WEP mentioned, so I searched the thread with google. I found some posts tht tried to address WEP specifically, read them, and was confused. So I posted the results of what I have in configuration, as I had seen done many times in this thread.

Thanks again for the reference to WICD.

[lorenmcc]

Have you noticed post #2? It might be the solution.

I have written a script based on Post #2 (before I asked the question). This script has a loop in it abd will continue until the connection is made. I actually had to limit the looping since the laptop took a long time to connect. Connection is very intermittent, I am currently running the script for the second time (with a loop limit of 100) and it has still not connected.

[Target2019]

Tried Wicd. It wouldn't find the hidden network using any of the supplicant modes, unfortunately. I found on Wicd forum that when ndiswrapper is used, there are additional problems. I re-installed network manager, and I'm back on. I'll try to keep it simple by using network manager.

I'll keep searching for what I need to do to get a hidden network listed, and maybe there'll be a way to store the WEP key too.

[wieman01]

Tried Wicd. It wouldn't find the hidden network using any of the supplicant modes, unfortunately. I found on Wicd forum that when ndiswrapper is used, there are additional problems. I re-installed network manager, and I'm back on. I'll try to keep it simple by using network manager.

I'll keep searching for what I need to do to get a hidden network listed, and maybe there'll be a way to store the WEP key too.
Hidden networks should not be an issue any longer in Feisty. You need to select "Connect to other wireless network..." however. Then type in the name and you are ready to roll.

[lorenmcc]

I have written a script based on Post #2 (before I asked the question). This script has a loop in it abd will continue until the connection is made. I actually had to limit the looping since the laptop took a long time to connect. Connection is very intermittent, I am currently running the script for the second time (with a loop limit of 100) and it has still not connected.

I have gotten this to work more reliably, but it begs the question as to why this is occurring, possibly some startup sequence issue?

I had to add the following to the loop in my script


killall dhclient wpa_supplicant dhclient3
rm /var/run/dhclient.*


and now I can connect almost every time on the first loop (but not always).

Any ideas?

BTW, I have never gotten wicd to connect, this is the only method I have gotten to work (as in posts #1 and #2)

[Target2019]

Hidden networks should not be an issue any longer in Feisty. You need to select "Connect to other wireless network..." however. Then type in the name and you are ready to roll.
I installed Wicd as you suggested. This uninstalled network manager. With Wicd I could not connect to hidden network using any of the supplicant modes.

I re-installed network manager, which uninstalled Wicd. Now I have the "connect to other networks" item, and can manually enter SSID and WEP key.

I am back to network manager, and wondering if there is a way to configure the hidden network and WEP key, so that I don't have to re-enter them each time I boot (or awake).

Thank you very much.

[wieman01]

I installed Wicd as you suggested. This uninstalled network manager. With Wicd I could not connect to hidden network using any of the supplicant modes.

I re-installed network manager, which uninstalled Wicd. Now I have the "connect to other networks" item, and can manually enter SSID and WEP key.

I am back to network manager, and wondering if there is a way to configure the hidden network and WEP key, so that I don't have to re-enter them each time I boot (or awake).

Thank you very much.
I think you are looking for a tool called "GNOME Keyring Manager". There are a number of tutorials for it.

[Target2019]

I think you are looking for a tool called "GNOME Keyring Manager". There are a number of tutorials for it.
Thanks for that tip. Keyring Manager come into play after I open Network Manager and enter the hidden SSID and WEP key.

Just tried something different. I re-booted, then opened keyring. Open network manager and enter the SSID and WEP. I was thinking that the WEP key, properly stored in keyring would auto-connect, but it doesn't seem to matter.

I guess I'll have to search further for a way to configure this, or just wait for some improvements to ubuntu, or maybe a better wifi management app.

I'll have to accept that there is no way to enter the required information to a network config file.

[wieman01]

Thanks for that tip. Keyring Manager come into play after I open Network Manager and enter the hidden SSID and WEP key.

Just tried something different. I re-booted, then opened keyring. Open network manager and enter the SSID and WEP. I was thinking that the WEP key, properly stored in keyring would auto-connect, but it doesn't seem to matter.

I guess I'll have to search further for a way to configure this, or just wait for some improvements to ubuntu, or maybe a better wifi management app.

I'll have to accept that there is no way to enter the required information to a network config file.
You did not find anything on the forums? I am sure I have seen something concerning it a while ago. I'll post if I find something tomorrow.

[Target2019]

You did not find anything on the forums? I am sure I have seen something concerning it a while ago. I'll post if I find something tomorrow.
I searched SSID + hidden + WEP, and found a few threads that confirm the problem.

Finally cleared up the keyring problem by installing pam-keyring, so that my user login pass gets passed to keyring manager.

[gladstone]

If you posted the contents of "/etc/network/interfaces" it would help a lot. I don't know if "DISABLED=1" is the right command at the moment.

Hi, my etc/network/interfaces looked like this:


auto lo
iface lo inet loopback

auto eth1
iface eth1 inet static
address 192.168.1.2
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid Toupe
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk [MY HASHED PSK]


I have a laptop and my wireless adaptor is an Intel pro 2200BG

[wieman01]

Hi, my etc/network/interfaces looked like this:


auto lo
iface lo inet loopback

auto eth1
iface eth1 inet static
address 192.168.1.2
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid Toupe
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk [MY HASHED PSK]


I have a laptop and my wireless adaptor is an Intel pro 2200BG
Looks fine actually. You have disabled SSID broadcast and use WPA-TKIP. What does a scan yield?
sudo iwlist scan

[jabberwauki]

In my experience, the following instruction from the main thread

<quote>
VERY IMPORTANT:
Now convert your WPA ASCII password using the following command (' ' single quotes required):

wpa_passphrase 'ssid' 'ascii_key'
</quote>

did not actually require single quotes. wpa_passphrase generated a different key when single quotes were used which was rejected by my router. removing the single quotes and generating the key again solved this for me.

i am using a netgear wgr614v5 wireless router with a netgear wg511 (version 1 made in taiwan) pcmcia card on an acer laptop.

[wieman01]

In my experience, the following instruction from the main thread

<quote>
VERY IMPORTANT:
Now convert your WPA ASCII password using the following command (' ' single quotes required):

wpa_passphrase 'ssid' 'ascii_key'
</quote>

did not actually require single quotes. wpa_passphrase generated a different key when single quotes were used which was rejected by my router. removing the single quotes and generating the key again solved this for me.

i am using a netgear wgr614v5 wireless router with a netgear wg511 (version 1 made in taiwan) pcmcia card on an acer laptop.
Thanks for highlighting that. I have corrected the tutorial accordingly. :-)

[gladstone]

Looks fine actually. You have disabled SSID broadcast and use WPA-TKIP. What does a scan yield?

It gives me:

sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:14:7F:58:E8:19
ESSID:"BTHomeHub-4543"
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=29/100 Signal level=-82 dBm
Extra: Last beacon: 272ms ago
Cell 02 - Address: 00:03:2F:2B:71:6B
ESSID:"<hidden>"
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=71/100 Signal level=-57 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 520ms ago


My router is "Cell 02" in that list. I also use MAC filters, would that make an effect?

I also managed to enable the front LED and when I used my earlier /etc/network/interfaces and rebooted, Ubuntu slowed at 3/4 of the way and resulted in the GNOME.DESKTOP error I mention, but the LED was solid i.e. connected :confused:

[wieman01]

@Gladstone:

Everything looks fine to me. But beats me, I don't know what's going on. MAC filtering could be an issue but only if the registered MAC isn't the same as the one listed above (00:03:2F:2B:71:6B).

Have you turned roaming off?

[vandetta]

I have a problem. I installed ubuntu in my machine and there's one problem. Wireless problem. The OS detect all the hardware perfectly and everything runs fine except for the wireless. The OS can detect wireless networks but could not connect to it. I attach together the screenshot and hopefully anyone can try to give me solution for this. Oh yes, the wireless was Realtek RTL8187. Thanks.

http://i16.photobucket.com/albums/b34/lazrus/ubuntuerrorscreenshot.png

[wieman01]

I have a problem. I installed ubuntu in my machine and there's one problem. Wireless problem. The OS detect all the hardware perfectly and everything runs fine except for the wireless. The OS can detect wireless networks but could not connect to it. I attach together the screenshot and hopefully anyone can try to give me solution for this. Oh yes, the wireless was Realtek RTL8187. Thanks.

http://i16.photobucket.com/albums/b34/lazrus/ubuntuerrorscreenshot.png
Please open a new separate thread for your this issue. It has not really anything do to with this one. But feel free to send me the link by PM.

[vandetta]

Oh, I'm sorry I will open new thread for this :)

[houms]

I followed these steps (after trying ALOT of other methods) but couldnt get it to work. I decided to test if it would work after a reboot, instead I was given the gnome-settings-daemon error.

Initially having no idea what had happened (I couldn't login), I managed to pin-point it back to the /etc/network/interfaces file I just edited.

The bug has been discussed here:

https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/61381

and more specifically:

https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/61381/comments/43

https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/61381/comments/23

However, during that time, my wireless was working!

Is there anything I can try? I can remember another guide adding something like DISABLED=1 to /etc/wpa_supplicant.conf (I saw it mentioned in the Launchpad thread)... Is that the correct command?

what does your /etc/network/interfaces look like..? what wireless card and driver are you using? A quick glance at your earlier post show you have a
dns-nameserver
in your interfaces file?

[gladstone]

Horrrayy!

Thanks houms, it was that rogue dns-nameservers that was causing all the problems. I'm not sure where I picked that up from, but I've been adding bits of things from all over the place over the last 2 weeks to get this working :( I hope it's not just all part of the learning curve!

I also have to use the network restart script for it to work (as described in post 2 here (http://ubuntuforums.org/showpost.php?p=1351902&postcount=2))

[houms]

Horrrayy!

Thanks houms, it was that rogue dns-nameservers that was causing all the problems. I'm not sure where I picked that up from, but I've been adding bits of things from all over the place over the last 2 weeks to get this working I hope it's not just all part of the learning curve!

I also have to use the network restart script for it to work (as described in post 2 here)
I'm glad I could help...don't worry, you'll learn quickly because the community here is great...really first rate. Just a quick suggestion... if you're having problems with the wireless starting up every time you boot up add the following using the post-up command and see if it helps...
in your etc/network/interfaces file... say your wireless interface is eth1....currently your last line at the end of the configuration setting for eth1 is

wpa-psk yourhexkeyhere

what you want to do add these two lines to the end

post-up iface down
post-up iface up

this works like a charm for me.... I just boot up and my wireless "just works".....Let me know if ya need help.

[latino.negro]

gracias hombre por tu ayuda

[latino.negro]

pero puedes hacer un en espanol para mi amigos

[wieman01]

pero puedes hacer un en espanol para mi amigos
In Spanish? No pienso tan.

[gladstone]

I've just upgraded to Gutsy and thankfully this method still works (although now I can select WPA in Network Managers Manual settings).

As a note, I left my etc/network/interfaces intact after the upgrade. On every subsequent boot, the IPW2200 driver would have 80 - near 100% CPU usage. I removed the network restart script (as described in post 2 of this thead) and replaced it with the

post-up iface down
post-up iface up

as described by Houms above. The problem seems to have gone away! Perhaps the original bug has been fixed, but I'll leave the post-up commands in for now.

[wieman01]

I've just upgraded to Gutsy and thankfully this method still works (although now I can select WPA in Network Managers Manual settings).

As a note, I left my etc/network/interfaces intact after the upgrade. On every subsequent boot, the IPW2200 driver would have 80 - near 100% CPU usage. I removed the network restart script (as described in post 2 of this thead) and replaced it with the

post-up iface down
post-up iface up

as described by Houms above. The problem seems to have gone away! Perhaps the original bug has been fixed, but I'll leave the post-up commands in for now.
Could you post your interfaces file? I will update the tutorial and post your method instead. Seems a lot simpler. Thanks.

[gladstone]

Just simply adding

post-up iface down
post-up iface up

to the end, like:

auto lo
iface lo inet loopback

auto eth1
iface eth1 inet static
address 192.168.1.2
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid Toupe
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk [MY HASHED PSK]
post-up iface down
post-up iface up

Connecting works fine, although the problem with the IPW2200 driver nearing 100% CPU usage is inconclusive as it's happening randomly (when I reboot, it's fine)

[Tex-Twil]

Hello,
I have problems with using wpa_supplicant with my R8187 card:


root@xx:~# wpa_supplicant -Dipw -iwlan0 -c/etc/wpa_supplicant.conf
Trying to associate with 00:13:f7:01:b9:e1 (SSID='SMC_Chaloupka' freq=0 MHz)
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:13:f7:01:b9:e1 (SSID='SMC_Chaloupka' freq=0 MHz)
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:13:f7:01:b9:e1 (SSID='SMC_Chaloupka' freq=0 MHz)
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys


any ideas ?

[wieman01]

Hello,
I have problems with using wpa_supplicant with my R8187 card:


root@xx:~# wpa_supplicant -Dipw -iwlan0 -c/etc/wpa_supplicant.conf
Trying to associate with 00:13:f7:01:b9:e1 (SSID='SMC_Chaloupka' freq=0 MHz)
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:13:f7:01:b9:e1 (SSID='SMC_Chaloupka' freq=0 MHz)
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:13:f7:01:b9:e1 (SSID='SMC_Chaloupka' freq=0 MHz)
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys


any ideas ?
This has nothing to do with this tutorial, hence I cannot help much. But one thing I have noticed:
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
That normally means that your hardware does not support WPA or the use of wpa_supplicant. Now use another driver as "ipw" has been deprecated:
wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
"wext" will do for "ndiswrapper".

[Tex-Twil]

Hello,

This has nothing to do with this tutorial, hence I cannot help much.

Sorry, I thought this was the right thread for this question.


"wext" will do for "ndiswrapper".


I've allready tried this before and here is the output:


root@xx:~# wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
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 -



Btw, my card is and Alfa Awus36H.

Thanks for you help.

[wieman01]

Hello,


Sorry, I thought this was the right thread for this question.



I've allready tried this before and here is the output:


root@xx:~# wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
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 -



Btw, my card is and Alfa Awus36H.

Thanks for you help.
No problem.

I have seen this error message before. Does the Windows driver that you are using really support WPA? Could you check the change-log please?

[Tex-Twil]

No problem.
I have seen this error message before. Does the Windows driver that you are using really support WPA? Could you check the change-log please?

Hi,
Yes, on Windows XP/Vista WPA is ok. FYI, I'm using patched drivers from aircrack :

http://www.aircrack-ng.org/doku.php?id=r8187

The readme of the original drivers says that WPA is supported


- Support WEP and WPAPSK connection]


Maybe I can try to recompile the drivers, without patching them and see what will happen.

see ya.

[wieman01]

Hi,
Yes, on Windows XP/Vista WPA is ok. FYI, I'm using patched drivers from aircrack :

http://www.aircrack-ng.org/doku.php?id=r8187

The readme of the original drivers says that WPA is supported



Maybe I can try to recompile the drivers, without patching them and see what will happen.

see ya.
Do you use "ndiswrapper" at all? The drivers shows as "wlan0". Weird.

[Tex-Twil]

Do you use "ndiswrapper" at all? The drivers shows as "wlan0". Weird.

Not as far as I know ... :confused:

[wieman01]

Not as far as I know ... :confused:
Did you check out TKIP (WPA1) as well? Might be an option. If that does not work, you will need to recompile... :-(

[Tex-Twil]

Did you check out TKIP (WPA1) as well? Might be an option.
What do you mean ?

[wieman01]

What do you mean ?
Rather than using WPA2 (AES) you could also configure the router and card to use WPA (TKIP). Sometimes that makes a difference. Some cards & drivers can do WPA (TKIP) but not WPA2.

There is an example for WPA given in the tutorial.

[Tex-Twil]

Rather than using WPA2 (AES) you could also configure the router and card to use WPA (TKIP). Sometimes that makes a difference. Some cards & drivers can do WPA (TKIP) but not WPA2.

There is an example for WPA given in the tutorial.
ok. The router is configured to "'TKIP+AES(WPA/WPA2)". The other option is "WPA2 only" so I presume it is on WPA now.

[wieman01]

ok. The router is configured to "'TKIP+AES(WPA/WPA2)". The other option is "WPA2 only" so I presume it is on WPA now.
That should do. Now you can try this script - assuming that SSID broadcast it turned on:
auto wlan0
iface wlan0 inet dhcp
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>

[Tex-Twil]

That should do. Now you can try this script - assuming that SSID broadcast it turned on:
Hi,
I think there is something I missed cos I don't have the commands "auto wlan0" , "wpa-ssid" ...

[wieman01]

Hi,
I think there is something I missed cos I don't have the commands "auto wlan0" , "wpa-ssid" ...
Oh oh... Then could you post your stuff instead? Let's see what's going on.

[Tex-Twil]

Oh oh... Then could you post your stuff instead? Let's see what's going on.
My stuff ??

[wieman01]

My stuff ??
This file:
sudo gedit /etc/network/interfaces
There must be something wrong I suppose.

[Tex-Twil]

This file:

There must be something wrong I suppose.
Ah sorry. I was triyng to run those commands in a sheel instead of writing them to the /etc/network/interfaces file. Well here is the result of your script. I commented all other interfaces and let only wlan0 :


root@xx:~# sudo /etc/init.d/networking 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 - 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.


then dhclient keeps on trying to get something but obviously something went wrong before ...

[wieman01]

Please post the contents as well:
sudo gedit /etc/network/interfaces
This does not look promising at the moment.

[Tex-Twil]

Hi,
well the content is what you told me to write inside ;) i.e. :


auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid mySSID
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk myHexKeyWhichIsVeryLong



I commented all the other interfaces except the loopback

auto lo
iface lo inet loopback

#auto eth0
#iface eth0 inet dhcp

The error is the same when I use wpa_supplicant:


ioctl[SIOCSIWENCODEEXT]: Operation not supported

[wieman01]

Hi,
well the content is what you told me to write inside ;) i.e. :


auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid mySSID
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk myHexKeyWhichIsVeryLong



I commented all the other interfaces except the loopback

auto lo
iface lo inet loopback

#auto eth0
#iface eth0 inet dhcp

The error is the same when I use wpa_supplicant:


ioctl[SIOCSIWENCODEEXT]: Operation not supported


Alright then. :-) It now appears that the Windows driver does not support WPA or does not really work well together with "ndiswrapper". Sorry about that... :-(

[Tex-Twil]

Alright then. :-) It now appears that the Windows driver does not support WPA
But why are you talkning about the windows driver ? I'm using the RTL8187 Linux driver version 1.1

[wieman01]

But why are you talkning about the windows driver ? I'm using the RTL8187 Linux driver version 1.1
Sorry, confused it with another thread. Yes, your current driver I mean.

What chipset has it got by the way?

[Tex-Twil]

well .. my card (Alfa Awus036H) has a Realtek chipset ... rtl8187 :)

[wieman01]

well .. my card (Alfa Awus036H) has a Realtek chipset ... rtl8187 :)
Tough luck. I don't think it supports WPA at all... WEP is ok, isn't it?

[Tex-Twil]

Tough luck. I don't think it supports WPA at all... WEP is ok, isn't it?

Yep, WEP is ok. But as I said in a previous post, according to the readme file of the drivers, WPA should be supported. Strange.

[wieman01]

Yep, WEP is ok. But as I said in a previous post, according to the readme file of the drivers, WPA should be supported. Strange.
This might call for "ndiswrapper" perhaps. I could not find anything relating to Reaktek & WPA on Google either.

[mart78]

hello everyone ;)

like most other people in this thread i need some help and advice with my wlan setup.
i have an ibm x30 with a intersil prism II 2.5 wavelan mini-pci card running gutsy that i want to get running with wpa if possible.
i know that the prism 2.5 doesn't support wpa by itself so i flashed it with new primary and station firmware as i read that many people got these cards to work with wpa after the update.

the update went all good, the card is running find in unsecured wlan s but wpa is still giving me a hard time.

at first i tried with the network manager, then with a wpa_supplicant.conf and finally i found the howto on here, but none of it worked so far.

here is the wlan part of my /etc/network/interfaces

auto wlan0
iface wlan0 inet static
address 192.168.0.25
gateway 192.168.0.1
dns-nameservers 192.168.0.1
netmask 255.255.255.0
wpa-driver hostap
wpa-ssid OpenWRT
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 00csa0d0aw0asd0a9sd09as0 (the scrambled version of my key)

i noticed that iwlist scan reports the Group Cipher to be WEP-40 no matter what i set in my wrt. i saw someone reported this earlier in this thread but i couldn't find any additional info. might this (= gutsy) be the source of my wpa problems?

my main concern is to find out whether there is a chance that i'll succeed getting the prism card to run with wpa or if i'd be better off buying a new one as wlan without wpa is of no use for me. but by now i couldn't even locate the source of my wpa problem so I'd be greatful for any support ....

[wieman01]

hello everyone ;)

like most other people in this thread i need some help and advice with my wlan setup.
i have an ibm x30 with a intersil prism II 2.5 wavelan mini-pci card running gutsy that i want to get running with wpa if possible.
i know that the prism 2.5 doesn't support wpa by itself so i flashed it with new primary and station firmware as i read that many people got these cards to work with wpa after the update.

the update went all good, the card is running find in unsecured wlan s but wpa is still giving me a hard time.

at first i tried with the network manager, then with a wpa_supplicant.conf and finally i found the howto on here, but none of it worked so far.

here is the wlan part of my /etc/network/interfaces

i noticed that iwlist scan reports the Group Cipher to be WEP-40 no matter what i set in my wrt. i saw someone reported this earlier in this thread but i couldn't find any additional info. might this (= gutsy) be the source of my wpa problems?

my main concern is to find out whether there is a chance that i'll succeed getting the prism card to run with wpa or if i'd be better off buying a new one as wlan without wpa is of no use for me. but by now i couldn't even locate the source of my wpa problem so I'd be greatful for any support ....
Hello,

If your card does not recognize your WPA settings as such, there is a pretty good chance that it does not support it. Your interfaces is referred to as "wlan0"... Am I right in that you have installed it using "ndiswrapper"? If so, replacing the most recent Windows driver with the latest one (check the vendor's web site for details) would be a sensible thing to do. As it appears the current driver is flawed. That could be the source of your problems.

Post here if you need further support.

[Marcellus]

Hi -- another stumped newbie here.

With the search I've not succeeded in finding it in the 50+ pages of this topic; If I overlooked it, my sincerest apologies.

I have a practical problem in that wifi is my ONLY connection to the outside world --- I have a 1997 laptop with telephone-port (but no telephone internet in sight) and my wifi is WPA2. So, getting files off the 'net onto the lappy is a struggle.

I've followed the recipe I think -- dhcp because my functioning laptop has that setting --- cat /etc/network/interfaces gives me
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid radiogauguin
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 4a37-----deleted-password-in-hex------------e728

But the <restart> just gives failures. Is the problem that
cat /etc/modprobe.d/ndiswrapper
cat: /etc/modprobe.d/ndiswrapper: No such file or directory

possibly? Is it uninstalled? How do I install it (add/remove programmes ---> that seems to only talk about a GUI on top of it or am I wrong?)
Once I know what I'm doing I can go find a WEP or passwordless access point (but I have to ask nicely -- no battery in old laptop, so wardriving not an option outside of its illegality). This takes time, so I want to have a reasonable chance of success before I go.

[wieman01]

Hi -- another stumped newbie here.

With the search I've not succeeded in finding it in the 50+ pages of this topic; If I overlooked it, my sincerest apologies.

I have a practical problem in that wifi is my ONLY connection to the outside world --- I have a 1997 laptop with telephone-port (but no telephone internet in sight) and my wifi is WPA2. So, getting files off the 'net onto the lappy is a struggle.

I've followed the recipe I think -- dhcp because my functioning laptop has that setting --- cat /etc/network/interfaces gives me


But the <restart> just gives failures. Is the problem that

possibly? Is it uninstalled? How do I install it (add/remove programmes ---> that seems to only talk about a GUI on top of it or am I wrong?)
Once I know what I'm doing I can go find a WEP or passwordless access point (but I have to ask nicely -- no battery in old laptop, so wardriving not an option outside of its illegality). This takes time, so I want to have a reasonable chance of success before I go.
"wlan0" may not be the right interface name. "wlan0" is usually used by "ndiswrapper" (if you don't know what it is, ignore the comment), hence I doubt it is the right one.

Please do a scan for me and let me know which interfaces (e.g. eth1) return scan results (i.e. networks around you):
sudo iwlist scan
What wireless adapter have you got?

[ebozzz]

I just wanted to say thank you to the OP. As a first time laptop user and also the first time that I have had wireless as a part of my network configuration, I just knew that I would have to use the info inside this thread. Well, I am happy to say that it wasn't needed! I am posting via my WLAN connection now. No configuration was required but I am glad that this resource was available if needed. =D>

My Setup:

Dell Vostro 1500
Intel 3945a/b/g
Ubuntu Studio 7.10 Gutsy Gibbons
Netgear WNR834B RangeMax NEXT Wireless-N Router
WPA2


eth1 Scan completed :
Cell 01 - Address:**:**:**:**:**:**
ESSID:"<hidden>"
Protocol:IEEE 802.11bg
Mode:Master
Channel:6
Frequency:2.437 GHz (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=-31 dBm Noise level=-31 dBm
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 28ms ago

[houms]

Hi -- another stumped newbie here.

With the search I've not succeeded in finding it in the 50+ pages of this topic; If I overlooked it, my sincerest apologies.

I have a practical problem in that wifi is my ONLY connection to the outside world --- I have a 1997 laptop with telephone-port (but no telephone internet in sight) and my wifi is WPA2. So, getting files off the 'net onto the lappy is a struggle.

I've followed the recipe I think -- dhcp because my functioning laptop has that setting --- cat /etc/network/interfaces gives me


But the <restart> just gives failures. Is the problem that

possibly? Is it uninstalled? How do I install it (add/remove programmes ---> that seems to only talk about a GUI on top of it or am I wrong?)
Once I know what I'm doing I can go find a WEP or passwordless access point (but I have to ask nicely -- no battery in old laptop, so wardriving not an option outside of its illegality). This takes time, so I want to have a reasonable chance of success before I go.

The first thing I notice is that you have dhcp instead of static..... are you trying to set a static ip for your laptop ? Based on my experience your line should look like this
auto wlan0 iface
wlan0 inet static
Also is your router set to broadcast its ssid, if not you should also change ap scan to 2

I would try this for you interface....if its wlan0
auto wlan0 iface
wlan0 inet static
address yourip
netmask 255.255.255.0
gateway yourgateway
wireless-essid yourssid
wpa-driver wext
wpa-ssid yourssid
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk yourhexkeyhere

please post your output for these two commands
ifconfig
iwconfig

Also what kind of wireless card are you using?

[mart78]

Hello,

If your card does not recognize your WPA settings as such, there is a pretty good chance that it does not support it. Your interfaces is referred to as "wlan0"... Am I right in that you have installed it using "ndiswrapper"? If so, replacing the most recent Windows driver with the latest one (check the vendor's web site for details) would be a sensible thing to do. As it appears the current driver is flawed. That could be the source of your problems.

Post here if you need further support.

Hi, I'm not using ndiswrapper as the Prism 2.5 card is supported by the hostap driver and this gives me a wlan0 and a wifi0 interface.
Here's the output of iwlist scan (i omitted the non wlan parts):

wifi0 Scan completed :
Cell 01 - Address: 00:16:B8:40:D3:C5
ESSID:"OpenWrtWLAN"
Mode:Master
Frequency:2.412 GHz (Channel 1)
Encryption key:on
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : TKIP WEP-40
Authentication Suites (1) : PSK

wlan0 Scan completed :
Cell 01 - Address: 00:16:B8:40:D3:C5
ESSID:"OpenWrtWLAN"
Mode:Master
Frequency:2.412 GHz (Channel 1)
Encryption key:on
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : TKIP WEP-40
Authentication Suites (1) : PSK

it seems that gutsy still reports the Group Cipher to be always WEP-40 eventhough OpenWRT usually sets the Group Cipher to the same as the configured Pairwise Cipher.

As of now i have read about several other people who got WPA running with the Prism 2.5 Chipset following the instructions on http://linux.junsun.net/intersil-prism/ and i see no reason why it shouldn't work for me besides the wrong Group Cipher mentioned above.
Is there a way I can set the Group Cipher manually or a method how I can track down my problem?

[ToohTaah]

My wifi connection at home is using WEP, but it is WPA2 at my friend's place. I am wondering if there is a command line to connect WPA2 network at my friend's.

Thanks

[mart78]

My wifi connection at home is using WEP, but it is WPA2 at my friend's place. I am wondering if there is a command line to connect WPA2 network at my friend's.

Thanks

I'm relatively new to the whole wlan stuff but I wouldn't know of a simple command line that would do that. Afaik you have to either enter the parameters of your friends network into /etc/network/interfaces or create a wpa_supplicant.conf file which is basically the same as i see it.

Why don't you use the Network Manager? It supports network profiles, so you can configure your box for different networks and just select the one you want to use. Besides my wpa problems mentioned in my last post the Network Manager works really good for me....

[ToohTaah]

The thing is, as I said before, I am usually connect to wep network, and sometimes (once a week) I will connect to wpa2 network. Will putting wpa2 parameters in /etc/network/interfaces or wpa_supplicant.conf have no problem even I start my laptop in my home network (wep)?

[ToohTaah]

I just found that I can use "sudo wpa_supplicant -iath0 -c/etc/wpa_supplicant.conf -Dmadwifi " to connect to wpa2 network, so my problem has been solved...

[wieman01]

I just found that I can use "sudo wpa_supplicant -iath0 -c/etc/wpa_supplicant.conf -Dmadwifi " to connect to wpa2 network, so my problem has been solved...
I recommend Network Manager to all Laptop (mobile) users. But good to hear the mentioned method works for you. Network Manager might make things even simpler.

[afterburnerbg]

I recommend Network Manager to all Laptop (mobile) users. But good to hear the mentioned method works for you. Network Manager might make things even simpler.

I am using Network Manager on Gutsy with a Dell Inspiron 6400. It's with the firmware that comes for the bcm43xx card within the Gutsy distribution from the Restricted Drivers Manager. It works OK @ home (Linksys WRT54gl) but the speed is somewhat low - about 8-10Mbit/s, when the card is working in 24Mbit/s mode. Also, very often when I try to connect to some other network, when I choose the network, the manager tries to connect, but after some time (if the network for exemple only authorises by MAC address, so it does not return a dhcp offer) the network manager causes the bcm43xx module to stop functioning - the light representing the wireless on the laptop stops. Even if I do rmmod bcm43xx and then modprobe bcm43xx there is no difference - I have to restart the whole machine to make it work again. It would be nice if that does not happen. Is this the usual behaviour of network manager, or should I report a bug?

I'd be very grateful if someone answers, cuz I'm somewhat new to Ubuntu and linux.

[wieman01]

I am using Network Manager on Gutsy with a Dell Inspiron 6400. It's with the firmware that comes for the bcm43xx card within the Gutsy distribution from the Restricted Drivers Manager. It works OK @ home (Linksys WRT54gl) but the speed is somewhat low - about 8-10Mbit/s, when the card is working in 24Mbit/s mode. Also, very often when I try to connect to some other network, when I choose the network, the manager tries to connect, but after some time (if the network for exemple only authorises by MAC address, so it does not return a dhcp offer) the network manager causes the bcm43xx module to stop functioning - the light representing the wireless on the laptop stops. Even if I do rmmod bcm43xx and then modprobe bcm43xx there is no difference - I have to restart the whole machine to make it work again. It would be nice if that does not happen. Is this the usual behaviour of network manager, or should I report a bug?

I'd be very grateful if someone answers, cuz I'm somewhat new to Ubuntu and linux.
No, how could that be normal? I would file a bug immediately if I were you.

[afterburnerbg]

No, how could that be normal? I would file a bug immediately if I were you.

When I said normal, I meant that this may be a known bug ;) It doesn't matter, I just submitted a bug report, thanks again! :)

[LordMau]

Some users reported (including myself) that the network has to be restarted every time after startup... Apparently this is a bug.

Here is a workaround that helps restart the network during boot so that one does not have to do it manually after logging on to the system.

Create startup script:

Add this line & save file:

Change permission (executable):

Create symbolic link:

[Note: You may have to choose a boot sequence other than S40.]

Restart...

I have the same issue under 7.10 with an airlink101 / RT61 wifi pci card. In lieu of that script I experimented with adding a pre-up command in the /etc/network/interface file itself as so:

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid ##########
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk #############3
pre-up dhclient wlan0

Pretty consistent so far, if for any reason though if you manually restart the network it will take a bit longer as the dhcp server seems to go twice before accepting a new lease (I use a static dhcp server).

[wieman01]

@LordMau:

Thanks for letting us know. This has been highlighted by another user as well, so I should really update the guide. Will do so soon, have not had the time so far.

[adbrown]

Following this guide is the only way I have managed to get WPA2 working with static ip. However I seem to have hampered my laptop so that it only works properly when the network is turned on. With it turned off the network card seems to be scanning all the time for the non existent network. Going through all of the posts I have seen a suggestion that I should try configuring using network-manager. Does anyone have a good guide for this - I have tried the wiki entry (https://help.ubuntu.com/community/WifiDocs/WPAHowTo?highlight=%28wpa%29) with little success.

ta

a

[wieman01]

Following this guide is the only way I have managed to get WPA2 working with static ip. However I seem to have hampered my laptop so that it only works properly when the network is turned on. With it turned off the network card seems to be scanning all the time for the non existent network. Going through all of the posts I have seen a suggestion that I should try configuring using network-manager. Does anyone have a good guide for this - I have tried the wiki entry (https://help.ubuntu.com/community/WifiDocs/WPAHowTo?highlight=%28wpa%29) with little success.

ta

a
No idea if Network Manager supports the use of static IP yet. I seriously doubt it.

WICD might be an option for you:

http://wicd.sourceforge.net/

[jcsaintpo]

I try installing wpa on my laptop!
i use xubuntu 6.06.1 because only 64ram

i tried the gedit commands, but it didn't work!
is there an other way i must handle?

[wieman01]

I try installing wpa on my laptop!
i use xubuntu 6.06.1 because only 64ram

i tried the gedit commands, but it didn't work!
is there an other way i must handle?
Good question... you can try...
sudo nano /etc/network/interfaces
...instead. "gedit" is Gnome's text editor. Since you are running Xubuntu, it is not available. Sorry for not having mentioned that.

[adbrown]

No idea if Network Manager supports the use of static IP yet. I seriously doubt it.

WICD might be an option for you:

http://wicd.sourceforge.net/

Thanks very much, WICD did work for me - it enabled me to remove the line
auto eth1
from my interfaces file and I can now use WICD to switch the network on and off - so can other users without the root password

[jcsaintpo]

Good question... you can try...

...instead. "gedit" is Gnome's text editor. Since you are running Xubuntu, it is not available. Sorry for not having mentioned that.

It worked!

But i used a simpler way to programme wpa (found here (http://forum.ubuntu-nl.org/message/123169#p123169))



iface ra0 inet dhcp
pre-up ifconfig ra0 up
pre-up ifconfig ra0 down
pre-up ifconfig ra0 up
pre-up ifconfig ra0 down
pre-up iwconfig ra0 essid “Naam_van_je_netwerk�
pre-up iwconfig ra0 mode Managed
pre-up iwpriv ra0 set AuthMode=WPAPSK
pre-up iwpriv ra0 set EncrypType=TKIP
pre-up iwpriv ra0 set WPAPSK=� Wachtwoord_van_je_netwerk�
pre-up ifconfig ra0 up
auto ra0




after restarting i was immediately online

[wieman01]

It worked!

But i used a simpler way to programme wpa (found here (http://forum.ubuntu-nl.org/message/123169#p123169))



iface ra0 inet dhcp
pre-up ifconfig ra0 up
pre-up ifconfig ra0 down
pre-up ifconfig ra0 up
pre-up ifconfig ra0 down
pre-up iwconfig ra0 essid “Naam_van_je_netwerk�
pre-up iwconfig ra0 mode Managed
pre-up iwpriv ra0 set AuthMode=WPAPSK
pre-up iwpriv ra0 set EncrypType=TKIP
pre-up iwpriv ra0 set WPAPSK=� Wachtwoord_van_je_netwerk�
pre-up ifconfig ra0 up
auto ra0




after restarting i was immediately online
You have a Ralink wireless adapter. My approach wouldn't work for you anyway...

[jimisdead]

I have an old laptop that I use as a file/printer/everything server, that is currently connected via ethernet by a large ugly cable trailled through my apartment.

I want to change it to use a spare netgear wireless usb card, which after updating to gutsy I now see is supported - and is automatically shown as wlan0 when plugged in.

without further ado here is my /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 static
address 192.168.2.2
netmask 255.255.255.0
network 192.168.2.0
broadcast 192.168.2.255
dns-nameservers 192.168.2.1

gateway 192.168.2.1

auto wlan0
iface wlan0 inet static
address 192.168.2.10
gateway 192.168.2.1
dns-nameservers 192.168.2.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid MYNETWORKSSID
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk MYNETWORKKEYKEYKEY




if I boot this this config I can ping and ssh into either 192.168.2.2 or 192.168.2.10 and everything is great. If I then unplug the ethernet cable I can not ping 192.168.2.2 anymore (obviously), but nor can I ping 192.168.2.10 - and I can't get any network connection from the serverside either..

... Does anyone have any idea what is going on?


*this was all down while the ethernet cable was still plugged in*
*SSIDNAME* is my SSID
user@server:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0
0.0.0.0 192.168.2.1 0.0.0.0 UG 100 0 0 wlan0
0.0.0.0 192.168.2.1 0.0.0.0 UG 100 0 0 eth0
user@server:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

user@server:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:02:A5:B5:76:CA
inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::202:a5ff:feb5:76ca/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:331 errors:0 dropped:0 overruns:0 frame:0
TX packets:424 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:30499 (29.7 KB) TX bytes:65646 (64.1 KB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets: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:0F:B5:90:B6:E6
inet addr:192.168.2.10 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wmaster0 Link encap:UNSPEC HWaddr 00-0F-B5-90-B6-E6-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

user@server:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 No scan results

user@server:~$ iwlist scanning
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 No scan results

user@server:~$ sudo iwlist wlan0 scanning
[sudo] password for user:
wlan0 Scan completed :
Cell 01 - Address: 00:1C:4A:D0:F2:8A
ESSID:"FRITZ!Box Fon WLAN 7141"
Mode:Master
Channel:6
Frequency:2.437 GHz
Signal level=25/100
Encryption key:on
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) : TKIP
Authentication Suites (1) : PSK
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=000001a7444d8206
Cell 02 - Address: 00:12:BF:5F:15:B3
ESSID:"SSIDNAME"
Mode:Master
Channel:11
Frequency:2.462 GHz
Signal level=57/100
Encryption key:on
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Preauthentication Supported
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:tsf=000000302c561427

user@server:/etc$ more resolv.conf
nameserver 192.168.2.1

[wieman01]

@jimisdead:

What happens when you reboot with the Ethernet cable unplugged? Please do so and post the results of (after you have rebooted):
sudo ifdown -v wlan0
sudo ifup -v wlan0

[jimisdead]

@jimisdead:

What happens when you reboot with the Ethernet cable unplugged? Please do so and post the results of (after you have rebooted):

After reboot it still has not network access.

ifdown wlan0 -v (i had to redirect stdout and stderr since it had no net access)

ryan@orwell:~$ more wlandown
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 5273).
ryan@orwell:~$ more wlandownerr
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.2.1 metric 100 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

ifup wlan0 -v
ryan@orwell:~$ more wlanup
OK
ryan@orwell:~$ more wlanuperr
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
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 -
ifconfig wlan0 192.168.2.10 netmask 255.255.255.0 up
route add default gw 192.168.2.1 metric 100 wlan0
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/wpasupplicant

[dannytherocker]

It worked!

But i used a simpler way to programme wpa (found here (http://forum.ubuntu-nl.org/message/123169#p123169))



iface ra0 inet dhcp
pre-up iwconfig ra0 essid “Naam_van_je_netwerk�
pre-up iwconfig ra0 mode Managed
pre-up iwpriv ra0 set AuthMode=WPAPSK
pre-up iwpriv ra0 set EncrypType=TKIP
pre-up iwpriv ra0 set WPAPSK=� Wachtwoord_van_je_netwerk�
pre-up ifconfig ra0 up
auto ra0




after restarting i was immediately online


Does this approach work on Gutsy ??? It does on Feisty....yesterady I had to get back to feisty after an upgrading because wless did not work and I forgot to try this approach....

[wieman01]

@jimisdead:

ioctl[SIOCSIWAUTH]: Operation not supported
You card does not seem to support WPA2. Please try WPA1 (WPA, TKIP) instead. That might do.

[wieman01]

Does this approach work on Gutsy ??? It does on Feisty....yesterady I had to get back to feisty after an upgrading because wless did not work and I forgot to try this approach....
It should as far as I know. But frankly I never got WPA to work using this method.

[dannytherocker]

It should as far as I know. But frankly I never got WPA to work using this method.


I can guarantee WPA does work using the approach above....I'm only afraid to install Gutsy again without having wless working....

[jimisdead]

@jimisdead:


You card does not seem to support WPA2. Please try WPA1 (WPA, TKIP) instead. That might do.

thanks for the reply.

but I get the same deal as before. :(

[wieman01]

thanks for the reply.

but I get the same deal as before. :(
Can you tell me more about your hardware & driver? Perhaps the driver is the culprit.

[jimisdead]

It's a netgear WG111 (http://www.netgear.com/Products/Adapters/GWirelessAdapters/WG111.aspx) 54Mbps USB dongle. plugged into an old compaq evo laptop running fully updated gutsy.

I've tried the wext and the madwifi driver, neither has worked.

[wieman01]

It's a netgear WG111 (http://www.netgear.com/Products/Adapters/GWirelessAdapters/WG111.aspx) 54Mbps USB dongle. plugged into an old compaq evo laptop running fully updated gutsy.

I've tried the wext and the madwifi driver, neither has worked.
I guess you will have to do some googling on the web and try to find out if others have been able to set it up using WPA. I'll try to find something useful as well.

[AZzKikR]

Recently upgraded to Gutsy. I have a Linksys card, RT2500 chipset. My previous /etc/network/interfaces could not be used to authenticate myself using this type of scheme:
iface ra0 inet dhcp
pre-up iwconfig ra0 essid "networkname"
pre-up iwconfig ra0 mode Managed
pre-up iwpriv ra0 set AuthMode=WPAPSK
pre-up iwpriv ra0 set EncrypType=TKIP
pre-up iwpriv ra0 set WPAPSK="unencryptedpw"
pre-up ifconfig ra0 up
auto ra0

I tried using Ubuntu's network manager which now has a choice to pick WPA1/2 encryption. After doing that, it wrote something different to the /etc/network/interfaces file. It uses the 'wext' driver for instance, and it writes an encrypted WPA password to the file.

After executing `sudo ifup ra0`, I got a few errors ([SIOCSAUTH]: Operation not supported or something like that), but the internet connection was established. After adding `auto ra0` to the file, it even fails to establish a connection during startup. And I think it is because of those errors.

I am going to reinstall Gutsy tonight, perhaps something else was corrupted or the like.

Anyone else had the same thing? I am sorry I cannot post any real samples of the files yet (at work at this moment).

[oobuntu]

Hi,

Just thought it might be helpful to post my experience with setting this up.

I've got an Acer Aspire 5630 laptop and have managed to get the wireless working to my d-com router using WPA2 with the following configuration:

root@our-laptop:/etc/network# cat interfaces
auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid <your-ssid>
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <get this using the wpa_passphrase utility>

#auto eth0

Then after restarting the networking this worked great. Thanks for a great OS and a great forum.

[wieman01]

Hi,

Just thought it might be helpful to post my experience with setting this up.

I've got an Acer Aspire 5630 laptop and have managed to get the wireless working to my d-com router using WPA2 with the following configuration:

root@our-laptop:/etc/network# cat interfaces
auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid <your-ssid>
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <get this using the wpa_passphrase utility>

#auto eth0

Then after restarting the networking this worked great. Thanks for a great OS and a great forum.
TKIP is WPA1 actually. Try AES instead which is the latest WPA(2) standard encryption. But I don't know if your adapter supports it.

[ericderace]

Hi,

I am trying to connect to a University network which is WPA, PEAP, TKIP and PAP/MSCHAPv2. I've tried networkmanager, I've tried editing /etc/network/interfaces... Does not seem to work.

What I believe happens is that it does not authenticate my username and password. It looks like it connects, gives me an IP, the wireless Icon on the laptop keeps flashing, then it disconnects.

Is there any log file or any way to check for authentication problems ?

Thanks,

Eric

[wieman01]

Hi,

I am trying to connect to a University network which is WPA, PEAP, TKIP and PAP/MSCHAPv2. I've tried networkmanager, I've tried editing /etc/network/interfaces... Does not seem to work.

What I believe happens is that it does not authenticate my username and password. It looks like it connects, gives me an IP, the wireless Icon on the laptop keeps flashing, then it disconnects.

Is there any log file or any way to check for authentication problems ?

Thanks,

Eric
Yes, you could do:
sudo ifdown -v <your_interface>
sudo ifup -v <your_interface>

[ericderace]

That doesn't print any information about authentication.

[AZzKikR]

Alright, I installed Gutsy. Everything is working fine I guess, but internet is working flaky.

I have a Linksys PCI card, with Ralink RT2500 chipset. Using the Network Setup utility (System -> Administration -> Network) I was able to get a network connection. WPA1/TKIP. Browsing works fine.

This is my /etc/network/interfaces:
auto lo
iface lo inet loopback


iface wlan0 inet static
address 192.168.1.7
netmask 255.255.255.0
gateway 192.168.1.1
wpa-psk 2c...<my WPA key>... c52
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA
wpa-ssid porrus

auto wlan0


What I notice is:

I no longer have ra0 as interface, but wlan0
It computes a WPA passphrase. Before I had to just put it in plaintext here
It uses wext as a driver here


So what am I complaining about? Well, when I do a manual ifdown/ifup, this is what I see:

krpors@krpors-desktop:~$ sudo ifdown wlan0
[sudo] password for krpors:
krpors@krpors-desktop:~$ sudo ifup wlan0
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - krpors@krpors-desktop:~$

Connection is working nicely though :S At booting the internet connection won't be established and I think this is causing it.

Any ideas? I'm puzzled.

[MartenH]

HI,

I followed this guide to the letter (WPA TKIP-PSK variant) on my linksys WPC54g v2 card. The result? I get several "operation not supported" errors cast by wext and then my computer freezes completely.

Any suggestion? What kind of information/logs should i supply?

//MartenH

[wieman01]

Alright, I installed Gutsy. Everything is working fine I guess, but internet is working flaky.

I have a Linksys PCI card, with Ralink RT2500 chipset. Using the Network Setup utility (System -> Administration -> Network) I was able to get a network connection. WPA1/TKIP. Browsing works fine.

This is my /etc/network/interfaces:
auto lo
iface lo inet loopback


iface wlan0 inet static
address 192.168.1.7
netmask 255.255.255.0
gateway 192.168.1.1
wpa-psk 2c...<my WPA key>... c52
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA
wpa-ssid porrus

auto wlan0


What I notice is:

I no longer have ra0 as interface, but wlan0
It computes a WPA passphrase. Before I had to just put it in plaintext here
It uses wext as a driver here


So what am I complaining about? Well, when I do a manual ifdown/ifup, this is what I see:

krpors@krpors-desktop:~$ sudo ifdown wlan0
[sudo] password for krpors:
krpors@krpors-desktop:~$ sudo ifup wlan0
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - krpors@krpors-desktop:~$

Connection is working nicely though :S At booting the internet connection won't be established and I think this is causing it.

Any ideas? I'm puzzled.
Actually I believe that something is definitely wrong. The Ralink apapter should not work at all using this approach (as highlighted in the tutorial).

When you restart the network (putting the error messages aside for now), is then that you get a working (WPA) connection?

You can get a working connection upon restart if you follow the instructions given in post #2.

[wieman01]

HI,

I followed this guide to the letter (WPA TKIP-PSK variant) on my linksys WPC54g v2 card. The result? I get several "operation not supported" errors cast by wext and then my computer freezes completely.

Any suggestion? What kind of information/logs should i supply?

//MartenH
Well, what chipset has your card got? Broadcom?

That error message usually means that your card does not support WPA i.e. "wext". You could - of course - try other WPA-drivers as well.

You could post this:
sudo ifdown -v <your_interface>
sudo ifup -v <your_interface>
Please also the contents of:
sudo gedit /etc/network/interfaces

[McDuff]

actually, ralink drivers should work in gutsy, since after acception of the new wireless stack in linux, the drivers' maintainers worked hard to get the rt2x00 to work with it. new driver is included in gutsy and works very well for me (wpa driver being wext)
cheers
georg

[wieman01]

actually, ralink drivers should work in gutsy, since after acception of the new wireless stack in linux, the drivers' maintainers worked hard to get the rt2x00 to work with it. new driver is included in gutsy and works very well for me (wpa driver being wext)
cheers
georg
First time I hear of it. Thought the current version in Gutsy is broken. Lots of other forum members can confirm the issue.

Good to hear they are making progress.

[Chuckels550]

This how-to thread didn't just set out how to set up wireless security, it showed how to set up a wireless connection. Can the name of the permanent thread be changed from HOWTO: Wireless Security - WPA1, WPA2, LEAP, etc. to HOW TO: Set UP Wireless Connections?

Looking at the list of people having problems with Network Manager - an application that should have been dropped from the distro - your what I regard as essential HOWTO might cut down on the pounding the forum is taking if people realized that it was not just about secure connections.

And by the way thanks for the HOWTO

[monomaniacpat]

Hello again wieman.

I foolishly decided to upgrade all my packages last night and it has resulted in no more wireless connections for me.

The problem appears to be that the ndiswrapper module is not inserted at boot. It's not listed with lsmod, anyway.

Therefore I have been trying to modprobe ndiswrapper. The first time I tried I got "invalid argument". I searched google for this and someone said they'd got it to work by installing ndiswrapper-common and ndiswrapper-utils. I couldn't find -common in my repos, but I managed to install -utils.

With -utils installed I now get:

Setting up ndiswrapper-utils (1.8-0ubuntu2) ...

patrick@inspiron-8200:~$ sudo modprobe ndiswrapper
Segmentation fault
patrick@inspiron-8200:~$


Do you have any idea what I can do to get it working again?

Thanks for your help prior to today and any adivce - I had it working for several months!

mono.

EDIT: I just looked at lsmod again and ndiswrapper is now listed. Presumably because of the previous terminal command I mentioned where I got the segmentation fault... Still no wireless devices, though.

[monomaniacpat]

EDIT: Don't worry yourself for now. I've just tried using ndiswrapper on the liveCD and it seems to work, so I'll probably just use a fresh install.

Just found this in /var/log/messages:

Oct 27 10:04:45 localhost kernel: [17179611.860000] apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
Oct 27 10:04:45 localhost kernel: [17179611.860000] apm: overridden by ACPI.
Oct 27 10:04:45 localhost loadndisdriver: loadndisdriver: main(544): version 1.9 doesn't match driver version 1.7
Oct 27 10:04:45 localhost kernel: [17179611.980000] ndiswrapper version 1.8 loaded (preempt=yes,smp=no)
Oct 27 10:04:45 localhost loadndisdriver: loadndisdriver: main(544): version 1.9 doesn't match driver version 1.7
Oct 27 10:04:45 localhost kernel: [17179612.016000] ndiswrapper version 1.8 loaded (preempt=yes,smp=no)
Oct 27 10:04:45 localhost loadndisdriver: loadndisdriver: main(544): version 1.9 doesn't match driver version 1.7
Oct 27 10:04:45 localhost kernel: [17179612.052000] ndiswrapper version 1.8 loaded (preempt=yes,smp=no)
Oct 27 10:04:46 localhost kernel: [17179612.380000] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).

[Startacus]

Ok, I am going good on this until the very end. When I run the "wpa_passprhase <myessid> <passphrase>" command I get.

bash: <My ssid>: event not found


Is there something you have to do first for it to work?

I am trying to connect to my router which is WPA, TKIP, SSID No broadcast, DHCP.

Is there anything I'm missing? Thanks.

[monomaniacpat]

Please ignore my earlier posts. I have now reformatted and installed a fresh Gutsy Gibbon. On wireless now! :)

So that's the Linksys WPC11 V.4 working on Gutsy with Ndiswrapper and latest windows NET8180.inf driver. WPA-PSK. :guitar:

[wieman01]

This how-to thread didn't just set out how to set up wireless security, it showed how to set up a wireless connection. Can the name of the permanent thread be changed from HOWTO: Wireless Security - WPA1, WPA2, LEAP, etc. to HOW TO: Set UP Wireless Connections?

Looking at the list of people having problems with Network Manager - an application that should have been dropped from the distro - your what I regard as essential HOWTO might cut down on the pounding the forum is taking if people realized that it was not just about secure connections.

And by the way thanks for the HOWTO
It is about wireless security, nothing else. Or isn't it? I don't really explain how you set up your network & wireless adapter, just how you add security. That's it.

[wieman01]

Ok, I am going good on this until the very end. When I run the "wpa_passprhase <myessid> <passphrase>" command I get.




Is there something you have to do first for it to work?

I am trying to connect to my router which is WPA, TKIP, SSID No broadcast, DHCP.

Is there anything I'm missing? Thanks.
Well, what is your ESSID (wireless network name)? The replace <myessid> with that and it ought to work. :-)

E.g.:
wpa_passprhase default 123456

[wieman01]

Please ignore my earlier posts. I have now reformatted and installed a fresh Gutsy Gibbon. On wireless now! :)

So that's the Linksys WPC11 V.4 working on Gutsy with Ndiswrapper and latest windows NET8180.inf driver. WPA-PSK. :guitar:
Sorry for the late reply. Glad you got it working. Gutsy's Ralink drivers did not work for you I reckon.

[Startacus]

Well, what is your ESSID (wireless network name)? The replace <myessid> with that and it ought to work. :-)

E.g.:

I do, I put my networks SSID instead of <myessid> and I get that error.

If I run the command "iwlist scan" The result under wlan1 is "No scan results."


If I set the Wireless Connection to "roaming" and then go to "Connect to other network" and enter in my information there. The icon switches to bars to show the signal strength but they are all empty and the "wpa_passphrase" command still doesn't work. I am really lost now.

I know the network works because I am typing this message on my XP laptop connected to the same network.

[RandomUsr]

I have two rather weighted questions. First this how-to answered about as many questions as it inpired from myself.

Right now I'm using the Intel iwl4965 on my home network with WPA2 and it's shaky at best. Also I have to re-enter the PSK and restart the driver evey time I start the computer. Is there a way around this?
Keep in mind that I installed no additional software for my network card to work. Using GUTSY

Further, I want to use LEAP w/ 802.11 WEP.

Essentially I want to continue using WPA2 on my home network, and I want to enter Credentials (LEAP) everytime I log on at work using WEP802.11

I'm guessing this might be a hassle have two networks and switching between them?

What options do i have, and which do you recommend?
Looking forward to your thoughts.

[wieman01]

Right now I'm using the Intel iwl4965 on my home network with WPA2 and it's shaky at best. Also I have to re-enter the PSK and restart the driver evey time I start the computer. Is there a way around this?

See post #2.
Further, I want to use LEAP w/ 802.11
WEP.

I'm guessing this might be a hassle have two networks and switching between them?

Best option for you is to use Network Manager or WICD (google for it) which both support LEAP and network profiles (for switching between networks). It should work for you as well.

[RandomUsr]

So, would this only entail installing on of those programs? and Would I need to compile from source or would synaptic do the job?

[wieman01]

Network Manager is part of the default installation.

Instructions for WICD can be found here:

http://wicd.sourceforge.net/download.php

You don't have to compile from source of course.

[RandomUsr]

Any recomendations as far as the shaky behaviour?

PS, How do I start Network manager if it's already installed...

I'm fairly certain that it's not that silly thing running up in the corner that has no support for wireless profiles.

[wieman01]

Any recomendations as far as the shaky behaviour?
Could be due to a number of things. I generally recommend that you adjust & tune the physical settings of your wireless networks. This has worked for me on a number of occasions while I was facing random dropouts. Start off with the default bacon interval and reduce the value. I cannot tell what the culprit is in your case, but you get my point...

[RandomUsr]

Come to think of it I think I know what's going on but I won't be able to test it until a bit later.

Could be due to a number of things. I generally recommend that you adjust & tune the physical settings of your wireless networks. This has worked for me on a number of occasions while I was facing random dropouts. Start off with the default bacon interval and reduce the value. I cannot tell what the culprit is in your case, but you get my point...



Default Bacon? I've always liked a good BLT

[wieman01]

Come to think of it I think I know what's going on but I won't be able to test it until a bit later.

Default Bacon? I've always liked a good BLT
With a bit of Chili & Pepper, definitely!

Beacon interval of course. Let us know what your findings are.

[RandomUsr]

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

--------------------------------------------------------------------------------

Quote:
Originally Posted by wieman01
Well, what is your ESSID (wireless network name)? The replace <myessid> with that and it ought to work.

E.g.:

I do, I put my networks SSID instead of <myessid> and I get that error.

If I run the command "iwlist scan" The result under wlan1 is "No scan results."


If I set the Wireless Connection to "roaming" and then go to "Connect to other network" and enter in my information there. The icon switches to bars to show the signal strength but they are all empty and the "wpa_passphrase" command still doesn't work. I am really lost now.

I know the network works because I am typing this message on my XP laptop connected to the same network.

Startacus, what are the chances you have an AN Intel wi-fi card?

[Startacus]

Startacus, what are the chances you have an AN Intel wi-fi card?

Not very good I'm afraid. I have the Belkin 54g Wireless USB. I think it's F5D7050.

[RandomUsr]

wieman01,

I´m still working on my wireless issues/connectivity etc. I would like some further input if possible.

I want to use the knetwork manager (front end) for gnome, which synaptic states will work with gnome. The issue is that knetwork manager isn´t pulling any data from network manager itself. How can one make knetwork manager play well with gnome and networkmanager so they communicate to one another?


This would be extremely helpful

[helpdeskdan]

GAH! I don't get it! What did I do WRONG? I spent hours trying to get it to work, followed the instruction exactly. Finally, in desperation, I commented out everything and put in:

auto eth0
iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant.conf

with the simplest wpa_supplicant you can imagine - just an ssid and a psk. Worked great! I just don't get it, I didn't even specify a driver!

Any ideas?

I guess if you are having problems, I suggest trying it.

I DID have to create a init.d script (see second post). I did NOT restart networking - too slow. I just did a ifdown etho and an ifup eth0. Works great. Also, use sysvconfig to enable it - that way you don't have to guess the boot sequence. (Wonderful little obscure tool)

[saltydog]

I have an ipw2100 Intel card, and I can't get connected to a WPA-PSK (FKID) wireless router. I have tried with NetworkManager and Wicd either, no way to get thru. The card is perfectly working on Windows, but on Gutsy I have a lot of messages in log, such as this:
"ipw2100: Fatal interrupt. Scheduling firmware restart."

Any suggestion?

[helpdeskdan]

Well, yeah, you and half the internet - try googling it. It's a bug, apparently - you'll have to wait till it's fixed or see if somebody has found a work around.

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/24776

[saltydog]

Well, yeah, you and half the internet - try googling it. It's a bug, apparently - you'll have to wait till it's fixed or see if somebody has found a work around.

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/24776

I have seen the bug before posting here, but as it is there since october 2005 I gave up with the hope to have it fixed. I'm just looking for a workaround, if any...

This is sad. My Windows collegues are laughing. :-(

[wieman01]

GAH! I don't get it! What did I do WRONG? I spent hours trying to get it to work, followed the instruction exactly. Finally, in desperation, I commented out everything and put in:

auto eth0
iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant.conf

with the simplest wpa_supplicant you can imagine - just an ssid and a psk. Worked great! I just don't get it, I didn't even specify a driver!

Any ideas?

I guess if you are having problems, I suggest trying it.

I DID have to create a init.d script (see second post). I did NOT restart networking - too slow. I just did a ifdown etho and an ifup eth0. Works great. Also, use sysvconfig to enable it - that way you don't have to guess the boot sequence. (Wonderful little obscure tool)
What hardware have you got? Does it support WPA at all?

What does a scan yield:
sudo iwlist scan

[wieman01]

I have an ipw2100 Intel card, and I can't get connected to a WPA-PSK (FKID) wireless router. I have tried with NetworkManager and Wicd either, no way to get thru. The card is perfectly working on Windows, but on Gutsy I have a lot of messages in log, such as this:
"ipw2100: Fatal interrupt. Scheduling firmware restart."

Any suggestion?
Mmm... really beats me. What version of Ubuntu are you on? It used to work with the IPW2100.

[wieman01]

I have seen the bug before posting here, but as it is there since october 2005 I gave up with the hope to have it fixed. I'm just looking for a workaround, if any...

This is sad. My Windows collegues are laughing. :-(
What version of Ubuntu are you on?

Does your card recognize the WPA network as such? Do:
sudo iwlist scan

[saltydog]

Mmm... really beats me. What version of Ubuntu are you on? It used to work with the IPW2100.

7.10 Gutsy.
uname -a
Linux Plato 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux


I have also made a complete fresh system reinstall.

[saltydog]

What version of Ubuntu are you on?

Does your card recognize the WPA network as such? Do:

The card recognizes the WPA network, iwlist scan is fine, but it will never get associated. Doesn't get the ip from the dhcp server.

On another WPA-PSK (FKIP) network I can happily get connected, but after booting the laptop I am experiencing this other bug (https://bugs.edge.launchpad.net/ubuntu/+source/wpasupplicant/+bug/160457).

[wieman01]

Could you also post:
sudo gedit /etc/network/interfaces
And this one:
sudo ifdown -v <wireless_interface>
sudo ifup -v <wireless_interface>
Need to go for now. Will check later again.

[saltydog]

Need to go for now. Will check later again.


Strange things happen...

cat /etc/network/interfaces

auto lo
iface lo inet loopback

sudo ifdown -v eth1
ifdown: interface eth1 not configured

sudo ifup -v eth1
Ignoring unknown interface eth1=eth1.

But this is my iwconfig (at the moment the wireless is connected to another network):
iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

irda0 no wireless extensions.

eth1 IEEE 802.11b ESSID:"Saltydog_FM" Nickname:"ipw2100"
Mode:Managed Frequency:2.462 GHz Access Point: 00:14:C1:19:3E:54
Bit Rate=11 Mb/s Tx-Power:16 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=100/100 Signal level=-43 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:1 Missed beacon:0

[helpdeskdan]

Are you using the latest firmware? I've heard that helps.
http://ipw2100.sourceforge.net/

[saltydog]

Are you using the latest firmware? I've heard that helps.
http://ipw2100.sourceforge.net/

I am using Gutsy's firmware ipw2100-1.3-p.fw

[wieman01]

Strange things happen...

cat /etc/network/interfaces

auto lo
iface lo inet loopback

sudo ifdown -v eth1
ifdown: interface eth1 not configured

sudo ifup -v eth1
Ignoring unknown interface eth1=eth1.

But this is my iwconfig (at the moment the wireless is connected to another network):
iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

irda0 no wireless extensions.

eth1 IEEE 802.11b ESSID:"Saltydog_FM" Nickname:"ipw2100"
Mode:Managed Frequency:2.462 GHz Access Point: 00:14:C1:19:3E:54
Bit Rate=11 Mb/s Tx-Power:16 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=100/100 Signal level=-43 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:1 Missed beacon:0
Let's see... If you add these to lines to "/etc/network/interfaces" and reboot, are you able to connect?
auto eth1
iface eth1 inet dhcp

I know that NM requires you to remove your interface information, but somehow sometimes it helps to add it. An unpleasant experience I made recently.

So what happens after a restart?

[saltydog]

Let's see... If you add these to lines to "/etc/network/interfaces" and reboot, are you able to connect?

I know that NM requires you to remove your interface information, but somehow sometimes it helps to add it. An unpleasant experience I made recently.

So what happens after a restart?

Mmmh... nothing good happens. NM gets angry, and after a networking restart this is the output:
Listening on LPF/eth1/00:0c:f1:2b:cc:b9
Sending on LPF/eth1/00:0c:f1:2b:cc:b9
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15

[wieman01]

Odd... Could you do another network restart please? After having added those 2 lines:
sudo ifdown -v eth1
sudo ifup -v eth1
And another scan:
sudo iwlist scan

[saltydog]

Odd... Could you do another network restart please? After having added those 2 lines:
And another scan:

Here it is. After having added thos two lines:
sudo ifdown -v eth1

Configuring interface eth1=eth1 (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
dhclient3 -r -pf /var/run/dhclient.eth1.pid -lf /var/lib/dhcp3/dhclient.eth1.leases eth1
There is already a pid file /var/run/dhclient.eth1.pid with pid 5350
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:0c:f1:2b:cc:b9
Sending on LPF/eth1/00:0c:f1:2b:cc:b9
Sending on Socket/fallback
DHCPRELEASE on eth1 to 192.168.1.1 port 67
ifconfig eth1 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



sudo ifup -v eth1
Configuring interface eth1=eth1 (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

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.eth1.pid -lf /var/lib/dhcp3/dhclient.eth1.leases eth1
There is already a pid file /var/run/dhclient.eth1.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:0c:f1:2b:cc:b9
Sending on LPF/eth1/00:0c:f1:2b:cc:b9
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 9
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
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


sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:14:C1:19:3E:54
ESSID:"Saltydog_FM"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Frequency:2.462 GHz (Channel 11)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 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 Signal level:0 Noise level:0
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : TKIP WEP-40
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : TKIP WEP-40
Authentication Suites (1) : PSK
Extra: Last beacon: 3932ms ago

irda0 Interface doesn't support scanning.


iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 unassociated ESSID:off/any Nickname:"ipw2100"
Mode:Managed Channel=0 Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:16 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

irda0 no wireless extensions.

[wieman01]

@Saltydog:

I believe your card is fine. I cannot explain why NM does not pick it up i.e. is able to connect to your WPA network, however, have you tried this tutorial yet?

You could remove NM entirely and configure your WPA network manually. Use WPA-TKIP and make sure the router is set to WPA-TKIP as well (not WPA2). Then restart the network as described above (verbose) and post the results along with "/etc/network/interfaces".

I think that's the only way we could get it up & running right now...

[saltydog]

@Saltydog:

I believe your card is fine. I cannot explain why NM does not pick it up i.e. is able to connect to your WPA network, however, have you tried this tutorial yet?

..

I didn't try yet without NM as I am often moving with my lap from one location to others and I need several different configurations active. 2 or 3 of my locations are WEP, and other 2 are WPA-PSK. I don't know how to handle multiple locations without NM.

[wieman01]

I didn't try yet without NM as I am often moving with my lap from one location to others and I need several different configurations active. 2 or 3 of my locations are WEP, and other 2 are WPA-PSK. I don't know how to handle multiple locations without NM.
I see... then that's not an option either.

What are the exact symptoms when you say NM refuses to connect? And what are the exact router settings? WPA or WPA2?

Please make sure the router is set to WPA(1) and TKIP, then try to connect once again. Please whatever findings you have here.

Another tool I can recommend is Wifi-Radar which is also in the repositories.

[saltydog]

The most critical access point is the one I have at work. It is a LinkSys (don't remember the model) and it is set to WPA2-PSK and TKIP. NM tries to connect and then ask for password. I enter the right password then NM's icon starts looking for connection, then it asks again for password and so on.

In that case I have several of this lines in dmesg:
ipw2100: Fatal interrupt. Scheduling firmware restart

[wieman01]

WPA2-TKIP is a rather unusual setting, because TKIP is actually part of the WPA1 suite, although WPA2 is downwards compatible. That might explain why NM does not like it.

That said it could also relate to a bug as mentioned earlier. I found this as well:

http://bughost.org/bugzilla/show_bug.cgi?id=329

Have you been able to connect with any WPA network yet? Or is this the first attempt?

[saltydog]

Fisrt of all, thank you for your great patience!

/show_bug.cgi?id=329[/URL]

Have you been able to connect with any WPA network yet? Or is this the first attempt?

Not really... Here at home I have an USR router ad wireless security is set as:
Network authentication: WPA2 and WPA (recommended)
WPA encyiption: TKIP


On this router I have another strange behaviour. When I boot the laptop, it tries to connect to the network, without success. dmesg says that eth1 is not ready. If I clear the gconf key related to my network, then NM asks me for the password and get connected. The same if I simply restart dbus with:

sudo /etc/init.d/dbus restart


Anyway, at the end I get connected, but I have to do one of those 2 actions when I reboot the pc.

[wieman01]

Fisrt of all, thank you for your great patience!

Anyway, at the end I get connected, but I have to do one of those 2 actions when I reboot the pc.
No problem at all.

Are you sure your company's network is a WPA-PSK one and not WPA-EAP with a user name & a password?

That said, I need to think about it for a while. I'll get back to you tomorrow if I have another idea.

[saltydog]

No problem at all.

Are you sure your company's network is a WPA-PSK one and not WPA-EAP with a user name & a password?

That said, I need to think about it for a while. I'll get back to you tomorrow if I have another idea.

No. It is WPA-PSK, with just one key. With windows I connect immediately.

[wieman01]

No. It is WPA-PSK, with just one key. With windows I connect immediately.
Alright then.

You said you are using WPA-TKIP both at home & at work... What could be the difference between one and the other? At home you can connect immediately (despite a few difficulties after a restart) but at work you can't. What different settings could there be?

[saltydog]

Alright then.

You said you are using WPA-TKIP both at home & at work... What could be the difference between one and the other? At home you can connect immediately (despite a few difficulties after a restart) but at work you can't. What different settings could there be?

The problem is that I cannot access to the office's AP configuration. I can connect to it only from windows..

[saltydog]

@wieman:

This morning I finally could get connected in office!
This is what I did:

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


iface eth1 inet dhcp
wpa-psk <crypted-key>
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA
wpa-ssid evb
wpa-pairwise TKIP
wpa-group TKIP
auto eth1

then:

sudo ifdown eth1
sudo ifup eth1


I got the connection, but no way to let NM working on this AP...

[wieman01]

@wieman:

This morning I finally could get connected in office!
This is what I did:

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


iface eth1 inet dhcp
wpa-psk <crypted-key>
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA
wpa-ssid evb
wpa-pairwise TKIP
wpa-group TKIP
auto eth1

then:

sudo ifdown eth1
sudo ifup eth1


I got the connection, but no way to let NM working on this AP...
That's weird. It does not surprise me that works, however, the fact that NM fails to do the job is really strange.

Frankly I am running out of ideas here...

[_sluimers_]

Hi there,

My router aperently supports Pre-shared key WPA with AES.
I've tried setting this up but now
my network manager applet crashes with a segmentation fault when I select my SSID.

Here's my 'cat /etc/network/interfaces' output:


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 static
address 192.168.2.100
gateway 192.168.2.1
dns-nameservers 192.168.2.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid sluimers
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 7a55779fd6a53b83d3d2582216d80ac4a01178a759f45185e9 bf8118617cc9c9



Another problem is that 'cat resolv.conf' output returns:


# generated by NetworkManager, do not edit!


and it should have a line added with 'nameserver 192.168.x.x', right?

[wieman01]

Another problem is that 'cat resolv.conf' output returns:


# generated by NetworkManager, do not edit!


and it should be nameserver 192.168.2.1., right?
Can you connect using this configuration via "interfaces"? If not please post:
sudo ifdown -v wlan0
sudo ifup -v wlan0
"resolv.conf" only lists your name server once you have successfully connected to the router. Yes, it should list your router's IP address.

[_sluimers_]

rogier@rogier-laptop:/$ sudo ifdown -v wlan0
ifdown: interface wlan0 not configured



rogier@rogier-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
wlan0: ERROR while getting interface flags: No such device
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[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[SIOCGIFINDEX]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 7 value 0x0 - Failed to disable WPA in the driver.
ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 5 value 0x0 - ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAP]: No such device
ioctl[SIOCGIFFLAGS]: No such device
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1

ifconfig wlan0 192.168.2.100 netmask 255.255.255.0 up
SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
wlan0: ERROR while getting interface flags: No such device
Failed to bring up wlan0.

[wieman01]

rogier@rogier-laptop:/$ sudo ifdown -v wlan0
ifdown: interface wlan0 not configured



rogier@rogier-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
wlan0: ERROR while getting interface flags: No such device
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[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[SIOCGIFINDEX]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 7 value 0x0 - Failed to disable WPA in the driver.
ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 5 value 0x0 - ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAP]: No such device
ioctl[SIOCGIFFLAGS]: No such device
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1

ifconfig wlan0 192.168.2.100 netmask 255.255.255.0 up
SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
wlan0: ERROR while getting interface flags: No such device
Failed to bring up wlan0.

I am pretty sure the interface name ("wlan0") is incorrect. What does a scan yield:
sudo iwlist scan

[_sluimers_]

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:13:10:92:70:62
ESSID:"BeukWIFI"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=14/94 Signal level=-81 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Cell 02 - Address: 00:50:FC:F3:1F:66
ESSID:"sluimers"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=45/94 Signal level=-50 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; 54 Mb/s; 9 Mb/s; 18 Mb/s
36 Mb/s; 48 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:13:49:53:14:40
ESSID:"Mireille"
Mode:Master
Frequency:2.422 GHz (Channel 3)
Quality=19/94 Signal level=-76 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=200
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
Cell 04 - Address: 00:50:18:4D:20:A4
ESSID:"Area51"
Mode:Master
Frequency:2.432 GHz (Channel 5)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
Cell 05 - Address: 00:90:4C:7E:00:6E
ESSID:"@Home51040"
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; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK

vmnet1 Interface doesn't support scanning.

vmnet8 Interface doesn't support scanning.

[wieman01]

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:13:10:92:70:62
ESSID:"BeukWIFI"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=14/94 Signal level=-81 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

Alright. The interface name was wrong. Now edit your "interfaces" configuration file once again and restart the network:
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto ath0
iface ath0 inet dhcp
address 192.168.2.100
gateway 192.168.2.1
dns-nameservers 192.168.2.1
netmask 255.255.255.0
wpa-driver madwifi
wpa-ssid sluimers
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 7a55779fd6a53b83d3d2582216d80ac4a01178a759f45185e9 bf8118617cc9c9
Then restart:
sudo ifdown -v ath0
sudo ifup -v ath0
SSID broadcast is disabled ("wpa-ap-scan 2")?

[_sluimers_]

This looks a lot better, but nm-applet still crashes when I select my SSID

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/avahi-autoipd
run-parts: executing /etc/network/if-down.d/postfix
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.ath0.pid -lf /var/lib/dhcp3/dhclient.ath0.leases ath0
There is already a pid file /var/run/dhclient.ath0.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:14:a4:85:e4:6a
Sending on LPF/ath0/00:14:a4:85:e4:6a
Sending on Socket/fallback
DHCPRELEASE on ath0 to 192.168.2.1 port 67
ifconfig ath0 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.ath0.pid
Stopped /sbin/wpa_supplicant (pid 23186).



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: wpa-driver madwifi
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.ath0.pid -i ath0 -D madwifi -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/ath0
wpa_supplicant: wpa-ap-scan 2 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "sluimers" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise CCMP -- OK
wpa_supplicant: wpa-group CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.ath0.pid -lf /var/lib/dhcp3/dhclient.ath0.leases ath0
There is already a pid file /var/run/dhclient.ath0.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:14:a4:85:e4:6a
Sending on LPF/ath0/00:14:a4:85:e4:6a
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 11
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/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/openssh-server
run-parts: executing /etc/network/if-up.d/postfix
run-parts: executing /etc/network/if-up.d/wpasupplicant

[wieman01]

Ok, WPA support is there, looks fine.

Now please turn on SSID broadcast on the router, then edit "interfaces" again and make it look exactly like this (yes, I removed all data):
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp
Then restart the PC and see if NM connects.

[_sluimers_]

At least this time I allowed to enter the key.
NM crashed after a minute of trying to connect and on second attempt is back to the old crashing when choosing the SSID again.

[wieman01]

At least this time I allowed to enter the key.
NM crashed after a minute of trying to connect and on second attempt is back to the old crashing when choosing the SSID again.
Ok, the last option is that we remove NM completely and do everything manually as described in this tutorial. I don't know if you can live with it, but that's all I can offer right now...

[_sluimers_]

You mean doing everything written in post #2?

I did that without removing nm and I have a connection, yay! \o/

Thanks!

Now I've got one more network problem left. Nothing to do with security, but
every time I connect to my router, not any other router, the line 'nameserver 192.168.2.1' in /etc/resolv.conf disappears. How can I fix that?

[wieman01]

You mean doing everything written in post #2?

I did that without removing nm and I have a connection, yay! \o/

Thanks!

Now I've got one more network problem left. Nothing to do with security, but
every time I connect to my router, not any other router, the line 'nameserver 192.168.2.1' in /etc/resolv.conf disappears. How can I fix that?
Cool.

Question: Do you need the entry in "/etc/resolv.conf" or does it have an impact on your connectivity? I never edit that file or pay attention to it at all.

[_sluimers_]

Yes, it prevented me from certain ports, including 80. I dunno why. Anyway, I got it solved. Hurray! Thank you wieman01. :KS You're the best! :KS

[flaviusc]

Hi everyone! I’ve been trying lately to get online but so far the success was rather limited, I was unable to get WPA to work.

On Ubuntu 7.10, I am using a WLAN card with a Texas Instruments chipset and ndiswrapper instead of the native acx driver.

flavius@mbo:~$ sudo lspci -nn

01:09.0 Network controller [0280]: Texas Instruments ACX 100 22Mbps Wireless Interface [104c:8400]


The card and driver are working, I was able to connect to open networks as well as to WEP enabled networks (using Network Manager).

I removed Network Manager and tried to get WPA, following this guide. Unfortunately I think that the card is unable to get an IP address as I can see from the following:

flavius@mbo:~$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces...
There is already a pid file /var/run/dhclient.wlan0.pid with pid 5800
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:03:2f:18:8d:cb
Sending on LPF/wlan0/00:03:2f:18:8d:cb
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.2.1 port 67
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:03:2f:18:8d:cb
Sending on LPF/wlan0/00:03:2f:18:8d:cb
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
[ OK ]


The network uses WPA2 with PSK, there are several computers using it without a problem. The router has no restrictions regarding DHCP.

Below is the info required for debug. Thanks for your help!


flavius@mbo:~$ 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 wlan0
0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 wlan0

flavius@mbo:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

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

flavius@mbo:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:0C:6E:9B:CB:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17 Base address:0xa000

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:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1596 (1.5 KB) TX bytes:1596 (1.5 KB)

wlan0 Link encap:Ethernet HWaddr 00:03:2F:18:8D:CB
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:20 Memory:e2014000-e2015000

wlan0:ava Link encap:Ethernet HWaddr 00:03:2F:18:8D:CB
inet addr:169.254.6.213 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:20 Memory:e2014000-e2015000

flavius@mbo:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :

Cell 04 - Address: 00:16:38:E7:02:21
ESSID:"My_ESSID"
Protocol:IEEE 802.11FH
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:100/100 Signal level:90/154 Noise level:160/154
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
Extra:bcn_int=100
Extra:atim=0

flavius@mbo:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid My_ESSID
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk My__hex_key

flavius@mbo:~$ cat /etc/modprobe.d/ndiswrapper
alias wlan0 ndiswrapper

flavius@mbo:~$ cat /etc/resolv.conf
# generated by NetworkManager, do not edit!

nameserver 192.168.2.1

[wieman01]

@flaviusc:

Can you confirm that you have got the right Windows driver? Does it really support WPA?

The scan does not really list any WPA networks so I was wondering why...

[flaviusc]

Hi,

thanks for the prompt answer.

Can you confirm that you have got the right Windows driver?

It all depends on do you understand by "right". The Ubuntu "Device Manager" gives me the data mentioned below, but as far as I was able to understand, the card is actually a D-Link AirPlus DWL-520+ sold under another name here in Germany.


Vendor - Texas Instruments
Product - ACX 100 22Mbps Wireless Interface
OEM Vendor - Global Sun Technology Inc
OEM Product - WL-8305 IEEE802.11b+ Wireless LAN PCI Adapter


The PCI ID matches as well, so I downloaded the D-Link driver specified on the ndiswrapper web page and I was able to successfully install and use the card without a glitch.


Does it really support WPA?


Well, the Windows driver does NOT support WPA, it only supports WEP. But as far as I was able to understand it is the task of wpasupplicant to add WPA capabilities to a wireless card that lacks them (like the one I'm using).

This is what dmesg tells me about the driver:


flavius@mbo:~$ dmesg |grep ndis
[ 39.344994] ndiswrapper version 1.45 loaded (smp=yes)
[ 39.424256] ndiswrapper: driver airplus (D-Link,09/08/2003,4.15.5.1) loaded
[ 39.425251] ndiswrapper: using IRQ 20
[ 40.023332] ndiswrapper (set_encr_mode:673): setting encryption mode to 6 failed (C00000BB)
[ 40.026065] usbcore: registered new interface driver ndiswrapper


Is there any change on getting WPA to work on this card? Or should I start shopping for a new one?

[wieman01]

Well, the Windows driver does NOT support WPA, it only supports WEP. But as far as I was able to understand it is the task of wpasupplicant to add WPA capabilities to a wireless card that lacks them (like the one I'm using).
That's exactly your problem, mate. As the driver does not really support WPA, it won't work. wpa-supplicant will help you only if the wireless adapter understands the protocol.

The last resort is to buy another card as WEP is highly insecure. But that's up to you of course.

[flaviusc]

Hi,

This page http://www.seattlewireless.net/DlinkDwl520plus claims that the card supports WPA on Windows XP using driver version 3.07. That's exactly the driver I'm using with ndiswrapper, but it looks that the info might not be true :(

I am really at a lost here. Especially since the card properly identifies the IP address of the router and it actually asks for an IP address ...

And I am sure that I've seen somewere a mention of another Windows driver for an acx 100 based card also supporting WPA. Maybe I can dig up a driver like that. Is there a way to find out if a driver supports WPA or not?

[wieman01]

And I am sure that I've seen somewere a mention of another Windows driver for an acx 100 based card also supporting WPA. Maybe I can dig up a driver like that. Is there a way to find out if a driver supports WPA or not?
Yes, the change log. Every driver should come with a change log or README. It should state whether it supports WPA or not.

[myharshdesigner]

cooooooooooolllllllllllllllllllllllll :)

[.zoXan.]

Hi all,

I'm having trouble with my wireless connection. My SSID is set to broadcast, but Ubuntu doesn't pick it up. It picks up my neighbor's ["Tamago"] but not mine. I'm using the ipw3945 driver AFAIK.

I'm using WPA2 and I don't know how to set it up. Here's everything that I can provide to help you:

http://rafb.net/p/BtupXn50.html

Can you please help me?

[wieman01]

Hi all,

I'm having trouble with my wireless connection. My SSID is set to broadcast, but Ubuntu doesn't pick it up. It picks up my neighbor's ["Tamago"] but not mine. I'm using the ipw3945 driver AFAIK.

I'm using WPA2 and I don't know how to set it up. Here's everything that I can provide to help you:

http://rafb.net/p/BtupXn50.html

Can you please help me?
Please also provide:
sudo cat /etc/network/interfaces
Does network manager list any other networks around you?

[FokkerCharlie]

Hi All-

Any chance of a hand with my wifi? I've had it working fine on WinXP, using WPA-PSK/TKIP, which is all fine.

Network manager doesn't want to play the WPA game (I don't think this is news to anyone!), and worse, often when I try to tweak the settings, the system crashes, and won't re-start, see : http://ubuntuforums.org/showthread.php?t=613133 I'm not alone!

My network/interfaces currently only contains:

auto lo
iface lo inet loopback

Device manager reports that the card is:
Texas Instruments
ACX 111 54Mbps Wireless Interface
Bus type PCI
Device Type / Capabilities unknown

OK- I know this doesn't look right, but I am afraid to fiddle in case I get the crash, and then have to re-install (for the 9th time) when Ubuntu won't re-start.

Please help a noob!

Charlie

[wieman01]

Hi All-

Any chance of a hand with my wifi? I've had it working fine on WinXP, using WPA-PSK/TKIP, which is all fine.

Network manager doesn't want to play the WPA game (I don't think this is news to anyone!), and worse, often when I try to tweak the settings, the system crashes, and won't re-start, see : http://ubuntuforums.org/showthread.php?t=613133 I'm not alone!

My network/interfaces currently only contains:

auto lo
iface lo inet loopback

Device manager reports that the card is:
Texas Instruments
ACX 111 54Mbps Wireless Interface
Bus type PCI
Device Type / Capabilities unknown

OK- I know this doesn't look right, but I am afraid to fiddle in case I get the crash, and then have to re-install (for the 9th time) when Ubuntu won't re-start.

Please help a noob!

Charlie
Ok, let's do a scan first (post the results please):
sudo iwlist scan
What driver do you use? Did the adapter work out of the box?

[FokkerCharlie]

Hi wieman

Here's the results of the scan:

ca@ca-laptop:~$ sudo iwlist scan
[sudo] password for ca:
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:16:E3:13:30:B9
ESSID:"CharlesNet"
Mode:Master
Frequency:2.412 GHz (Channel 1)
Quality=52/100 Signal level=33/100 Noise level=0/100
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Cell 02 - Address: 00:19:E4:12:88:89
ESSID:"2WIRE605"
Mode:Master
Frequency:2.422 GHz (Channel 3)
Quality=36/100 Signal level=10/100 Noise level=0/100
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Cell 03 - Address: 00:19:E4:12:88:8B
ESSID:"BT Fusion-8605"
Mode:Master
Frequency:2.422 GHz (Channel 3)
Quality=36/100 Signal level=10/100 Noise level=0/100
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Cell 04 - Address: 00:16:0A:09:13:DB
ESSID:""
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=37/100 Signal level=12/100 Noise level=0/100
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 22 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Cell 05 - Address: 00:18:4D:3E:DC:CA
ESSID:"NETGEAR"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=31/100 Signal level=3/100 Noise level=0/100
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 22 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Cell 06 - Address: 00:0F:B5:CE:AB:FA
ESSID:"PRIV_WIFI2"
Mode:Master
Frequency:2.412 GHz (Channel 1)
Quality=31/100 Signal level=3/100 Noise level=0/100
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 22 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s


I'm afraid that I am not sure what drive I'm using- a complete Linux noob. Network manager sees the wifi adapter, and lists a handful of networks, which is what I would expect. Unfortunately, after trying some settings, the crashes and problems start. So I suppose that means that the driver isn't working correctly?!

Cheers
Charlie

[ubulap]

FokkerCharlie,

if I'm not mistaken Texas Instruments
ACX 111 54Mbps linux driver does not yet support WPA.
(The module should be called acx)

I guess you need to try ndiswrapper, and make use of the windows driver with it.

[juje]

Ok, this maybe sound like i'm quite lazy and didn't try it harder, but that's not riught...i really follow the original threat and only get this...i can configure my network only with wpa and broadcast essid. It works fine, but every time i restart my pc it's has some trouble to connect...on the other hand, i want to get the wpa2 secure connection, any clue?

This is what i've tried and works (any change to this it doesn't works:
auto wlan0
iface wlan0 inet static
address 192.168.1.100
gateway 192.168.1.1
dns-nameservers 200.69.32.5
netmask 255.255.255.0
wpa-driver wext
wpa-ssid xxxxxxxxxxxxx
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk c53ad64bde66e72384da57fe1536917e994ca4bfdc79bd7c30 9c76ca02aa9afe

I'm a gutsy user with d-link DWL-G510 Rev C and a wrt54g linksys router

Thanks and sorry for my lousy english...

[wieman01]

FokkerCharlie,

if I'm not mistaken Texas Instruments
ACX 111 54Mbps linux driver does not yet support WPA.
(The module should be called acx)

I guess you need to try ndiswrapper, and make use of the windows driver with it.
I am afraid you are right. Scanning lists a number of networks, but there is no mention of WPA secured ones. That generally means that the driver does not recognize them as such... bad news.

[wieman01]

Ok, this maybe sound like i'm quite lazy and didn't try it harder, but that's not riught...i really follow the original threat and only get this...i can configure my network only with wpa and broadcast essid. It works fine, but every time i restart my pc it's has some trouble to connect...on the other hand, i want to get the wpa2 secure connection, any clue?

This is what i've tried and works (any change to this it doesn't works:
auto wlan0
iface wlan0 inet static
address 192.168.1.100
gateway 192.168.1.1
dns-nameservers 200.69.32.5
netmask 255.255.255.0
wpa-driver wext
wpa-ssid xxxxxxxxxxxxx
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk c53ad64bde66e72384da57fe1536917e994ca4bfdc79bd7c30 9c76ca02aa9afe

I'm a gutsy user with d-link DWL-G510 Rev C and a wrt54g linksys router

Thanks and sorry for my lousy english...
So you are saying that you need to restart the network after a reboot? Please see post #2 of this thread for a workaround/solution.

Have you tried WPA2 as well (RSN)? Were you any successful or did you have trouble connecting in that case?

[FokkerCharlie]

Wieman, ubalap, thanks for your help.

I'll have a go with NDISWRAPPER.

Charlie

[FokkerCharlie]

Hi again

Just in case you're interested- I had a go with Ndiswrapper.

It worked a treat, until I'd re-booted a couple of times, and then it stopped. I have no idea why. I am completely sure that I had not changed any configuration in the meantime- in fact I was starting and stopping the computer just to see if the WLAN would stay working! Same results with WICD and Network Manager.

Anyway, maybe I'll ask in the Ndiswrapper forums for help there.

Cheerio!
Charlie