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

[wieman01]

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
I can help you with it if you don't mind. Please send me the link by PM and I'll support you. Please check out my own 'ndiswrapper' HOWTO (see signature) as well... perhaps you have missed a step or two.

What tutorial have you used?

[ubulap]

FokkerCharlie,

one of the things that I found of need to do, when I was using ndiswrapper (I've now moved to rt73 driver) to have it working, was that I needed to restart the network at each boot, to have it working.
Maybe this is why after rebooting it stopped working for you?

I had to run the following command:
sudo /etc/init.d/networking restart

[wieman01]

FokkerCharlie,

one of the things that I found of need to do, when I was using ndiswrapper (I've now moved to rt73 driver) to have it working, was that I needed to restart the network at each boot, to have it working.
Maybe this is why after rebooting it stopped working for you?

I had to run the following command:
sudo /etc/init.d/networking restart
Post #2 of this thread tries to fix that. Check it out.

[FokkerCharlie]

Hi Ubulap

The problem I am facing is that the connection needs to be re-set every couple of minutes while the computer is running- ie it does not need to be re-booted to need to wake-up.

See the new thread:
http://ubuntuforums.org/showthread.php?p=3842134#post3842134

Nice try, tho, thanks!
Charlie

[markw365]

Ok, I've been playing with this for a couple of days. Our network guys tell me the setup is PEAP-TLS. I've tried every combination in the network-manager, wpa-enterprise, wpa2-enterprise, etc. It seems to connect then drop the connection, like something is wrong with the authentication handshake.

Here's my settings for wireless in XP:

Under the network properties "Association Tab".

Network Authentication is set to "Open"
Data Encryption is set to "WEP"

Under the Authentication Tab:

"Enable IEEE 802.1x authentication for this network" checked
EAP Type: Protected EAP(PEAP)
Authenticate as a computer when computer information is available. Checked.

Under PEAP Properties, the
"Validate server certificate" is checked along with our company certificate.

Then in the Select authentication pull down it has "Secured Password (EAP-MSCHAPv2) selected, which uses my domain/user creditentials.

Under the Connection tab it has "connect when in range".

This all works fine under XP, but when I boot into Linux, and select WPA or WPA2 enterprise, mschapv2, etc. it doesn't work. I've got the certificate on the machine in both .p7b and .pem formats. It looks like it gets close, but it doesn't come up. In the username/password dialog I give the domain/username and my domain login.

Any help would be appriciated.

Card is built in laptop with the intel 2200 chipset, works fine at home and everywhere else. I also have a drawer full of USB wireless adapters I can try.

Thanks,
Mark

[wieman01]

Ok, I've been playing with this for a couple of days. Our network guys tell me the setup is PEAP-TLS. I've tried every combination in the network-manager, wpa-enterprise, wpa2-enterprise, etc. It seems to connect then drop the connection, like something is wrong with the authentication handshake.

Here's my settings for wireless in XP:

Under the network properties "Association Tab".

Network Authentication is set to "Open"
Data Encryption is set to "WEP"

Under the Authentication Tab:

"Enable IEEE 802.1x authentication for this network" checked
EAP Type: Protected EAP(PEAP)
Authenticate as a computer when computer information is available. Checked.

Under PEAP Properties, the
"Validate server certificate" is checked along with our company certificate.

Then in the Select authentication pull down it has "Secured Password (EAP-MSCHAPv2) selected, which uses my domain/user creditentials.

Under the Connection tab it has "connect when in range".

This all works fine under XP, but when I boot into Linux, and select WPA or WPA2 enterprise, mschapv2, etc. it doesn't work. I've got the certificate on the machine in both .p7b and .pem formats. It looks like it gets close, but it doesn't come up. In the username/password dialog I give the domain/username and my domain login.

Any help would be appriciated.

Card is built in laptop with the intel 2200 chipset, works fine at home and everywhere else. I also have a drawer full of USB wireless adapters I can try.

Thanks,
Mark
Tough one... I don't user Network Manager much. But the IPW2200 driver is definitely capable of PEAP. Could you post screenshots of your NM settings?

Perhaps 'dmesg" (command line) tells us more:
dmseg

[Marcellus]

A follow-up on my newbie-post from long ago: (search on username)

I didn't succeed in getting WPA to work on two pcmcia wifi cards while the cards were known to work perfectly with WEP: one was Linksys WPC11 (I don't remember which version), the other a Senao NL-2511CD. In the end it was the cards' fault: they were pretty old 802.11b-only cards that turned out not to support WPA.

I replaced them with a new usb dongle --- Azurewave AW-GU210 --- which immediately worked under 7.04 and 7.10. However, after an hour (or sometimes 3) or so it would overheat, I think, and fail to connect for several minutes. Possibly because it tries to move fast broadband over USB1.1?

This I replaced with a similar Belkin usb dongle that has been working perfectly with the same setups --- USB1.1 on a 2.2ghz celeron desktop and on a celeron 1.1ghz laptop.

[tnunamak]

Hi,

I have a working wireless connection when it it unencrypted, but I've tried following your guide to connect to my university's LEAP network and when I restart the networking service I get the following:

sudo /etc/init.d/networking restart
* Reconfiguring network interfaces... * Stopping the Firestarter firewall...
...done.
* Starting the Firestarter firewall...
...fail!
run-parts: /etc/network/if-down.d/50firestarter exited with return code 2
There is already a pid file /var/run/dhclient.eth0.pid with pid 6102
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/eth0/00:19:7d:8c:cd:22
Sending on LPF/eth0/00:19:7d:8c:cd:22
Sending on Socket/fallback
DHCPRELEASE on eth0 to 1.1.1.1 port 67
There is already a pid file /var/run/dhclient.eth0.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:19:7d:8c:cd:22
Sending on LPF/eth0/00:19:7d:8c:cd:22
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
oDHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
* Stopping the Firestarter firewall...
...done.
* Starting the Firestarter firewall...
...fail!
run-parts: /etc/network/if-up.d/50firestarter exited with return code 2


My interfaces file reads as follows:

# The loopback network interface
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

# The primary network interface
iface eth1 inet dhcp

#iface eth0 inet dhcp
#wireless-essid TUGuest
#auto eth0

auto eth0
iface eth0 inet dhcp
wpa-driver wext
wpa-ssid TUSecure
wpa-ap-scan 1
wpa-eap LEAP
wpa-key-mgmt IEEE8021X
wpa-identity tnunamak
wpa-password mypassword


Any ideas?

[wieman01]

@tnunamak:

Please post the output of (while your are near the network:
sudo iwlist scan
Then also let me know what wireless adapter you have got & what chipset it uses. Not all adapters are PEAP-capable.

[buccaneere]

2. No firewall & configuration tool is running (e.g. Firestarter).

How do I ascertain this?

[wieman01]

How do I ascertain this?
If you haven't installed anything like that, you don't have it. :-) You could also check through Synaptic, the package manager.

[buccaneere]

If you haven't installed anything like that, you don't have it. :-) You could also check through Synaptic, the package manager.

Excellent - thanks.

