Open roque-canales opened 6 years ago
I'll look into that some time (but it can take a few months, sorry).
Did some googling.
The AWUS036ACH really looks promising, finally a card with high power amps both on 2.4 and 5Ghz and two transmit/receive chains. It uses the same 2.4Ghz amps as the 036NHA, so should in theory give the same output power. The RTL8812AU chipset also supports STBC and LDPC which should increase range and robustness of the link in theory.
I did some search about monitor mode/injection and drivers, there are like 10 or more different forks of various Realtek driver version available on Github, the most promising driver seems to be the rtl8812au from the aicrack-ng guys (https://github.com/aircrack-ng/rtl8812au). This driver also supports the rtl8814au used on the Alfa AC1900 which could be a good RX card (3 transmit/receive chains plus LNA in the frontends).
However, to support the new Raspberry Pi 3B+ in the future, we'll have to wait until the Raspberry Kernel and firmware has stabilized. From what I read on the Raspberry forum, they also plan to transition to kernel 4.14 in the near future so I think it doesn't really make much sense putting work in getting this driver to work with kernel 4.9.
If somebody wants to have a try at this themselseves in the meantime, quick "howto":
Hello Rodizio,
Thank you so much for this feedback.
Could be possible that you compile actual version of EZ WBC with theses modifications for thoses who want to test rtl8812AU boards ?
For my part I can do lot tests, I already have two boards AWUS036ACH (power output, range on some channels, range with different baudrate setings) when you release out quite firmware and share it whith the community.
I don't have any realtek 8812 cards to test with, so doesn't make much sense. I'll give it a try when I got some.
Rodizio,
give me your adress and I send you two boards
my email: kuspower @ live . fr
Dear Rodizio,
Regarding your comment about rpi3b+ - would it be possible to skip right to driver compilation & testing on rpi3b+ez-wbc1.6? Is rpi3b+ somehow necessary?
Hello Rodizio,
Coudl you please send upgraded ezwbc img with kernel compatible with https://github.com/astsam/rtl8812au ?
I made many attemps but after upgrade for be able to use make, ezwbc not start.
@rodizio1 Raspbian has now been moved up to kernel 4.14, I have ordered two of the 036NHA dongles and should hopefully get them by the end of next week, then I will take a shot at getting it up and running using your recommendations and can also help testing then.
If any one else has already made progress with Kernel 4.14 I would appreciate the head start.
Thanks!
Hey @rodizio1, I managed to compile and install the driver for AWUS036ACH as well as the wifibraodcast software on RPI 3 B+. The problem now is, that I don't get it to listen to my RPI 3 B (no plus) with my AWUS036NHA.
I followed the instructions here to make the prepare the kernel for the build: https://raspberrypi.stackexchange.com/questions/50240/missing-build-file-when-building-for-rtl8812au-driver
Then I cloned the driver fork from aircrack-ng https://github.com/aircrack-ng/rtl8812au and i changed the following lines in the makefile of the driver:
CONFIG_PLATFORM_I386_PC = n
CONFIG_PLATFORM_ARM_RPI = y
dkms install didn't work so I chose the normal way via make and make install.
Then I continued with some recommendations from another issue here: https://github.com/bortek/EZ-WifiBroadcast/issues/108
i set up the monitor mode and listened to channel 13
sudo service network-manager stop && \
sudo ifconfig wlan1 down && \
sudo iw dev wlan1 set monitor otherbss fcsfail && \
sudo ifconfig wlan1 up && \
sudo iwconfig wlan1 channel 13
so far so good. When I start to to listen now, I don't get anything
sudo ./sharedmem_init_rx
sudo ./rx -b 8 -r 4 -f 1024 wlan1
So my guess was, that either the Tx is not working or not sending on channel 13 (although I do see that I get packets on the Rx with ifconfig).
I hope this helps somebody and I'd appreciate some help on how to check if the Tx is working correctly ... when I plug in a screen it always starts as Rx.
thanks in advance!
Hello @wstoettinger Could you please share on wetransfer your ezwbc image for we test the AWUS036ACH ?
like the we can share our result with all?
Thank you so much!
I think this needs to be a priority, compatible wifi cards are drying up quickly, with only the ALFA AWUS036NHA and AWUS051NH still readily available.
ubiquity wifistation cards are not made any more AWUS052NH are not made any more TPLink TL-WN722N V1 are not made any more TP-Link TL-WDN3200 are not made any more
@roque-canales I'm sorry, I currently don't have the time to work on that. However I think that my setup is easy to reproduce with the detailed instructions I gave.
Let me know, if you run into problems!
Hello, I want to test the AWUS036ACH for rx (Pi 2 B) and the AWUS036AC for tx (Pi zero 1.3). I've first checked that the 2 cards were working on my laptop wiyh Ubuntu 18.04, and they do very well after having installed the rtl8812au-dkms driver from ubuntu. Then I've tried them with the Pis and ezwbc 1.6 rc6, without modifying anything. On the rx side (Pi 2) I think the cards are recognized and initialized, because the blue led are blinking after a few seconds. For now I can't log on the Pi with ssh, because I'm waiting for a swith. But on the tx side both cards didn't work : no blue led. I think it's a problem with the micro usb port of the Pi zero, and with its output power. I've tried to power the AWUS036AC directly, but no success. For the next step I will try to solder the usb D+ and D- directly on the Pi zero. I've also tested a small wifi "Edup" dongle on the TX, and could receive a very bad image on the rx. I thnk it's normal because the dongle has no antenna and very low power.
So this confirm that all seems to work for the rx, and the problem is the connection of the AWUS036AC with the Pi zero.
I will give you later more news.
ps : it's my first experiences with ezwbc !!
Some more infos here (in russion, can be translated with google translate though):
http://forum.rcdesign.ru/f90/thread515083-7.html#post7421810 http://forum.rcdesign.ru/f90/thread515083-7.html#post7426801 http://forum.rcdesign.ru/f90/thread515083-9.html#post7446277
To go further in my tests, I've try to buy a compatible 5 Ghz card for the TX. The last available one is (was) the TP-Link TL-WDN3200 (RT5572 chipset). I've ordered one, but I received a TP-Link Archer T4U (8812AU) instead of it, because the TL-WDN3200 isn't anymore available ! So today, no more 5 Ghz wifi cards usable with EZ-WBC are any more available.
Today almost all dual band cards have a 8812AU (or 8814AU) chipset. I've tried the AWUS036AC and AWUS036ACH, and I can confirm that they are working "out of the box" as RX with 1.6RC6, because you had added 8812AU support in 1.6RC1 ("Support for RTL8812AU cards added (only RX, not tested, for experimenting)"). That's already a good thing !
I have now an AWUS1900, and will soon try to install the aircrack-ng 8814AU driver on my RX Pi.
But on the TX side, I don't know what to do to have 8812AU support ...
My "dream" is to have a working 5 Ghz EZ-WBC system working with, as TX a Pi0 with a AWUS036ACH (or AWUS036AC because it's smaller), and as RX a Pi2B with an AWUS1900.
I hope I will see it in the near future, and do what I can to help ...
Does anybody found solution?
36ACH should be arriving tomorrow. I don't know anything about coding and the primary reason I got this was to have 5G hotspot for the various Android apps.
I have tried a couple non wfb 5G dongles for the hotspot on the RX side and they are not recognized.
My Hope Is but that I can use the 5G Mac address for the hotspot to receive video wirelessly and then also have 3 rx atheros cards running 2.3/2.4.
I kind of assumed that everything was working with the 5G side but after reading this it doesn't sound like that's the case?
This was a $50 Wi-Fi card and my thinking was that it could be used in the future on the TX side in the air for 2. 4/5. 8 diversity.
Any comments or feedback would be appreciated.
@htcohio, hello, did you reach to upgrade EZWBC for use 8812AU ?
@rodizio1 Hi, could you explain us my the awus036ach is working on the rx side and not on the tx side. What should be added for making it work on the tx ? Please give us some informations and point us into the good direction.
Thanks for your help.
I can now confirm that the image of this post (http://forum.rcdesign.ru/f90/thread515083-9.html#post7446277) is working very well with 8812au and 8814au. Awus036ac, awus036ach and awus1900 are all working as TX and RX, on Pi zero, Pi2b/3b (I've no Pi3b+)
I am trying to clean up the clutter @Yes21 , do you know if this is still relevant or can we close it ?
I will soon close it when I will be sure that rtl8812/14 are really supported ...
When I was testing this, there was packetloss with that driver/card on the RX, did anybody actually test for packetloss?
This can be tested quite easily:
With the v5.2.20 branch of the driver, I always have ZERO packetloss.
Thanks for claryifing. Great that the newer driver version seems to have fixed it.
And with this driver, I can make work an AWUS1900 on the groundPi and a AWUS036ACH on the airPi ...
Want to give this image another try. Which stages do I have to repeat from the last one I build several days ago? All stages or just certain ones?
Von meinem iPhone gesendet
Am 04.11.2018 um 13:26 schrieb Yes21 notifications@github.com:
And with this friver, I can make work an AWUS1900 on the groundPi and a AWUS036ACH on the airPi ...
โ You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
Due to the many modifications in the kernel stage it would probably be better to redo everything. Actually, a clean git clone in a new folder would probably be advisable. Once the kernel issues have been fixed you'll probably not touch step 2 for a long while.
Thank you very much... I will exactly do so. My house is rather getting cold - this is a welcome excuse for letting the CPU crunch some numbers this afternoon. ๐ - will report back
Von meinem iPhone gesendet
Am 04.11.2018 um 13:31 schrieb Jelle Tigchelaar notifications@github.com:
Due to the many modifications in the kernel stage it would probably be better to redo everything. Actually, a clean git clone in a new folder would probably be advisable. Once the kernel issues have been fixed you'll probably not touch step 2 for a long while.
โ You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
Please hold one moment, i'm changing some thing around
Okay, if you get the latest it at least starts the kernel build again. No guarantees beyond that ๐
Alright! Thanks for the warring... Restarting ;-)
Von meinem iPhone gesendet
Am 04.11.2018 um 14:16 schrieb Jelle Tigchelaar notifications@github.com:
Okay, if you get the latest it at least starts the kernel build again. No guarantees beyond that ๐
โ You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
hello after check AWUS036ACH is only 21dbm, twpower_ralink no change anythingโฆ
How to set up the tx power on this board ?
sudo iw yourinterface set txpower fixed 4000
-> 40 db
thank you, is your interface the mac adress?
Yes, without ":" Example "00c0ca9679c8"
Hello,
I can confirm that max power is arround 21-22dbm @ datarate 2. I measured the ouput power and max is 140mw.
So I expect that 8814AU is more sensible to allow 1km range.
With AWUS052NH we get 800mw.
awus052nh no exist anymore,
AWUS036ACH is now injection compatible, there's is any body that can help us for make that this 5ghz board work correctly with ezw?