PDA

View Full Version : When using airmon-ng, my wireless adapter is recognized but driver and chipset arent



icethrone5
2016-10-02, 02:46
I dual-boot with Mac OSX. I use the TP-Link WN822N wireless adapter. I am able to access the Internet. However, the fact that Kali doesn't recognize the chipset prevents it from making a "mon0" when trying to go into monitor mode.

# airmon-ng

PHY Interface Driver Chipset

null wlan0 ??????
phy0 wlan1 brcmfmac Broadcom Limited BCM43602 802.11ac Wireless LAN SoC (rev 01)

# lsusb
Bus 002 Device 002: ID 05ac:8406 Apple, Inc.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 05ac:0273 Apple, Inc. Internal Keyboard/Trackpad (ISO)
Bus 001 Device 003: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller
Bus 001 Device 002: ID 2357:0108
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

# ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 18 bytes 1058 (1.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 18 bytes 1058 (1.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.178 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::1aa6:f7ff:fe1a:dc86 prefixlen 64 scopeid 0x20<link>
ether 18:a6:f7:1a:dc:86 txqueuelen 1000 (Ethernet)
RX packets 7620 bytes 7235337 (6.9 MiB)
RX errors 0 dropped 5 overruns 0 frame 0
TX packets 5797 bytes 969669 (946.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether c4:b3:01:ce:84:ff txqueuelen 1000 (Ethernet)
RX packets 172 bytes 68546 (66.9 KiB)
RX errors 0 dropped 172 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Any reasons why Kali doesn't recognize my wireless adapter?

grid
2016-10-03, 11:48
That's odd. Have you tried doing running airmon-ng start wlan0 to see if you get an error? Is the card listed as being compatible with the aircrack-ng suite over at aircrack-ng.org?

Have you tried sniffing packets using Wireshark? Does that work?