At what point in your sequence must I unplug the ethernet hardwire? (so that I can cut and paste current configurations, instead of using another machine's connection)

[buccaneere]

Is mac filtering a function of my router, or of my laptop? Or both?

EDIT: Mac filtering is off, on the router. Is there filtering of this type on the laptop?

[wieman01]

Is mac filtering a function of my router, or of my laptop? Or both?

EDIT: Mac filtering is off, on the router. Is there filtering of this type on the laptop?
No, there isn't. It's entirely a router function.

Unplug the (Ethernet) cable as soon as your reboot the PC or restart the network. That's enough.

[buccaneere]

Wireless configuration tools??? Where are they to disable?

[wieman01]

Wireless configuration tools??? Where are they to disable?
You mean Network Manager or what? Are you referring to my comments on the first page? Just turn NM off (right-click, close) and continue.

[buccaneere]

Are you referring to my comments on the first page?

Yes.

I am attempting to follow the instructions explicitly...

Where is roaming to disable?

[wieman01]

Yes.

I am attempting to follow the instructions explicitly...

Where is roaming to disable?
Somewhere in NM or the other network applet... not sure, really. Because I don't use NM very often. But that's what people have told me... sorry, mate.

[buccaneere]

Somewhere in NM or the other network applet... not sure, really. Because I don't use NM very often. But that's what people have told me... sorry, mate.

I cannot enable hidden wireless. (My windows vistabox loses its connection.) Does this preclude connecting linux and windows at the same time?

[wieman01]

I cannot enable hidden wireless. (My windows vistabox loses its connection.) Does this preclude connecting linux and windows at the same time?
No, it does not. You can connect any sort of client, no matter what OS they run.

Then enable SSID broadcast. It adds no extra security anyway (at least not much).

[buccaneere]

Supplicant installed.

Return of iwconfig : (no extensions except for this)

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

In order?

[wieman01]

Supplicant installed.

Return of iwconfig : (no extensions except for this)

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

In order?
Looks ok. What does this yield:
sudo ifdown ath0
sudo ifup ath0
sudo iwlist ath0

[buccaneere]

Looks ok. What does this yield:

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

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:19:7d:29:74:13
Sending on LPF/ath0/00:19:7d:29:74:13
Sending on Socket/fallback

----------------------------------------------------------------------------------------
chuckb@chuckb-laptop:~$ sudo ifup ath0
Error for wireless request "Set Encode" (8B2A) :
invalid argument "passcobwebcobwebphrase".
There is already a pid file /var/run/dhclient.ath0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:19:7d:29:74:13
Sending on LPF/ath0/00:19:7d:29:74:13
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 11
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
-------------------------------------------------------------------------------------------------------------------


chuckb@chuckb-laptop:~$ sudo iwlist ath0
iwlist: unknown command `ath0'

Ethernet hardwire is still on.
Roaming mode unknown.
Hidden broadcast disabled.

[wieman01]

Ok, try this again:
sudo iwlist scan
Please also post the contents of:
sudo gedit /etc/network/interfaces

[buccaneere]

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:18:39:DF:0E:BD
ESSID:"linksys"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=1/94 Signal level=-94 dBm Noise level=-95 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 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:14:95:A6:47:89
ESSID:"2WIRE493"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=17/94 Signal level=-78 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 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
Cell 03 - Address: 00:14:95:BA:79:91
ESSID:"2WIRE272"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=18/94 Signal level=-77 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
Cell 04 - Address: 00:19:5B:05:F0:12
ESSID:"cobweb"
Mode:Master
Frequency:2.412 GHz (Channel 1)
Quality=53/94 Signal level=-42 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

sit0 Interface doesn't support scanning.



Network device: ath0
Hardware address: not available
IP address: not available
Netmask: not available
Broadcast: not available
Multicast: not available
MTU: not available
Link speed: not available
State: not available
Transmitted packets: 0
Transmission errors: 0
Received packets: 0
Reception errors: 0
Collisions: 0


Huh?

[buccaneere]

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 wlan0
iface wlan0 inet dhcp


iface ath0 inet dhcp
wireless-essid cobweb
wireless-key p...e

auto ath0


I am cobweb

[wieman01]

Hang on a minute... you have not configured it yet, have you? Everything looks set, so I think you can continue with the WPA section ("/etc/network/interfaces").

[buccaneere]

Hang on a minute... you have not configured it yet, have you? Everything looks set, so I think you can continue with the WPA section ("/etc/network/interfaces").

I do not know if I have completely configured for wireless, or not. You have skipped me forward I think, through configuration steps...

I'm now at #3???

EDIT: I now see notes........................



auto wlan0
iface wlan0 inet static
address 192.168.168.40
gateway 192.168.168.230
dns-nameservers 192.168.168.230
netmask 255.255.255.0
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key> [IMPORTANT: See "WPA-PSK key generation"]

[wieman01]

I do not know if I have completely configured for wireless, or not. You have skipped me forward I think, through configuration steps...

I'm now at #3???



auto wlan0............................................. ..........this will be ath0 ?
iface wlan0 inet static.........................................ifa ce ath0 inet dynamic?
address 192.168.168.40.................................... .address of router?
gateway 192.168.168.230..................................d efault gateway? from router?
dns-nameservers 192.168.168.230...................?
netmask 255.255.255.0..................................... .subnet mask?
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key> [IMPORTANT: See "WPA-PSK key generation"]
Alright.

Watch out tough... The scan says that you use WPA-TKIP. That is WPA1 rather than WPA2. An example is provided as well.

[buccaneere]

How do you exit after saving edited file?


This look good?

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto wlan0
iface wlan0 inet dhcp


iface ath0 inet dhcp
wireless-essid cobweb
wireless-key p...e

auto ath0
iface ath0 inet dhcp
00:19:5B:05:F0:12
192.168.0.1
192.168.0.1
255.255.255.0
wpa-driver wext
wpa-ssid cobweb
wpa-ap-scan 1
wpa-proto wpa
wpa-pairwise tkip
wpa-group tkip
wpa-key-mgmt wpa-psk
wpa-psk 2057043c4c9c2e031ac0ba3c960f4c5b3b8c8a5b319cbaab4a 93445f429f0727

[buccaneere]

route -n
kernel ip routing table
destination gateway genmask flags metric ref use iface


iwconfig
ath0
ieee 802.11b essid : " "
mode:managed channel 0 access point not associated
bit rate 0 kbs tx power 0dbm sensitivity 0/3
retry off rts thr:off fragment thr:off
power management off
link quality 0 sig level 0 noise 0
rx invalid nwid 0 crypt 0 frag 0
tx retries 0 invalid misc 0 missed beacon 0

no other wireless extensions



ifconfig
no items returned



iwlist scan
ath0 no scan results
all other interfaces do not support scanning



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

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto wlan0
iface wlan0 inet dhcp


iface ath0 inet dhcp
wireless-essid cobweb
wireless-key p...e

auto ath0
iface ath0 inet dhcp
00:19:5B:05:F0:12
192.168.0.1
192.168.0.1
255.255.255.0
wpa-driver wext
wpa-ssid cobweb
wpa-ap-scan 1
wpa-proto wpa
wpa-pairwise tkip
wpa-group tkip
wpa-key-mgmt wpa-psk
wpa-psk 2057043c4c9c2e031ac0ba3c960f4c5b3b8c8a5b319cbaab4a 93445f429f0727



cat /etc/modprobe.d/ndiswrapper
no file or directory



cat /etc/resolve.conf
no file or directory

[wieman01]

@buccaneere:

Ok, edit your "interfaces" file and post this (replacing all contents):
auto lo
iface lo inet loopback

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-ssid cobweb
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 2057043c4c9c2e031ac0ba3c960f4c5b3b8c8a5b319cbaab4a 93445f429f0727
The restart the network and post the output:
sudo ifdown ath0
sudo ifup ath0
By the way... why do you not use Network Manager? Do you need a static IP? The script above is for DHCP.

[buccaneere]

@buccaneere:

Ok, edit your "interfaces" file and post this (replacing all contents):.

I did edit the interfaces file.

Did I put in incorrect values?


By the way... why do you not use Network Manager?
You mean the GUI? I don't know the values there to enter any more than with CLI.

Do you need a static IP?
I don't know. Do I?

[wieman01]

I did edit the interfaces file.

Did I put in incorrect values?



You mean the GUI? I don't know the values there to enter any more than with CLI.


I don't know. Do I?
The value weren't quite correct. So I corrected them for you. Please use the latest script that I have posted.

Yes, I was referring to NM, the networking GUI.

Let's try DHCP first of all. The script should be fine. You probably don't need static IP.

[buccaneere]

@buccaneere:

Ok, edit your "interfaces" file and post this (replacing all contents):

The restart the network and post the output:


By the way... why do you not use Network Manager? Do you need a static IP? The script above is for DHCP.

Done.

After edit, restart, sudo ifdown, and sudo ifup, functions executed, I plugged in the ethernet hardwire to copy and paste, instead of typing in another machine. No problem?

ifdown return:

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

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:19:7d:29:74:13
Sending on LPF/ath0/00:19:7d:29:74:13
Sending on Socket/fallback
DHCPRELEASE on ath0 to 192.168.0.1 port 67


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

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:19:7d:29:74:13
Sending on LPF/ath0/00:19:7d:29:74:13
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 192.168.0.1
DHCPREQUEST on ath0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1
bound to 192.168.0.101 -- renewal in 4885 seconds.
chuckb@chuckb-laptop:~$

Thanks again for help............

[buccaneere]

GUI windows are now not responding for network configuration.

Wireless icon for signal strength has appeared at 86% - 18 inches from router???

System/administration/networking tools/network settings: wireless, wired, and modem connections are not enabled, nor are they configured. ?

How am I now browsing? Eth hardwire is plugged in...

[buccaneere]

This post is with hardwire unplugged; all connections still not enabled or configured............

[wieman01]

This post is with hardwire unplugged; all connections still not enabled or configured............
Unplugged or plugged?
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 192.168.0.1
DHCPREQUEST on ath0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1
bound to 192.168.0.101 -- renewal in 4885 seconds.
This tells me you are connected... Please restart the network once again and post:
route
You should be able to ping Google:
ping www.google.com

[MarceloPereira]

Hi everyone,

I´m facing a problem, if anyone could help i will thank.

My notebook is a FE770G Sony Vaio, 3945ABG wireless card, using Ubuntu 7.10, updated.

I´m trying to use it with a D-Link DI-524 Wireless router.

I´m trying to use WPA2, but I only get it working with WPA.

My .../interfaces file is the default one, static IP.

Is there any problem with this configuration and WPA2 ?

thanks

[wieman01]

Hi everyone,

I´m facing a problem, if anyone could help i will thank.

My notebook is a FE770G Sony Vaio, 3945ABG wireless card, using Ubuntu 7.10, updated.

I´m trying to use it with a D-Link DI-524 Wireless router.

I´m trying to use WPA2, but I only get it working with WPA.

My .../interfaces file is the default one, static IP.

Is there any problem with this configuration and WPA2 ?

thanks
There shouldn't be a problem. Just use the standard networking applet called Network Manager to configure it. No issues I would think.

[buccaneere]

Post # 1037 was with hardwire UNplugged. Wireless was functional (with wireless, wired, and modem connections NOT enabled, OR configured).

I've re-started the machine, and the server (router) connection was lost. I opened gui for wireless configgin', enabled, put in ssid and passkey, and wireless is enabled.

If I make a backup for etc/network/interfaces, I can adjust wired settings, to restore hardwire connection???

[wieman01]

Post # 1037 was with hardwire UNplugged. Wireless was functional (with wireless, wired, and modem connections NOT enabled, OR configured).

I've re-started the machine, and the server (router) connection was lost. I opened gui for wireless configgin', enabled, put in ssid and passkey, and wireless is enabled.

If I make a backup for etc/network/interfaces, I can adjust wired settings, to restore hardwire connection???
For both wireless and wired please use this one:
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-ssid cobweb
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 2057043c4c9c2e031ac0ba3c960f4c5b3b8c8a5b319cbaab4a 93445f429f0727
VERY IMPORTANT: Please follow post #2 of this thread if you lose connection after a restart. That's a known bug and I posted a workaround there.

[kboykowboy]

I'm using my other computer at my girlfriends house. She has wpa-psk encryption. i have a USB - TEW-424UB 3.0 card. i have 7.10 ubuntu. I can't get online with my ubuntu machine via wire or wireless so i cant really install wpa supplicant on my ubuntnu - but could i somehow how download it and put it on my usb disk and then stick that into my ubuntu?!

my second question is - how do i make the USB - TEW-424UB 3.0 work via wpa supplicant?! should i run some commands so you know how my laptop is setup etc?!

[buccaneere]

I'm using my other computer at my girlfriends house. She has wpa-psk encryption. i have a USB - TEW-424UB 3.0 card. i have 7.10 ubuntu. I can't get online with my ubuntu machine via wire or wireless so i cant really install wpa supplicant on my ubuntnu - but could i somehow how download it and put it on my usb disk and then stick that into my ubuntu?!

Yes.

I burned some driver packages to a CD with a windows box, and then loaded it onto a ubuntu machine successfully.

my second question is - how do i make the USB - TEW-424UB 3.0 work via wpa supplicant?! should i run some commands so you know how my laptop is setup etc?!


There might be info in this thread that's helpful:
http://ubuntuforums.org/showthread.php?t=619955&page=4
The OP's wireless device address is a USB controller; not a PCI controller. The driver had to be manually configured for the USB address. See post # 40 of that thread. I'd like to know if that works for ya'.

I can help no further - I'm still a rookie, but know what to look for...

[tnunamak]

@tnunamak:

Please post the output of (while your are near the network:

Then also let me know what wireless adapter you have got & what chipset it uses. Not all adapters are PEAP-capable.

This is really long because I think there are multiple routers throughout the building. The network I'm trying to connect to is TUSecure.

tnunamak@atlas:~$ sudo iwlist scanning
[sudo] password for tnunamak:
lo Interface doesn't support scanning.

eth1 Interface doesn't support scanning.

eth0 Scan completed :
Cell 01 - Address: 00:14:6A:F0:BF:E0
ESSID:"TrinityAP"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:9/100 Signal level:-90 dBm Noise level:-96 dBm
Encryption key: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
Cell 02 - Address: 00:14:6A:F0:BF:E1
ESSID:"TUGuest"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:7/100 Signal level:-91 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 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
Cell 03 - Address: 00:14:6A:F0:BF:E4
ESSID:"TUSecure"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:7/100 Signal level:-91 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x
Cell 04 - Address: 00:0F:8F:46:B9:50
ESSID:"TrinityAP"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:17/100 Signal level:-85 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
Cell 05 - Address: 00:0F:8F:46:B9:D0
ESSID:"TrinityAP"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:23/100 Signal level:-81 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
Cell 06 - Address: 00:0F:8F:4C:39:90
ESSID:"TrinityAP"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:9/100 Signal level:-90 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
Cell 07 - Address: 00:0F:8F:4C:39:91
ESSID:"TUGuest"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:17/100 Signal level:-85 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 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
Cell 08 - Address: 00:0F:8F:4C:39:94
ESSID:"TUSecure"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:17/100 Signal level:-85 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x
Cell 09 - Address: 00:0F:8F:46:B9:D1
ESSID:"TUGuest"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:26/100 Signal level:-79 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 10 - Address: 00:0F:8F:46:B9:D4
ESSID:"TUSecure"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:21/100 Signal level:-82 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x
Cell 11 - Address: 00:0F:8F:46:C1:24
ESSID:"TUSecure"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:3/100 Signal level:-94 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x
Cell 12 - Address: 00:0F:8F:49:FD:30
ESSID:"TrinityAP"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:4/100 Signal level:-93 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
Cell 13 - Address: 00:0F:8F:49:FD:31
ESSID:"TUGuest"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:4/100 Signal level:-93 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 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
Cell 14 - Address: 00:0F:8F:49:FD:34
ESSID:"TUSecure"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:0/100 Signal level:-96 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x


Running lspci gives "Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 01)"

Thanks for the help!

[wieman01]

This is really long because I think there are multiple routers throughout the building. The network I'm trying to connect to is TUSecure.

tnunamak@atlas:~$ sudo iwlist scanning
[sudo] password for tnunamak:
lo Interface doesn't support scanning.

eth1 Interface doesn't support scanning.

eth0 Scan completed :
Cell 14 - Address: 00:0F:8F:49:FD:34
ESSID:"TUSecure"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:0/100 Signal level:-96 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x


Running lspci gives "Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 01)".
Looks quite promising in fact, although there is no mention of PEAP. At least your card recognized the cipher correctly and also detects the right (although generic) authenticaion suite.

Question... the latest (CVS) version of Network Manager apparently supports PEAP. Would it not be easier to compile it from source if this does not work for you? You could open a new thread, send me the link by PM and we try to work it out together.

[wieman01]

I'm using my other computer at my girlfriends house. She has wpa-psk encryption. i have a USB - TEW-424UB 3.0 card. i have 7.10 ubuntu. I can't get online with my ubuntu machine via wire or wireless so i cant really install wpa supplicant on my ubuntnu - but could i somehow how download it and put it on my usb disk and then stick that into my ubuntu?!

my second question is - how do i make the USB - TEW-424UB 3.0 work via wpa supplicant?! should i run some commands so you know how my laptop is setup etc?!
If you are on Ubuntu 7.10 "wpa-supplicant" is already installed. It comes with the default install.

Have you tried the default networking applet called Network Manager? It should let you connect to various types of networks, including secured wireless ones. Try it first and see if it works for you. In that case you can avoid messing around with command line.

[kboykowboy]

If you are on Ubuntu 7.10 "wpa-supplicant" is already installed. It comes with the default install.

Ok nice - what should i look for!?

Have you tried the default networking applet called Network Manager? It should let you connect to various types of networks, including secured wireless ones. Try it first and see if it works for you. In that case you can avoid messing around with command line.

I tryed it, and it finds the network, and when i click connect and type in the password for it it also "loads" and sais acquiering ip adress or something like that.. but after that there is no connection... even though it looks like it should have worked... my network card also sais (on the package) that it supports WPA encryption... so i'm kinda confused!

Thanks to both of you for replying by the way!

[wieman01]

Ok nice - what should i look for!?



I tryed it, and it finds the network, and when i click connect and type in the password for it it also "loads" and sais acquiering ip adress or something like that.. but after that there is no connection... even though it looks like it should have worked... my network card also sais (on the package) that it supports WPA encryption... so i'm kinda confused!

Thanks to both of you for replying by the way!
Do you have a WPA option? And how do you type in the password, what format, etc. Could you post a screenshot of the applet while you enter all the required information?

You can configure WPA manually, but that a lot more hassle.

[buccaneere]

For both wireless and wired please use this one:

VERY IMPORTANT: Please follow post #2 of this thread if you lose connection after a restart. That's a known bug and I posted a workaround there.

I have not lost wireless connectivity after re-start on another occasion.

Thanks much for the help!!!. Your personal help was slightly better than the step by step at the beginning of the thread. One reason: knowing what the equivalent values are to edit into /etc/network/interfaces file. I noticed by the third page, that someone else had asked this question (I read just a little further of the 100+ pages, and am not knowing how many others are wondering the same ).

I have two other laptops to get configured, so I got my fingers crossed (and my little piggies, my eyes, my teeth, etc., ...). Just watch for the cloud toward the west:biggrin:

[wieman01]

I have not lost wireless connectivity after re-start on another occasion.

Thanks much for the help!!!. Your personal help was slightly better than the step by step at the beginning of the thread. One reason: knowing what the equivalent values are to edit into /etc/network/interfaces file. I noticed by the third page, that someone else had asked this question (I read just a little further of the 100+ pages, and am not knowing how many others are wondering the same ).

I have two other laptops to get configured, so I got my fingers crossed (and my little piggies, my eyes, my teeth, etc., ...). Just watch for the cloud toward the west:biggrin:
Waiting then, buddy. :-)

[MarceloPereira]

There shouldn't be a problem. Just use the standard networking applet called Network Manager to configure it. No issues I would think.

Hi Wieman01,

I´ve start using ../interfaces approaching cause NetworkManager didn´t work.

Is there any limitation in the WPA passphrase ? special characters ? If I can remember, the error was concerned to the key.

[wieman01]

Hi Wieman01,

I´ve start using ../interfaces approaching cause NetworkManager didn´t work.

Is there any limitation in the WPA passphrase ? special characters ? If I can remember, the error was concerned to the key.
Some special characters cause problems, however, if you avoid single quotes ' and double quote " you should be ok. Try alphanumeric characters first perhaps.

[tnunamak]

Looks quite promising in fact, although there is no mention of PEAP. At least your card recognized the cipher correctly and also detects the right (although generic) authenticaion suite.

Question... the latest (CVS) version of Network Manager apparently supports PEAP. Would it not be easier to compile it from source if this does not work for you? You could open a new thread, send me the link by PM and we try to work it out together.

Well...

I compiled NetworkManager from source after getting past a few stumbling blocks (dependencies mostly), and installed it, but for some reason it still said the stable version was installed in Synaptic, and when I uninstalled that version, it said NetworkManager was not installed at all, as if the source installation had no effect. I'm not sure what was going on with that.

Anyway, I got it to work using the native drivers...

I uninstalled ndiswrapper, installed fwcutter and bcm43xx through the restricted manager, but I had a wierd issue with some ieee80211 modules not existing with my kernel. I reinstalled the kernel modules package and they appeared, so I used wpa supplicant and it finally authenticated.

This whole thing has been a pretty big headache but it finally works. I'm hopeful that when NetworkManager 0.7 is released it will make all of these problems go away...

Thanks for the help

[wieman01]

Well...

I compiled NetworkManager from source after getting past a few stumbling blocks (dependencies mostly), and installed it, but for some reason it still said the stable version was installed in Synaptic, and when I uninstalled that version, it said NetworkManager was not installed at all, as if the source installation had no effect. I'm not sure what was going on with that.

Anyway, I got it to work using the native drivers...

I uninstalled ndiswrapper, installed fwcutter and bcm43xx through the restricted manager, but I had a wierd issue with some ieee80211 modules not existing with my kernel. I reinstalled the kernel modules package and they appeared, so I used wpa supplicant and it finally authenticated.

This whole thing has been a pretty big headache but it finally works. I'm hopeful that when NetworkManager 0.7 is released it will make all of these problems go away...

Thanks for the help
No problem. Would you do me a favor and post:
sudo iwlist scan
sudo gedit /etc/network/interfaces
Just so that I know what it is supposed to look like when you scan for PEAP networks, etc. That information might help others. Thanks, buddy.

[boob11]

Thanx man

[tnunamak]

No problem. Would you do me a favor and post:


Just so that I know what it is supposed to look like when you scan for PEAP networks, etc. That information might help others. Thanks, buddy.

Sure thing, here they are:

sudo iwlist scan

lo Interface doesn't support scanning.

eth1 Interface doesn't support scanning.

eth0 Scan completed :
Cell 04 - Address: 00:0F:8F:44:30:86
ESSID:"TUSecure"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:68/100 Signal level:-52 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x


My /etc/network/interfaces file
# 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
address 127.0.0.1
netmask 255.0.0.0

# The primary network interface
iface eth1 inet dhcp

# Guest network
iface eth0 inet dhcp
wireless-essid TUGuest

# Secure network
#auto eth0
#iface eth0 inet dhcp
#wpa-driver wext
#wpa-ssid TUSecure
#wpa-ap-scan 1
#wpa-eap LEAP
#wpa-key-mgmt IEEE8021X
#wpa-identity tnunamak
#wpa-password password

auto eth1
auto eth0


I am using wpa_supplicant to authenticate, however. If I get a chance I might try network manager again and uncomment those lines in my interfaces file, but for now, here's my wpa_supplicant.conf file:

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="TUSecure"
key_mgmt=WPA-EAP
scan_ssid=1
proto=WPA2
eap=LEAP
identity="tnunamak"
password="password"
}

In case anyone is wondering how to use wpa_supplicant, create the file and load it with the following command:
sudo wpa_supplicant -Dwext -ieth0 -c wpa_supplicant.conf

Where eth0 is your wireless network device (if you're using ndiswrapper replace Dwext with Dndiswrapper).

[salefish]

Help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
My wireless will not connect on restart, and I have to manually restart it twice to get it to connect each time. My service provider also drops my connection repeatidly in an hour which requires restart, only one.
I followed your tutorial and got my Atheros chipset to work, when I manually restart the connection twice.
I tried to follow your post 2 but when I enter the command "sudo chmod +x wireless-network.sh" I get "chmod: cannot access `wireless-network.sh': No such file or directory" in return.
I then went to your post with member pfs01089 (http://ubuntuforums.org/showthread.php?t=225290&page=11) and followed your instructions on page 11, cd /etc/init.d/
sudo gedit wireless-network.sh
sudo chmod +x wireless-network.sh then /etc/init.d/networking restart and finally cd /etc/rcS.d/
sudo ln -s /etc/init.d/wireless-network.sh S35wireless-network
This seemed to work, now I only have to restart the network manually once (sometimes) after I start the computer.
Can you help me to get this thing to connect on restart, and to stay connected?
Thank you for the excellent tutorial, my wireless configuration is now

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-ssid BarrynTheresaDeux
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <my key here>

This set up seems to be working perfectly

[wieman01]

Help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
My wireless will not connect on restart, and I have to manually restart it twice to get it to connect each time. My service provider also drops my connection repeatidly in an hour which requires restart, only one.
You have to restart it twice? Man, out of the frying pan and into the fire. ;-)

Please do this as well:
sudo ln -s /etc/init.d/wireless-network.sh /etc/rcS.d/S41wireless-network
Now your network will be restart twice during the boot process. That ought to work.

And thanks for the note on...
"chmod: cannot access `wireless-network.sh': No such file or directory"
The command that I had posted were ambiguous and rather confusing, so I have changed them accordingly.

[salefish]

First thank you for the prompt response.
I tried that and I am still having to restart the network twice. The first time the laptop is getting no response from the router. The second time it gets a response on the first request and then connects on the second.
I assume that reconnecting after a dropped connection is a seperate issue. Is this true?
I do want to apologize, I am a complete novice at linux, but I am trying very hard. Thanks for your help.

[wieman01]

First thank you for the prompt response.
I tried that and I am still having to restart the network twice. The first time the laptop is getting no response from the router. The second time it gets a response on the first request and then connects on the second.
I assume that reconnecting after a dropped connection is a seperate issue. Is this true?
I do want to apologize, I am a complete novice at linux, but I am trying very hard. Thanks for your help.
Have you installed Firestarter (GUI for IP tables)?

[salefish]

Um, have I done what with what?
I guess that would be a no. I will work on that right now, let me read up on what it is.
Oh, no firewall of any kind. At least nothing but what comes preinstalled.

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

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:16:e3:e9:dd:fd
Sending on LPF/ath0/00:16:e3:e9:dd:fd
Sending on Socket/fallback
DHCPRELEASE on ath0 to 192.168.1.1 port 67
Ignoring unknown interface eth0=eth0.
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:16:e3:e9:dd:fd
Sending on LPF/ath0/00:16:e3:e9:dd:fd
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6
DHCPOFFER from 192.168.1.1
DHCPREQUEST on ath0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.104 -- renewal in 33536 seconds.
[ OK ]

I changed my settings to enable ssid broadcast, and now it only requires one restart every time.
You have to remember I am very new to Ubuntu and Linux in general, so this is taking me a while to read up on what you are saying.

[wieman01]

Um, have I done what with what?
I guess that would be a no. I will work on that right now, let me read up on what it is.
Oh, no firewall of any kind. At least nothing but what comes preinstalled.

I changed my settings to enable ssid broadcast, and now it only requires one restart every time.
You have to remember I am very new to Ubuntu and Linux in general, so this is taking me a while to read up on what you are saying.
I am sorry if I confuse you. But you are learning quite a number of new things here, which I think are very useful. :-) So I hope you enjoy it.

Having said that, you are right, you don't use Firestarter if you have not installed it yourself. But frankly I am running out of ideas here. Let me do some more thinking & perhaps a little research. No clue as to what we should try next right now.

[salefish]

Well, thanks for sticking with me on this. The biggest reason that I am so adamant about this working is, I own four computers and all of them are wireless. Two desktops and two laptops. I would like to upgrade all but one to Ubuntu, the one being the gaming rig.
Plus the first few lines of the restart state that it is disabling an existing program. Is that something that I should do in terminal, on a permanent basis?
I have just begun reading about the wireless manager WICD. Any thoughts?

[wieman01]

Plus the first few lines of the restart state that it is disabling an existing program. Is that something that I should do in terminal, on a permanent basis?
On a permanent basis, meaning that you should remove it using the package manager (Synaptic).
I have just begun reading about the wireless manager WICD. Any thoughts?
Yes, it is reportedly a fairly good substitute for Network Manager. I would check it out on the 2 laptops perhaps if NM does not do the job. WICD supports the use of Static IP which NM does not.

