Prev: Strange work of eth0.
Next: kdm not working after upgrade from KDE 3.5 to 4.3.4
From: Paul Scott on 19 Jan 2010 04:00
Hi,

Wicd is mostly not working for me on networks using WPA2 including a
Linksys WRT54G2 router I configured myself for WPA2. Testing this
connection when encryption is disabled works fine. When I set the
router to WPA2 Personal I currently get:
Connection failed: bad password

2010/01/19 01:44:32 :: Connecting to wireless network bliss
2010/01/19 01:44:32 :: iwconfig eth1
2010/01/19 01:44:32 :: /sbin/dhcpcd-bin -k eth1
2010/01/19 01:44:32 :: ifconfig eth1 0.0.0.0
2010/01/19 01:44:32 :: /sbin/ip route flush dev eth1
2010/01/19 01:44:32 :: ifconfig eth1 down
2010/01/19 01:44:32 :: ifconfig eth1 up
2010/01/19 01:44:32 :: wpa_cli -i eth1 terminate
2010/01/19 01:44:33 :: /sbin/dhcpcd-bin -k eth0
2010/01/19 01:44:33 :: ifconfig eth0 0.0.0.0
2010/01/19 01:44:33 :: /sbin/ip route flush dev eth0
2010/01/19 01:44:33 :: ifconfig eth0 down
2010/01/19 01:44:33 :: ifconfig eth0 up
2010/01/19 01:44:33 :: Putting interface down
2010/01/19 01:44:33 :: ifconfig eth1 down
2010/01/19 01:44:33 :: Releasing DHCP leases...
2010/01/19 01:44:33 :: /sbin/dhcpcd-bin -k eth1
2010/01/19 01:44:33 :: Setting false IP...
2010/01/19 01:44:33 :: ifconfig eth1 0.0.0.0
2010/01/19 01:44:33 :: Stopping wpa_supplicant
2010/01/19 01:44:33 :: wpa_cli -i eth1 terminate
2010/01/19 01:44:34 :: Flushing the routing table...
2010/01/19 01:44:34 :: /sbin/ip route flush dev eth1
2010/01/19 01:44:34 :: iwconfig eth1 mode managed
2010/01/19 01:44:34 :: Putting interface up...
2010/01/19 01:44:34 :: ifconfig eth1 up
2010/01/19 01:44:34 :: iwconfig eth1
2010/01/19 01:44:36 :: enctype is wpa
2010/01/19 01:44:36 :: Generating psk...
2010/01/19 01:44:36 :: ['/usr/bin/wpa_passphrase', 'bliss', '********']
2010/01/19 01:44:36 :: Attempting to authenticate...
2010/01/19 01:44:37 :: ['wpa_supplicant', '-B', '-i', 'eth1', '-c',
'/var/lib/wicd/configurations/0023690f97d7', '-D', 'wext']
2010/01/19 01:44:37 :: ['iwconfig', 'eth1', 'essid', 'bliss']
2010/01/19 01:44:37 :: iwconfig eth1 channel 11
2010/01/19 01:44:37 :: iwconfig eth1 ap 00:23:69:0F:97:D7
2010/01/19 01:44:37 :: WPA_CLI RESULT IS ASSOCIATING
....
2010/01/19 01:45:13 :: wpa_supplicant authentication may have failed.
2010/01/19 01:45:13 :: connect result is Failed
2010/01/19 01:45:13 :: exiting connection thread
2010/01/19 01:45:13 :: Sending connection attempt result bad_pass
2010/01/19 01:45:13 :: ifconfig eth0
2010/01/19 01:45:13 :: ifconfig eth1
2010/01/19 01:45:13 :: Forced disconnect on
2010/01/19 01:45:13 :: iwconfig eth1
2010/01/19 01:45:13 :: /sbin/dhcpcd-bin -k eth1
2010/01/19 01:45:13 :: ifconfig eth1 0.0.0.0
2010/01/19 01:45:14 :: /sbin/ip route flush dev eth1
2010/01/19 01:45:14 :: ifconfig eth1 down
2010/01/19 01:45:14 :: ifconfig eth1 up
2010/01/19 01:45:14 :: wpa_cli -i eth1 terminate
2010/01/19 01:45:14 :: /sbin/dhcpcd-bin -k eth0
2010/01/19 01:45:14 :: ifconfig eth0 0.0.0.0
2010/01/19 01:45:14 :: /sbin/ip route flush dev eth0

TIA for any ideas,

Paul Scott



