This could be a btlejack issue rather than a Mirage issue, but when I run
sudo btlejack -c any -d /dev/ttyACM0 -d /dev/ttyACM1 -d /dev/ttyACM2
I can successfully see a known JustWorks pairing attempt about 50% of the time (if I use 3 sniffers. Less reliable with only 1 of course.)
When I try to do the same thing from within Mirage, issuing:
sudo mirage ble_sniff SNIFFING_MODE=newConnections CRACK_KEY=yes INTERFACE=microbit0 INTERFACEA=microbit1 INTERFACEB=microbit2
I've so far only had one success (out of perhaps 20 attempts. Coincidentally(?) it was the first attempt, with a single microbit rather than the 3 which I tried to improve reliability.)
The failure is that it just prints
[INFO] Mirage process terminated !
sometimes even before I have a chance to hit the "pair" button on the Android phone.
This might be another reason to update Sniffle support, since Sniffle is pretty reliable now, whereas btlejack isn't being updated anymore AFAIK.
p.s. I notice in the example documentation it says firmware version : 3.14 for microbit. The latest released version is 2.1.1, so do I need to use this firmware to be more reliable?
This could be a btlejack issue rather than a Mirage issue, but when I run
I can successfully see a known JustWorks pairing attempt about 50% of the time (if I use 3 sniffers. Less reliable with only 1 of course.)
When I try to do the same thing from within Mirage, issuing:
I've so far only had one success (out of perhaps 20 attempts. Coincidentally(?) it was the first attempt, with a single microbit rather than the 3 which I tried to improve reliability.)
The failure is that it just prints
sometimes even before I have a chance to hit the "pair" button on the Android phone.
This might be another reason to update Sniffle support, since Sniffle is pretty reliable now, whereas btlejack isn't being updated anymore AFAIK.
p.s. I notice in the example documentation it says
firmware version : 3.14for microbit. The latest released version is 2.1.1, so do I need to use this firmware to be more reliable?