[salefish]

Yes, is that something that I should disable in synaptic or is that something that I should ignore?

[wieman01]

Yes, is that something that I should disable in synaptic or is that something that I should ignore?
You find Gnome Network Manager in Synaptic. It's better to remove it entirely if you don't use it. Use Synaptic to do so.

[salefish]

Well, the real question is, should I?
And if I should, what should I remove and more specifically how?
gnome-nettool?

[salefish]

Ah-ha a break through! I followed your instructions on post number 64 of this thread and VIOLA it connects. Which obviously means I neglected to do a step you had given.
Now I am going to attempt to strengthen my security.

[wieman01]

Ah-ha a break through! I followed your instructions on post number 64 of this thread and VIOLA it connects. Which obviously means I neglected to do a step you had given.
Now I am going to attempt to strengthen my security.
Great!

If you want to remove Network Manager by the way (which is totally safe as you can reinstall it anytime) you have to do:
sudo apt-get remove network-manager-gnome
You install it issuing:
sudo apt-get install network-manager-gnome

[phekdra]

Hello - I've just moved to Ubuntu from Gentoo and having been having problems with my rt61 card. As many here I've had to follow the instructions of post #2 in order to get my wireless network to appear on startup. I've trawled through most of the pages in this thread but I haven't seen any explanation of why this works and what is the bug that's causing it. Does anyone know? Is there a link to the related bug as I was unable to find it?

Additionally I had the card working reliably under Gentoo with the latest CVS rt2x00 drivers merged into the kernel, but with Ubuntu the network keeps stalling sporadically, requiring a restart. I presume this is due to Ubuntu using older versions of the drivers. Can anyone give me any idea how often the ubuntu kernel is generally updated as I believe that the rt2x00 drivers are included as part of vanilla 2.6.24.

Don't worry - I'm not thinking of going back to Gentoo yet :p but it is a little frustrating...

Andrew

[wieman01]

Hello - I've just moved to Ubuntu from Gentoo and having been having problems with my rt61 card. As many here I've had to follow the instructions of post #2 in order to get my wireless network to appear on startup. I've trawled through most of the pages in this thread but I haven't seen any explanation of why this works and what is the bug that's causing it. Does anyone know? Is there a link to the related bug as I was unable to find it?
So far I have not put much effort into it, so I cannot answer your question... All I know is that it is necessary in quite a number of cases.
Additionally I had the card working reliably under Gentoo with the latest CVS rt2x00 drivers merged into the kernel, but with Ubuntu the network keeps stalling sporadically, requiring a restart. I presume this is due to Ubuntu using older versions of the drivers. Can anyone give me any idea how often the ubuntu kernel is generally updated as I believe that the rt2x00 drivers are included as part of vanilla 2.6.24.
I don't know when the new Ralink drivers will be available. If you have stability problems, you might want to consider my "ndiswrapper" tutorial or compile Serialmonkey's driver from source. I prefer the use of "ndiswrapper" since it works great and lets you use Network Manager for WPA(2) security.

[phekdra]

So far I have not put much effort into it, so I cannot answer your question... All I know is that it is necessary in quite a number of cases.

Ah. Perhaps I will look into it myself!

I don't know when the new Ralink drivers will be available. If you have stability problems, you might want to consider my "ndiswrapper" tutorial or compile Serialmonkey's driver from source. I prefer the use of "ndiswrapper" since it works great and lets you use Network Manager for WPA(2) security.

I might try ndiswrapper, although I've been trying to avoid that up until now! Under Gentoo I had the most problems with the Ralink drivers (and the Serialmonkey enhanced versions) which prompted my switch to the beta rt2x00 drivers which worked perfectly, and which according to lsmod I'm using at the moment, so I can only assume that the ones provided by Ubuntu are an older, more bugged version. As you say, building them from source might be a solution until the developers (Linux and Ubuntu) release the new kernel with included rt2x00 drivers. Hopefully it won't be too long... :neutral:

Andrew

[kboykowboy]

Do you have a WPA option? And how do you type in the password, what format, etc. Could you post a screenshot of the applet while you enter all the required information?

You can configure WPA manually, but that a lot more hassle.

I just type in the word its like "jeggadgodtdetlortvirkede" just type it ind like that... like it's a normal word. I may be able to take a screenshot tonight. I've been really busy.

once again thanks alot to all of you for helping!

[kboykowboy]

Do you have a WPA option? And how do you type in the password, what format, etc. Could you post a screenshot of the applet while you enter all the required information?

You can configure WPA manually, but that a lot more hassle.

Hi Wieman01
now i finaly got the screen shots taken. hope they help out?!

http://picasaweb.google.com/KboyKowboy/Ubuntu

the General-, DNS-, and Host-tabs are completely blank.

Just to sum up. This networkcard works WITH the xubuntu on my wpe encryptet network, so i ASSUME the network card is installed correctly.

thanks to all!

K

[wieman01]

Hi Wieman01
now i finaly got the screen shots taken. hope they help out?!

http://picasaweb.google.com/KboyKowboy/Ubuntu

the General-, DNS-, and Host-tabs are completely blank.

Just to sum up. This networkcard works WITH the xubuntu on my wpe encryptet network, so i ASSUME the network card is installed correctly.

thanks to all!

K
Just a shot in the dark, but would changing the network name to one that does not contain spaces (blanks) help?

[kboykowboy]

Just a shot in the dark, but would changing the network name to one that does not contain spaces (blanks) help?

it might, but it is not my network ... my girfriend lives in a place where she kinda just rents the network.... and i can't change any settings on it! sooo... all i can do is change settings on the computer!

[buccaneere]

@buccaneere:

Ok, edit your "interfaces" file and post this (replacing all contents):

The restart the network and post the output:


By the way... why do you not use Network Manager? Do you need a static IP? The script above is for DHCP.

Where's that wireless swami guru???

I had the disk out of the machine, to copy all contents onto the original Acer HDD. All went perfect, including settings. Almost.

Wireless did not auto connect this time, as it had, after you first got me linked.

I brought up 'interfaces' file, and found some extras tagged onto the end of the interfaces list:

auto lo
iface lo inet loopback

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-ssid cobweb
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 2057043c4c9c2e031ac0ba3c960f4c5b3b8c8a5b319cbaab4a 93445f429f0727
wireless-essid cobweb
wireless-key passcobwebcobwebphrase

iface eth0 inet dhcp

So I made a back-up, deleted the vagrant electrons (in red), restarted the network, and I got the auto connect.

Is this the same bug described in post #2?

[wieman01]

@buccaneere:

You definitely need to remove those lines in red as you have done, because you cannot have 2 different setups at the time using this approach.

The reconnection issue could relate to what is outlined in post #2, yes. Check it out. Do you have other issues apart from this?

[buccaneere]

@buccaneere:

You definitely need to remove those lines in red as you have done, because you cannot have 2 different setups at the time using this approach.

The reconnection issue could relate to what is outlined in post #2, yes. Check it out. Do you have other issues apart from this?

No, no other issues. Everything that you said was spot on.

Now, on to the other three wireless machines...

[hobojjr]

so this is only for wpa? How about wep?

[wieman01]

so this is only for wpa? How about wep?
Only WEP I am afraid. Why do you not use Network Manager for WEP? Or do you need a static IP? In that case I could help. Please explain what the exact issue is and I'll try to help you out with a script.

[hobojjr]

I found http://mediakey.dk/~cc/howto-use-wep-encryption-with-ubuntu-linux/

I was setting up ubuntu server 7.10 without desktop and I didn't want to change my network setting from wep to wap because other people where using it already.

[Sordelka]

4. NetworkManager, Wifi-Radar & similar wireless configuration tools are disabled/turned off and not in use.

How to actually turn off the Network Manager?

[wieman01]

How to actually turn off the Network Manager?
Simply remove it using Synaptic. You can reinstall it later on if you would like to:
sudo apt-get remove network-manager-gnome

[din]

Hi.
after i type :
sudo gedit /etc/network/interfaces

I get :
auto lo
iface lo inet loopback

iwlist scan
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
eth1 No scan results
irda0 Interface doesn't support scanning.

when: iwconfig
i get info about eth1 wireless.

What i missed?
It meens i dont have wireless installed?

thanks.

[wieman01]

iwlist scan
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
eth1 No scan results
irda0 Interface doesn't support scanning.
No scan results generally means bad news. What hardware have you got?

Please post:
sudo lshw -C network

[din]

No scan results generally means bad news. What hardware have you got?

Please post:

Hi

A use laptop : Acer Extenza 5620Z

results:

sudo lshw -C network
*-network
description: Ethernet interface
product: NetLink BCM5787M Gigabit Ethernet PCI Express
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 02
serial: 00:1d:72:05:08:c0
capacity: 1GB/s
width: 64 bits
clock: 33MHz
capabilities: pm vpd msi pciexpress bus_master cap_list ethernet physical mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=3.77 firmware=5787m-v3.23 latency=0 link=no module=tg3 multicast=yes port=twisted pair
*-network DISABLED
description: Wireless interface
product: BCM94311MCG wlan mini-PCI
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:04:00.0
logical name: eth1
version: 01
serial: 00:1d:d9:68:fd:7a
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=bcm43xx driverversion=2.6.22-14-generic latency=0 link=no module=bcm43xx multicast=yes wireless=IEEE 802.11b/g

[wieman01]

@din:

Oh, broadcom. A notorious troublemaker. Look for tutorials for the bcm43xx chipset. There are a few in the forums. I am sorry I cannot advise more than that.

[DasCrushinator]

https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx/Feisty_No-Fluff

That works fine for me on both FF and GG.

[wieman01]

https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx/Feisty_No-Fluff

That works fine for me on both FF and GG.
Cool, Thanks, dude.

[din]

OK
Thanks

[DasCrushinator]

@ wieman01 and @din: No problem :)

[buccaneere]

Hey sensai Wieman...

EDITED!!!

Got it.

2 down; 2 to go.

'interfaces' file modified from 'wpa-driver madwifi', to wpa-driver wext . Machine is a Gateway MX6xxx/broadcom 4318

Connection!:guitar:

Now, onto the new desktop build w/TP-Link wireless card (atheros), then the HPdv9xxx (???).

[wieman01]

Hey sensai Wieman...

EDITED!!!

Got it.

2 down; 2 to go.

Now, onto the new desktop build w/TP-Link wireless card (atheros), then the HPdv9xxx (???).
Cool. Keep me in the loop, dude!

[gizmom]

Hi, I am rather a beginner with Linuw and cannot connect to my wireless network. I know that it is because my network uses wpa-psk and i need to set up support for this in Linux, but have no idea how to start. I have read lots of posts on the subject on the forums but they all just confuse me further. Is there a simple method to allow Linux to communicate via WPA?
Linux can see my network and wireless card without problems but cannot pass security to actually connect.

[gizmom]

Hi, I am rather a beginner with Linuw and cannot connect to my wireless network. I know that it is because my network uses wpa-psk and i need to set up support for this in Linux, but have no idea how to start. I have read lots of posts on the subject on the forums but they all just confuse me further. Is there a simple method to allow Linux to communicate via WPA?
Linux can see my network and wireless card without problems but cannot pass security to actually connect

[Schiz0]

I can't seem to get connected to my router. I'm using a DLink WBR-1310 using WPA2 and AES on a hidden network.

The following information as requested:

# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
(There aren't any routing entries)

# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 802.11b/g Mode:Managed Frequency=2.462 GHz
Access Point: Not-Associated Bit Rate:11 Mb/s
Retry:on Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

# ifconfig
eth0 Link encap:Ethernet HWaddr 00:03:25:45:0E:68
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
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:C0:A8:DF:FB:81
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:153 dropped:189 overruns:0 frame:0
TX packets:2040 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:85680 (83.6 KB)
Interrupt:18 Memory:f886a000-f886a100

# iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1B:11:54:1B:9D
ESSID:"<hidden>"
Protocol:IEEE 802.11g
Mode:Master
Channel:1
Encryption key:on
Bit Rates:54 Mb/s
Extra: Rates (Mb/s): 1 2 5.5 9 11 6 12 18 24 36 48 54
Quality:0 Signal level:0 Noise level:158
Extra: Last beacon: 64ms ago

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

audo wlan0

iface wlan0 inet static
address 192.168.1.211
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid TheFearsomeRouter
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk fb653bab0e272741bfe3762a4a805424003c36d9c598a946f6 5bf31b472c3db6

#iface eth0 inet dhcp

# cat /etc/modprobe.d/ndiswrapper
(File not found)

# cat /etc/resolv.conf
nameserver 192.168.1.1
nameserver 4.2.2.1

I did get it working at one point with help from a guy on IRC (So I know the hardware works). However, I'm completely stuck now. Thanks for any help.

[wieman01]

Hi, I am rather a beginner with Linuw and cannot connect to my wireless network. I know that it is because my network uses wpa-psk and i need to set up support for this in Linux, but have no idea how to start. I have read lots of posts on the subject on the forums but they all just confuse me further. Is there a simple method to allow Linux to communicate via WPA?
Linux can see my network and wireless card without problems but cannot pass security to actually connect
The easiest option is Network Manager which happens to be the default network application that you see in the upper right corner. It should let you connect to all sorts of wireless networks including WPA secured ones. If you don't have a WPA option, then your wireless adapter does not support it because...

A. the current driver cannot handle WPA,
B. the hardware is not capable of WPA.

To begin with, what hardware have you got? Please also post the results of this:
sudo iwlist scan
From command line please. Enter your password when prompted for it.

[wieman01]

I can't seem to get connected to my router. I'm using a DLink WBR-1310 using WPA2 and AES on a hidden network.

The following information as requested:

# iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1B:11:54:1B:9D
ESSID:"<hidden>"
Protocol:IEEE 802.11g
Mode:Master
Channel:1
Encryption key:on
Bit Rates:54 Mb/s
Extra: Rates (Mb/s): 1 2 5.5 9 11 6 12 18 24 36 48 54
Quality:0 Signal level:0 Noise level:158
Extra: Last beacon: 64ms ago

I did get it working at one point with help from a guy on IRC (So I know the hardware works). However, I'm completely stuck now. Thanks for any help.
The script looks fine, however, the scan is not too promising. The scan should recognize the WPA network as such and should mention that is a WPA secured one. In your card it doesn't so I suspect that the kernel driver cannot handle it.

What chipset is your card and what driver are you using in case you know?

[Schiz0]

The script looks fine, however, the scan is not too promising. The scan should recognize the WPA network as such and should mention that is a WPA secured one. In your card it doesn't so I suspect that the kernel driver cannot handle it.

What chipset is your card and what driver are you using in case you know?

The output for lshw for the wireless adapter:
*-network
description: Wireless interface
product: RTL-8185 IEEE 802.11a/b/g Wireless LAN Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 9
bus info: pci@0000:08:09.0
logical name: wlan0
version: 20
serial: 00:c0:a8:df:fb:81
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=rtl8180 ip=192.168.1.211 latency=64 maxlatency=64 mingnt=32 module=r8180 multicast=yes wireless=802.11b/g


Thanks for the help, I appreciate the time.

[wieman01]

The output for lshw for the wireless adapter:
*-network
description: Wireless interface
product: RTL-8185 IEEE 802.11a/b/g Wireless LAN Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 9
bus info: pci@0000:08:09.0
logical name: wlan0
version: 20
serial: 00:c0:a8:df:fb:81
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=rtl8180 ip=192.168.1.211 latency=64 maxlatency=64 mingnt=32 module=r8180 multicast=yes wireless=802.11b/g


Thanks for the help, I appreciate the time.
Ah... bad news. I don't think the rtl8180 supports WPA... You need to do some further research, but I have not heard much good stuff about it (at least in that respect).

[kboykowboy]

Hey All -
so i assume there is no way of getting on the wpa network onless you have admin rights on it and can change the settings of the router?!

wish all a nice december!

[loopiv]

Thanks for the howto. It worked for me, but I needed to do the below:

-
apt-get remove network-manager
apt-get install ndiswrapper-utils-1.9 ndiswrapper-common
download the driver file from linksys. It's an EXE file, but you can unzip it and find the driver for version 4.
depmod -a
modprobe ndiswrapper
ndiswrapper -i <version 4 .inf file>
blacklist the included rt2x00 and rt2500 drivers. Edited /etc/modprobe.d/blacklist and added the following at the end of the file:

blacklist rt2500usb
blacklist rt2x00usb
blacklist rt2x00lib

- add ndiswrapper to /etc/modules
- add the following to /etc/init.d/rc.local
/etc/init.d/networking restart
- reboot

[wieman01]

Hey All -
so i assume there is no way of getting on the wpa network onless you have admin rights on it and can change the settings of the router?!

wish all a nice december!
Yes, that's pretty much it. You need to know the network key or have access to the router. Two options in fact.

[kboykowboy]

Yes, that's pretty much it. You need to know the network key ...

What's the network key? i know pretty much everything about the network, but can't change any of the settings !

[wieman01]

What's the network key? i know pretty much everything about the network, but can't change any of the settings !
The network key is the secret WPA passphrase if you know what I mean. A password that lets you access the wireless network. Have you got it?

[merlin666]

Wow this howto is getting long. Anyway, I got the wpa going a few months ago but it was not consistent. I tried again with new ndiswrapper, but have no success. iwlist -scan shows all sorts of networks around on eth1, just not mine. I changed wlan0 to eth1 in the interfaces file, but that did not help. Are there any other diagnostics that I could try?

[wieman01]

Wow this howto is getting long. Anyway, I got the wpa going a few months ago but it was not consistent. I tried again with new ndiswrapper, but have no success. iwlist -scan shows all sorts of networks around on eth1, just not mine. I changed wlan0 to eth1 in the interfaces file, but that did not help. Are there any other diagnostics that I could try?
Man, that's sort of strange. You have the ability to see other networks but not your own? How odd is that?! Would you mind posting the results of:
sudo iwlist scan
Let's see what is going on... What hardware have you got?

[merlin666]

Man, that's sort of strange. You have the ability to see other networks but not your own? How odd is that?! Would you mind posting the results of:

Let's see what is going on... What hardware have you got?

I have an emachines laptop running 64-bit Gutsy (netbc564 driver), dlink 524 router. I rebooted the router and now I can see my MAC address listed, also the iwlist scan shows my network, though as cell 05 and not on top as I would expect. strange thing is that there's also an eth1:avahi. I had this before and it seems to be an indicator of some dysfunction. So although I seem to be connected, there is no transmission of data once I unplug the network cable and disable eth0.

rolf@ubuntu:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:14:D1:35:36:62
ESSID:"TRENDnet"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:40/100 Signal level:-70 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:14:BF:8D:FB:97
ESSID:"linksys"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:87/100 Signal level:-40 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 03 - Address: 00:40:96:A1:01:18
ESSID:"TELUS"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:17/100 Signal level:-85 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 04 - Address: 00:16:B6:6B:AA:69
ESSID:"Above0"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.432 GHz (Channel 5)
Quality:12/100 Signal level:-88 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
Cell 05 - Address: 00:11:95:37:5D:CD
ESSID:"aldersbrook"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:87/100 Signal level:-40 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK

rolf@ubuntu:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:03:25:15:5F:EB
inet addr:192.168.0.101 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::203:25ff:fe15:5feb/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4868 errors:0 dropped:0 overruns:0 frame:0
TX packets:3960 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5453931 (5.2 MB) TX bytes:361309 (352.8 KB)
Interrupt:23 Base address:0x1800

eth1 Link encap:Ethernet HWaddr 00:90:4B:8C:F9:E7
inet6 addr: fe80::290:4bff:fe8c:f9e7/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:974 errors:0 dropped:0 overruns:0 frame:0
TX packets:991 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:110062 (107.4 KB) TX bytes:138388 (135.1 KB)
Interrupt:18 Memory:d0000000-d0002000

eth1:avah Link encap:Ethernet HWaddr 00:90:4B:8C:F9:E7
inet addr:169.254.11.50 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:18 Memory:d0000000-d0002000

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

rolf@ubuntu:~$

[wieman01]

I have an emachines laptop running 64-bit Gutsy (netbc564 driver), dlink 524 router. I rebooted the router and now I can see my MAC address listed, also the iwlist scan shows my network, though as cell 05 and not on top as I would expect. strange thing is that there's also an eth1:avahi. I had this before and it seems to be an indicator of some dysfunction. So although I seem to be connected, there is no transmission of data once I unplug the network cable and disable eth0.
Sorry... I have not smart advice to offer, really. Beats me.

[parameter]

This post is from a year and a half ago. Three new versions of Ubuntu been released since the post was made. Is this post still relevant?

[wieman01]

This post is from a year and a half ago. Three new versions of Ubuntu been released since the post was made. Is this post still relevant?
According to the poll (which I keep an eye on), yes, it is. There is a support thread where you should have posted your question... see post #2. There you see it is still relevant (hope this changes though after the next release).

[kboykowboy]

The network key is the secret WPA passphrase if you know what I mean. A password that lets you access the wireless network. Have you got it?

YEs - i have all info about the network, but i just can't change it (since it is not my network to administrate). as i wrote earlyer the network is called "lykkes Net" and i think you asked if i could change the name so there was no blank spaces in it... and that's a "no"

Marry chrismas !!

[buccaneere]

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...

Oookay... Where's wieman01WKB (wireless knowledge base)

How do I determine the value for 'boot sequence'; i. e., S40

2 of my 4 boxes have atheros wireless, and need the 'post-boot restart fix'.

Thanks again!!!

[wieman01]

Oookay... Where's wieman01WKB (wireless knowledge base)

How do I determine the value for 'boot sequence'; i. e., S40

2 of my 4 boxes have atheros wireless, and need the 'post-boot restart fix'.

Thanks again!!!
Hey there, buddy!

Use S40 to begin with. Change it to another value (e.g. S50) if that does not work for you. But S40 should really do.

[ebutton]

Wow! This thread certainly IS STILL VALID! I just got Gutsy/ Intel 3945ABG working with a "full up" WPA2 Enterprise network in my wireless lab at work.

That might have happened a few days sooner, but I thought something was missing from this HowTo - how to install the client certificate from my CA.

Why is that step, required with XP, not needed? I don't understand how the client can authenticate my RADIUS server's Certificate, since it's from a local/private CA.

By the way, I'm using a Cisco router for DHCP service and a ZeroShell virtual appliance (inside VM Player on an XP host) as my CA and RADIUS servers. ZeroShell also can be a DHCP server.

[ebutton]

Hi.
If you are still having problems, go back to the beginning of this thread and find the variations of WPA, PSK, PEAP, and so forth that have been edited in. (Note also the Change Log a little further down that first page.) Read a little more about WEP, WPA, and WPA2 (Google) if you need to better understand the very confusing and huge quantity of acronyms and options in wireless security. Then you should be able to quickly choose which method you need.

For me, I needed to read the caveat about not putting quotation marks around the SSID and that I could substitute eth1 for wlan0 in the /etc/networks/interfaces file. Other than that, I just did a copy/paste of the section "***Sample conf. PEAP, AES, DHCP, ESSID broadcast***" to my interfaces file, and a copy/paste of the network restart command to a shell window. It worked immediately.

In fact, it was anticlimactic after all the research/learning curve activity. Still I was very amazed and happy - and very thankful to wieman01 for doing the "heavy lifting" for us.

Warm Regards,
EdB

[wieman01]

In fact, it was anticlimactic after all the research/learning curve activity. Still I was very amazed and happy - and very thankful to wieman01 for doing the "heavy lifting" for us.
And you are very welcome. Thanks for letting me know this still works. :-)

