FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 01-19-2010, 07:53 AM
Paul Scott
 
Default problems using wicd on WPA2 secured networks

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:977
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@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-19-2010, 09:02 AM
Liam O'Toole
 
Default problems using wicd on WPA2 secured networks

On 2010-01-19, Paul Scott <waterhorse@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@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-19-2010, 09:26 AM
Paul Scott
 
Default problems using wicd on WPA2 secured networks

Liam O'Toole wrote:

On 2010-01-19, Paul Scott <waterhorse@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@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-19-2010, 10:14 AM
Bob Brewer
 
Default problems using wicd on WPA2 secured networks

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@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-19-2010, 10:45 AM
Liam O'Toole
 
Default problems using wicd on WPA2 secured networks

On 2010-01-19, Paul Scott <waterhorse@ultrasw.com> wrote:
> Liam O'Toole wrote:
>> On 2010-01-19, Paul Scott <waterhorse@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@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-19-2010, 03:30 PM
Paul Scott
 
Default problems using wicd on WPA2 secured networks

Liam O'Toole wrote:

On 2010-01-19, Paul Scott <waterhorse@ultrasw.com> wrote:

(...)



I'm using backported wicd 1.6.2.2 on lenny.


I believe I have made many attempts with 1.6.2.2 but I will try it again.


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.


Ok. I will try that on my home situation.

OTOH I need to connect at a coffee shop which uses a given "password"

Wicd just tells me that the connection is WPA2. When I set Wicd
properties for that connection either to


WPA 1/2 Passphrase
or
WPA 1/2 Preshared Key

I get the same bad password rejection from Wicd.

That was with 1.7. I'm installing 1.6.2.2 right now.

Thanks,

Paul




--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-19-2010, 04:26 PM
Arthur Machlas
 
Default problems using wicd on WPA2 secured networks

On Tue, Jan 19, 2010 at 5:45 AM, Liam O'Toole <liam.p.otoole@gmail.com> wrote:




On 2010-01-19, Paul Scott <waterhorse@ultrasw.com> wrote:
> Liam O'Toole wrote:
>> On 2010-01-19, Paul Scott <waterhorse@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.


*
*
Not to belabour the obvious, but are you certain the passwords match? One time I generated a password on the router not realizing that my caps lock key was on.
Best,
Arthur
 
Old 01-19-2010, 06:01 PM
Liam O'Toole
 
Default problems using wicd on WPA2 secured networks

On 2010-01-19, Paul Scott <waterhorse@ultrasw.com> wrote:

> Wicd just tells me that the connection is WPA2. When I set Wicd
> properties for that connection either to
>
> WPA 1/2 Passphrase
> or
> WPA 1/2 Preshared Key
>
> I get the same bad password rejection from Wicd.
>

When I select "WPA 1/2 (Preshared Key)" I use the hexadecimal
representation of the key. I didn't use a passphrase to
generate the key, so I don't use the other option.

--
Liam O'Toole
Birmingham, United Kingdom



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-19-2010, 06:50 PM
Freeman
 
Default problems using wicd on WPA2 secured networks

On Tue, Jan 19, 2010 at 09:30:46AM -0700, Paul Scott wrote:
> Liam O'Toole wrote:
> >On 2010-01-19, Paul Scott <waterhorse@ultrasw.com> wrote:
> (...)
>
> >>>
> >>>I'm using backported wicd 1.6.2.2 on lenny.
>
> I believe I have made many attempts with 1.6.2.2 but I will try it again.
>
> >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.
>
> Ok. I will try that on my home situation.
>
> OTOH I need to connect at a coffee shop which uses a given "password"
>
> Wicd just tells me that the connection is WPA2. When I set Wicd
> properties for that connection either to
>
> WPA 1/2 Passphrase
> or
> WPA 1/2 Preshared Key
>
> I get the same bad password rejection from Wicd.
>
> That was with 1.7. I'm installing 1.6.2.2 right now.
>

I had problems with the encrypted connection at my office starting with an
upgrade sometime back. It is a WEP hexadecimal passphrase.

No rejection of the passphrase though. It claims failure finding the DNS
server. Also an WRT54G and Wicd 1.6.2.2, on squeeze.

At first I thought it wasn't connecting. After playing with every setting
possible, I discovered it was timing out sometimes on the first try. I
finally settled for 60 seconds of working off line while I wait, with an
occasional second try.

Instantly connects to everything else instantly, even the office occasionally.

--
Kind Regards,
Freeman


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-19-2010, 08:55 PM
Paul Scott
 
Default problems using wicd on WPA2 secured networks

Arthur Machlas wrote:



On Tue, Jan 19, 2010 at 5:45 AM, Liam O'Toole <liam.p.otoole@gmail.com
<mailto:liam.p.otoole@gmail.com>> wrote:






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

Not to belabour the obvious, but are you certain the passwords match?
One time I generated a password on the router not realizing that my caps
lock key was on.


Yes. They are both visible to me at some point.

Thanks,

Paul




--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 06:59 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org