If this is your first visit, be sure to
check out the Forum Rules by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

I have bt installed and running for a while, now using bt4pf(well chuffed wiv it). The alfa was injecting before, but of late I have been learning other things, so not used it. Now I go back to using, it will not inject, but it will go into monitor mode but will not connect to my own wep.

Also, post the steps you are using to try to connect to an AP and how you show that it is not functioning. Please do this with an AP under your control so you can be sure to eliminate unforeseen variables (like MAC address filtering, etc). Injection is more advanced, if you really can not connect to an AP then that says your card is probably having issues and I wouldn't go further with it.

Yea sorry about the double, getting frustrated. I have tried changing the driver etc, I am thinking the card maybe stuffed, just do not understand why.

The AP's are not the problem since I gave birth to em.

root@tcas-laptop:~# airmon-ng start wlan0
Found 1 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!

@I just use "Wicd Manager" to connect, I am lazy and it is easy When I try to connect wicd just hangs iwconfig below done at the same time "Wicd" is thinking.

you should not bother to bring up wicd prior to/after starting X in this scenario; at least to avoid any possible unnecessary complications/confusion.

@If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!

PID Name
5757 dhclient

did you issue #kill 5757 at this point?

you mention having a live bt3 final option. your card looks as though it should be functional. an easy way to verify the issue is not your card would be to simply rule out the drivers and any other changes/cli mistakes you have made during previous attempts. the alfa should inject and associate properly in monitor mode in bt3 with very little hassle without the confusion sometimes caused by those not used to using the mon0 interface. you could simply bring up the alfa via #airmon-ng start wlan0 (ap channel #),verify monitor mode, and then use an automagic such as wesside-ng via #wesside-ng -i wlan0 (ap channel #) to verify AP association and injection and rule out the card as being defective/failed.

I have not even heard off wesside-ng Ok to rule out - I reloaded bt3 final usb(cd). Issued airmon-ng start wlan0, it is now in m/mode with no 'pid' warning. Issued aireplay-ng --test wlan0 and it is not injecting But it shows mac of 02:1a:70:e1::79:5e for 'tcas_vap'