[jago25_98]

This is a very long thread and I've been keeping off replying for as long as I can.

But now the question.

What else do you guys use for network configuration? I use knetworkmanager so I don't have to go through all the guff you guys are going through on this thread... only it could be working better.


I've been using NetworkManager via knetworkmanager, and the problem is it often doesn't allow me to select the correct encryption (WPA), listing only WEP. I then have to use `Connect to other wireless network` to then successfully connect via WPA.

Also, it doesn't connect on it's own. The connect button is greyed out until I change an option and put it back again.

Try out these helping tools. You may need them if you travel to new networks. Perhaps there is a better network config aide available? Command line perhaps?

[wieman01]

This is a very long thread and I've been keeping off replying for as long as I can.

But now the question.

What else do you guys use for network configuration? I use knetworkmanager so I don't have to go through all the guff you guys are going through on this thread... only it could be working better.


I've been using NetworkManager via knetworkmanager, and the problem is it often doesn't allow me to select the correct encryption (WPA), listing only WEP. I then have to use `Connect to other wireless network` to then successfully connect via WPA.

Also, it doesn't connect on it's own. The connect button is greyed out until I change an option and put it back again.

Try out these helping tools. You may need them if you travel to new networks. Perhaps there is a better network config aide available? Command line perhaps?
Personally I use KNetworkManager (Kubuntu), but as it does not support static IP addresses, it is of limited use as far as my local network is concerned. Hence this thread. Also there is no reconnection issue, this version lets you connect at boot. So therefore the thread is still valid, although I wished it wasn't.

[buccaneere]

Hey there, buddy!

Use S40 to begin with. Change it to another value (e.g. S50) if that does not work for you. But S40 should really do.

Both atheros chipset-equipped boxes took boot sequence value S40. Good job!

Why S40 tho'?

And what DID we do? Add a totally new startup process? Why could not the restart command be added to an existing process?

[buccaneere]

I've been using NetworkManager via knetworkmanager, and the problem is it often doesn't allow me to select the correct encryption (WPA), listing only WEP.



I had this problem.

The Broadcom-equipped machine ( 4318 ) was properly configured, thanks to wieman. Then, I updated from Edgy, to 7.04, and lost configuration, and all clues to resolve again. The GUI encryption option was as yours - only WEP. :confused:

I could not re-configure. It was a new install; I had to re-install.

I know only that it was a driver conflict gig.

[wieman01]

Both atheros chipset-equipped boxes took boot sequence value S40. Good job!

Why S40 tho'?

And what DID we do? Add a totally new startup process? Why could not the restart command be added to an existing process?
S40 is sort of reserved for networking. Each boot range is reserved for certain processes, although I cannot remember all of them. S40 is networking, but of course you could change that.

What we did is we simply restarted the network b/c wpa-supplicant requires you to do so. So no new processes has been added, we merely "killed" the old one and started a new one. As simple as that.

Google for "boot sequence, linux, run levels" to learn more about it. :-)

[SonWon]

Help! :(

Can't get wireless working using wpa-1, works fine with WEP. Using Ubuntu 6.10 Edgy Eft. Here is the information:

route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.128.0 * 255.255.255.0 U 0 0 0 vmnet1
192.168.99.0 * 255.255.255.0 U 0 0 0 vmnet8


iwconfig
lo no wireless extensions.

eth1 unassociated ESSID:"RDC"
Mode:Managed Frequency=2.412 GHz Access Point: 00:18:F8:75:D3:5B
Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0
Retry 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:710 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 no wireless extensions.

vmnet1 no wireless extensions.

vmnet8 no wireless extensions.


sudo iwlist scan
lo Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:18:F8:75:D3:5B
ESSID:"RDC"
Protocol:IEEE 802.11bg
Mode:Master
Channel:1
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=73/100 Signal level=-54 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 2980ms ago
Cell 02 - Address: 00:0F:B5:E5:7D:CE
ESSID:"Cutco"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=59/100 Signal level=-65 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 3004ms ago
Cell 03 - Address: 00:1C:58:6D:A5:70
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; 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=48/100 Signal level=-72 dBm
Extra: Last beacon: 3004ms ago
Cell 04 - Address: 00:50:F2:CD:A9:4A
ESSID:"MSHOME"
Protocol:IEEE 802.11b
Mode:Master
Channel:6
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Quality=31/100 Signal level=-81 dBm
Extra: Last beacon: 3108ms ago
Cell 05 - Address: 00:0D:72:B6:39:01
ESSID:"2WIRE663"
Protocol:IEEE 802.11b
Mode:Master
Channel:6
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
Quality=33/100 Signal level=-80 dBm
Extra: Last beacon: 3124ms ago
Cell 06 - Address: 00:15:62:8C:B5:F0
ESSID:"<hidden>"
Protocol:IEEE 802.11bg
Mode:Master
Channel:1
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=37/100 Signal level=-78 dBm
Extra: Last beacon: 3240ms ago
Cell 07 - Address: 00:1B:5B:F3:5F:09
ESSID:"2WIRE162"
Protocol:IEEE 802.11bg
Mode:Master
Channel:2
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=31/100 Signal level=-81 dBm
Extra: Last beacon: 7868ms ago

eth0 Interface doesn't support scanning.

vmnet1 Interface doesn't support scanning.

vmnet8 Interface doesn't support scanning.


sudo lshw -C network
*-network:0
description: Wireless interface
product: PRO/Wireless 2200BG Network Connection
vendor: Intel Corporation
physical id: a
bus info: pci@00:0a.0
logical name: eth1
version: 05
serial: 00:0e:35:0c:1b:85
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ipw2200 driverversion=1.1.2kmprq firmware=ABG:9.0.2.6 (Mar 22 2005) link=yes multicast=yes wireless=IEEE 802.11g
resources: iomemory:f0000000-f0000fff irq:201
*-network:1
description: Ethernet interface
product: VT6102 [Rhine-II]
vendor: VIA Technologies, Inc.
physical id: 12
bus info: pci@00:12.0
logical name: eth0
version: 74
serial: 00:40:d0:53:3d:af
size: 10MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegociation
configuration: autonegociation=on broadcast=yes driver=via-rhine driverversion=1.2.0-2.6 duplex=half link=no multicast=yes port=MII speed=10MB/s
resources: ioport:e300-e3ff iomemory:f0001900-f00019ff irq:209


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


iface eth0 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp



auto eth0

iface eth1 inet dhcp
wpa-driver wext
wpa-ssid RDC
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <my_hex_key>




auto eth1

[graysn05]

I'm connecting to a network that uses wpa, tkip, and peap

my /etc/network/interfaces is

iface eth1 inet dhcp
wpa-driver wext
wpa-ssid UNI-Wireless
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-eap PEAP
wpa-key-mgmt WPA-EAP
wpa-identity ad-its\compsci
wpa-password **********

I've also set up the startup script from post #2

This all works but the startup is amazingly slow. is there a way to have the script just restart the wireless connection and not the ethernet connection? (Eth0) in my case.

[SonWon]

Shameless bump.

[buccaneere]

I'm connecting to a network that uses wpa, tkip, and peap

my /etc/network/interfaces is

iface eth1 inet dhcp
wpa-driver wext
wpa-ssid UNI-Wireless
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-eap PEAP
wpa-key-mgmt WPA-EAP
wpa-identity ad-its\compsci
wpa-password **********

I've also set up the startup script from post #2

This all works but the startup is amazingly slow. is there a way to have the script just restart the wireless connection and not the ethernet connection? (Eth0) in my case.

You say your startup is slow.

???

Do you mean connection speed maybe?

I found a thread for configurin' wireless, which said that of two ways to configure wireless [broadcom, I think]. one of the two supports only 11megs, and the other supports 54megs connection speed.

Just a thought........

[wieman01]

Help! :(

Can't get wireless working using wpa-1, works fine with WEP. Using Ubuntu 6.10 Edgy Eft. Here is the information:

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


iface eth0 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp



auto eth0

iface eth1 inet dhcp
wpa-driver wext
wpa-ssid RDC
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <my_hex_key>

auto eth1

You script looks fine in fact. Please do this for me and post the results:
sudo ifdown -v eth1
sudo ifup -v eth1
In the meantime please check if you have somehow made a mistake while generating the pass phrase. Please also check post #2 of this thread. You might have to restart the network.

[wieman01]

I'm connecting to a network that uses wpa, tkip, and peap

my /etc/network/interfaces is

iface eth1 inet dhcp
wpa-driver wext
wpa-ssid UNI-Wireless
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-eap PEAP
wpa-key-mgmt WPA-EAP
wpa-identity ad-its\compsci
wpa-password **********

I've also set up the startup script from post #2

This all works but the startup is amazingly slow. is there a way to have the script just restart the wireless connection and not the ethernet connection? (Eth0) in my case.
Reverting to a static IP address instead of DHCP will definitely speed things up. That's the only option I can offer.

[SonWon]

You script looks fine in fact. Please do this for me and post the results:

Quote:
sudo ifdown -v eth1

Quote:
sudo ifup -v eth1

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/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 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:0e:35:0c:1b:85
Sending on LPF/eth1/00:0e:35:0c:1b:85
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/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.eth1.pid
Stopped /sbin/wpa_supplicant (pid 8621).

sudo ifup -v eth1
ifup: interface eth1 already configured

[wieman01]

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/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 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:0e:35:0c:1b:85
Sending on LPF/eth1/00:0e:35:0c:1b:85
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/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.eth1.pid
Stopped /sbin/wpa_supplicant (pid 8621).

sudo ifup -v eth1
ifup: interface eth1 already configured
First off I would remove Network Manager (you can reinstall it later on). Second, what network hardware have you got?

[SonWon]

what network hardware have you got?

Intel PRO/Wireless 2200BG Network


I would remove Network Manager

I move around a lot will this make it harder to reconfigure the wireless stuff? I can edit each time if needed but I guess I am lazy. :)


Thank you for your help.

[wieman01]

Intel PRO/Wireless 2200BG Network




I move around a lot will this make it harder to reconfigure the wireless stuff? I can edit each time if needed but I guess I am lazy. :)


Thank you for your help.
IPW2200BG? Man, you don't need this tutorial. :-) Why don't you use Network Manager instead? It only support DHCP (no static IP addresses) but it does a fairly good job, in particular if you need roaming. Why bother (politely asked)?

[SonWon]

Why don't you use Network Manager instead?

Even after just over a year of running Ubuntu I am still a nub. :)

When I goto the Network Manager applet eth0 and eth1 do not show in the list?

I also never see the signal strength on the gnome menu bar?

And the wireless network does work with a wep or open network which I can configure from the System | Administration | Networking menu pick (Network Administration Tool?).

Maybe edgy eft problem?

Thank you again,

[wieman01]

Maybe edgy eft problem?

Thank you again,
Not sure, really. But update "/etc/network/interfaces" so that it looks like:
auto lo
iface lo inet loopback

Only 2 lines left, don't be afraid, you can restore the contents anytime you like. :-) Then reboot the PC and see if NM detects your interfaces.

[graysn05]

Reverting to a static IP address instead of DHCP will definitely speed things up. That's the only option I can offer.

I work for a university and we are trying to get the dual boot laptops to connect to wireless for active directory authentication. I don't have the option to static IP since someone else manages the wireless. Did anyone get the script from post #32 to work? That seemed just restart the wireless connection at startup rather than all networking. When the machines starts one can see when this networking restart happens and it restarts the wired connection first which is where it hangs for a little while.

Thanks.

[wieman01]

I work for a university and we are trying to get the dual boot laptops to connect to wireless for active directory authentication. I don't have the option to static IP since someone else manages the wireless. Did anyone get the script from post #32 to work? That seemed just restart the wireless connection at startup rather than all networking. When the machines starts one can see when this networking restart happens and it restarts the wired connection first which is where it hangs for a little while.

Thanks.
Question... Does Network Manager not support PEAP? I thought it does. That would solve all your problems. The latest version (Gutsy) should do the job.

[elamericano]

Question... Does Network Manager not support PEAP?
NetworkManager supports PEAP.

[SonWon]

Only 2 lines left, don't be afraid, you can restore the contents anytime you like. Then reboot the PC and see if NM detects your interfaces.

