can you please post the commands and the order in which you are using them?
you should be doing things this way:
did you read pureh@te's thread on starting networking?Code:/etc/init.d/networking start wicd && wicd-client&
Hi,
I'm having a problem with Wicd, Iøm running Backtrack 4 Final in VirtualBox, and it sees my network perfectly, my network is WPA2 encrypted, and when I initialize wicd it gives me this:
---------------------------
wicd initializing...
---------------------------
Automatically detected wireless interface wlan0
found wireless_interface in configuration wlan0
setting wireless interface wlan0
automatically detected wired interface eth0
found wired_interface in configuration eth0
setting wired interface eth0
found wpa_driver in configuration wext
setting wpa driver wext
found always_show_wired_interface in configuration False
found use_global_dns in configuration False
setting use global dns to False
setting use global dns to boolean False
found global_dns_1 in configuration None
found global_dns_2 in configuration None
found global_dns_3 in configuration None
setting global dns
global dns servers are None None None
found auto_reconnect in configuration True
setting automatically reconnect when connection drops
found debug_mode in configuration 0
found wired_connect_mode in configuration 1
found signal_display_type in configuration 1
found dhcp_client in configuration 0
Setting dhcp client to 0
found link_detect_tool in configuration 0
found flush_tool in configuration 1
Wireless configuration file found...
Wired configuration file found...
chmoding configuration files 0600...
chowning configuration files root:root...
Using wired interface...eth0
Using wireless interface...wlan0
autoconnecting... wlan0
wlan0 Interface doesn't support scanning : Device or resource busy
Attempting to autoconnect with wired interface...
Putting interface down
Releasing DHCP leases...
There is already a pid file /var/run/dhclient.pid with pid 5804
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit DHCP | Internet Systems Consortium
Bind socket to interface: No such device
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit DHCP | Internet Systems Consortium
Bind socket to interface: No such device
Setting false IP...
Stopping wpa_supplicant and any DHCP clients
wpa_supplicant: no process killed
dhclient: no process killed
dhclient3: no process killed
pump: no process killed
dhcpcd-bin: no process killed
Flushing the routing table...
Nothing to flush.
Nothing to flush.
Putting interface up...
Running DHCP
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit DHCP | Internet Systems Consortium
Listening on LPF/eth0/08:00:27:fa:5e:23
Sending on LPF/eth0/08:00:27:fa:5e:23
Sending on Socket/fallback
receive_packet failed on eth0: Network is down
DHCP connection failed
exiting connection thread
No wired connection present, attempting to autoconnect to wireless network
Unable to autoconnect, you'll have to manually connect
Anything wrong with this? When trying to connect, it just hangs when "Connecting" the bar just goes back and forth forever... This is a clean install of backtrack, I've only installed the guest additions for backtrack, are there anything else I should install to be able to connect to WPA?
can you please post the commands and the order in which you are using them?
you should be doing things this way:
did you read pureh@te's thread on starting networking?Code:/etc/init.d/networking start wicd && wicd-client&
thou shalt treat all computers as thou wouldst treat thyself, for thou art the creator of thine own problems.
Bump!.....
As has been pointed out many times before, please don't bump your posts.
Stop bringing wlan0 up using ifconfig, actually just stop bringing it up period. wicd handles the network interfaces, and brings them up and down as it needs them. If you do what I told you to do, you shouldn't have a problem. If you do have a problem, it's most likely a PEBKAC error, and should be handled via your local PEBKAC specialist.
Something else to note is that you're using VirtualBox. If you're trying to use a PCI/miniPCI (aka built-in) WiFi, it's not going to find it or use it. Get a USB wifi dongle, if this is the case, and pass it through to your VM.
thou shalt treat all computers as thou wouldst treat thyself, for thou art the creator of thine own problems.