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

Single wlan interface, multiple monitor instances #30

Open
Pazitos10 opened this issue Sep 4, 2014 · 4 comments
Open

Single wlan interface, multiple monitor instances #30

Pazitos10 opened this issue Sep 4, 2014 · 4 comments

Comments

@Pazitos10
Copy link

I can't use wifite in Manjaro 0.8.10 Ascella 64 bits. Everytime I run it, I have this problem:
http://imgur.com/qz506v3
And if I choose any of that options, it happens again.
I've downloaded wifite from google code and from AUR. I already tried with older versions with same results.
Why is happening this?. I ran wifite before with Ubuntu and it worked perfectly.

@rzr
Copy link

rzr commented Mar 25, 2015

same for me It used to work fine
dont you have suspecious messages in logs ie :

sudo tail /var/log/syslog
Mar 25 23:31:53 lap NetworkManager[987]: (mon0): supplicant interface state: starting -> down
Mar 25 23:31:53 lap wpa_supplicant[2535]: Could not set interface mon1 flags (UP): Name not unique on network
Mar 25 23:31:53 lap wpa_supplicant[2535]: nl80211: Could not set interface 'mon1' UP
Mar 25 23:31:53 lap wpa_supplicant[2535]: Could not set interface mon1 flags (UP): Name not unique on network

@derv82
Copy link
Owner

derv82 commented May 25, 2015

same for me It used to work fine

Can you provide a link to the last working version? I can diff it with the current version and try to find where this bug was introduced.


Also, the script uses iwconfig to detect devices with Mode:Monitor ... can you paste the output of iwconfig to see if there's some inconsistency there?

@iggy
Copy link

iggy commented Jun 14, 2015

I was getting something similar. Stopped network manager and the problem went away. I know, my own fault, but it would be nice if this was caught/warned about.

@Pazitos10
Copy link
Author

Now I'm in archlinux and the problem persists but something in what @iggy said its related to something I discover a few days ago:

I was getting something similar. Stopped network manager and the problem went away. I know, my own fault, but it would be nice if this was caught/warned about.

I was trying to make it work putting my interface in monitor mode using airmon-ng manually and before it start, it suggests that some processes may cause troubles, in that list I have:

PID | Name
... | avahi-daemon
... | NetworkManager
... | avahi-daemon
... | wpa_supplicant
... | dhclient

I tried stop NetworkManager and it worked perfectly!.

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

4 participants