I was confused, I do have the icon on the Gnome menubar, sorry. I did delete all of the lines but the two and after reboot no difference. When I go to configure the network setting via the icon there are no settings for WEP, PSA, etc.? Only thing available is SSID, password type, network passwork.

Thank you,

[ilektron]

Thank you to whomever set up these wireless tutorials. After days of searching finally a tutorial on using /etc/network/interfaces for wireless w/o a gui. Is all this documented somewhere?

[wieman01]

Thank you to whomever set up these wireless tutorials. After days of searching finally a tutorial on using /etc/network/interfaces for wireless w/o a gui. Is all this documented somewhere?
It is documented here. :-) I could not find any other documentation back then (2006) but it might have changed in the meantime, who knows.

[kboykowboy]

YEs - i have all info about the network, but i just can't change it (since it is not my network to administrate). as i wrote earlyer the network is called "lykkes Net" and i think you asked if i could change the name so there was no blank spaces in it... and that's a "no"

Marry chrismas !!

bounce .... Think this threat shows Ubuntu still have some way to go before it is really human... hope the next dist. will have good wpa support - untill then maybe i just have to give up...

[graysn05]

Question... Does Network Manager not support PEAP? I thought it does. That would solve all your problems. The latest version (Gutsy) should do the job.

It does support PEAP, but we need the computer to connect at startup so that it connects before attempting to connect to the ldap server. i'm thinking about writing my own script to restart just the wireless connection rather than calling /etc/init.d/networking restart, we'll see how it goes.

[wieman01]

It does support PEAP, but we need the computer to connect at startup so that it connects before attempting to connect to the ldap server. i'm thinking about writing my own script to restart just the wireless connection rather than calling /etc/init.d/networking restart, we'll see how it goes.
Then simply do a "ifdown" and "ifup". And revert to using a static IP address which will speed up the boot process. Keep us posted.

[rootware]

Just one question please, where should I write my WPA-2 password to make it permanent?

Currently I write @ every boot-time the password. And how can I make to make the wlan card to connect at the boot time? Because I have to wait after the sistem has been loaded about 10 seconds for it to communicate with the wireless router.

[rootware]

Just one question please, where should I write my WPA-2 password to make it permanent?

Currently I write @ every boot-time the password. And how can I make to make the wlan card to connect at the boot time? Because I have to wait after the sistem has been loaded about 30 seconds for it to communicate with the wireless router.

[wieman01]

Just one question please, where should I write my WPA-2 password to make it permanent?

Currently I write @ every boot-time the password. And how can I make to make the wlan card to connect at the boot time? Because I have to wait after the sistem has been loaded about 30 seconds for it to communicate with the wireless router.
Permanent? Did you follow this tutorial or are you using Network Manager for wireless networking? What version of Ubuntu are you on?

[rootware]

Permanent? Did you follow this tutorial or are you using Network Manager for wireless networking? What version of Ubuntu are you on?

Greetings!

I am using my network manager GUI from KDE and I am using Feisty!

Thanks!

[wieman01]

Greetings!

I am using my network manager GUI from KDE and I am using Feisty!

Thanks!
Gutsy will let you connect at startup. So upgrading will certainly help as Gutsy has a new version of NM,

[rootware]

Gutsy will let you connect at startup. So upgrading will certainly help as Gutsy has a new version of NM,

