Phillip Romero
asked on
Tp-link WN722N Kali linux nethunter
I need the drivers for my tp-link for it to work with Kali linux nethunter? Can you please point me in the right direction??
you might be lucky with a modern kernel:
At least in 4.12.12 there is this line, found using :
grep -ri TL-WN722N /usr/src/linux
/usr/src/linux/drivers/sta ging/rtl81 88eu/os_de p/usb_intf .c: {USB_DEVICE(0x2357, 0x010c)}, /* TP-Link TL-WN722N v2 */
So the rtl8188eu driver may be of help, usbid = 2357:010c it is still in the staging directory so it might need separate compilation...
The TODO file holds: (from july 3rd this year). But it depends on at least your device being a v2.
TODO:
- find and remove remaining code valid only for 5 HGz. Most of the obvious
ones have been removed, but things like channel > 14 still exist.
- find and remove any code for other chips that is left over
- convert any remaining unusual variable types
- find codes that can use %pM and %Nph formatting
- checkpatch.pl fixes - most of the remaining ones are lines too long. Many
of them will require refactoring
- merge Realtek's bugfixes and new features into the driver
- switch to use LIB80211
- switch to use MAC80211
- figure out what to do with this code in rtw_recv_indicatepkt():
rcu_read_lock();
rcu_dereference(padapter-> pnetdev->r x_handler_ data);
rcu_read_unlock();
Perhaps delete it, perhaps assign to some local variable.
Please send any patches to Greg Kroah-Hartman <gregkh@linuxfoundation.or g>,
and Larry Finger <Larry.Finger@lwfinger.net >.
At least in 4.12.12 there is this line, found using :
grep -ri TL-WN722N /usr/src/linux
/usr/src/linux/drivers/sta
So the rtl8188eu driver may be of help, usbid = 2357:010c it is still in the staging directory so it might need separate compilation...
The TODO file holds: (from july 3rd this year). But it depends on at least your device being a v2.
TODO:
- find and remove remaining code valid only for 5 HGz. Most of the obvious
ones have been removed, but things like channel > 14 still exist.
- find and remove any code for other chips that is left over
- convert any remaining unusual variable types
- find codes that can use %pM and %Nph formatting
- checkpatch.pl fixes - most of the remaining ones are lines too long. Many
of them will require refactoring
- merge Realtek's bugfixes and new features into the driver
- switch to use LIB80211
- switch to use MAC80211
- figure out what to do with this code in rtw_recv_indicatepkt():
rcu_read_lock();
rcu_dereference(padapter->
rcu_read_unlock();
Perhaps delete it, perhaps assign to some local variable.
Please send any patches to Greg Kroah-Hartman <gregkh@linuxfoundation.or
and Larry Finger <Larry.Finger@lwfinger.net
As noci suggested, working with a more recent Kernel will likely be required.
Also, you might find your setup easier if you just install Ubuntu latest (Artful, which runs Kernel 4.13) as Ubuntu will likely handle your hardware.
Then use the https://askubuntu.com/ques tions/7724 95/proper- installati on-of-kali -linux-too ls-in-ubun tu-16-04-l ts instructions to run the Kali package installer script.
Normally this approach works very well, with all hardware.
Also, you might find your setup easier if you just install Ubuntu latest (Artful, which runs Kernel 4.13) as Ubuntu will likely handle your hardware.
Then use the https://askubuntu.com/ques
Normally this approach works very well, with all hardware.
ASKER
Thank you for your feedback i really do appreciate it! I am going to try what you suggested,
and I do have the WN722N model. I am having another issue with my nethunter? I can not use my
Terminal it wont open at all? It just opens and shuts and man its starting to get on my nerves! If
you have any feedback on that also i would appreciate it?
and I do have the WN722N model. I am having another issue with my nethunter? I can not use my
Terminal it wont open at all? It just opens and shuts and man its starting to get on my nerves! If
you have any feedback on that also i would appreciate it?
Best to open a new question about your terminal issue.
And, also best to start with a recent Kernel, as other problems may mysteriously clear up with a recent Kernel.
And, also best to start with a recent Kernel, as other problems may mysteriously clear up with a recent Kernel.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
With the usbid it will be possible to find if some driver can support this. ( some equipment has similar USB-id's but different brands names or model numbers, als some model might have several USB-id if changes to the manufacturing process were made. So brand name & type are not the most exact thing to search on).
2nd: did you plug it in? and did a driver auto load? (lsmod from before & after plugging in)
Did the kernel see anything?: use dmesg to gather info on that.