Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

Sorry Guest, you are banned from posting and sending personal messages on this forum.

This ban is not set to expire.

[PsySc0rpi0n]

I'm using Debian Jessie with 3.12.6-031206-generic kernel.

I have installed Kali Linux in VirtualBox and I was wondering if it was possible to use aircrack-ng there.

When I issue

Code: [Select]

airmon-ng
I get this

Code: [Select]

Interface              Chipset                 Driver




[rastamouse]

What chipset are you using?

[PsySc0rpi0n]

lspci -vv shows this:

Code: [Select]


04:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)
Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half-size Mini PCIe Card
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at f7900000 (64-bit, non-prefetchable) [size=512K]
Expansion ROM at f7980000 [disabled] [size=64K]
Capabilities: <access denied>
Kernel driver in use: ath9k


[misterx]

Could you post dmesg?

[PsySc0rpi0n]

I could if it wasn't filled up with thousands of evbug useless messages...

I have already tried to remove evbug from modules with rmmod evbug but it gets loaded again! Tried to remove it with modeprobe -r evbug but it gets loaded again!

[PsySc0rpi0n]

Do you want my current system dmesg or dmesg from kali linux from VirtualBox?

[misterx]

From the Kali in the virtualbox.

Attach the content as a file or post it on pastebin. Could you also post the content of lspci and lsusb.

[syworks]

have u try ifconfig -a ?

[ArchKudo]

I don't know if this might help, but here are some troubleshooting information :

1. Is your network card set to UP??
It should be some what similar to this:

Code: [Select]

$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether c8:0a:a9:5f:da:e2 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
    link/ether 78:e4:00:05:2f:1e brd ff:ff:ff:ff:ff:ff
5: wlp0s18f2u1: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether d8:5d:4c:8c:6f:6d brd ff:ff:ff:ff:ff:ff
9: mon0: <BROADCAST,ALLMULTI,PROMISC,NOTRAILERS,UP,LOWER_UP> mtu 1500 qdisc mq state UNKNOWN mode DEFAULT group default qlen 1000
    link/ieee802.11/radiotap d8:5d:4c:8c:6f:6d brd ff:ff:ff:ff:ff:ff

  See the UP in angular bracket wlp2s0 but there is none wlp0s18f2u1 .................

2. When you issue any of the commands are you already associated with a access point??
    if so try deauthenticating it.....

3. Also what is the output of

Code: [Select]

dmesg | tail     does it have output like

Code: [Select]

device mon0 entered promiscuous mode
device mon0 left promiscuous mode
Also you could try dmesg | grep <interface_name>

[PsySc0rpi0n]

Hope this help you helping me:

ifconfig output:
http://paste.debian.net/98109/

dmesg
http://paste.debian.net/98111/

lspci
http://paste.debian.net/98112/

lsusb
http://paste.debian.net/98114/

[misterx]

Sorry, I should have paid more attention to the fact you were trying to use a card link to the PCI/PCIe bus. That is not gonna work in a virtual machine. You will have to boot Kali if you want to use that card. As explained in the wiki, in a virtual machine, the card MUST be USB.