Skip to content
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

Closed
RealYukiSan opened this issue May 23, 2024 · 6 comments
Closed

Cannot start hostapd #588

RealYukiSan opened this issue May 23, 2024 · 6 comments

Comments

@RealYukiSan
Copy link

RealYukiSan commented May 23, 2024

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

Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * monitor
                 * mesh point
                 * P2P-client
                 * P2P-GO
                 * outside context of a BSS

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 sometimes mon0:

05-23-2024_000

How to prevent airgeddon from renaming network interface?

@RealYukiSan
Copy link
Author

I try to force rename the interface while running the airgeddon:

ip link set dev wlan0mon down
ip link set dev wlan0mon name wlan0
ip link set dev wlan0 up

but it makes the airgeddon not work properly:
05-23-2024_001

@xpz3
Copy link
Collaborator

xpz3 commented May 23, 2024

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

@xpz3
Copy link
Collaborator

xpz3 commented May 23, 2024

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..

@RealYukiSan
Copy link
Author

It seems I'm misunderstanding the problem. Any suggestions for debugging the problem? let me know if you need additional information

@xpz3
Copy link
Collaborator

xpz3 commented May 23, 2024

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..

@RealYukiSan
Copy link
Author

okay! I've joined the discord

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants