Wicd will not start!

[imported_epoch]

I'm sorry, I couldn't resist. The exclamation points I know must have had some of you frothing at the mouth. But I actually have a kind of related problem. I tried searching and came up with nothing that was related (other than to the title of this thread). Maybe my search-fu sucks and if it does, I apologize.

Wicd will not connect to my WEP protected router. It was working earlier today, and just suddenly stopped working.When it tries to connect It says "dd-wrt1: Putting Interface Down..." and then straight to not connected very quickly. Wicd has no problem connecting to my unprotected router and goes through all the normal steps

I have tried restarting the router. Here is the Wicd log.

2009/12/01 22:35:17 :: ---------------------------
2009/12/01 22:35:17 :: wicd initializing...
2009/12/01 22:35:17 :: ---------------------------
2009/12/01 22:35:17 :: Automatically detected wireless interface wlan0
2009/12/01 22:35:17 :: found wireless_interface in configuration wlan0
2009/12/01 22:35:17 :: setting wireless interface wlan0
2009/12/01 22:35:17 :: Couldn't detect a wired interface.
2009/12/01 22:35:17 :: found wired_interface in configuration None
2009/12/01 22:35:17 :: setting wired interface None
2009/12/01 22:35:17 :: found wpa_driver in configuration wext
2009/12/01 22:35:17 :: setting wpa driver wext
2009/12/01 22:35:17 :: found always_show_wired_interface in configuration False
2009/12/01 22:35:17 :: found use_global_dns in configuration False
2009/12/01 22:35:17 :: setting use global dns to False
2009/12/01 22:35:17 :: setting use global dns to boolean False
2009/12/01 22:35:17 :: found global_dns_1 in configuration None
2009/12/01 22:35:17 :: found global_dns_2 in configuration None
2009/12/01 22:35:17 :: found global_dns_3 in configuration None
2009/12/01 22:35:17 :: setting global dns
2009/12/01 22:35:17 :: global dns servers are None None None
2009/12/01 22:35:17 :: found auto_reconnect in configuration True
2009/12/01 22:35:17 :: setting automatically reconnect when connection drops
2009/12/01 22:35:17 :: found debug_mode in configuration False
2009/12/01 22:35:17 :: found wired_connect_mode in configuration 1
2009/12/01 22:35:17 :: found signal_display_type in configuration 0
2009/12/01 22:35:17 :: found dhcp_client in configuration 0
2009/12/01 22:35:17 :: Setting dhcp client to 0
2009/12/01 22:35:17 :: found link_detect_tool in configuration 0
2009/12/01 22:35:17 :: found flush_tool in configuration 0
2009/12/01 22:35:17 :: Wireless configuration file found...
2009/12/01 22:35:17 :: Wired configuration file found...
2009/12/01 22:35:17 :: chmoding configuration files 0600...
2009/12/01 22:35:17 :: chowning configuration files root:root...
2009/12/01 22:35:17 :: Using wired interface...
2009/12/01 22:35:17 :: Using wireless interface...wlan0
2009/12/01 22:35:17 :: autoconnecting... wlan0
2009/12/01 22:35:20 :: No wired connection present, attempting to autoconnect to wireless network
2009/12/01 22:35:20 :: Unable to autoconnect, you'll have to manually connect
2009/12/01 22:35:26 :: No wired connection present, attempting to autoconnect to wireless network
2009/12/01 22:35:26 :: Unable to autoconnect, you'll have to manually connect
2009/12/01 22:35:30 :: No wired connection present, attempting to autoconnect to wireless network
2009/12/01 22:35:30 :: Unable to autoconnect, you'll have to manually connect
2009/12/01 22:35:33 :: No wired connection present, attempting to autoconnect to wireless network
2009/12/01 22:35:33 :: Unable to autoconnect, you'll have to manually connect
2009/12/01 22:35:33 :: Connecting to wireless network dd-wrt1
2009/12/01 22:35:33 :: Putting interface down
2009/12/01 22:35:34 :: Releasing DHCP leases...
2009/12/01 22:35:34 :: Setting false IP...
2009/12/01 22:35:34 :: Stopping wpa_supplicant and any DHCP clients
2009/12/01 22:35:34 :: Flushing the routing table...
2009/12/01 22:35:34 :: Generating psk...
2009/12/01 22:35:34 :: Attempting to authenticate...
2009/12/01 22:35:34 :: Putting interface up...
2009/12/01 22:35:34 :: exiting connection thread
2009/12/01 22:35:36 :: Connecting to wireless network dd-wrt
2009/12/01 22:35:36 :: Putting interface down
2009/12/01 22:35:36 :: Releasing DHCP leases...
2009/12/01 22:35:36 :: Setting false IP...
2009/12/01 22:35:36 :: Stopping wpa_supplicant and any DHCP clients
2009/12/01 22:35:36 :: Flushing the routing table...
2009/12/01 22:35:36 :: Generating psk...
2009/12/01 22:35:36 :: Putting interface up...
2009/12/01 22:35:37 :: Running DHCP
2009/12/01 22:35:37 :: Internet Systems Consortium DHCP Client V3.1.1
2009/12/01 22:35:37 :: Copyright 2004-2008 Internet Systems Consortium.
2009/12/01 22:35:37 :: All rights reserved.
2009/12/01 22:35:37 :: For info, please visit REDACTED
2009/12/01 22:35:37 :: 
2009/12/01 22:35:37 :: wmaster0: unknown hardware address type 801
2009/12/01 22:35:38 :: wmaster0: unknown hardware address type 801
2009/12/01 22:35:38 :: Listening on LPF/wlan0/00:01:3d:23:5c:87
2009/12/01 22:35:38 :: Sending on   LPF/wlan0/00:01:3d:23:5c:87
2009/12/01 22:35:38 :: Sending on   Socket/fallback
2009/12/01 22:35:41 :: DHCPREQUEST of 192.168.1.146 on wlan0 to 255.255.255.255 port 67
2009/12/01 22:35:41 :: DHCPACK of 192.168.1.146 from 192.168.1.1
2009/12/01 22:35:41 :: bound to 192.168.1.146 -- renewal in 39277 seconds.
2009/12/01 22:35:41 :: DHCP connection successful
2009/12/01 22:35:41 :: Connecting thread exiting.
2009/12/01 23:02:48 :: Connecting to wireless network dd-wrt1
2009/12/01 23:02:48 :: Putting interface down
2009/12/01 23:02:48 :: Releasing DHCP leases...
2009/12/01 23:02:48 :: Setting false IP...
2009/12/01 23:02:48 :: Stopping wpa_supplicant and any DHCP clients
2009/12/01 23:02:48 :: Flushing the routing table...
2009/12/01 23:02:48 :: Generating psk...
2009/12/01 23:02:48 :: Attempting to authenticate...
2009/12/01 23:02:48 :: Putting interface up...
2009/12/01 23:02:48 :: exiting connection thread
2009/12/01 23:02:52 :: Connecting to wireless network dd-wrt1
2009/12/01 23:02:52 :: Putting interface down
2009/12/01 23:02:52 :: Releasing DHCP leases...
2009/12/01 23:02:52 :: Setting false IP...
2009/12/01 23:02:52 :: Stopping wpa_supplicant and any DHCP clients
2009/12/01 23:02:52 :: Flushing the routing table...
2009/12/01 23:02:52 :: Generating psk...
2009/12/01 23:02:52 :: Attempting to authenticate...
2009/12/01 23:02:52 :: Putting interface up...
2009/12/01 23:02:52 :: exiting connection thread
2009/12/01 23:02:57 :: No wired connection present, attempting to autoconnect to wireless network
2009/12/01 23:02:57 :: Unable to autoconnect, you'll have to manually connect
2009/12/01 23:03:02 :: No wired connection present, attempting to autoconnect to wireless network
2009/12/01 23:03:02 :: Unable to autoconnect, you'll have to manually connect
2009/12/01 23:04:10 :: Connecting to wireless network dd-wrt1
2009/12/01 23:04:10 :: Putting interface down
2009/12/01 23:04:10 :: Releasing DHCP leases...
2009/12/01 23:04:10 :: Setting false IP...
2009/12/01 23:04:10 :: Stopping wpa_supplicant and any DHCP clients
2009/12/01 23:04:10 :: Flushing the routing table...
2009/12/01 23:04:10 :: Generating psk...
2009/12/01 23:04:10 :: Attempting to authenticate...
2009/12/01 23:04:10 :: Putting interface up...
2009/12/01 23:04:10 :: exiting connection thread
2009/12/01 23:04:12 :: Connecting to wireless network dd-wrt
2009/12/01 23:04:12 :: Putting interface down
2009/12/01 23:04:12 :: Releasing DHCP leases...
2009/12/01 23:04:12 :: Setting false IP...
2009/12/01 23:04:12 :: Stopping wpa_supplicant and any DHCP clients
2009/12/01 23:04:12 :: Flushing the routing table...
2009/12/01 23:04:12 :: Generating psk...
2009/12/01 23:04:13 :: Putting interface up...
2009/12/01 23:04:13 :: Running DHCP
2009/12/01 23:04:13 :: Internet Systems Consortium DHCP Client V3.1.1
2009/12/01 23:04:13 :: Copyright 2004-2008 Internet Systems Consortium.
2009/12/01 23:04:13 :: All rights reserved.
2009/12/01 23:04:13 :: For info, please visit REDACTED
2009/12/01 23:04:13 :: 
2009/12/01 23:04:13 :: wmaster0: unknown hardware address type 801
2009/12/01 23:04:14 :: wmaster0: unknown hardware address type 801
2009/12/01 23:04:14 :: Listening on LPF/wlan0/00:01:3d:23:5c:87
2009/12/01 23:04:14 :: Sending on   LPF/wlan0/00:01:3d:23:5c:87
2009/12/01 23:04:14 :: Sending on   Socket/fallback
2009/12/01 23:04:18 :: DHCPREQUEST of 192.168.1.146 on wlan0 to 255.255.255.255 port 67
2009/12/01 23:04:18 :: DHCPACK of 192.168.1.146 from 192.168.1.1
2009/12/01 23:04:18 :: bound to 192.168.1.146 -- renewal in 32724 seconds.
2009/12/01 23:04:18 :: DHCP connection successful
2009/12/01 23:04:18 :: Connecting thread exiting.

I have also tried to connect manually

dhclient -r
ifconfig wlan0 down
macchanger -a wlan0
iwconfig wlan0 essid "dd-wrt1" key 00:11:22:33:44
ifconfig wlan0 up
dhclient wlan0

Is there a place where I can find a more detailed log?

[Thorn]

Yes, the exclamation points are annoying.

Did you follow the install video?
http://www.offensive-security.com/vi...backtrack.html

And I have to ask... Who in his right mind would run WEP as an encryption scheme?

[lupin]

Please remember OP, with exclamation points it's one or none.

[imported_epoch]

I'm sorry to say that I did not watch the video until now. But I was able to connect just a few hours ago. I hate giving up and restarting everything from scratch. I've done everything my limited knowledge and search-fu can do. I made no changes and all of a sudden - my problem. Is it possible that the file in which the keys/information are kept got corrupted somehow?

And I'm not really using WEP encryption. I have two routers, one with encryption and one without connected to a switch. I'll bet it doesn't make sense, but I've created a lab in my house so that I can learn about all this stuff. This is a distraction problem that I can't seem to fix. I'm really doing other stuff when this happened. I have no training in computers at all, it's just a really interesting hobby.

I'm also trying to teach myself Python, if you can help me there too. I programmed BASIC on a Commodore64 when I was a kid, then the hobby went away until recently. Anyway, I digress....

Please remember OP, with exclamation points it's one or none.

Sorry, if you'd edit them out, Id appreciate it.

That was the sum of the results I got from searching, and thought you old timers would get a kick out of it.

[Thorn]

It's doubtful that the keys are corrupted. Linux is pretty straightforward in storing most information (such as keys) as straight text.

It looks like several DHCP functions are potentially conflicting. You also said before that you're running WEP on the router and are having trouble connecting. Yet, part of the log says that it's trying to exchange WPA-PSK keys.

...

I have no training in computers at all, it's just a really interesting hobby.
...

'Well, there's your problem.' You have no training, and it would appear that you don't have much experience either. While you seem to at least have a passing familiarity with some Linux commands, but it looks like that knowledge is at the beginner stage. BackTrack is an advanced Linux distro for advanced users. Specifically, it's designed for professionals who are in the Information Security specialty of Penetration Testing. All in all, you've jumped in to the deep end of the pool, and you can barely dog paddle.

Setting up a lab is a great step, but it would seem that you need to gain the basic experience with a Linux distro that's a lot more user friendly, as well as knowledge of networking. I'd suggest starting with Ubuntu. If, in the future, you decide to come back to BT4, the knowledge will be worth it, as BT4 is based on Ubuntu.

It would also seem that need to start with the networking basics. Based on the logs and your statements, it appears a couple of things are happening. You said you have two wireless routers connected to a switch, I hope that lab is isolated. Having that kind of setup can and will cause problems in an of itself; having it hooked up to a live Internet connection can cause you all sorts of grief.

Start with the basics, and take small steps. Read and understand how TCP/IP works, and then set up ONE router on an isolated LAN. (The lab LAN.) Get that to work properly on a wired connection with manual IPs. Gain understanding of the basics of how IP addressing and routing works, and then step to DHCP, and see how that works. Once you've done that, then try it with wireless WITHOUT encryption, and repeat the manual IP and DHCP steps. At the point you understand that, then add encryption. Personally, I'd skip WEP, as it is known to be broken, and go to WPA2 AES directly.

[iforgetmyname]

Ok, I can try to help you manually configure it all:
replace all the "" stuff with your actual info
I am assuming you are using WEP open shared key (hex)
I am also assuming you are using 192.168.x.x , if not change it accordingly

$sudo iwconfig wlan0 essid "whatever"
$sudo iwconfig wlan0 key "whatever"

$sudo ifconfig wlan0 up
$sudo ifconfig wlan0 192.168.x.x broadcast 192.168.x.x
$sudo ifconfig wlan0 set default gw 192.168.x.x

now open a browser and try to connect to your router's page.

If fails try this:
$sudo update-rc.d wicd