Issue with TP-Link WN722N

[hedgyman]

I have a WN722N wireless card I'm using with my Raspberry Pi.

I have checked lsusb and have been provided the following output:

root@kali:~# lsusb
Bus 001 Device 004: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@kali:~#

when checking dmesg | tail

root@kali:~# dmesg | tail
[    9.649071] cfg80211:   (57240000 KHz - 59400000 KHz @ 2160000 KHz), (N/A, 2800 mBm)
[    9.716865] cfg80211:   (59400000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4400 mBm)
[    9.765117] cfg80211:   (63720000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 2800 mBm)
[   11.785591] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[   23.242290] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[   23.862778] NET: Registered protocol family 10
[   23.901652] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   24.837019] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[   26.006808] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   26.017629] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
root@kali:~#

checking iwconfig

root@kali:~# iwconfig
wlan0     IEEE 802.11bgn  ESSID:off/any
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off

lo        no wireless extensions.

mon0      IEEE 802.11bgn  Mode:Monitor  Tx-Power=20 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off

eth0      no wireless extensions.

root@kali:~#

ifconfig

root@kali:~# ifconfig
eth0      Link encap:Ethernet  HWaddr b8:27:eb:20:d5:23
          inet addr:192.168.0.123  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::ba27:ebff:fe20:d523/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2442 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2311 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:181542 (177.2 KiB)  TX bytes:332875 (325.0 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:140 errors:0 dropped:0 overruns:0 frame:0
          TX packets:140 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:13348 (13.0 KiB)  TX bytes:13348 (13.0 KiB)

mon0      Link encap:UNSPEC  HWaddr A0-F3-C1-21-EB-C0-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1354577 errors:0 dropped:1354558 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:91805639 (87.5 MiB)  TX bytes:0 (0.0 B)

wlan0     Link encap:Ethernet  HWaddr a0:f3:c1:21:eb:c0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

root@kali:~#

It appears as if the drivers for the ath9k have been loaded. It appears that the mac address is correct and showing up in monitor mode and for the wlan0. I how to

Not sure if people have a solution for this or if there is anything else that needs to be done to have success. My level of knowledge with Linux based OS' is very limited, but I'm trying to learn more each day.

I have been successful in setting a static IP for my eth0 and setting up ssh. Everything appears to work well through terminal services. I'm not sure if maybe I'm missing some components for the aircrack suite to test 100% if my card is functional. I would assume that I should be able to see AP's to associate with via terminal services to connect to one. (unless you have to manually set that in /etc/networking/interfaces)

Any help from a seasoned kali expert would be greatly appreciated. I've scoured numerous posts to see if anyone else has a similar problem and have only observed people having issues with VM ware setups.

[hedgyman]

It appears I have the wireless card working to monitor networks, just checking some more of the aircrack suite to see if I can get the rest of the software operational. Thank you to those that offered help.