-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Compatibility
v1s1t0r edited this page Jul 7, 2019
·
98 revisions
This page lists all Linux distributions compatible with airgeddon. It's an alphabetically sorted and up-to-date list.
tux and v1s1t0r used to play together since they were little, so they teamed up and created the tool called airgeddon
It is developed on Linux and designed for Linux 👽💚🐧
It can run on any Linux distribution that passes the tools validations. Some of them have already been tested and listed here.
- Arch 4.6.2-1 to 5.0.2-arch1-1-ARCH
- Backbox 4.5.1 to 5.x
- BlackArch 2016.01.10 to 2018.06.01
- CentOS 6 and 7
- Cyborg Hawk 1.1
- Debian 7 (Wheezy) to 9 (Stretch)
- Fedora 24 to 28
- Gentoo 20160514 to 20180206
- Kali 2.0, 2016.1 to 2019.x and arm versions (Raspberry Pi)
- Mint 18.x (Serena to Sylvia)
- OpenMandriva LX3
- OpenSUSE Leap 42.1 to 42.3
- Parrot Security 2.2.1 or higher (3.x, 4.x) and arm versions (Raspberry Pi)
- Raspbian 7 (Wheezy) to 9 (Stretch) (Raspberry Pi)
- Red Hat 7 (Maipo)
- Ubuntu/Xubuntu 15.10 to 18.04
- Wifislax 4.11.1 to 64-2.0
If you wish to run airgeddon in any different Operating System, you can use a Docker container.
- Any Linux distribution run under Windows subsystem is NOT supported.
- In
airgeddon<=8.10
, onlyairmon
compatible wireless cards are supported. If your card is unable to change its mode by performing anairmon
command out ofairgeddon
, it won't work. Fromairgeddon>=8.11
any card can be used if the monitor mode is supported. - In order to work with Wayland graphic system (instead on using X window system), you must add permissions to root user in this way:
~$ xhost si:localuser:root
. Doing that, root user (or usingairgeddon
as sudo) is able to detect the screen resolution. - For some Linux distributions like Ubuntu or Debian, it is highly recommended to modify grub in order to let the system to name wireless interface cards using classic name style (wlan0, wlan1, etc). If you see your wireless card named as wlx00c0ca9208dc or similar, you should modify your
/etc/default/grub
file in order to add thisnet.ifnames=0 biosdevname=0
to yourGRUB_CMDLINE_LINUX
line. For example:GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"
orGRUB_CMDLINE_LINUX="find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US net.ifnames=0 biosdevname=0"
. Just addnet.ifnames=0 biosdevname=0
to your existing options. After modifying the file, executegrub-update
and then reboot. After that, your wireless interface cards will be named again as always. If this change is not done, maybe you could experience uncontrolled errors.
Content & Features
Requirements
- Requirements
- Compatibility
- Essential Tools
- Optional Tools
- Update Tools
- Internal Tools
- Known Incompatibilities
Getting Started
Learning
Project & Development
- Plugins system
- Supported Languages
- Contributing & Code of Conduct
- Merchandising Online Shop
- Changelog
- Disclaimer & License
- Contact
Acknowledgments & References