I can't upgrade to Gutsy because it's a failure on my HP Pavilion laptop :(

[wieman01]

I can't upgrade to Gutsy because it's a failure on my HP Pavilion laptop :(
Alternatively, install NM from scratch by compiling it yourself. Sorry, I cannot give you any further advice.

[Axtilmor]

Hello,

On Gutsy, I'm trying to connect a Netgear MA311 PCI card to a Linksys WRT54G wireless router using WPA(1), TKIP, and DHCP.

At first, I tried using Network Manager. My network's name showed up on the list of wireless networks, but when I tried to connect to it, the only security types that I was allowed to select were WEP and LEAP. I tried selecting "Connect to Other Network" and was able to enter the proper information, but the network manager showed the connection as having no bars, and I wasn't able to access the network.

After some Googling I found this excellent tutorial, but I'm still having some difficulties. Here's the information requested by the tutorial:

route:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
link-local * 255.255.0.0 U 0 0 0 wlan1
default * 0.0.0.0 U 1000 0 0 wlan1

iwconfig:
wifi0 IEEE 802.11b ESSID:"test" Nickname:""
Mode:Managed Frequency:2.437 GHz Access Point: None
Bit Rate:2 Mb/s Sensitivity=1/3
Retry short limit:8 RTS thr:off Fragment thr:off
Power Management:off

wlan1 IEEE 802.11b ESSID:"test" Nickname:""
Mode:Managed Frequency:2.437 GHz Access Point: None
Bit Rate:2 Mb/s Sensitivity=1/3
Retry short limit:8 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=0/70 Signal level=-73 dBm Noise level=-73 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:16 Missed beacon:0

sudo iwlist scan:
wifi0 Scan completed :
Cell 01 - Address: 00:13:10:F0:34:F1
ESSID:"OMFGSTFU"
Mode:Master
Frequency:2.417 GHz (Channel 2)
Signal level=-79 dBm Noise level=-90 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
Extra:bcn_int=100
Extra:resp_rate=10

wlan1 No scan results

sudo lshw -C network:
*-network:0
description: Wireless interface
product: Prism 2.5 Wavelan chipset
vendor: Intersil Corporation
physical id: b
bus info: pci@0000:00:0b.0
logical name: wifi0
version: 01
serial: 00:09:5b:11:9d:af
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list logical wireless ethernet physical
configuration: broadcast=yes driver=hostap driverversion=0.4.4-kernel firmware=1.3.6 latency=32 module=hostap_pci multicast=yes wireless=IEEE 802.11b
*-network:1 DISABLED
description: Ethernet interface
product: RTL-8139/8139C/8139C+
vendor: Realtek Semiconductor Co., Ltd.
physical id: d
bus info: pci@0000:00:0d.0
logical name: eth0
version: 10
serial: 00:e0:4c:d8:58:4e
size: 10MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=8139too driverversion=0.9.28 duplex=half latency=32 link=no maxlatency=64 mingnt=32 module=8139too multicast=yes port=MII speed=10MB/s


Here's my interfaces file (which still bears a few scars from me trying to figure this out):
auto lo
iface lo inet loopback

#auto eth1
#iface eth1 inet dhcp

#auto eth2
#iface eth2 inet dhcp

#auto ath0
#iface ath0 inet dhcp

#auto wlan0
#iface wlan0 inet dhcp

auto wlan1
iface wlan1 inet dhcp
wpa-driver hostap
wpa-ssid OMFGSTFU
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <MY HEX SHARED KEY>

And here's what I get when I try to do a /etc/init.d/networking restart:
econfiguring network interfaces...
There is already a pid file /var/run/dhclient.wlan1.pid with pid 5833
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/wlan1/00:09:5b:11:9d:af
Sending on LPF/wlan1/00:09:5b:11:9d:af
Sending on Socket/fallback
ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported
There is already a pid file /var/run/dhclient.wlan1.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/wlan1/00:09:5b:11:9d:af
Sending on LPF/wlan1/00:09:5b:11:9d:af
Sending on Socket/fallback
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
[ OK ]
axtilmor@axtilmor-desktop:~$ sudo /etc/init.d/networking restart >> network_rest
art.txt
There is already a pid file /var/run/dhclient.wlan1.pid with pid 6103
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/wlan1/00:09:5b:11:9d:af
Sending on LPF/wlan1/00:09:5b:11:9d:af
Sending on Socket/fallback
ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported
There is already a pid file /var/run/dhclient.wlan1.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/wlan1/00:09:5b:11:9d:af
Sending on LPF/wlan1/00:09:5b:11:9d:af
Sending on Socket/fallback
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

I'm running out of ideas on what I should be searching the net for to solve my problem, so any help would be appreciated.

[wieman01]

@Axtilmor:

This is a tough one... But let's start with a few observations that I have made.

A. Your network interface seems to be "wifi0" rather than "wlan1".
B. The scan results list your network ("OMFGSTFU"), however, there is no mention of WPA. This could be either because you are using WEP or because the current driver (Prism) does not support WPA (that's what I suspect).
C. This error message kind of confirms that there is no WPA support:
ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported
D. The script looks ok apart from the fact that the network interface is incorrect. Also I do not know if you have generated the passphrase correctly (wpa-psk). Please check the relevant section in my tutorial once again. The right scipt would be:
auto wifi0
iface wifi0 inet dhcp
wpa-driver hostap
wpa-ssid OMFGSTFU
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <MY HEX SHARED KEY>
If all this fails, you can replace the current Prism driver with "ndiswrapper" and the native Windows driver. But let's try this first.

[Axtilmor]

I tried changing the interfaces file to list wifi0 as you mentioned, but got the same sort of output upon running /etc/init.d/networking restart. Given that this card is very old, I feel like you're right about it being the driver. I'll try changing the driver tomorrow when its not so late.

[wieman01]

I tried changing the interfaces file to list wifi0 as you mentioned, but got the same sort of output upon running /etc/init.d/networking restart. Given that this card is very old, I feel like you're right about it being the driver. I'll try changing the driver tomorrow when its not so late.
It is a wireless B card, isn't it? So it must be fairly old and I doubt that the Windows driver supports WPA... But you should know as you have used it before I guess.

It is definitely on the list of supported devices ("ndiswrapper"):

http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list_m-n/

Try to get hold of an up-to-date Windows driver that specifically supports WPA/WPA2. I can guide you through the installation process if you like to.

[lunatico]

Hello,
This is my first post to this forum, I have read it all and tried several things but I'm still having problems.
I have a IBM Thinkpad T61 with an Atheros wifi card, Ubuntu loaded the madwifi drivers and I installed the wpa-supplicant. The wireless work very well on my home wireless which I have open, with no encryption just MAC address filtering.
I am on my college network. I have attached the instructions they provide for Windows XP and Vista and Mac OS to configure the laptop to work with this network, and I have also attached a screenshot of the settings I have used on my nm-applet which have worked but is very hard to get the connection and once you get connected it will be very unstable.
Please help. :)

[wieman01]

Hello,
This is my first post to this forum, I have read it all and tried several things but I'm still having problems.
I have a IBM Thinkpad T61 with an Atheros wifi card, Ubuntu loaded the madwifi drivers and I installed the wpa-supplicant. The wireless work very well on my home wireless which I have open, with no encryption just MAC address filtering.
I am on my college network. I have attached the instructions they provide for Windows XP and Vista and Mac OS to configure the laptop to work with this network, and I have also attached a screenshot of the settings I have used on my nm-applet which have worked but is very hard to get the connection and once you get connected it will be very unstable.
Please help. :)
This could be due to a number of reasons, but it is impossible for me to find out what the real issue is. Plus it's not really related to the topic of this thread. Please open up a new thread and feel free to send me the link by PM.

[lunatico]

Sorry for my past irrelevant message. Now this one I think does have a lot to do with this thread. Basically I'm trying to setup the interfaces file to work with DHCP, WPA-Enterprise, TKIP, PEAP, EAP-MSCHAPv2, with fast reconnect. If I run iwconfig it looks like it is getting associated with the AP but not authenticated. I have attached on the file all the output you request at the beginning of this howto.
I think I have something wrong on the way I write the interfaces file, the order of things or something like that. If it has relevance I would appreciate all help provided.

[wieman01]

Sorry for my past irrelevant message. Now this one I think does have a lot to do with this thread. Basically I'm trying to setup the interfaces file to work with DHCP, WPA-Enterprise, TKIP, PEAP, EAP-MSCHAPv2, with fast reconnect. If I run iwconfig it looks like it is getting associated with the AP but not authenticated. I have attached on the file all the output you request at the beginning of this howto.
I think I have something wrong on the way I write the interfaces file, the order of things or something like that. If it has relevance I would appreciate all help provided.
No problem. The scripts looks fine. Could you post this as well please:
sudo ifdown -v ath0
sudo ifup -v ath0
I am not entirely sure your card really supports PEAP, but let's see.

EDIT:
Please change the script so that is looks like this (SSID broadcast):
auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-ssid COMPSCIwireless
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-EAP
wpa-eap PEAP
wpa-phase2 auth=MSCHAPV2
wpa-identity castromd
wpa-password xoo6Quud

[lunatico]

Thank you very much for your help! Find attached the output after I changed what you said plus the two other commands you ask.
Let me mention that I have been able to connect using the nm-applet, on my first post on this thread you can find a screenshot of the configuration used. As I said, I have been able (2 or 3 times) to connect, but is very rare and the connection will not stay up for long.
I do think my card works fine with PEAP because I use it on Windows XP and Vista with no problem (I have dual boot).

[maycitybomber]

My Wifi ESSID is labelled as MY_WIFI
I have input the HEX Passphrase; encryption being WPA1+WPA2 Mixed Mode
followed instructions.. is still not working any help??

route
Brings up:

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

iwconfig
Brings up:
lo no wireless extensions.

eth0 no wireless extensions.

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

sit0 no wireless extensions.

sudo iwlist scan
Brings up:

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

ath0 Scan completed :
Cell 01 - Address: 00:01:38:99:2B:F2
ESSID:"wireless"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=2/94 Signal level=-93 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 22 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=200
Cell 02 - Address: 00:18:39:A2:D0:AC
ESSID:"MY_WIFI"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=47/94 Signal level=-48 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 22 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:rsn_ie=30140100000fac020100000fac040100000fa c020000
Cell 03 - Address: 00:04:ED:0A:43:02
ESSID:"benbenLAN"
Mode:Master
Frequency:2.417 GHz (Channel 2)
Quality=11/94 Signal level=-84 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:wpa_ie=dd160050f20101000050f20201000050f2020 1000050f202
Cell 04 - Address: 00:0F:B5:15:FD:A8
ESSID:"smudgemouth"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=4/94 Signal level=-91 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 22 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:wpa_ie=dd160050f20101000050f20201000050f2020 1000050f202
Cell 05 - Address: 00:0C:E3:61:0B:A1
ESSID:"Virgin Broadband"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=6/94 Signal level=-89 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f2020 1000050f2020000

sit0 Interface doesn't support scanning.

sudo lshw -C network
Brings up:

*-network:0
description: Ethernet interface
product: SiS900 PCI Fast Ethernet
vendor: Silicon Integrated Systems [SiS]
physical id: 4
bus info: pci@00:04.0
logical name: eth0
version: 91
serial: 00:c0:9f:9a:2c:38
size: 10MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegociation
configuration: autonegociation=on broadcast=yes driver=sis900 driverversion=v1.08.09 Sep. 19 2005 duplex=half link=no multicast=yes port=MII speed=10MB/s resources: ioport:2000-20ff iomemory:e2003000-e2003fff irq:177
*-network:1
description: Wireless interface
product: Atheros Communications, Inc.
vendor: Atheros Communications, Inc.
physical id: b
bus info: pci@00:0b.0
logical name: ath0
version: 01
serial: 00:0e:9b:b2:38:c0
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ath_pci driverversion=0.9.6.0 (EXPERIMENTAL) multicast=yes wireless=IEEE 802.11
resources: iomemory:e2010000-e201ffff irq:225


cat /etc/network/interfaces
Brings up:
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto ath0
iface ath0 inet dhcp

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-ssid "MY_WIFI"
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk MY_HEX_PASSKEY [IMPORTANT: See "WPA-PSK key generation"]

This is from a fresh install so the drivers would be supported(?)

using madwifi on an Atheros Card - Ubuntu grabbed it up straight from the install, which im glad cause installing these has been a bit hairy in the past on gentoo and other distros (possible user error?)

it can see the SSID from my card i have it on broadcast however the card doesnt like to associate with the router..

i had some trouble getting essid to stick as well but i finally got it in there... i have the correct hex passphrase in there but i can't see whether or not its accepted by the router when i try to connect

dhcp times out everytime and static IP within the subnet assigned just doesnt want to work either.. it binds but somehow doesn't see the network..

even tried to 'hard' route with bind and route to the gw but again doesnt see the network, pings always fail, and my router doesnt pick up the mac address of my wifi NIC when i check it.

Im guessing its possibly a driver to card interface issue or possibly im missing something in the way of wpa_supplicant setup

but then thats a bit of speculatation...

please help or my gf is going to kill me for sitting in the damn PC room so i can nets my *nix :(

[wieman01]

Thank you very much for your help! Find attached the output after I changed what you said plus the two other commands you ask.
Let me mention that I have been able to connect using the nm-applet, on my first post on this thread you can find a screenshot of the configuration used. As I said, I have been able (2 or 3 times) to connect, but is very rare and the connection will not stay up for long.
I do think my card works fine with PEAP because I use it on Windows XP and Vista with no problem (I have dual boot).
This is really strange. Just for the fun of it, could you try this please:
auto ath0
iface ath0 inet dhcp
wpa-driver wext
wpa-ssid COMPSCIwireless
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-EAP
wpa-eap PEAP
wpa-phase2 auth=MSCHAPV2
wpa-identity castromd
wpa-password xoo6Quud
The post:
sudo ifdown -v ath0
sudo ifup -v ath0
Have you tried Network Manager as well?

[wieman01]

My Wifi ESSID is labelled as MY_WIFI
I have input the HEX Passphrase; encryption being WPA1+WPA2 Mixed Mode
followed instructions.. is still not working any help??
Ok, let's look at the scan results first:
Cell 02 - Address: 00:18:39:A2:D0:AC
ESSID:"MY_WIFI"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=47/94 Signal level=-48 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 22 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:rsn_ie=30140100000fac020100000fac040100000fa c020000
It says that encryption is turned on but does not list the network as a WPA secured one. That is bad news and generally indicates that WPA is not supported by the driver.

In addition see this:
configuration: broadcast=yes driver=ath_pci driverversion=0.9.6.0 (EXPERIMENTAL) multicast=yes wireless=IEEE 802.11
The system seems to be using an experimental version of the driver. Whether it ought to support WPA or not, I don't know, but there is a pretty good chance that it doesn't.

You might have to replace the driver and make use of "ndiswrapper" instead...

[maycitybomber]

Yeah it seems that would be the case, this is the one that came with ubuntu??

ndiswrapper i'll give it a go

[wieman01]

Yeah it seems that would be the case, this is the one that came with ubuntu??

ndiswrapper i'll give it a go
Pretty much. It's the one that has been loaded by the default install.

If you need a hand setting up your card, let me know. Use my Ralink ("ndiswrapper") tutorial as reference if you like to. It should work for you as well.

[maycitybomber]

Well I have a question, will this work considering my card is atheros chipset??

[wieman01]

Well I have a question, will this work considering my card is atheros chipset??
Do you find your card listed anywhere here?

http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list/

[lunatico]

I tried with wext instead of madwifi but it was no fun, didn't work... When you say "Network Manager" you are referring to the nm-applet right? I have tried that, as posted before and as shown on the image posted on my first input here.
The COMPSCIwireless network has to ways to authenticate, with WPA which we are trying to figure out and also with LEAP which have worked for me a couple of times using the nm-applet. So with the nm-applet I have tried in both ways but no luck.

[maycitybomber]

hmm have been trying to install the latest mad wifi driver... and ndiswrapper... issue being now on this fresh install make wont find my kernel :(

Makefile.inc:81: *** Cannot detect kernel version - please check compiler and KERNELPATH. Stop.


arrrgh

this is getting crazy im going backwardser and backwardser!

[wieman01]

hmm have been trying to install the latest mad wifi driver... and ndiswrapper... issue being now on this fresh install make wont find my kernel :(

Makefile.inc:81: *** Cannot detect kernel version - please check compiler and KERNELPATH. Stop.


arrrgh

this is getting crazy im going backwardser and backwardser!
"ndiswrapper" is in the repositories. You don't have to compile it yourself. See my Ralink tutorial (signature) for more.

[wieman01]

I tried with wext instead of madwifi but it was no fun, didn't work... When you say "Network Manager" you are referring to the nm-applet right? I have tried that, as posted before and as shown on the image posted on my first input here.
The COMPSCIwireless network has to ways to authenticate, with WPA which we are trying to figure out and also with LEAP which have worked for me a couple of times using the nm-applet. So with the nm-applet I have tried in both ways but no luck.
Last thing we can try is to remove NM (Network Manager) entirely using Synaptic. Then execute the script once again.

[lunatico]

Removed NetworkManager... nothing.... this is sad....

[lunatico]

- Should the password be plain text or should it be converted with wpa_passphrase?
- Does the order of commands matter?
- Will "extra" commands affect?

Thanks!

[wieman01]

Removed NetworkManager... nothing.... this is sad....
Could it be that your card does not support PEAP after all? This error message is suspicious:
wifi0: unknown hardware address type 801

[wieman01]

- Should the password be plain text or should it be converted with wpa_passphrase?
- Does the order of commands matter?
- Will "extra" commands affect?

Thanks!
You will need to generate a passphrase in this case.

The order has no impact.

What "extra" commands are you referring to?

[maycitybomber]

hmm i have a feeling i missed installing a compiler.. looking pretty stupid atm lol

[wieman01]

hmm i have a feeling i missed installing a compiler.. looking pretty stupid atm lol
'ndiswrapper' is in the respositories, so in fact you don't need a compiler at all. You can compile the package yourself in case you need a more recent version, however, the one in respository works for the majority of people.

[maycitybomber]

was attempting to get the madwifi driver up..

i have ndiswrapper just wanted to get madwifi installed to a more stable version in regards to wpa

[wieman01]

was attempting to get the madwifi driver up..

i have ndiswrapper just wanted to get madwifi installed to a more stable version in regards to wpa
Ok, got it. Let me know how you go later on.

[maycitybomber]

hmm ive loaded ndiswrapper and the correct driver (XP one which i find curious :D)

going to test the wpa settings now

[wieman01]

hmm ive loaded ndiswrapper and the correct driver (XP one which i find curious :D)

going to test the wpa settings now
Also check against my Ralink tutorial so as to make sure that you don't miss anything.

[Sementis]

See http://ubuntuforums.org/showthread.php?t=664586 for my problem

~sorry for double posting~

[Cammy]

Ok. I've been through everything and I'm still stumped. I could get the laptop connected using WPA if I used NetworkManager and typed my ssid/pass/etc in manually, every time, but I couldn't get it to do it after a reboot.

So I followed this thread, uninstalled NetworkManager, and edited /etc/network/interfaces so it looks like this:

auto lo
iface lo inet loopback

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-ssid myssid
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk myloooonghexpasskey

and when I do /etc/init.d/networking restart, I get (at the very end, after a few DHCPDISCOVERs:

No DHCPOFFERS received
No working leases in persistent database - sleeping

What could I possibly be doing wrong?

P.S. It's a Dell Inspiron 1100 and the wifi card is an Airlink 101 with an Atheros chip.

[wieman01]

Ok. I've been through everything and I'm still stumped. I could get the laptop connected using WPA if I used NetworkManager and typed my ssid/pass/etc in manually, every time, but I couldn't get it to do it after a reboot.

So I followed this thread, uninstalled NetworkManager, and edited /etc/network/interfaces so it looks like this:

auto lo
iface lo inet loopback

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-ssid myssid
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk myloooonghexpasskey

and when I do /etc/init.d/networking restart, I get (at the very end, after a few DHCPDISCOVERs:

No DHCPOFFERS received
No working leases in persistent database - sleeping

What could I possibly be doing wrong?

P.S. It's a Dell Inspiron 1100 and the wifi card is an Airlink 101 with an Atheros chip.
Did you generate the pass phrase as indicated in the tutorial?

Please post:
sudo iwlist scan
sudo ifdown -v ath0
sudo ifup -v ath0

[Axtilmor]

It is a wireless B card, isn't it? So it must be fairly old and I doubt that the Windows driver supports WPA... But you should know as you have used it before I guess.

It is definitely on the list of supported devices ("ndiswrapper"):

http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list_m-n/

Try to get hold of an up-to-date Windows driver that specifically supports WPA/WPA2. I can guide you through the installation process if you like to.


Sorry to get back to this so late.

I tried the card out on my Windows installation, and I didn't have any luck connecting there, either. However, I need to run cable into that room, anyway, so I'll just move the router.

Thanks for all of your help!

[Cammy]

Did you generate the pass phrase as indicated in the tutorial?:
Yep!

sudo iwlist scan:

ath0 Scan completed :
Cell 01 - Address: 00:15:E9:5F:02:CA
ESSID:""
Mode:Master
Frequency:2.412 GHz (Channel 1)
Quality=43/70 Signal level=-52 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK



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/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 5381
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:18:02:5b:19:bb
Sending on LPF/ath0/00:18:02:5b:19:bb
Sending on Socket/fallback
DHCPRELEASE on ath0 to 192.168.0.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/madwifi
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 3966).

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/madwifi
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 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "FoxBunny" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP -- OK
wpa_supplicant: wpa-group TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -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:18:02:5b:19:bb
Sending on LPF/ath0/00:18:02:5b:19:bb
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 1
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

[wieman01]

Yep!
Mmm... Same trouble as this user used to have: maycitybomber.

Perhaps it's good to contact him by PM and ask him for advice. Apparently he was able to solve his problems with his Atheros based card. Worth a shot.

I think he had to replace his driver somehow...

EDIT:
If there is no response, please let me know. I can ask him for you.

[Cammy]

FIXED! I somehow got wpa_supplicant to work after poaching some info from this thread (http://ubuntuforums.org/showthread.php?t=263136).

I'm all working 100% now :D

[wieman01]

FIXED! I somehow got wpa_supplicant to work after poaching some info from this thread (http://ubuntuforums.org/showthread.php?t=263136).

I'm all working 100% now :D
What information did you change? Would be nice if you shared your stuff with us, so that other have a reference. :-)

[Cammy]

Ok, I'll give it a shot.

The below is for my Atheros card on ath0, and using a madwifi driver. It can probably be changed to suit needs.

First off, I think you need to have wpa_supplicant installed. I think I installed this and it did not come with gutsy.

sudo apt-get install wpasupplicant

Then, I did this:

wpa_passphrase myssid my_passphrase

which resulted in this appearing in the terminal:

network={
ssid="myssid"
#psk="my_passphrase"
psk=my_looong_hex_passhrase_thing
}

Copy this somewhere, as you'll need it in the next step.

Then:

sudo gedit /etc/wpa_supplicant/wpa_supplicant.conf

And pasted in the code above. Then I added the following lines in blue::


ctrl_interface=/var/run/wpa_supplicant

network={
ssid="myssid"
scan_ssid=1
proto=WPA RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
#psk="my_passphrase"
psk=my_looong_hex_passhrase_thing
}

Save and close it.

Then I did:

sudo gedit /etc/network/interfaces

And added this:

auto ath0
iface ath0 inet dhcp

pre-up wpa_supplicant -Bw -Dmadwifi -iath0 -c/etc/wpa_supplicant/wpa_supplicant.conf
post-down killall -q wpa_supplicant

Save and close.

Then rebooted and was online.

[lime4x4]

can't get a linksys wmp300n wireless card to connect to my router using wpa
if i disable the secrutiy of the router i can connect just fine. i removed network managers and configured my interface like this

auto lo
iface lo inet loopback



auto wlan0
iface wlan0 inet static
address 192.168.1.105
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid transformers
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk my passkey

if i run iwlist scan i get this

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

wlan0 Scan completed :
Cell 01 - Address: 00:1C:10:C7:52:26
ESSID:"transformers"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.422 GHz (Channel 3)
Quality:90/100 Signal level:-38 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

So it sees my router but won't connect when i try to run encryption.
If it matters the router is a linksys wrt300N

[wieman01]

can't get a linksys wmp300n wireless card to connect to my router using wpa
if i disable the secrutiy of the router i can connect just fine. i removed network managers and configured my interface like this

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
address 192.168.1.105
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid transformers
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk my passkey

What chipset is your adapter?

Please also post:
sudo lshw -C network
sudo ifdown -v <your_interface>
sudo ifup -v <your_interface>

[dynamethod]

Can someone please confirm this will work with a fresh install of Kubuntu 7.10? because ive found Kubuntu absolutely shocking with wireless (using ralink rt73 usb adapter)

EDIT: Does work, i forgot to install the ralink drivers.

[wieman01]

Can someone please confirm this will work with a fresh install of Kubuntu 7.10? because ive found Kubuntu absolutely shocking with wireless (using ralink rt73 usb adapter)

EDIT: Does work, i forgot to install the ralink drivers.
What drivers did you install eventually?

[lime4x4]

*-network
description: Wireless interface
product: BCM43XG
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:01:00.0
logical name: wlan0
version: 01
serial: 00:1d:7e:9d:1e:3a
width: 32 bits
clock: 33MHz
capabilities: bus_master ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.45+Linksys, A Division of Cisc ip=192.168.1.105 latency=64 link=yes module=ndiswrapper multicast=yes wireless=IEEE 802.11g

[mariner8905]

Ive followed everything that was said in this thread to get my WPA wireless running but to no avail. im running a Ibook G3 PPC with an Airport that i know could use WPA before i loaded up Ubuntu 6.06. my current setup is as follows in interfaces
auto eth1
iface eht10 inet dhcp
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key>

I have everything that should be filled in filled in as per the instructions. I just noticed a few errors when i run a network restart so im posting that as well, hoping it might help.
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/eth1/00:30:65:0a:cf:e8
Sending on LPF/eth1/00:30:65:0a:cf:e8
Sending on Socket/fallback
DHCPRELEASE on eth1 to 192.168.1.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Invalid argument
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/eth1/00:30:65:0a:cf:e8
Sending on LPF/eth1/00:30:65:0a:cf:e8
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
No DHCPOFFERS received.
Trying recorded lease 192.168.1.7
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

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

No working leases in persistent database - sleeping.
[ ok ]

if anyone can help id greatly appreciate it. and as much detail on what to do would be good, im very new to linux and its workings.

[wieman01]

@mariner8905:

Does not look too promising at the moment:
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Invalid argument
You driver does not appear to support the 'wext' interface.

Please issue these commands and post the results:
sudo iwlist scan
sudo lshw -C network
What chipset does your wireless adapter have?

[mariner8905]

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:17:0F:8C:AC:E0
ESSID:"UWLAN"
Mode:Master
Frequency=2.462 GHz (Channel 11)
Signal level:-67 dBm Noise level:-99 dBm
Encryption key:on
Cell 02 - Address: 00:0F:34:C0:44:70
ESSID:"UWLAN"
Mode:Master
Frequency=2.437 GHz (Channel 6)
Signal level:-70 dBm Noise level:-96 dBm
Encryption key:on
Cell 03 - Address: 00:11:20:4B:F0:90
ESSID:"UWLAN"
Mode:Master
Frequency=2.462 GHz (Channel 11)
Signal level:-79 dBm Noise level:-99 dBm
Encryption key:on
Cell 04 - Address: 00:16:46:71:7C:10
ESSID:"UWLAN"
Mode:Master
Frequency=2.462 GHz (Channel 11)
Signal level:-80 dBm Noise level:-99 dBm
Encryption key:on

sit0 Interface doesn't support scanning.

*-network
description: Ethernet interface
product: UniNorth/Pangea GMAC (Sun GEM)
vendor: Apple Computer Inc.
physical id: f
bus info: pci@20:0f.0
logical name: eth0
version: 00
serial: 00:0a:95:77:67:2e
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 66MHz
capabilities: bus_master ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegociation
configuration: autonegociation=on broadcast=yes driver=sungem driverversion=0.98 duplex=full ip=138.49.32.116 link=yes multicast=yes port=MII speed=100MB/s
resources: iomemory:f5200000-f53fffff irq:41
*-network
description: Wireless interface
physical id: 1
logical name: eth1
serial: 00:30:65:0a:cf:e8
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=orinoco driverversion=0.15rc3 firmware=Lucent/Agere 8.70 link=no multicast=yes wireless=IEEE 802.11b

i think that is all you requested, if you need more, let me know.

[wieman01]

@mariner8905:

Tough luck... This driver (Orinoco) does not support WPA as far as I can tell. Now we have 2 options... You either revert to WEP or you install 'ndiswrapper' to get it working. 'ndiswrapper' might not be an option since this is a MacBook and no Windows machine.

There is another user who might give some useful advice: Kevdog. Perhaps you can contact him as well. He maintains a very useful thread which you find here:

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

Let me know if there is anything else I can do...

[mariner8905]

well id like to exhaust any options you might have first before moving onto someone else and having to reexplain everything again. how would i install the ndiswrapper driver? and were do i find it?

[wieman01]

well id like to exhaust any options you might have first before moving onto someone else and having to reexplain everything again. how would i install the ndiswrapper driver? and were do i find it?
Alright then. You find instructions in my own Ralink tutorial. It is basically for Ralink based chip-sets, however, it should also work for other drivers. It explains how to install "ndiswrapper" and how to deploy the Windows drivers.

Are there Windows drivers out there for your wireless adapter?

[lime4x4]

Quote:
Originally Posted by lime4x4 View Post
can't get a linksys wmp300n wireless card to connect to my router using wpa
if i disable the secrutiy of the router i can connect just fine. i removed network managers and configured my interface like this

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
address 192.168.1.105
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid transformers
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk my passkey
What chipset is your adapter?

Please also post:
Quote:
sudo lshw -C network
sudo ifdown -v <your_interface>
sudo ifup -v <your_interface>

here is the info you requested. This was done with my router unsecured

pammy@pammy-desktop:~$ sudo lshw -C network
*-network
description: Wireless interface
product: BCM43XG
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:01:00.0
logical name: wlan0
version: 01
serial: 00:1d:7e:9d:1e:3a
width: 32 bits
clock: 33MHz
capabilities: bus_master ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.45+Linksys, A Division of Cisc ip=192.168.1.105 latency=64 link=yes module=ndiswrapper multicast=yes wireless=IEEE 802.11g
pammy@pammy-desktop:~$ 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/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
route del default gw 192.168.1.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
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 9344).
pammy@pammy-desktop:~$ 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: using default driver type: 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

ifconfig wlan0 192.168.1.105 netmask 255.255.255.0 up
route add default gw 192.168.1.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
pammy@pammy-desktop:~$

[wieman01]

@lim4x4:

Please post the full output of...
sudo ifup -v wlan0
... once again. Some bits are missing. And also provide:
sudo iwlist scan
Thanks, mate.

[lime4x4]

my router is called transformers

pammy@pammy-desktop:~$ 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: using default driver type: 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

ifconfig wlan0 192.168.1.105 netmask 255.255.255.0 up
route add default gw 192.168.1.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
pammy@pammy-desktop:~$ sudo iwlist scan
lo Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1C:10:C7:52:26
ESSID:"transformers"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.422 GHz (Channel 3)
Quality:76/100 Signal level:-47 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:13:10:99:EA:F2
ESSID:"linksys"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:17/100 Signal level:-85 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 03 - Address: 00:14:D1:3D:71:9F
ESSID:"TRENDnet"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:9/100 Signal level:-90 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 04 - Address: 00:13:10:79:34:CA
ESSID:"coyote"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:15/100 Signal level:-86 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0

pammy@pammy-desktop:~$

[wieman01]

my router is called transformers

pammy@pammy-desktop:~$ 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: using default driver type: 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

This is really strange, there is some stuff missing (number of extra rows saying OK).

What does a scan yield once you have turned on(!) WPA?
sudo iwlist scan

[chriswil]

Weiman01,

This is still very relevant.
The standard Network tool from the GUI does not seem to add the psk line to the networks file. (7.10)

I have just got my Netgear WPN111 adapter working. After fiddling around for hours looking at other posts I manually edited the networks as per your original posting and it all sprang to life!!


auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid xxxxxxxxxxxxx
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx x

Many Thanks

[antisho]

I'm having some trouble with this. The network is WPA, AES, PEAP, MSCHAPV2. I have a Broadcom card and use ndiswrapper. Currently I have this in /etc/network/interfaces:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp
wpa-driver ndiswrapper
wpa-ssid (ssid)
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-eap PEAP
wpa-key-mgmt WPA-EAP
wpa-identity (username)
wpa-password (password)

I've rebooted twice and restarted /etc/init.d/networking several times, but it hasn't worked.

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

ifdown:
Configuring interface eth0=eth0 (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/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-down.d/openvpn
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp3/dhclient.eth0.leases eth0
There is already a pid file /var/run/dhclient.eth0.pid with pid 6412
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/eth0/00:12:3f:d0:a9:7b
Sending on LPF/eth0/00:12:3f:d0:a9:7b
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.1.1 port 67
ifconfig eth0 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:
Configuring interface eth0=eth0 (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[SIOCSIWMODE]: Operation not supported
ioctl[SIOCGIWRANGE]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Operation not supported

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

Listening on LPF/eth0/00:12:3f:d0:a9:7b
Sending on LPF/eth0/00:12:3f:d0:a9:7b
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
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/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntp
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/openvpn
run-parts: executing /etc/network/if-up.d/wpasupplicant

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

iwlist:
eth1 Scan completed :
Cell 01 - Address: 00:1A:A2:FC:71:80
ESSID:""
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:64/100 Signal level:-55 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : 802.1x
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : 802.1x
Cell 02 - Address: 02:13:02:17:E2:0B
ESSID:"DCDS Wireless"
Protocol:IEEE 802.11g
Mode:Ad-Hoc
Frequency:2.462 GHz (Channel 11)
Quality:59/100 Signal level:-58 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 03 - Address: 00:1A:A2:FC:45:A0
ESSID:""
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:23/100 Signal level:-81 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : 802.1x
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : 802.1x
Cell 04 - Address: FA:EA:DE:16:F9:DC
ESSID:"EPSON"
Protocol:IEEE 802.11g
Mode:Ad-Hoc
Frequency:2.412 GHz (Channel 1)
Quality:87/100 Signal level:-40 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0

lshw:
*-network
description: Ethernet interface
product: NetXtreme BCM5751 Gigabit Ethernet PCI Express
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 01
serial: 00:12:3f:d0:a9:7b
capacity: 1GB/s
width: 64 bits
clock: 33MHz
capabilities: pm vpd msi pciexpress bus_master cap_list ethernet physical mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=3.77 firmware=5751-v3.29a latency=0 link=no module=tg3 multicast=yes port=twisted pair
*-network
description: Wireless interface
product: BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller
vendor: Broadcom Corporation
physical id: 3
bus info: pci@0000:03:03.0
logical name: eth1
version: 02
serial: 00:90:4b:fb:e4:d7
width: 32 bits
clock: 33MHz
capabilities: bus_master ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.49+Broadcom,10/12/2006, 4.100. latency=64 link=no module=ndiswrapper multicast=yes wireless=IEEE 802.11g

route:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
link-local * 255.255.0.0 U 0 0 0 eth0
default * 0.0.0.0 U 1000 0 0 eth0

[wieman01]

@Antisho:

This would be the right configuration. Please try again and post your results:
auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid (ssid)
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-eap PEAP
wpa-key-mgmt WPA-EAP
wpa-identity (username)
wpa-password (password)
SSID broadcast turned off, right?

[antisho]

Right, I just noticed it should be eth1. It didn't work. Will try again with wext.

SSID broadcast: how do I check that?

[wieman01]

Right, I just noticed it should be eth1. It didn't work. Will try again with wext.

SSID broadcast: how do I check that?
When scanning for the wireless network, do you recognize its name or is it hidden/blank?

[antisho]

When scanning for the wireless network, do you recognize its name or is it hidden/blank?It does not appear in, say, nm-applet when in roaming mode. So I assume so.

[antisho]

@Antisho:

This would be the right configuration. Please try again and post your results:

SSID broadcast turned off, right?This works. Thanks!

[rootware]

Greetings, I have figured out how to configure my wlan card, but the problem is sometimes when I boot into the sistem the internet it's not working, even if I put that network-restart script on my startup.

What can I do?:(

[wieman01]

Greetings, I have figured out how to configure my wlan card, but the problem is sometimes when I boot into the sistem the internet it's not working, even if I put that network-restart script on my startup.

What can I do?:(
Hello,

I don't think this has much to do with this thread. But how about that: You open up a new thread, outline your problem there and also mention the hardware you have got, etc. and you can send me the link to your post by PM?

EDIT:

Oops, I am really sorry... I mistakenly edited your post and pressed "save". I did it unintentionally, I am not yet really familiar with my new role as admin, so I hit the wrong button. My apologies.

[mssever]

Just a quick note to point out that NetworkManager can handle WPA2 without manually messing with wpa-supplicant or any other such nonsense. My network uses WPA2 with AES encryption. I use the bcm43xx driver. I simply ask NetworkManager to connect to the network, enter my key, and I'm in. No manual configuration necessary.

[wieman01]

Just a quick note to point out that NetworkManager can handle WPA2 without manually messing with wpa-supplicant or any other such nonsense. My network uses WPA2 with AES encryption. I use the bcm43xx driver. I simply ask NetworkManager to connect to the network, enter my key, and I'm in. No manual configuration necessary.
I know that it can. But it cannot handle static IP addresses. That's the point of this nonsense.

[lime4x4]

well i ended up installing wicd and now my wireless connection is working fine using wep. i also tried wpa/wpa2 and they work as well. Don't know why this method wouldn't work for me

[mssever]

I know that it can. But it cannot handle static IP addresses. That's the point of this nonsense.

My apologies. I missed the static IP part.

[Paris Heng]

Dear sir,

I saw your post about WPA configuration. I have few question on this, can you help me? I using Atheros + Madwifi for the wifi NIC.

Questions:
(1) hostapd
I recently configure a WPA in a own build Linux access point (AP. But the configuration i not configured in /etc/network/interfaces. I using another program name hostapd to perform the WPA. I configured all the WPA configuration in hostapd config file. My problems not is, I run the hostapd daemon, but the client can connect to the AP without being authenticate by WPA. Did you know about hostapd + Madwifi, please assist me.

Starting the daemon:
/etc/init.d/hostapd start

hostapd.conf:
######################### hostapd configuration file ##########################

#Experiemnt for WPA-PSK



############################# Initial #########################################

interface=ath0

driver=madwifi

logger_syslog=-1

logger_syslog_level=2

logger_stdout=-1

logger_stdout_level=2

debug=4

dump_file=/tmp/hostapd.dump

ctrl_interface=/var/run/hostapd

ctrl_interface_group=0



###################### IEEE 802.11 related config #############################

ssid=heng_AP2

macaddr_acl=0



###### You need create 2 file, /etc/hostapd.accept and /etc/hostapd.deny #####

# Station MAC address -based authentication #

# 0 = accept unless in deny list #

# 1 = deny unless in accept list #

# 2 = use external RADIUS server (accept/deny lists are searched first) #

################################################## ############################

accept_mac_file=/etc/hostapd.allow

#deny_mac_file=/etc/hostapd.deny



################################################## ############################

# IEEE 802.11 specifies two authentication algorithms. hostapd can be #

# configured to allow both of these or only one. Open system authentication #

# should be used with IEEE 802.1X. #

# Bit fields of allowed authentication algorithms: #

# bit 0 = Open System Authentication #

# bit 1 = Shared Key Authentication (requires WEP) #

################################################## ############################

auth_algs=3



######################### IEEE 802.1X related config #########################

# Require IEEE 802.1X authorization

#ieee8021x=0



# EAPOL-Key index workaround (set bit7) for WinXP Supplicant (needed only if

# only broadcast keys are used)

#eapol_key_index_workaround=0



######### IEEE 802.11f - Inter-Access Point Protocol (IAPP) ##################

# Interface to be used for IAPP broadcast packets

#iapp_interface=eth0



####################### WPA/IEEE 802.11i config ##############################

wpa=1

#wpa_psk=701459761a3d17c5ddead0deafbeeffeedbadf00d c659db31e2e3d36f00a12b1

wpa_passphrase=hengfookyauhengfookyauhengfo

wpa_key_mgmt=WPA-PSK

wpa_pairwise=TKIP CCMP


(2) WPA_Supplicant + Madiwif + Network Manager
When I was client, the information about the existing AP even the ESSID name did not shown in network manager. Why?

Thank, please help.

[wieman01]

My apologies. I missed the static IP part.
No problem. This Sticky Thread will be removed as soon as Hardy is released.

[wieman01]

Dear sir,

I saw your post about WPA configuration. I have few question on this, can you help me? I using Atheros + Madwifi for the wifi NIC.

Questions:
(1) hostapd
I recently configure a WPA in a own build Linux access point (AP. But the configuration i not configured in /etc/network/interfaces. I using another program name hostapd to perform the WPA. I configured all the WPA configuration in hostapd config file. My problems not is, I run the hostapd daemon, but the client can connect to the AP without being authenticate by WPA. Did you know about hostapd + Madwifi, please assist me.

Starting the daemon:


hostapd.conf:
[/COLOR]

(2) WPA_Supplicant + Madiwif + Network Manager
When I was client, the information about the existing AP even the ESSID name did not shown in network manager. Why?

Thank, please help.
Frankly I have no experience with the Madwifi driver and it's no real topic for this thread... However, what happens when you do:
sudo iwlist scan
sudo lshw -C network
What device have you got there?

[quodlibetor]

great post, it seems like it almost works for me ;)

I've got a bit of a problem: when i followed your instructions everything seemed to work fine, including up to the "/etc/init.d/networking restart" showing me the new preferences that i wanted and apparently connecting to the correct network, but then my computer freezes.

Based on my system monitor it looks like the CPU over-revs and gets locked down, but i don't know how to check because my computer becomes completely frozen (mouse stuck, ctrl+alt+f1 does nothing, alt+sysrq+r doesn't help...)

I can wirelessly connect to unsecured networks, it's just i've been unable to set up WPA1, which is what i'm trying to do.

some basic stats:
U 7.10
Linksys WMP300n with NDISwrapper

thanks in advance

[wieman01]

great post, it seems like it almost works for me ;)

I've got a bit of a problem: when i followed your instructions everything seemed to work fine, including up to the "/etc/init.d/networking restart" showing me the new preferences that i wanted and apparently connecting to the correct network, but then my computer freezes.

Based on my system monitor it looks like the CPU over-revs and gets locked down, but i don't know how to check because my computer becomes completely frozen (mouse stuck, ctrl+alt+f1 does nothing, alt+sysrq+r doesn't help...)

I can wirelessly connect to unsecured networks, it's just i've been unable to set up WPA1, which is what i'm trying to do.

some basic stats:
U 7.10
Linksys WMP300n with NDISwrapper

thanks in advance
This could be a problem relating to 'ndiswrapper'. I have heard of similar problems before, 'ndiswrapper' making the system freeze and all that stuff. So upgrading to the latest SVN version might help. This thread is a great source:

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

[quodlibetor]

This could be a problem relating to 'ndiswrapper'. I have heard of similar problems before, 'ndiswrapper' making the system freeze and all that stuff. So upgrading to the latest SVN version might help. This thread is a great source:

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

Thanks i'll check that out.

[tad1073]

If I am the one connecting to an AP with WPA2(auto) TPIK I need to configure etc/wpa_supplicant.conf as lited below? Also, I need to use the network key that was genrated when I created the wirless network on the machine that is connected to the router? Will i be able to do this in roaming mode also, because when I use manual configuration I am not able to connect. I an using madwifi w/ Network Manager and ath0 is my wireless device.

auto ath0
iface ath0 inet dhcp
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key> [IMPORTANT: See "WPA-PSK key generation"]

[wieman01]

If I am the one connecting to an AP with WPA2(auto) TPIK I need to configure etc/wpa_supplicant.conf as lited below? Also, I need to use the network key that was genrated when I created the wirless network on the machine that is connected to the router? Will i be able to do this in roaming mode also, because when I use manual configuration I am not able to connect. I an using madwifi w/ Network Manager and ath0 is my wireless device.

auto ath0
iface ath0 inet dhcp
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key> [IMPORTANT: See "WPA-PSK key generation"]
If you want to continue using Network Manager, then this thread is of no use to you. You don't have to do anything manually if NM does the job for you (unless you are in need of static IP addresses).

[jwmcgee1]

Help. I am trying to get my system running on WiFi.

I am using an Apple router, and a Linksys WMP54G adapter on Ubuntu 7.1.

I am trying to use WPA2, DHCP, no SSID broadcast. As long as my SSID IS broadcast, and I enter the info using the network control panel it works ok, but it will not work if the SSID is not broadcast.

Here is the info I have:

Interfaces:

auto lo
iface lo inet loopback

auto wlan1
iface wlan1 inet static
address 10.0.1.112
gateway 10.0.1.1
dns-nameservers 10.0.1.1
netmask 255.255.255.0
wpa-ap-scan 2
wpa-pairwise CCMP
wpa-group CCMP
wpa-psk bd01c01aa270beff1cbc71a7d0df7ce9d398c1d494e7aed1ac cb3ccf09dc1985
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto RSN
wpa-ssid OKCBears


wlan1 IEEE 802.11g ESSID:"OKCBears"
Mode:Managed Frequency:2.462 GHz Access Point: 00:19:E3:FA:BB:61
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Link Signal level=-50 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 Link encap:Ethernet HWaddr 00:07:E9:63:3F:AD
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

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

wlan1 Link encap:Ethernet HWaddr 00:1D:7E:9D:A9:4E
inet addr:10.0.1.112 Bcast:10.0.1.255 Mask:255.255.255.0
inet6 addr: fe80::21d:7eff:fe9d:a94e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:123751 errors:0 dropped:0 overruns:0 frame:0
TX packets:87035 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:9091096 (8.6 MB) TX bytes:65516603 (62.4 MB)

wmaster0 Link encap:UNSPEC HWaddr 00-1D-7E-9D-A9-4E-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)

Any help would be appreciated!!!

[wieman01]

Help. I am trying to get my system running on WiFi.

I am using an Apple router, and a Linksys WMP54G adapter on Ubuntu 7.1.

I am trying to use WPA2, DHCP, no SSID broadcast. As long as my SSID IS broadcast, and I enter the info using the network control panel it works ok, but it will not work if the SSID is not broadcast.

Here is the info I have:

Any help would be appreciated!!!
Frankly I don't know how to help. Some adapters cannot cope with hidden SSIDs, occasionally it has to do with the drivers, then again Network Manager is the culprit. Tell you what... turning off SSID broadcast does not add any extra security, why do you not leave it enabled? I think it makes sense, I do the same thing simply because client computers work better with SSID broadcast turned on.

[jwmcgee1]

I was afraid you were going to say that.

I figured it was the Linksys card giving me grief!

[Happibun]

Hello, and thank you for what looks like a phenomenal thread.

I am an utter Noob to Linux, having not even used a Linux machine until 48 hours ago, but always wanted to get started with it. I was given a laptop yesterday with no operating system, so I went for it and installed Gutsy 7.1. All worked beautifully except for wireless networking.

It seems that I have innocently stumbled upon the most problematic area by shear folly and ignorance. Such is life :(

Anyhow, this is the set up so far:

Dell Latitude 120L Laptop.
Ubuntu 7.10, Gnome.
Broadcom internal network card chipset, running with ndiswrapper.
Netgear DG834GT router with up to date firmware, was set to hidden SSID with MAC filtering on.
Now broadcasting SSID, using WPA-PSK encryption, and MAC filtering.

I have been able to connect wirelessly when the SSID was broadcast, and I had keyed the MAC addresses in to the router. However, I feel I need an extra level of security if I have to broadcast my SSID.
I would prefer to hide my SSID and I really want to keep the MAC filtering on. I'm not too bothered about WPA, the way I see it - MAC filtering is the most secure way to protect my network. I would like the laptop to be able to connect to my network when it boots, without me having to jigger about with he router or terminal each time I want to connect.

Any help would be greatly appreciated.

I'll warn you now that I am not a wireless network expert, and I'm swamped by commands and acronyms. Please be gentle with me 8-[

Jo

[wieman01]

@Happibun:

Welcome first of all.

Before we go ahead a couple of comments... MAC filtering isn't really a security feature. It takes experienced users like me 5 seconds to get around it. Hiding SSID is no security feature either, and in fact makes your system less secure. See this for more:

http://blogs.technet.com/steriley/archive/2007/10/16/myth-vs-reality-wireless-ssids.aspx

Also you are right in that WPA is the way to go. Again it would take me about 15 minutes to crack your WEP key and take control of your network.

Having said that, do you really want to turn off SSID broadcast? I think WPA is fine. And if network manager (the networking applet that you are most likely using) does a good job with SSID broadcast enabled, I'd go for it. Why bother?

That's my most informed opinion. :-)

If you still have troubles with WPA, please do me a favor, open a terminal (command line), type in the following commands and post the results:
sudo iwlist scan
sudo lshw -C network
"-C" is a capital C. Please post the output.

No worries, this is the right thread to ask all these questions. Bear with me (and Ubuntu) and I promise you it will be a very pleasant experience.

[MountainX]

My wireless networking fails to get a valid IP address after I suspend/resume.

I have already tried (without success) the suggestions here:
http://lilserenity.wordpress.com/2007/10/31/fix-ubuntu-dropping-wireless-on-suspendhibernate-resume/
The core change recommended, which I did, was:
/etc/default/acpi-support:
Change STOP_SERVICES to read:
STOP_SERVICES="networking"

Here is some info on my system:

~$ sudo iwlist scan
Password or swipe finger:
lo Interface doesn't support scanning.

vmnet1 Interface doesn't support scanning.

vmnet8 Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:1B:11:68:7C:69
ESSID:"my-essid"
Protocol:IEEE 802.11bg
Mode:Master
Channel:1
Frequency:2.412 GHz (Channel 1)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 9 Mb/s; 11 Mb/s
6 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=92/100 Signal level=-39 dBm Noise level=-39 dBm
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : PSK
Preauthentication Supported
Extra: Last beacon: 240ms ago

username@computername:~$ sudo lshw -C network
*-network
description: Ethernet interface
product: 82566MM Gigabit Network Connection
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: eth0
version: 03
serial: 00:1e:37:86:99:22
capacity: 1GB/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000 driverversion=7.3.20-k2-NAPI firmware=0.3-0 latency=0 link=no module=e1000 multicast=yes port=twisted pair
*-network
description: Wireless interface
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: eth1
version: 02
serial: 00:1c:bf:75:fc:15
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ipw3945 driverversion=1.2.2mp.ubuntu1 firmware=14.2 1:0 () latency=0 link=no module=ipw3945 multicast=yes wireless=unassociated
username@computername:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:1E:37:86:99:22
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)
Base address:0x1840 Memory:fe200000-fe220000

eth1 Link encap:Ethernet HWaddr 00:1C:BF:75:FC:15
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:3 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:21 Memory:d7dff000-d7dfffff

eth1:avah Link encap:Ethernet HWaddr 00:1C:BF:75:FC:15
inet addr:169.254.7.83 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:21 Memory:d7dff000-d7dfffff

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:68 errors:0 dropped:0 overruns:0 frame:0
TX packets:68 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6154 (6.0 KB) TX bytes:6154 (6.0 KB)


If I restart networking, my wireless device will get an IP address and then everything works. Seems like the change I made here doesn't go the trick.
/etc/default/acpi-support:
STOP_SERVICES="networking"

Should I remove this change or alter it? Or should I add the "sudo /etc/init.d/networking restart" command to a startup script as well?

BTW, I do not have the wireless networking icon in the upper right of my screen. How do I fix this? Thanks.

[wieman01]

@MountainX:

I know very little about ACPI. Therefore I cannot advise here. You could certainly create another startup script but I am not certain which run level that would be. I found some stuff here that could be interesting:

http://gentoo-wiki.com/TIP_ACPI_basic_configuration

For general wireless help & support please see this thread:

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

[wieman01]

@MountainX:

I think you would have to put it here:
sudo gedit /etc/acpi/resume.sh
Then add (no 'sudo'):
/etc/init.d/networking restart
Please try and let me know if it works.

[Average Joe]

wieman01, thanks for this nice how-to! I followed your instructions and it works like a charm.

In a previous post (http://ubuntuforums.org/showpost.php?p=4388526&postcount=1232) you linked to an article (http://blogs.technet.com/steriley/archive/2007/10/16/myth-vs-reality-wireless-ssids.aspx) that explains that hiding your SSID is not secure at all, and you stated that it makes your system even less secure. Maybe that is true, but why do you, as an expert, then configure your system (in the how-to) such that it does hide your SSID?

I use my wireless network for my laptop at home, and apart from using WPA2, I have configured it such that it hides my SSID, and that it uses MAC address filtering. I understand that those last two measures don't add (much) security to my system when I use it.

However, most of the day my laptop is switched off, and I would think that, since there is no wireless traffic then, it is more secure to hide your SSID and use MAC filtering. Or would it still be possible for an attacker to figure out both my SSID and my MAC address while my computer is switched off? My modem/router is on 24/7.

[wieman01]

wieman01, thanks for this nice how-to! I followed your instructions and it works like a charm.

In a previous post (http://ubuntuforums.org/showpost.php?p=4388526&postcount=1232) you linked to an article (http://blogs.technet.com/steriley/archive/2007/10/16/myth-vs-reality-wireless-ssids.aspx) that explains that hiding your SSID is not secure at all, and you stated that it makes your system even less secure. Maybe that is true, but why do you, as an expert, then configure your system (in the how-to) such that it does hide your SSID?

I use my wireless network for my laptop at home, and apart from using WPA2, I have configured it such that it hides my SSID, and that it uses MAC address filtering. I understand that those last two measures don't add (much) security to my system when I use it.

However, most of the day my laptop is switched off, and I would think that, since there is no wireless traffic then, it is more secure to hide your SSID and use MAC filtering. Or would it still be possible for an attacker to figure out both my SSID and my MAC address while my computer is switched off? My modem/router is on 24/7.
Hello,

You are quite right in that my previous advice on turning on SSID broadcast must sound quite ambiguous given the objective of my tutorial, however, I must admit that I have learned in the course of the months and that I was not aware of it by the time I compiled the tutorial.

What comes on top is the fact that a lot of people ask for it, therefore my attempt at explaining how you can achieve it, although I should know better.

The security risk imposed by disabling SSID broadcast are somewhat limited, in particular if you don't do much roaming (see article). To answer your question, yes, MAC filtering and disabling broadcast might make it appear more secure and it makes people feel better, then so be it.

But looking at it from another angle, a system is as secure as the weakest link that holds it together. In terms of wireless security, that would be your security protocol (e.g. WPA2) and your key (PSK). If an attacker can get around these, MAC filtering and a hidden SSID won't help you, either. But if she/he can't, she/he won't even notice you have enabled MAC filtering, and most certainly won't be able to take advantage of the fact that you are broadcast your SSID.

Do you understand what I am trying to get at? Good discussion.

[Average Joe]

Thank you for that explanation. I am using the WPA2 protocol and a strong PSK key, so I feel pretty safe.

Apart from the fact that it just feels more safe to do, I also hide my SSID and use MAC filtering for two reasons:

1) If someone would break in my wireless network, he would have to use my MAC address. I know this is very easy for him to get by just sniffing my network traffic. But it would mean that I would probably lose my connection, since I expect that the MAC address can only work for one computer at a time. Therefore, I would most likely notice that my system would be compromised, and take immediate action.

2) If my SSID is hidden, I would think that in case my computer is off, there are no probe requests from my computer to my non-broadcasting network, and a potential hacker would not be able to retrieve my SSID. Therefore, during the time that I don't use my computer (i.e. it is switched off) I am more safe to attacks on the wireless network.

I understand that the attacker would still need to get around the security protocol, but assuming (for the sake of argument) that he can, I think using MAC address filtering and a hidden SSID has some additional value, that is not only existing in the head of the user.

[wieman01]

Thank you for that explanation. I am using the WPA2 protocol and a strong PSK key, so I feel pretty safe.

Apart from the fact that it just feels more safe to do, I also hide my SSID and use MAC filtering for two reasons:

1) If someone would break in my wireless network, he would have to use my MAC address. I know this is very easy for him to get by just sniffing my network traffic. But it would mean that I would probably lose my connection, since I expect that the MAC address can only work for one computer at a time. Therefore, I would most likely notice that my system would be compromised, and take immediate action.

2) If my SSID is hidden, I would think that in case my computer is off, there are no probe requests from my computer to my non-broadcasting network, and a potential hacker would not be able to retrieve my SSID. Therefore, during the time that I don't use my computer (i.e. it is switched off) I am more safe to attacks on the wireless network.

I understand that the attacker would still need to get around the security protocol, but assuming (for the sake of argument) that he can, I think using MAC address filtering and a hidden SSID has some additional value, that is not only existing in the head of the user.
Hello,

Both valid reasons. This is in fact my own line of thinking as well. Again, it is little extra security and with a strong PSK I doubt an attacker would even have the slightest chance of breaking it and thus compromising your network, but one never knows. :-)

[Average Joe]

I am actually wondering why I cannot use the Network manager (nm-applet) to configure my wireless network.

This applet is now showing up as an icon in my notification area, basically doing nothing. However, since I am using a laptop, I would be convenient for me to use it for easy switching between wireless networks. However, whenever I make some changes with the Network Manager (i.e. switch to roaming) I lose my connection, and what is worse, I lose my settings as well, making me have to recreate the /etc/network/interfaces file from scratch again. This happens even after having saved (and reloaded) the working configuration in nm-applet.

This leaves me with two questions:

1) Is it not possible to use the Network-manager after having followed the how-to in the first post?

2) Is there another way to switch easily between wireless networks?

[wieman01]

@Average Joe:

If you configure your network/device using this approach, you cannot use NM any more. But there are options:

1. WICD (http://wicd.sourceforge.net/)
2. Wifi-Radar (repositories)

[Average Joe]

Thanks for pointing that out wieman01!

I tried them both. Wifi-radar didn't work too well for me. It shows all the wireless networks in range, but it does not show the signal strengths nor the encryption type. What is worse, I cannot edit any configuration with it, so I removed it.

However, Wicd works great! It shows all the information I want, and I can change all the settings for my wireless connection. I usually don't install applications outside the Ubuntu repositories, but for Wicd I made an exception.

I actually hate to tell you this, but I have now cleared all the wireless settings my /etc/network/interfaces file that you described so well in your nice how-to, and I also removed the additional network restart script that I required earlier. With Wicd I simply don't need it any longer.

I could very easy configure my wireless network settings with Wicd (I am using WPA2 with AES and a fixed IP address). I also don't need to convert my WPA ascii key to a hexadecimal pass phrase. All in all it seems less of a hassle to get my wireless network to work, plus I think with Wicd it seems easier to switch from one network to the other.

I think Wicd is actually what I have been looking for, I haven't experienced any drawbacks yet.

[wieman01]

Thanks for pointing that out wieman01!

I tried them both. Wifi-radar didn't work too well for me. It shows all the wireless networks in range, but it does not show the signal strengths nor the encryption type. What is worse, I cannot edit any configuration with it, so I removed it.

However, Wicd works great! It shows all the information I want, and I can change all the settings for my wireless connection. I usually don't install applications outside the Ubuntu repositories, but for Wicd I made an exception.

I actually hate to tell you this, but I have now cleared all the wireless settings my /etc/network/interfaces file that you described so well in your nice how-to, and I also removed the additional network restart script that I required earlier. With Wicd I simply don't need it any longer.

I could very easy configure my wireless network settings with Wicd (I am using WPA2 with AES and a fixed IP address). I also don't need to convert my WPA ascii key to a hexadecimal pass phrase. All in all it seems less of a hassle to get my wireless network to work, plus I think with Wicd it seems easier to switch from one network to the other.

I think Wicd is actually what I have been looking for, I haven't experienced any drawbacks yet.
Excellent! So this exercise did have a purpose. :-)

No problem, if WICD works best for you, so be it. Good news.

[wangrui]

Help please!

I have search for a very long time but still can't find any article talking about how to make LEAP wireless working.
This is my /etc/network/interfaces:


auto lo
iface lo inet loopback

iface ath0 inet dhcp
wpa-ap-scan 1
wpa-eap LEAP
wpa-identity <username>
wpa-password <password>
wireless-essid IBM

iface eth0 inet dhcp
address 10.1.0.5
netmask 255.255.255.0
gateway 10.1.0.1

auto eth0


But I can't get any IP, and ESSID is using another one:

iwconfig ath0

ath0 IEEE 802.11g ESSID:"IBMVISITOR" Nickname:""
Mode:Managed Frequency:2.422 GHz Access Point: Not-Associated
Bit Rate:1 Mb/s Tx-Power:8 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=3/70 Signal level=-92 dBm Noise level=-95 dBm
Rx invalid nwid:1700 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


ifconfig

ath0 Link encap:Ethernet HWaddr 00:19:7E:0D:B4:29
inet6 addr: fe80::219:7eff:fe0d:b429/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wifi0 Link encap:UNSPEC HWaddr 00-19-7E-0D-B4-29-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:30318 errors:0 dropped:0 overruns:0 frame:49856
TX packets:6272 errors:5 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:4462881 (4.2 MB) TX bytes:288404 (281.6 KB)
Interrupt:21


sudo dhclient ath0
and same result with "sudo dhclient wifi0"

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

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:19:7e:0d:b4:29
Sending on LPF/ath0/00:19:7e:0d:b4:29
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5
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 6
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


Can anybody help me? I still don't know whether ubuntu can support LEAP or not. If there is any library missing, I can copy them from another working OS (Our company offers all kind of software in a single package with Red Hat 5.1, but it's really unbelievable unbelievable unbelievable hard to use, besides a huge amount of spyware installed by the company). I don't know anything about linux networking. Some expert please help me. Even some instructions will be greatly appreciated. If somebody tell me how to do it, I can install a RH5.1 first, copy necessary files out, then throw it away.

[wieman01]

Hello wangrui:

First off I see that you are using a wireless adapter with an Atheros chipset. LEAP is a proprietary protocol developed by Cisco, so I cannot guarantee that the current Linux driver supports it. Actually I doubt it.

LEAP should not be used anyway, as it is highly insecure.

When you try to connect, please post the follwing:
sudo ifdown -v ath0
sudo ifup -v ath0
And also:
sudo iwlist scan
sudo lshw -C network

[wangrui]

Hi wieman01,

Thank you very much! This forum is really amazing. Every question is being answered without any delay. How can you guys do this. It's amazing service. Sometime, it may take me two days to reply all of the mails in my mailbox, even that's my work.

I have almost learned everything about LEAP recently. I know LEAP is insecure. There is also a EAP-TLS available, but whatever, I'm in a big building with may layered security. That won't be a problem.

Please see the detail. Thanks for your help.

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/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 7366
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:19:7e:0d:b4:29
Sending on LPF/ath0/00:19:7e:0d:b4:29
Sending on Socket/fallback
ifconfig ath0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/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 7341).


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: using default driver type: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.ath0.pid -i ath0 -D wext -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 1 -- 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:19:7e:0d:b4:29
Sending on LPF/ath0/00:19:7e:0d:b4:29
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 10
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/wpasupplicant
run-parts: executing /etc/network/if-up.d/wrfirewall


