jcptapar05
Posts: 1
Joined: Wed Oct 23, 2019 8:55 am

Re: (UPDATE) Drivers for TL-WN725N V2 - 3.6.11+ -> 4.xx.xx+

Wed Oct 23, 2019 9:04 am

Hi Everyone I have realtek 8188etv(I used 8188eu/4.19.79-v7.1273 driver) I followed the instructions but I can't enter to monitor mode? I tried sudo airmon-ng start wlan0 o ifconfig wlan0 mode monitor still the same mode(manage or auto). Please help me. I am using rpi 3b with 8188etv usb stick. How to enter to monitor mode? I installed the driver and after running airmon-ng it tells me operation not supported(-95)

bmichaelb
Posts: 3
Joined: Tue Jun 18, 2019 3:05 am

Re: (UPDATE) Drivers for TL-WN725N V2 - 3.6.11+ -> 4.xx.xx+

Sun Oct 27, 2019 1:41 am

MrEngman

I have the TL-WN725N v3, and bought it because it was on a list from Microsoft, supposedly guaranteed to work with WiFi Direct. I've even come across a video on Youtube, showing it working to connect to an Android phone, and I've come across threads saying it works as a p2p-device...but with a driver from 2014, no longer hosted on dropbox. It doesn't matter if I install using your script, or build from scratch, I can never get the '* P2P-device' listed under supported interfaces using 'iw list', and using a 'WiFi_Direct_User_Interface' P2P set up script from one of the threads I came across, it says,

Code: Select all

Interface doesn't accept private ioctl...
p2p_set (8BF0): Operation not permitted
Does something need to be enabled in the driver while compiling, or is my device just not capable of being a p2p-device?

Code: Select all

i@raspberrypi:~ $ iw list
Wiphy phy0
	max # scan SSIDs: 9
	max scan IEs length: 2304 bytes
	max # sched scan SSIDs: 0
	max # match sets: 0
	max # scan plans: 1
	max scan plan interval: -1
	max scan plan iterations: 0
	Retry short limit: 7
	Retry long limit: 4
	Coverage class: 0 (up to 0m)
	Supported Ciphers:
		* WEP40 (00-0f-ac:1)
		* WEP104 (00-0f-ac:5)
		* TKIP (00-0f-ac:2)
		* CCMP-128 (00-0f-ac:4)
	Available Antennas: TX 0 RX 0
	Supported interface modes:
		 * IBSS
		 * managed
		 * AP
		 * P2P-client
		 * P2P-GO
https://www.raspberrypi.org/forums/view ... hp?t=91891
https://docs.microsoft.com/en-us/window ... wifidirect
https://docs.microsoft.com/en-us/window ... compatlist
https://www.amazon.ca/gp/product/B008IFXQFU

IntrudersPi
Posts: 1
Joined: Fri Nov 01, 2019 10:46 am

Re: (UPDATE) Drivers for TL-WN725N V2 - 3.6.11+ -> 4.xx.xx+

Mon Nov 04, 2019 3:43 pm

Dears,

[EDIT] I've let the subject and bough a Ralink RT5370 - it work without any problem.


I come form this topic :
https://www.raspberrypi.org/forums/view ... p?t=220596

And followed that tutorial :
http://downloads.fars-robotics.net/

But I don't know how to do the last mile
I've put all the code below for debug purposes.

Code: Select all

pi@raspberrypi:~ $ sudo apt update
Get:1 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Fetched 15.0 kB in 1s (18.8 kB/s)                      
Reading package lists... Done
Building dependency tree       
Reading state information... Done
All packages are up to date.

pi@raspberrypi:~ $ sudo apt full-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.19.75-v7l+ #1270 SMP Tue Sep 24 18:51:41 BST 2019 armv7l GNU/Linux

pi@raspberrypi:~ $ lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter
Bus 001 Device 004: ID 03f0:134a HP, Inc Optical Mouse
Bus 001 Device 003: ID 03f0:0024 HP, Inc KU-0316 Keyboard
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
At this point TL-WN725N(EU) v3.0 is connected but not installed

Wireless interfaces check :

Code: Select all

pi@raspberrypi:~ $ iwconfig
wlan0     IEEE 802.11  ESSID:"WIFI_VISITORS"  
          Mode:Managed  Frequency:5.24 GHz  Access Point: 2C:3E:CF:60:C0:BF   
          Bit Rate=108 Mb/s   Tx-Power=31 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          Link Quality=42/70  Signal level=-68 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

eth0      no wireless extensions.

lo        no wireless extensions.

wlan1     unassociated  ESSID:""  Nickname:"<WIFI@REALTEK>"
          Mode:Auto  Frequency=2.412 GHz  Access Point: Not-Associated   
          Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr: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

Driver download :

Code: Select all

