#Jetson
ответ Nvidia
Here are some suggestions for your questions.
Status of RTL8812AU on Orin Nano, kernel 5.15
JetPack 6.2 / Jetson Linux 36.4.x for Orin Nano ships kernel 5.15 with Ubuntu 22.04. NVIDIA Developer Jetson Linux does not include an 8812au driver; people have always had to install one from GitHub on Jetson boards. That was already the case on the original Nano where users installed the Realtek driver or the aircrack-ng fork manually. NVIDIA Developer Forums
So on Orin Nano you are in the same situation:
You are using an out-of-tree Realtek driver (aircrack-ng’s rtl8812au). GitHub
This driver is maintained primarily for x86 desktop distros and Raspberry Pi. Kernel 5.15 support exists, but there are several GitHub issues about monitor mode or injection being flaky or broken on some setups, even when iwand airmon-ng claim that monitor mode is enabled. GitHub
There are Jetson users who managed to build and load 88xxAU drivers on Orin for earlier kernels (5.10, sometimes with RT patches) using DKMS, but then hit load or runtime problems as soon as the kernel changed. NVIDIA Developer Forums
That matches exactly what you see:
Interface exists
iw / airmon-ng say “monitor”
Injection tools report “success”
Sniffer on the ground side sees nothing
That is almost always a driver issue, not an NVIDIA/Jetson hardware problem. The USB bus and SoC happily move data; the driver simply does not send the frames on air in the way your tool expects (or it mangles radiotap flags, retries, or channel settings).
If you want to keep trying with RTL8812AU on Orin, the usual “best effort” path is:
Use a fork that explicitly supports monitor/injection and DKMS and is kept somewhat up to date with newer kernels, such as rodizio1/rtl8812au-2 (which is basically an aircrack-ng based fork with documented monitor mode setup). GitHub
Make sure you build against the exact Jetson kernel headers from your Jetson Linux release (the “kernel customization” docs and release notes describe how to get the matching source tree). NVIDIA Developer
Double-check the platform settings in the Makefile. Some forks have Nano-specific options for 32-bit ARM, but on Orin you want a generic 64-bit ARM platform, not PC or RPi.
Verify monitor/injection with two independent devices: one Jetson with your adapter, and a second Linux PC or AP acting as a sniffer to see whether raw frames actually appear.
This may still not give you something you can call production-quality. It is inherently “use at your own risk”.
Can Jetson be the AIR side for OpenHD or WFB-NG?
From the point of view of NVIDIA’s software, a Jetson is just a Linux machine with the standard networking stack. OpenHD / WFB-NG mainly require:
A driver that supports monitor mode + raw frame injection at the bitrate and channel you need.
Enough CPU / GPU to encode video and push packets.
Orin Nano is easily powerful enough. The question is purely your Wi-Fi driver. There is nothing in Jetson Linux that forbids this use case, but it is not a “supported configuration” from NVIDIA, because they do not ship or validate the out-of-tree Realtek drivers that OpenHD traditionally relies on.
In other words: yes, using Jetson as AIR is possible in principle, but success depends entirely on the specific Wi-Fi chipset + driver combo that you choose.
Chipset recommendations and “official” support
NVIDIA does not publish an “official monitor/injection adapter list” for Jetson. Their support matrix is about normal STA/AP networking. There is no special testing for penetration-testing or FPV broadcast workflows.
If you want a combination that is as close as possible to “just works” on Jetson, the usual recommendations from the Linux world still apply:
Prefer adapters that use in-kernel mac80211 drivers (no external DKMS). On Linux in general, chipsets like Atheros AR9271 / ath9k_htc and various Mediatek mt76-based devices are widely used exactly because their mainline drivers handle monitor and injection well.
When you pick such a chipset, Jetson sees it like any other ARM64 Linux machine.
