Does this driver support virtual interface as most of the wifi tools need this feature to work properly?
no i does not support virtual interface, an you are correct. this impact usage of airmon-ng.
the code is there, but isn't fixed or maintained. it should be a priority so i leave this report open for others to see.
Here is provided a commit that almost works, it just needs to be finished up.
@kimocoder Yeah it's there but it doesn't work yet properly.
@kimocoder and how is work going on this? any chances to make it work soon?
will try some fixes soon, it's not top priority at this point, as it works fine with setting it manually.
@kimocoder how it can be done manually? It would be nice if it will work with fluxion :D
@usuarionuevor which drivers will work with airgeddon? IT cannot switch to monitor mode when chosen on script, need to set IT manually and IT fails in evil twin attack. I'm using dkms drivers
Found some even more interesting stuff for adding "virtual interface" support.
These 2 commits were made to a v4.3.21 astsam fork. Don't have the time to test it (or port it for testing) at this time, but here they are.
https://github.com/cristi28/rtl8812au/commit/b4f97ee5bd323006b80a0a93a33052e175341c32
https://github.com/cristi28/rtl8812au/commit/7200f38cb27f83ee9a2b19985427244108387799
@vanrzuf airgeddon has a new release. Now it works with airmon non compatible cards, even with the evil twin attack.
Next release of the aircrack-ng (with airmon-ng) will have support for this driver.
Hi, I'm one of the authors of airgeddon. Yeah @jarilaos is right. From v8.11 now airgeddon can handle any card compatible with monitor mode even if it is not compatible to airmon. Happy hacking! 馃樃
It has been added anyway, the commit to aircrack-ng may be seen at https://github.com/aircrack-ng/aircrack-ng/commit/3cc9de5e7cbe6565c7e1fe12ebbcf2c6f7413c8d and at https://github.com/aircrack-ng/aircrack-ng/commit/b30a962ec20dc16501359c0aca21eda723e3f7ac
Great, any improvement or any new compatibility on aircrack is welcome! thanks for your work.
@kimocoder Have you read this https://wireless.wiki.kernel.org/en/users/documentation/iw#adding_interfaces_with_iw
I suppose this command is not working iw phy phy0 interface add moni0 type monitor.
ooooh no that won't work.. that's just to easy.
this is the output from the command:
ethtool failed...
Only mac80211 devices on kernel 2.6.33 or higher are officially supported by airmon-ng.
@kimocoder I suppose because it is not implemented in driver, as well as monitor flags, that is why this issue #240.
@kimocoder I find this in google https://www.wireshark.org/lists/wireshark-dev/201601/msg00066.html
"So it [the otherbss and control flag] will be set by default in most cases. However I can see that some other drivers do their own management in this area. So it is probably a good idea to set the flags anyway. Having a UI to manage the flags would be even better."
This is only going to happen if we move from nl80211/cfg80211 to mac80211. closing the issue.
Most helpful comment
Next release of the aircrack-ng (with airmon-ng) will have support for this driver.