xme
Timestamp not working
Not knowing exactly how Perl gets the localtime, on the Raspbian distribution I'm testing the script out on, I noticed that the "Last Seen" timestamps written by --dumpfile are all recorded based on a clock that starts at unix epoch when the script is run. If I restart the script, it starts back at epoch again despite the system time and timezone being already set and up to date.
If I figure this out I'll send back my findings.
I don't know how to offer suggestions, so I'll mention here that it would be nice if the --dumpfile could also include signal strength.
BTW, very nice script!
@arriflex: It seems to be fixed on the latest open pull request https://github.com/xme/hoover/pull/2
However seem like @xme didn't merged it yet :rage:
@xme: Can you take a look on the repo? :smile:
@crushedice2000 I was not able to make either of your scripts work at all on a Linux box where xme's script does work.
The Python one just sits indefinitely on Starting switch channel thread using a dely of 5 secondspress CTRL+C to exit without ever producing any probe requests.
The Perl one just sits indefinitely on Capturing on 'wlan0' without ever producing any probe requests.
On the same box, xme's script almost immediately produces
Capturing on 'wlan0'
1 ++ New probe request from...
with additional lines of probe requests soon thereafter.
Not sure how to troubleshoot, but happy to try.
@arriflex: Do you mean the scripts hosted in my github account/
I meant that you should use the latest non-merged PR of this project...
Mine is discontinued, later I'l review.