wicd problems

[venum]

Hi there,

I am relatively new to backtrack but i have been using Linux systems such as fedora and Ubuntu, but I'm having some trouble with the wicd interface which I'm using as a wireless connection.

I have checked the compatible wireless adapters and my USB adapter is in the list based on rt2800. The problem is the USB device is showing up when i issue iwconfig in console along with the driver information etc... but it seems that its not being assigned an address or picking up any networks. I have tried starting networking trying the rt2800 fix on the backtrack wiki.

I currently have one connection that is working which is eth0 all is fine with this, the only problem is i cant seem to pick up any networks using the wicd manager although it is showing up in konsole when the commands are issued.

Any help would be greatly appreciated

UPDATE:

Screens

http://i45.tinypic.com/sffgie.jpg

http://i48.tinypic.com/21msuhc.png

http://i50.tinypic.com/m75qnm.png

http://i46.tinypic.com/2na2q34.png

Thanks

venum.

[Sobeit]

Hey, im kinda new in BT also and the only advise i have is to try to connect manually.


for non WPA:
http://caleudum.com/how-to-connect-w...untubacktrack/

WPA:
http://blog.tplus1.com/index.php/200...-command-line/


I havent tried it so far, but it is worth a shot i guess, GL.

[venum]

Thanks ill give it a try ! will post on updates

[dobermann1601]

try to open preferences in wicd, check what is written there for your interface, should be wlan0

[venum]

I honestly feel like a tool now something as simple as that, I go and dive in to all other sorts of problems that it could be but a simple preference change worked, much appreciated the help from everyone special thanks to dobermann1601 !

[maverik35]

I think you are little confused.

In monitor mode, you cannot pick up or associate to any AP using WICD or Network Manager..You need to be in "managed" mode. If you are setting your interface (wlan0) in monitor mode, you need to use airodump-ng to see networks, this is done (monitor mode) to inject packets and audit wifi networks.

If you want to associate to a network, you do not have to set monitor mode..You need to set interface in managed mode:

ifconfig wlan0 down
iwconfig wlan0 mode managed
ifconfig wlan0 up

Now you have your interface in managed mode. Now try to associate to a network using either wicd or manually..

Ex: AP = "my_wifi_AP", channel 5, wep key 1234567890....First make sure to set the interface wlan0 in managed mode as instructed above, here I post the complete process:

MANUAL MODE:
ifconfig wlan0 down
iwconfig wlan0 mode managed
iwconfig wlan0 essid my_wifi_AP
iwconfig wlan0 channel 5
iwconfig wlan0 key 1234567890
ifconfig wlan0 up

So far, you must be associated to the AP, verify it: iwconfig

Now, you need to ask for an IP to the AP associated to: dhclient wlan0
You will see a DISCOVER, REQUEST, OFFER, etc..All managed by dhclient (except the OFFER, from AP)..Now you should get an valid IP.

USING WICD:
ifconfig wlan0 down
iwconfig wlan0 mode managed
ifconfig wlan0 up
/etc/init.d/wicd start

It will do all the above (Manually method), but need to be in "managed" mode first..

Now open wicd GUI and see how many networks you can see. Just select the one you want to associate..

When you use airmon-ng, you are setting wlan0 to "monitor mode", ready to inject packets and audit wifi AP's and then your new iface is phy0..If do it manually (monitor mode), your interface remains the same (wlan0)..It is up to you..Which one to use.

PS Sometimes the manual mode fails to associate, you need to try again..I,ve seen this and sometimes try it 3 times and then it associates..Sometimes the first time will do.

Luck.