for "sudo iwlist scan", there are 21 Cell from "Cell 01" to "Cell 21", with similar output:

ath0 Scan completed :
Cell 01 - Address: 00:17:59:DB:41:F0
ESSID:"IBM"
Mode:Master
Frequency:2.412 GHz (Channel 1)
Quality=52/70 Signal level=-43 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 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
...



sudo lshw -C network:

*-network
description: Wireless interface
product: AR5212 802.11abg NIC
vendor: Atheros Communications, Inc.
physical id: 0
bus info: pci@0000:03:00.0
logical name: wifi0
version: 01
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=ath_pci driverversion=0.9.4.5 (0.9.3.2) latency=0 module=ath_pci multicast=yes wireless=IEEE 802.11g


Thank you for looking into the problem. If it can't work, maybe I can copy some files from RedHat, but I don't know how to do it.

[wieman01]

Wangrui:

Guess we really enjoy what we are doing. So response time just reflects that. :-)

This does not look promising:
wpa_supplicant: wpa-ap-scan 1 -- OK
There should be a line for each line in "/etc/network/interfaces". I don't think the current driver supports LEAP.

Second you have cut off the interesting part of the scan... Could you scan once again and list the entire block pertaining to the network in question?

If all this does not yield any results, you probably have to replace the driver... You can do so using a tool called "ndiswrapper" which basically lets you install & use the Windows driver. Pretty cool, I used it as well for one of my Linksys adapters.

