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

Interference of NetworkManager on managed interface #31

Open
sophron opened this issue Feb 2, 2017 · 1 comment
Open

Interference of NetworkManager on managed interface #31

sophron opened this issue Feb 2, 2017 · 1 comment

Comments

@sophron
Copy link

sophron commented Feb 2, 2017

On Wifiphisher, we need to spawn a vif on managed mode that NetworkManager does not interfere with, so we can pass it to hostapd. Otherwise, hostapd will fail to set it on AP.

From the README:

In my experience, virtual interfaces are primarily used to recon, attack or some other tomfoolery but can also be used to analyze your wireless network. In either case, it is generally advised to create a virtual monitor interface and delete all others (on the same phy) - this makes sure that some external process like NetworkManager does not interfere with your shenanigans.

This seems to be true when you create a vif on Monitor mode. However, when I create a vif on Managed mode, NetworkManager will find it and interfere with it either way. For example, if you create a pyric0 vif (on managed mode) and delete (or not) the rest on the same phy, nmcli dev status will show the vif as recognized by NetworkManager. I come to the conclusion that the only way to avoid this interference is by either killing these kind of procs (e.g. like airmon-ng check kill does) or tell NetworkManager to stop messing with it (by specifying it to its .conf).

I am wondering if there is a way to spawn a vif directly on AP (or Master) mode (e.g. using devadd). Network-manager should not interfere with it then, and hostapd should happily accept it too.

@wraith-wireless
Copy link
Owner

Sorry for the late response, will look into this

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

No branches or pull requests

2 participants