--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Liam O'Toole on 19 Jan 2010 05:10
On 2010-01-19, Paul Scott <waterhorse(a)ultrasw.com> wrote:
> Hi,
>
> Wicd is mostly not working for me on networks using WPA2 including a
> Linksys WRT54G2 router I configured myself for WPA2. Testing this
> connection when encryption is disabled works fine. When I set the
> router to WPA2 Personal I currently get:
> Connection failed: bad password
>
--SNIP--
> 2010/01/19 01:45:13 :: wpa_supplicant authentication may have failed.
> 2010/01/19 01:45:13 :: connect result is Failed
> 2010/01/19 01:45:13 :: exiting connection thread
> 2010/01/19 01:45:13 :: Sending connection attempt result bad_pass
--SNIP--

I'm using backported wicd 1.6.2.2 on lenny. It authenticates
successfully using WPA2 with a WRT54G router. For encryption type I use
"WPA 1/2 Preshared Key" and enter the key in hexadecimal. No trouble.

How does that compare with your settings?

--
Liam O'Toole
Birmingham, United Kingdom



--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Paul Scott on 19 Jan 2010 05:30
Liam O'Toole wrote:
> On 2010-01-19, Paul Scott <waterhorse(a)ultrasw.com> wrote:
>> Hi,
>>
>> Wicd is mostly not working for me on networks using WPA2 including a
>> Linksys WRT54G2 router I configured myself for WPA2. Testing this
>> connection when encryption is disabled works fine. When I set the
>> router to WPA2 Personal I currently get:
>> Connection failed: bad password
>>
> --SNIP--
>> 2010/01/19 01:45:13 :: wpa_supplicant authentication may have failed.
>> 2010/01/19 01:45:13 :: connect result is Failed
>> 2010/01/19 01:45:13 :: exiting connection thread
>> 2010/01/19 01:45:13 :: Sending connection attempt result bad_pass
> --SNIP--
>
> I'm using backported wicd 1.6.2.2 on lenny. It authenticates
> successfully using WPA2 with a WRT54G router. For encryption type I use
> "WPA 1/2 Preshared Key" and enter the key in hexadecimal. No trouble.
>
> How does that compare with your settings?

This may lead me to ideas not made clear in docs I have read so far.

I am using WPA2 Personal with a text based password which appears to be
converted to a key by wicd.

How you create a Preshared Key?

In terms of either wicd or the router what's the difference between a
key and a password?

Thanks,

Paul


>


--
Paul Scott
Librarian
Southern Arizona Symphony Orchestra


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Bob Brewer on 19 Jan 2010 06:50
Paul Scott wrote:

> How you create a Preshared Key?

I used https://www.grc.com/passwords.htm


Bob


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Liam O'Toole on 19 Jan 2010 06:50
On 2010-01-19, Paul Scott <waterhorse(a)ultrasw.com> wrote:
> Liam O'Toole wrote:
>> On 2010-01-19, Paul Scott <waterhorse(a)ultrasw.com> wrote:
>>> Hi,
>>>
>>> Wicd is mostly not working for me on networks using WPA2 including a
>>> Linksys WRT54G2 router I configured myself for WPA2. Testing this
>>> connection when encryption is disabled works fine. When I set the
>>> router to WPA2 Personal I currently get:
>>> Connection failed: bad password
>>>
>> --SNIP--
>>> 2010/01/19 01:45:13 :: wpa_supplicant authentication may have failed.
>>> 2010/01/19 01:45:13 :: connect result is Failed
>>> 2010/01/19 01:45:13 :: exiting connection thread
>>> 2010/01/19 01:45:13 :: Sending connection attempt result bad_pass
>> --SNIP--
>>
>> I'm using backported wicd 1.6.2.2 on lenny. It authenticates
>> successfully using WPA2 with a WRT54G router. For encryption type I use
>> "WPA 1/2 Preshared Key" and enter the key in hexadecimal. No trouble.
>>
>> How does that compare with your settings?
>
> This may lead me to ideas not made clear in docs I have read so far.
>
> I am using WPA2 Personal with a text based password which appears to be
> converted to a key by wicd.
>
> How you create a Preshared Key?
>
> In terms of either wicd or the router what's the difference between a
> key and a password?
>

I find that the terms "key", "password", and "passphrase" tend to be
used interchangeably in the literature. The important thing to remember
is that the key can be 8-63 printable ASCII characters or 64 hexadecimal
characters. Hence the conversion you mention above.

To generate a PSK, you can use an online service like
https://www.grc.com/passwords.htm.

--
Liam O'Toole
Birmingham, United Kingdom



--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
 |  Next  |  Last
Pages: 1 2
Prev: Strange work of eth0.
Next: kdm not working after upgrade from KDE 3.5 to 4.3.4