pi@raspberrypi:~ $ wget http://downloads.fars-robotics.net/wifi-drivers/8188eu-drivers/8188eu-4.19.75-v7l-1270.tar.gz
--2019-11-04 16:29:08--  http://downloads.fars-robotics.net/wifi-drivers/8188eu-drivers/8188eu-4.19.75-v7l-1270.tar.gz
Resolving downloads.fars-robotics.net (downloads.fars-robotics.net)... 82.68.133.179
Connecting to downloads.fars-robotics.net (downloads.fars-robotics.net)|82.68.133.179|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 681881 (666K) [application/x-gzip]
Saving to: ‘8188eu-4.19.75-v7l-1270.tar.gz’

8188eu-4.19.75-v7l-1270.tar.gz                              100%[=========================================================================================================================================>] 665.90K  44.3KB/s    in 15s     

2019-11-04 16:29:23 (44.4 KB/s) - ‘8188eu-4.19.75-v7l-1270.tar.gz’ saved [681881/681881]

pi@raspberrypi:~ $ tar -zxvf 8188eu-4.19.75-v7l-1270.tar.gz
8188eu.ko
8188eu.conf
install.sh
Driver install :

Code: Select all

pi@raspberrypi:~ $ sudo install -p -m 644 8188eu.ko /lib/modules/$(uname -r)/kernel/drivers/net/wireless
pi@raspberrypi:~ $ sudo insmod /lib/modules/$(uname -r)/kernel/drivers/net/wireless/8188eu.ko
pi@raspberrypi:~ $ sudo depmod -a
Wireless interfaces check :

Code: Select all

pi@raspberrypi:~ $ iwconfig
wlan0     IEEE 802.11  ESSID:"WIFI_VISITORS"  
          Mode:Managed  Frequency:5.24 GHz  Access Point: 2C:3E:CF:60:C0:BF   
          Bit Rate=135 Mb/s   Tx-Power=31 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          Link Quality=43/70  Signal level=-67 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:11  Invalid misc:0   Missed beacon:0

eth0      no wireless extensions.

lo        no wireless extensions.

wlan1     unassociated  ESSID:""  Nickname:"<WIFI@REALTEK>"
          Mode:Auto  Frequency=2.412 GHz  Access Point: Not-Associated   
          Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr: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

Last command played is a sudo reboot and then another interfaces check

Code: Select all

pi@raspberrypi:~ $ iwconfig
wlan0     unassociated  ESSID:""  Nickname:"<WIFI@REALTEK>"
          Mode:Auto  Frequency=2.412 GHz  Access Point: Not-Associated   
          Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr: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

eth0      no wireless extensions.

lo        no wireless extensions.

wlan1     IEEE 802.11  ESSID:"WIFI_VISITORS"  
          Mode:Managed  Frequency:5.24 GHz  Access Point: 2C:3E:CF:60:C0:BF   
          Bit Rate=150 Mb/s   Tx-Power=31 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          Link Quality=46/70  Signal level=-64 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
Now, can someone be kind enough and tell me how to activate my wlan0 in a monitor mode ?
I'm stuck at this step for one week :cry:

Thanks in advance

Doub
Posts: 26
Joined: Fri Apr 07, 2017 9:48 pm

Re: (UPDATE) Drivers for TL-WN725N V2 - 3.6.11+ -> 4.xx.xx+

Mon Nov 25, 2019 2:40 am

The install script linked in the top post doesn't seem to support the Pi compute modules. Is that on purpose?

I have a CM3+ and a TP-Link RTL8188EUS-based Wifi dongle I'd like to use together. I had to add the following section to get the Pi detected:

Code: Select all

# check for Pi CM3+
    elif cat Pirevno | grep -i 'a02100' ; then
        echo "You have a Pi CM3+ v1.0"
        Pi=2
I've only run the (modified) script in check mode so far, as I have the dongle working in STA/Managed mode with default Raspbian drivers, and I don't want to break that.

But I'd like to enable mixed mode STA+AP, and I think the default driver won't let me do that. Would the driver installed by this script be capable of running as a client and access point at the same time?

MrEngman
Posts: 3870
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK

Re: (UPDATE) Drivers for TL-WN725N V2 - 3.6.11+ -> 4.xx.xx+

Fri Nov 29, 2019 11:21 am

Doub wrote:
Mon Nov 25, 2019 2:40 am
The install script linked in the top post doesn't seem to support the Pi compute modules. Is that on purpose?
No. I just don't have any CM modules. However, I will update the script to handle CM's.
I have a CM3+ and a TP-Link RTL8188EUS-based Wifi dongle I'd like to use together. I had to add the following section to get the Pi detected:

Code: Select all

# check for Pi CM3+
    elif cat Pirevno | grep -i 'a02100' ; then
        echo "You have a Pi CM3+ v1.0"
        Pi=2
I've only run the (modified) script in check mode so far, as I have the dongle working in STA/Managed mode with default Raspbian drivers, and I don't want to break that.

But I'd like to enable mixed mode STA+AP, and I think the default driver won't let me do that. Would the driver installed by this script be capable of running as a client and access point at the same time?
I don't know whether it will work as client and AP at the same time but doubt it will.


MrEngman
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra

Please post ALL technical questions on the forum. Please Do Not send private messages.

Return to “Troubleshooting”