Airgeddon non wifi card

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Airgeddon doesnt detect my wifi adapter #145

Airgeddon doesnt detect my wifi adapter #145

Comments

What is your airgeddon version?

What is your Linux O.S. and which version?

Which is the chipset of your wireless card?

Describe the issue and the steps to reproduce it

Hi, I recently installed Airgeddon as a way to make usage of Reaver and Bully easier, however whenever I try to select the interface to work with, all it shows is my ethernet adapter and not my wifi adapter. I tried looking for answers but it seems like I’m a special case as I cant find anyone else with the same issue. I do launch Airgeddon with the bash command as is said to do in the tutorial.

The text was updated successfully, but these errors were encountered:

Источник

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interface ‘enabled’ selected. Mode: (Non wifi card) #304

Interface ‘enabled’ selected. Mode: (Non wifi card) #304

Comments

What is your airgeddon version?

What is your Linux O.S. and which version?

Which is the chipset of your wireless card?

Describe the issue and the steps to reproduce it

First of all, I’m aware this chipset has issues, but with this latest driver I’ve got it to work perfectly with airmon, and this issue seems like a bug in the Airgeddon script rather than a driver / chipset issue. For some reason when I choose to set my adapter into monitor mode, Airgeddon will inform me that interface has changed its name (airmon doesn’t actually do this for me) and autoselect this new interface.

Monitor mode is enabled successfully, but what the script does afterwards, is select a non-existing interface called ‘enabled’. I figure this is probably a bug in how the output of iw / airmon commands is parsed?

The text was updated successfully, but these errors were encountered:

Источник

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Cards and Chipsets

Content & Features

Requirements

Getting Started

Project & Development

Acknowledgments & References

Clone this wiki locally

Rating legend: — Best — 😍 😄 ☺️ 😐 😞 — Worst —

Ordered alphabetically, some known compatible and fully working VIF capable chipsets/cards (Whitelist, recommended):

Users rating	Chipset	Card/s using it	Band/s	Interface	Link/Buy	Additional comments
😄	Atheros AR9271	Alfa AWUS036NHA / TP-Link TL-WN722N v1	2.4Ghz	USB	Link
😐	Intel L716NA02	Intel Wireless-AC 9560 card	2.4Ghz/5Ghz	PCIe	Link
☺️	MediaTek MT7610U	Alfa AWUS036ACHM / TP-Link Archer T2UH	2.4Ghz/5Ghz	USB	Link
😍	MediaTek MT7612U	Alfa AWUS036ACM	2.4Ghz/5Ghz	USB	Link	Not recommended for Virtual Machines if your host is Windows, only Native Linux or Linux VM at Linux host. Recommended kernel >= 5.3 . For Rpi 2/3 run this command to get it working echo «options mt76_usb disable_usb_sg=1» > /etc/modprobe.d/mt76_usb.conf
😐	Ralink RT2770	Alfa AWUS051NH	2.4Ghz/5Ghz	USB	Link
☺️	Ralink RT3070	TP-Link TL-WN7200ND / Alfa AWUS036NH	2.4Ghz	USB	Link
☺️	Ralink RT3572	Alfa AWUS052NHS / Linksys AE1000	2.4Ghz/5Ghz	USB	Link
😄	Ralink RT5370	Panda PAU04	2.4Ghz	USB	Link
😄	Ralink RT5372	D-Link DWA-137 / Panda PAU06	2.4Ghz	USB	Link
😍	Ralink RT5572	Panda PAU07 / Panda PAU09	2.4Ghz/5Ghz	USB	Link
😐	Realtek RTL8723BE	Realtek RTL8723BE card	2.4Ghz	PCIe	Link

Of course, there are more compatible and fully working chipsets, these are only some examples. Moreover, there are more cards and devices using the chipsets listed here as well. We list only some examples of cards to buy which are using fully working VIF (Multiple Virtual Interface) capable chipsets.

Ordered alphabetically, VIF capable chipsets but they are giving some problems and depending on driver and kernel can work. They require patched drivers (Greylist, not recommended):

• Atheros AR9170 present in TP-Link TL-WN822N v1 (2.4Ghz — USB)
• Realtek RTL8187 present in Alfa AWUS036H / Alfa AWUS036EW (2.4Ghz — USB)
• Realtek RTL8821CE present in Realtek RTL8821CE card (2.4Ghz/5Ghz — PCIe)
• Realtek RTL8822CE present in Realtek RTL8822CE card (2.4Ghz/5Ghz — PCIe)

Ordered alphabetically, chipsets with known problems or non-VIF capable chipsets/cards (Blacklist, not recommended at all):

• Intel Centrino Advanced-N 6205 present integrated in many laptops (2.4Ghz/5Ghz — PCIe)
• MediaTek MT7601U present in some unbranded cheap chinese dongles (2.4Ghz — USB)
• MediaTek MT7921 present integrated in many laptops (2.4Ghz/5Ghz — PCIe)
• Realtek RTL8188EU/S present in TP-Link TL-WN722N v2/v3 / Alfa AWUS036NHV (2.4Ghz — USB)
• Realtek RTL8811AU present in some unbranded cheap chinese dongles (2.4Ghz/5Ghz — USB)
• Realtek RTL8812AU present in Alfa AWUS036ACH (2.4Ghz/5Ghz — USB)
• Realtek RTL8812BU present in Comfast CF-913AC (2.4Ghz/5Ghz — USB)
• Realtek RTL8814AU present in TP-LINK Archer T9UH / Alfa AWUS1900 (2.4Ghz/5Ghz — USB)

These chipsets/cards are causing problems when working with airmon . As a consequence there are problems when working with airgeddon too. There are some reasons: airmon compatibility and available drivers. There are some closed issues discussing different problems while using them. We recommend to don’t use these cards.

Realtek fix

One community member worked hard in a solution for Realtek chipset based cards creating a plugin to fix the different behavior of these cards due the drivers. It was already released. Check Wiki Plugins Hall of Fame Section for more info. The plugin is valid for airgeddon=v10.0 but if you have airgeddon>=10.01 the plugin is not needed anymore because the fix was already included in the core code. Anyway, the plugin fixes the known problems for mode switching but there still are other problems not related to airgeddon that may consist in WPS failure, errors creating fake APs or non effective DoS during Evil Twin attacks due to lack of VIF capability. That problems are directly related to the hardware or the driver and airgeddon can’t do anything to deal with that.

Источник