-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
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
Cannot start hostapd #588
Comments
Renaming of the interface is intentional and has nothing to do with the failure of hostapd. It clearly says cant connect to kernel driver. So it's something else |
You don't have to manually rename the interface. When airgeddon uses airmon-ng to start monitor mode, the interface gets renamed to wlanXmon and while doing evil twin attack, additional vif is created with the name monX which is intentional.. |
It seems I'm misunderstanding the problem. Any suggestions for debugging the problem? let me know if you need additional information |
Not sure if your chipset is supported. Could be it or the driver.. join the discord server and others might be able to help you out with this.. |
okay! I've joined the discord |
What is your airgeddon version?
11.22
What is your Linux O.S. and which version?
Arch linux 6.8.9
Is your O.S. running in native mode or is a virtualized system? in that case, VMware? VirtualBox? Other?
Native mode
Which is the chipset of your wireless card?
Qualcomm Atheros AR9285
Describe the issue and the steps to reproduce it
The interface name somehow renamed when putting the interface into monitor mode and it cause the temporary hostapd configuration become invalid
sometimes it's named
wlan0mon
, and sometimesmon0
:How to prevent airgeddon from renaming network interface?
The text was updated successfully, but these errors were encountered: