No linux drivers available for TP Link TL-WN722N V 2.0

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

No linux drivers available for TP Link TL-WN722N V 2.0

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
23 Reply
Help me
2017-06-29 22:17:22
Please help me! I Cant install linux drivers for TP Link TL-WN722N V 2.0, Linux 2.0 kernel 4.9.0

mfruba wrote

Had same issue, and I have solved it. I have ported official driver which was prepared for Linux Kernel 2.6.18~3.19.3 to work on 4.9 kernel (tested on 4.9.0-kali3-amd64).


Below you can find source:
https://github.com/mfruba/kernel/tree/master/drivers/TL-WN722N_v2.0-Ralink
  0  
  0  
#12
Options
Re:No linux drivers available for TP Link TL-WN722N V 2.0
2017-06-29 22:31:43
mfruba please help me
uname -a
Linux kali 4.9.0-kali3-686-pae #1 SMP Debian 4.9.18-1kali1 (2017-04-04) i686 GNU/Linux
  0  
  0  
#13
Options
Re:No linux drivers available for TP Link TL-WN722N V 2.0
2017-07-01 03:19:08
mfruba's solution worked for me and my TP-Link TL-WN722N v2 (Realtek) in Kali. Here's how I used it:

I've downloaded all the code in a zip file from mfruba's repository: https://github.com/mfruba/kernel/archive/master.zip

> unzip ~\master.zip

> cd ~/master/drivers/TL-WN722N_v2.0-Ralink/rtl8188EUS_linux_v4.3.0.8_13968.20150417


> make

From now on, continue as root:

# make install

# insmod /lib/modules/4.9.0-kali4-amd64/kernel/drivers/net/wireless/8188eu.ko


It gave some errors. Using dmesg I saw:
........
Unknown symbol cfg80211_scan_done
Unknown symbol ieee80211_frequency_to_channel


This means that the modules lib80211 and cfg80211 were not loaded into the kernel. So, load these with:


# modprobe lib80211
# modprobe cfg80211


Now, insert the module:


# insmod /lib/modules/4.9.0-kali4-amd64/kernel/drivers/net/wireless/8188eu.ko


At this point, iwconfig returns:


wlan0 unassociated Nickname:""
Mode:Managed Frequency=2.412 GHz Access Point: Not-Associated
Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


# iwconfig wlan0 mode Monitor

# airmon-ng start wlan0

# airodump-ng wlan0
  0  
  0  
#14
Options
Re:No linux drivers available for TP Link TL-WN722N V 2.0
2017-07-01 17:03:03
Thank you! But after install, TP-Link TL-WN722N can use Fluxion, air crack...(moniter mode)?
  0  
  0  
#15
Options
Re:No linux drivers available for TP Link TL-WN722N V 2.0
2017-07-02 14:12:54
Does it works for anyone
  0  
  0  
#16
Options
Re:No linux drivers available for TP Link TL-WN722N V 2.0
2017-07-05 08:47:22
You don't need to compile the driver for Kali. There's a rtl8188eu driver (in staging) that is ready for use with the TP Link WN722N. The device just doesn't register with the driver. The fix is simple. Install the 8188eu driver package (firmware-realtek) and then do the following in terminal:

[CODE]

cd /sys/bus/usb/drivers/r8188eu
echo 2357 010c > new_id

[/CODE]

iwconfig to see if adapter shows up.

If you have the recurring wlan0: link is not ready dmesg issue, add the following lines to /etc/NetworkManager/NetworkManager.conf:

[CODE]

[device]
wifi.scan-rand-mac-address=no

[/CODE]

This is because realtek makes really shitty drivers that don't behave very well in linux

I've got the tp link wn722n working in kali, on both amd64 and armel (raspi), and monitor/injection works really well.

good luck
  0  
  0  
#17
Options
Re:No linux drivers available for TP Link TL-WN722N V 2.0
2017-07-08 17:07:50

throwaway_9999 wrote

You don't need to compile the driver for Kali. There's a rtl8188eu driver (in staging) that is ready for use with the TP Link WN722N. The device just doesn't register with the driver. The fix is simple. Install the 8188eu driver package (firmware-realtek) and then do the following in terminal:

[CODE]

cd /sys/bus/usb/drivers/r8188eu
echo 2357 010c > new_id

[/CODE]

iwconfig to see if adapter shows up.

If you have the recurring wlan0: link is not ready dmesg issue, add the following lines to /etc/NetworkManager/NetworkManager.conf:

[CODE]

[device]
wifi.scan-rand-mac-address=no

[/CODE]

This is because realtek makes really shitty drivers that don't behave very well in linux

I've got the tp link wn722n working in kali, on both amd64 and armel (raspi), and monitor/injection works really well.

good luck

Thank you! I want to use Wifiphisher, "Please ensure that at least two wireless adapters are connected to the device and they are compatible (drivers should support netlink). At least one must support Master (AP) mode and another must support Monitor mode."
TP 722N can be used wifiphisher?
  0  
  0  
#18
Options
Re:No linux drivers available for TP Link TL-WN722N V 2.0
2017-07-24 09:51:57
Its worked for me.but I don't know whether it supports aircrack or monitor mode
  0  
  0  
#19
Options
Re:No linux drivers available for TP Link TL-WN722N V 2.0
2017-07-24 09:54:46
It worked for me I don't know whether it supports aircrack or monitor mode
  0  
  0  
#20
Options
file not found
2017-08-15 16:43:47
Hello,

I tried following your tutorial, but seems to fail.

I'm using the latest Kali version (through VirtualBox, MACOS Sierra).

I successfully installed the firmware-realtek package, no issue here.

1/ lsusb does not identify the chipset

root@kali:~# lsusb
Bus 001 Device 002: ID 2357:010c
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


device is there; but there is no identification

2/ package firmware-realtek is there, but there is no /sys/bus/usb/drivers/r8188eu directory to apply the "echo" command you mentioned.

firmware-realtek/kali-rolling,now 20170404-0kali1 all [installed]


root@kali:~# ls /sys/bus/usb/drivers/
hub usb usbfs usbhid

an iwconfig does not see the usb adapter for now

Any idea of what step I missed ? thanks,
  0  
  0  
#21
Options