Re: HOWTO: Wireless Security - WPA1, WPA2, LEAP, etc.
Quote:
Originally Posted by
gladstone
Hi, my etc/network/interfaces looked like this:
Code:
auto lo
iface lo inet loopback
auto eth1
iface eth1 inet static
address 192.168.1.2
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid Toupe
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk [MY HASHED PSK]
I have a laptop and my wireless adaptor is an Intel pro 2200BG
Looks fine actually. You have disabled SSID broadcast and use WPA-TKIP. What does a scan yield?
Re: HOWTO: Wireless Security - WPA1, WPA2, LEAP, etc.
In my experience, the following instruction from the main thread
<quote>
VERY IMPORTANT:
Now convert your WPA ASCII password using the following command (' ' single quotes required):
wpa_passphrase 'ssid' 'ascii_key'
</quote>
did not actually require single quotes. wpa_passphrase generated a different key when single quotes were used which was rejected by my router. removing the single quotes and generating the key again solved this for me.
i am using a netgear wgr614v5 wireless router with a netgear wg511 (version 1 made in taiwan) pcmcia card on an acer laptop.
Re: HOWTO: Wireless Security - WPA1, WPA2, LEAP, etc.
Quote:
Originally Posted by
jabberwauki
In my experience, the following instruction from the main thread
<quote>
VERY IMPORTANT:
Now convert your WPA ASCII password using the following command (' ' single quotes required):
wpa_passphrase 'ssid' 'ascii_key'
</quote>
did not actually require single quotes. wpa_passphrase generated a different key when single quotes were used which was rejected by my router. removing the single quotes and generating the key again solved this for me.
i am using a netgear wgr614v5 wireless router with a netgear wg511 (version 1 made in taiwan) pcmcia card on an acer laptop.
Thanks for highlighting that. I have corrected the tutorial accordingly. :-)
Re: HOWTO: Wireless Security - WPA1, WPA2, LEAP, etc.
Quote:
Originally Posted by
wieman01
Looks fine actually. You have disabled SSID broadcast and use WPA-TKIP. What does a scan yield?
It gives me:
Code:
sudo iwlist scan
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
eth1 Scan completed :
Cell 01 - Address: 00:14:7F:58:E8:19
ESSID:"BTHomeHub-4543"
Protocol:IEEE 802.11bg
Mode:Master
Channel:6
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=29/100 Signal level=-82 dBm
Extra: Last beacon: 272ms ago
Cell 02 - Address: 00:03:2F:2B:71:6B
ESSID:"<hidden>"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 9 Mb/s; 11 Mb/s
6 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=71/100 Signal level=-57 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 520ms ago
My router is "Cell 02" in that list. I also use MAC filters, would that make an effect?
I also managed to enable the front LED and when I used my earlier /etc/network/interfaces and rebooted, Ubuntu slowed at 3/4 of the way and resulted in the GNOME.DESKTOP error I mention, but the LED was solid i.e. connected :confused:
Re: HOWTO: Wireless Security - WPA1, WPA2, LEAP, etc.
@Gladstone:
Everything looks fine to me. But beats me, I don't know what's going on. MAC filtering could be an issue but only if the registered MAC isn't the same as the one listed above (00:03:2F:2B:71:6B).
Have you turned roaming off?
Re: HOWTO: Wireless Security - WPA1, WPA2, LEAP, etc.
I have a problem. I installed ubuntu in my machine and there's one problem. Wireless problem. The OS detect all the hardware perfectly and everything runs fine except for the wireless. The OS can detect wireless networks but could not connect to it. I attach together the screenshot and hopefully anyone can try to give me solution for this. Oh yes, the wireless was Realtek RTL8187. Thanks.
http://i16.photobucket.com/albums/b3...screenshot.png
Re: HOWTO: Wireless Security - WPA1, WPA2, LEAP, etc.
Quote:
Originally Posted by
vandetta
I have a problem. I installed ubuntu in my machine and there's one problem. Wireless problem. The OS detect all the hardware perfectly and everything runs fine except for the wireless. The OS can detect wireless networks but could not connect to it. I attach together the screenshot and hopefully anyone can try to give me solution for this. Oh yes, the wireless was Realtek RTL8187. Thanks.
http://i16.photobucket.com/albums/b3...screenshot.png
Please open a new separate thread for your this issue. It has not really anything do to with this one. But feel free to send me the link by PM.
Re: HOWTO: Wireless Security - WPA1, WPA2, LEAP, etc.
Oh, I'm sorry I will open new thread for this :)
Re: HOWTO: Wireless Security - WPA1, WPA2, LEAP, etc.
Quote:
Originally Posted by
gladstone
I followed these steps (after trying ALOT of other methods) but couldnt get it to work. I decided to test if it would work after a reboot, instead I was given the gnome-settings-daemon error.
Initially having no idea what had happened (I couldn't login), I managed to pin-point it back to the /etc/network/interfaces file I just edited.
The bug has been discussed here:
https://bugs.launchpad.net/ubuntu/+s...ter/+bug/61381
and more specifically:
https://bugs.launchpad.net/ubuntu/+s...81/comments/43
https://bugs.launchpad.net/ubuntu/+s...81/comments/23
However, during that time,
my wireless was working!
Is there anything I can try? I can remember another guide adding something like DISABLED=1 to /etc/wpa_supplicant.conf (I saw it mentioned in the Launchpad thread)... Is that the correct command?
what does your /etc/network/interfaces look like..? what wireless card and driver are you using? A quick glance at your earlier post show you have a
dns-nameserver
in your interfaces file?
Re: HOWTO: Wireless Security - WPA1, WPA2, LEAP, etc.
Horrrayy!
Thanks houms, it was that rogue dns-nameservers that was causing all the problems. I'm not sure where I picked that up from, but I've been adding bits of things from all over the place over the last 2 weeks to get this working :( I hope it's not just all part of the learning curve!
I also have to use the network restart script for it to work (as described in post 2 here)