You are not logged in.

#1 2010-01-23 04:52:12

silentcontender
Member
Registered: 2009-12-16
Posts: 15

Wicd puts out "Bad Password" after upgrading to 2.6.32.4

I've just upgrade to 2.6.32.4 and had to rollback to 2.6.32.3.  I can't seem to get a wireless connection in 2.6.31.4, wicd keeping giving me "Bad Password" errors and I cannot connect manually either.  Everything worked fine earlier.

Pointers to where I look to fix this? Thanks.

Last edited by silentcontender (2010-01-24 01:21:23)

Offline

#2 2010-01-23 05:00:12

sHyLoCk
Member
From: /dev/null
Registered: 2009-06-19
Posts: 1,197

Re: Wicd puts out "Bad Password" after upgrading to 2.6.32.4

2.6.31.4 or 2.6.32.4? Does wicd-curses work?


~ Regards,
sHy
ArchBang: Yet another Distro for Allan to break.
Blog | GIT | Forum (。◕‿◕。)

Offline

#3 2010-01-23 05:08:09

Acecero
Member
Registered: 2008-06-21
Posts: 1,373

Re: Wicd puts out "Bad Password" after upgrading to 2.6.32.4

The current wicd in the repos is buggy. I recommend installing wicd-bzr to fix your problems

Offline

#4 2010-01-23 08:48:22

ise
Developer
From: Karlsruhe / Germany
Registered: 2005-10-06
Posts: 404
Website

Re: Wicd puts out "Bad Password" after upgrading to 2.6.32.4

Can you please specify it a bit more? Just to say it's buggy and that's all isn't really helpful!

It's really great that I push it to [testing] that people can file bug reports. And all I get was two or three positive feedbacks. Then I push it to extra and everyone is claiming that it's buggy!

Offline

#5 2010-01-23 09:56:17

kgas
Member
From: Qatar
Registered: 2008-11-08
Posts: 718

Re: Wicd puts out "Bad Password" after upgrading to 2.6.32.4

Now including this there are three threads for wicd ( 1, 2 and this one).
- in my case wicd fails to connect to wireless network with wep passphrase. if fails to get IP address. wired net work connects normal.
  the same is the case with wicd-bzr.

2010/01/23 10:29:02 :: dhcpcd: wlan0: broadcasting for a lease
2010/01/23 10:29:02 :: 
2010/01/23 10:29:32 :: dhcpcd: timed out
2010/01/23 10:29:32 :: 
2010/01/23 10:29:32 :: DHCP connection failed
2010/01/23 10:29:32 :: exiting connection thread
2010/01/23 10:29:37 :: Sending connection attempt result dhcp_failed
2010/01/23 10:29:37 :: Autoconnecting...
2010/01/23 10:29:37 :: Putting interface downAttempting to autoconnect with wired interface...

is the log.  Without wicd  I can connect to wireless without any issue. (ifconfig)

Offline

#6 2010-01-23 10:02:29

timttmy
Member
From: UK
Registered: 2008-12-01
Posts: 53

Re: Wicd puts out "Bad Password" after upgrading to 2.6.32.4

Hi ise, I've rolled back to wicd 1.6.2.2-3 (just a version I had laying around, I can't remember if this was the previous version. ) 1.7.0-1 would not connect to WEP or WPA access points that I use all the time wicd would time out and report that it failed to get an address. I could however connect to a WEP ap with iwconfig and dhclinet.


This Is My Truth, Tell Me Yours

Offline

#7 2010-01-23 10:46:59

Acecero
Member
Registered: 2008-06-21
Posts: 1,373

Re: Wicd puts out "Bad Password" after upgrading to 2.6.32.4

ise wrote:

Can you please specify it a bit more? Just to say it's buggy and that's all isn't really helpful!

For my problem at the time, I was getting dbus error messages everytime i logged into X with wicd-client which prevented me from accessing the internet via dhcp. Installing the latest from wicd-bzr fixed that issue.

I also helped another wicd user on the #archlinux channel with another problem about a dependency issue with not accessing the wicd-curses, which pointing to wicd-bzr worked out.

Those are the only bugs I know.

Last edited by Acecero (2010-01-23 10:54:11)

Offline

#8 2010-01-23 16:42:10

silentcontender
Member
Registered: 2009-12-16
Posts: 15

Re: Wicd puts out "Bad Password" after upgrading to 2.6.32.4

Yeah, I spoke too soon. big_smile  Wicd is the problem, not kernel 2.6.32.4.  I looked at kgas's links and I've had the "Connection Failed: Unable to get IP address" for a while now. I thought it was the kernel problem (again), but I worked around it.  I'll put up both logs for wicd 1.6.2.2-3 and 1.7.0-1.

[EDIT] kernel numbers are suppose to be 2.6.32.3 and 2.6.32.4, typo on my part.

Last edited by silentcontender (2010-01-23 16:44:54)

Offline

#9 2010-01-24 02:30:15

silentcontender
Member
Registered: 2009-12-16
Posts: 15

Re: Wicd puts out "Bad Password" after upgrading to 2.6.32.4

@ise

This is wicd 1.7.0

2010/01/23 11:26:28 :: ifconfig eth0 down
2010/01/23 11:26:28 :: ifconfig eth0 up
2010/01/23 11:26:28 :: Putting interface down
2010/01/23 11:26:28 :: ifconfig wlan0 down
2010/01/23 11:26:28 :: Releasing DHCP leases...
2010/01/23 11:26:28 :: /sbin/dhcpcd -k wlan0
2010/01/23 11:26:28 :: Setting false IP...
2010/01/23 11:26:28 :: ifconfig wlan0 0.0.0.0 
2010/01/23 11:26:29 :: iwconfig wlan0
2010/01/23 11:26:30 :: Stopping wpa_supplicant
2010/01/23 11:26:30 :: wpa_cli -i wlan0 terminate
2010/01/23 11:26:30 :: Flushing the routing table...
2010/01/23 11:26:30 :: /sbin/route del dev wlan0
2010/01/23 11:26:30 :: iwconfig wlan0 mode managed
2010/01/23 11:26:30 :: Putting interface up...
2010/01/23 11:26:30 :: ifconfig wlan0 up
2010/01/23 11:26:32 :: enctype is wpa
2010/01/23 11:26:32 :: Generating psk...
2010/01/23 11:26:32 :: ['/usr/sbin/wpa_passphrase', '*********', '************']
2010/01/23 11:26:32 :: Attempting to authenticate...
2010/01/23 11:26:32 :: ['wpa_supplicant', '-B', '-i', 'wlan0', '-c', '/var/lib/wicd/configurations/001b115f2c37', '-D', 'wext']
2010/01/23 11:26:32 :: ['iwconfig', 'wlan0', 'essid', '*********']
2010/01/23 11:26:32 :: iwconfig wlan0 channel 1
2010/01/23 11:26:32 :: iwconfig wlan0 ap 00:1B:11:5F:2C:37
2010/01/23 11:26:32 :: WPA_CLI RESULT IS DISCONNECTED
2010/01/23 11:26:33 :: WPA_CLI RESULT IS SCANNING
2010/01/23 11:26:34 :: WPA_CLI RESULT IS SCANNING
2010/01/23 11:26:35 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:26:36 :: iwconfig wlan0
2010/01/23 11:26:36 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:26:37 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:26:38 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:26:39 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:26:40 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:26:41 :: iwconfig wlan0
2010/01/23 11:26:41 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:26:42 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:26:43 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:26:44 :: WPA_CLI RESULT IS SCANNING
2010/01/23 11:26:45 :: WPA_CLI RESULT IS SCANNING
2010/01/23 11:26:46 :: iwconfig wlan0
2010/01/23 11:26:46 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:26:47 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:26:48 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:26:49 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:26:50 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:26:51 :: iwconfig wlan0
2010/01/23 11:26:51 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:26:52 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:26:53 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:26:54 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:26:55 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:26:56 :: iwconfig wlan0
2010/01/23 11:26:56 :: WPA_CLI RESULT IS SCANNING
2010/01/23 11:26:57 :: WPA_CLI RESULT IS SCANNING
2010/01/23 11:26:58 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:26:59 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:27:00 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:27:01 :: iwconfig wlan0
2010/01/23 11:27:01 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:27:02 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:27:03 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:27:04 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:27:05 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:27:06 :: iwconfig wlan0
2010/01/23 11:27:06 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/23 11:27:07 :: wpa_supplicant authentication may have failed.
2010/01/23 11:27:07 :: connect result is Failed
2010/01/23 11:27:07 :: exiting connection thread
2010/01/23 11:27:11 :: Sending connection attempt result bad_pass
2010/01/23 11:27:11 :: ifconfig eth0
2010/01/23 11:27:11 :: ifconfig wlan0
2010/01/23 11:27:11 :: iwconfig wlan0

