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.

It is not necessary to set your card in monitor mode in order to capture your own packets (i.e. packets traveling from your wireless card to the AP). So set your card to "managed" mode and make sure your wpa key is properly placed in the wireshark preferences. (Edit--> preferences--> protocols--> IEEE 802.11)

I don't think you understand. You don't have to change anything to get your card in managed mode (it's default). Monitor mode is used for sniffing all the packets in the air. What I am suggesting is to try to sniff and decrypt your own traffic to get a better understanding, before you try to sniff traffic from your other machine.

Whit Windows 7 and Connectifity Iv been able to capture a lot of information, and I think that I know how to use wireshark in Windows.

I did that, but at fhirst time I saw wlan0 at wireshark. usually its been mon0, but for that i had to use airmon-ng start wlan0

It seems that my capture is not decrypted.

I started using aircrack-ng but then I found out that they think that kismet is more easy for beginners, so Im using it now, I think, that it creates a capture file somewere so I can use Windows and wireshark to read and decrypt all data. Windows 7 is much faster than BT4 on VMware.

It there any way to see that data not decrypted, like joining to that WLAN? If , how to join WLAN, Iv been tying to use Networkmanager but it does nothing.

I tried to use airdecap-ng to decrypt that file, it just todt that it have 3458 WPA of all 22000 packets. It did nothing for that file...