Tp link v3

Briefly describe your issue below:

Hello guys I’m new to the linux world . A friend of mine gave me TP-Link TL-WN722N v3 for free. I installed it and it works perfectly on my parrot system in virtual box(browsing and stuff). I was wondering if I can change its mode from managed to monitor. I’ve done a lot of research both in google and in this forum and I have come to the conclusion that i cant. Although I do feel the need to ask you because maybe there is something that I can’t figure out.
If you can be as analytical as you can for two reasons:

  1. I want to learn from you
  2. As I said before I am new to the linux world.
    Thank you for your time.
    Sorry if this is a repost and I didn’t notice.

What version of Parrot are you running? (include version, edition, and architecture)
4.18.0.-parrot8 amd64 , Security edition

Configured to multiboot with other systems? (yes / no)
No

If there are any error messages or relevant logs, post them below:
After ifconfig wlan0 down
iwconfig wlan0 mode monitor
Error for wireless request ‘‘Set Mode’’ (8B06) :
Set failed on device wlan0 ; invalid arguement.

Have you tried the BETA drivers https://www.tp-link.com/ae/download/TL-WN722N_V3.html#Driver

It says it supports monitor mode in Ubuntu. Whether or not you can get it working in Parrot, i dont know.

Yes I already tried them. I will give it another shot tomorrow though… Thank you for your time !

sudo airmon-ng start wlan0?

I think only V1 uses the monitor mode chipset, but that being said I know of a few devices not working properly on this kernel so it could really be a whoknows

I see.
One thing that troubles me is that although the device is working perfect for wifi and stuff , is that no matter what the name of this device is not shown anywhere.
I tried both iwconfig and lsusb . The device is visible to both , but it’s name is not. It is actually blank.

I already tried airmon-ng killing all processes that may cause problems.

you may have missed the modprobe command after make install command, you can get more output by including the -v or -vv -vvv commands at the end of lsusb et cetera. Try those (the module name is repeated throughout the make and make install outputs) and also explore iw dev wlan# and post your results again and we can take another look

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

The first one is the wifi adapter.

lsusb -v

Bus 001 Device 002: ID 2357:010c
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x2357
idProduct 0x010c
bcdDevice 0.00
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 4.18
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12

Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x80ee VirtualBox
idProduct 0x0021 USB Tablet
bcdDevice 1.00
iManufacturer 1
iProduct 3
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 85
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10

Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0001 1.1 root hub
bcdDevice 4.18
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 255

Again , thank you for ur time.

Have you installed any udev dev packages and/or configured your user account permissions (not rooted to hell)?

Nope I didn’t . To be honest you lost me.
Should I install them ?
And if yes why ?
If u could explain me the reason that would be awesome.

The debian documentation will explain it thousands of times better than I will (and probably be shorter) but honestly it’s probably more likely the driver/module missing. You have to manually build and install the driver you need that the device uses before you can use the device in linux distros

1 Like

I see. It makes sense .
I will try ur solution and see if this will solve this problem.
Again , thank you very much for your time.

If you didnt install the driver for the wifi adapter you can be almost certain that is the issue. Some devices are plug and play like the pau09 but others take some configuration

I install the driver . The wifi adapter is working perfectly , but it wont go to monitor mode. Maybe its because its v3.

Probably, it’s a bitch sometimes to have to double and triple check if its supported and to what extent especially with products that have drastically different versions

Indeed it is. But its ok I guess. Thank you again !

1 Like

Hi, I now this is old topic, but I’m facing similar problems. My VMWare won’t even recognize that I have plugged in the adapter and I’m unable to install drivers I gate an error when I sudo make.

please use virtualbox
vmware is not officially supported as well