|
From: Joshua W. <jw...@ha...> - 2014-02-03 02:21:05
|
I'm reacquainting myself with the revisions to the Ubertooth tools. Where
previously ubertooth-nap was used to recover the NAP, I believe
ubertooth-rx does that job now.
However, I can't seem to find the correct syntax to perform UAP recovery:
root@astatine:~# ubertooth-rx
systime=1391392019 ch=39 LAP=a656f7 err=0 clk100ns=791221159 clk1=650883
s=-48 n=-90 snr=42
systime=1391392019 ch=39 LAP=a656f7 err=2 clk100ns=794145353 clk1=651351
s=-47 n=-90 snr=43
systime=1391392019 ch=39 LAP=a656f7 err=0 clk100ns=797102326 clk1=651824
s=-48 n=-90 snr=42
systime=1391392021 ch=39 LAP=a656f7 err=0 clk100ns=813295872 clk1=654415
s=-47 n=-91 snr=44
systime=1391392021 ch=39 LAP=a656f7 err=2 clk100ns=815084164 clk1=654701
s=-48 n=-91 snr=43
systime=1391392022 ch=39 LAP=a656f7 err=2 clk100ns=818785158 clk1=655293
s=-48 n=-90 snr=42
^Croot@astatine:~# ubertooth-rx -h
ubertooth-rx - passive Bluetooth discovery/decode
Usage:
-h this help
-i filename
-l <LAP> to decode (6 hex), otherwise sniff all LAPs
-u <UAP> to decode (2 hex), otherwise try to calculate (requires LAP)
-U <0-7> set ubertooth device to use
-c<filename> capture packets to PCAP file
-d<filename> dump packets to binary file
-e max_ac_errors (default: 2, range: 0-4)
-s reset channel scanning
If an input file is not specified, an Ubertooth device is used for live
capture.
Knowing the LAP, and seeing the "-u" argument "otherwise try to calculate"
I thought the UAP recovery would involve specifying the LAP and an empty
-u, but that returns an error:
root@astatine:~# ubertooth-rx -l a656f7 -u
ubertooth-rx: option requires an argument -- 'u'
What is the right way to recovery the UAP? I am using the git sources and
current git firmware. Thanks!
-Josh
|