Get back to me and we'll see. :-)

[wangrui]

Wangrui:

Guess we really enjoy what we are doing. So response time just reflects that. :-)

This does not look promising:

There should be a line for each line in "/etc/network/interfaces". I don't think the current driver supports LEAP.

Second you have cut off the interesting part of the scan... Could you scan once again and list the entire block pertaining to the network in question?

If all this does not yield any results, you probably have to replace the driver... You can do so using a tool called "ndiswrapper" which basically lets you install & use the Windows driver. Pretty cool, I used it as well for one of my Linksys adapters.

Get back to me and we'll see. :-)

Hi wieman01,

So glad you guys are having passion. I have passion years ago, but can't find any exciting topic recently.

Thank you for the tip. If the current driver don't support LEAP. Do you know what is the driver looks like? Is it a so or kernel module? Because I has a runnable system, maybe it's very easy for me if I can find it out. I just copy it and do some modprobe or linking.

Sorry about the missing lines. I cut two parts of the output. One is lshw, I remove the line which contains the serial no. The other one is the iwlist scan, because I don't understand it and not sure whether it's confidential or not. But after some googling, I found a similar line which only some position of the zeros is different. So I guess it's not confidential. The missing line looks something like:

Extra:wme_ie=dd180050f2020101810003a4000027a400004 2435e0062322f00

All cell is exactly the same.

[wieman01]

You are welcome of course.

A scan will not reveal anything confidential... Kind of would defeat the purpose of a security feature, don't you think? :-)

See, when you scan for networks, cards that support LEAP would state the encryption and authentication type. If no such information is given (only "Encryption key:on" for instance) then it does not recognize the encryption/authentication type. That's bad news.

Are you on Ubuntu 64-bit?

I use "ndiswrapper" with another chipset, so I won't be of much help. But first thing you should do is check if your card is listed here:

http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list/

If it is, get the latest Windows driver for your adapter from the vendor's website, the 64-bit version if you are on 64-bit Ubuntu. Then deploy it using 'ndiswrapper'.

Check out my Ralink tutorial (signature) to get a feel for what you will have to do. And simply post here if you have further questions, I'll try to help you.

[wangrui]

You are welcome of course.

A scan will not reveal anything confidential... Kind of would defeat the purpose of a security feature, don't you think? :-)

See, when you scan for networks, cards that support LEAP would state the encryption and authentication type. If no such information is given (only "Encryption key:on" for instance) then it does not recognize the encryption/authentication type. That's bad news.

Are you on Ubuntu 64-bit?

I use "ndiswrapper" with another chipset, so I won't be of much help. But first thing you should do is check if your card is listed here:

http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list/

If it is, get the latest Windows driver for your adapter from the vendor's website, the 64-bit version if you are on 64-bit Ubuntu. Then deploy it using 'ndiswrapper'.

Check out my Ralink tutorial (signature) to get a feel for what you will have to do. And simply post here if you have further questions, I'll try to help you.

Thanks a lot. Do you mean it's my network card driver don't support LEAP. If I can find a workable network card driver, everything will work?

I will have a try some later time. Thank you!