And 1.6.2

2010/01/22 17:32:25 :: ['/usr/sbin/wpa_passphrase', '**********', '*********']
2010/01/22 17:32:25 :: Attempting to authenticate...
2010/01/22 17:32:25 :: ['wpa_supplicant', '-B', '-i', 'wlan0', '-c', '/var/lib/wicd/configurations/001b115f2c37', '-D', 'wext']
2010/01/22 17:32:25 :: ['iwconfig', 'wlan0', 'essid', '********']
2010/01/22 17:32:25 :: iwconfig wlan0 channel 1
2010/01/22 17:32:25 :: iwconfig wlan0 ap 00:1B:11:5F:2C:37
2010/01/22 17:32:25 :: WPA_CLI RESULT IS DISCONNECTED
2010/01/22 17:32:26 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:27 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:28 :: iwconfig wlan0
2010/01/22 17:32:28 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:29 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:30 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:31 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:32 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:33 :: iwconfig wlan0
2010/01/22 17:32:33 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:34 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:35 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:36 :: WPA_CLI RESULT IS SCANNING
2010/01/22 17:32:37 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:38 :: iwconfig wlan0
2010/01/22 17:32:38 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:39 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:40 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:41 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:42 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:43 :: iwconfig wlan0
2010/01/22 17:32:43 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:44 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:45 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:46 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:47 :: WPA_CLI RESULT IS SCANNING
2010/01/22 17:32:48 :: iwconfig wlan0
2010/01/22 17:32:48 :: WPA_CLI RESULT IS SCANNING
2010/01/22 17:32:49 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:50 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:51 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:52 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:53 :: iwconfig wlan0
2010/01/22 17:32:53 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:54 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:55 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:56 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:57 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:58 :: iwconfig wlan0
2010/01/22 17:32:58 :: WPA_CLI RESULT IS ASSOCIATING
2010/01/22 17:32:59 :: WPA_CLI RESULT IS SCANNING
2010/01/22 17:33:00 :: wpa_supplicant authentication may have failed.
2010/01/22 17:33:00 :: Running DHCP
2010/01/22 17:33:00 :: /sbin/dhcpcd wlan0
2010/01/22 17:33:00 :: dhcpcd: version 5.1.4 starting
2010/01/22 17:33:00 :: 
2010/01/22 17:33:00 :: dhcpcd: wlan0: waiting for carrier
2010/01/22 17:33:00 :: 
2010/01/22 17:33:03 :: iwconfig wlan0
2010/01/22 17:33:08 :: iwconfig wlan0
2010/01/22 17:33:13 :: iwconfig wlan0
2010/01/22 17:33:18 :: iwconfig wlan0
2010/01/22 17:33:23 :: iwconfig wlan0
2010/01/22 17:33:27 :: iwconfig wlan0
2010/01/22 17:33:30 :: iwconfig wlan0
2010/01/22 17:33:30 :: dhcpcd: timed out
2010/01/22 17:33:30 :: 
2010/01/22 17:33:30 :: DHCP connection failed
2010/01/22 17:33:30 :: exiting connection thread
2010/01/22 17:33:30 :: Sending connection attempt result dhcp_failed

Let me know what other logs you need.  Thanks for the replies.

Offline

Board footer

Powered by FluxBB