|
|
Post by xtr4nge on Aug 8, 2015 9:06:00 GMT
--
|
|
|
|
Post by silverse on Apr 4, 2016 11:02:56 GMT
Hi again!
I also have some problems with thsi module haha.
If I try to start it using the web interface, it does not turn on. But If check sudo.log and run the same command manually, it works fine.
/usr/share/fruitywifi/www/modules/devicefinder/includes $ sudo python ik_wifi_device_finder.py -i wlan1mon -m aa:bb:cc:dd:ee:ff -l /usr/share/fruitywifi/logs/devicefinder.log -p 100
I had some error regarding pyaudio (don't care too much), but it should not be a problem that disallows the web interface from working...
"""
Initializing PyAudio...
(Warning messages about server socket and jack server are normal and may be discarded)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
Starting to measure. Press Ctrl-C to finish.
Start sniffing
"""
|
|
|
|
Post by xtr4nge on Apr 4, 2016 12:06:30 GMT
Hi silverse,
Start the monitor interface from the Menu/Config, it will start the monitor interface as mon0
On the module page, set the SSID or BSSID that you want to spot, and set the interface (default mon0, and should be that one)
you need to specify the channel that you want to listen (I will add this option to the module in some point)
iwconfig mon0 channel {number}
regards,
|
|
|
|
Post by silverse on Apr 6, 2016 10:23:41 GMT
Using the cli (copying and pasting from the sudo log) I do not specify the channel and it works (I am talking about the mon0 interface that is created using menu/config).
The script works fine. But using the web interface it does not start.
|
|
|
|
Post by xtr4nge on Apr 7, 2016 17:49:09 GMT
Hi silverse,
Here a few obvious tips, but just to verify that the module works or not.
- After initi monitor mode from MENU/Config and get mon0, be sure that you have selected mon0 on the pulldown (DeviceFinder module).
- If you are using macaddress mode, then change to essid mode (or backwards ), and try again.
- Try using essid mode with a simple name such as TEST just to confirm that the module starts.
let me know
regards,
|
|
