whad-client: MITM command that works on physical hardware doesn't work on Ubuntu 22.04 x86 or Ubuntu 24.04 ARM VMs
So now I’m getting back to testing the core issue I’ve been having with WHAD: it doesn’t seem to work for me in VMs. This is a deal breaker in terms of our ability to use it in the class. Because for in-person or OST2 classes we can’t be fiddling around with everyone’s random laptop configuration, so we need to be able to provide a single known-good Ubuntu Linux VMware VM for x86 and ARM (for the Mac students.)
The following command was confirmed to be working fine on bare-metal Ubuntu 22.04 with the latest main branch of whad-client.
wble-connect --log debug --log-file ./wble-connect-main-HW.log -i hci0 -r 7c:89:5c:89:5b:0c | wble-spawn --log debug --log-file ./wble-spawn-main-HW.log -i hci1 -p VirtualBP.json
(Where once again I was testing with 2x CSR dongles with BDADDRs spoofed to 11:11:11:11:11:11 and 22:22:22:22:22:22.)
The fact that it was working was confirmed via two Sniffle captures which showed the same traffic appearing at both sides. When I executed the same command on my ARM Ubuntu 24.04 VM, it didn’t work. For good measure, per ticket #52, I also tried reversing the order of wble-spawn and wble-connect, but this made no difference.
At that point I wanted to eliminate the variable that perhaps it was due to Ubuntu 24.04. (In general when setting up the class VM I had found that some tools which worked in the past on Ubuntu 20.04 and 22.04 didn’t work on 24.04.) So I started upgrading the bare-metal Linux system to Ubuntu 24.04. After upgrading to 24.04 I confirmed the command still works. This suggested that the issue wasn’t Ubuntu itself.
While waiting for the bare-metal system upgrade I also tested the other way, by opening an existing Ubuntu 22.04 x86 VM, and confirming the command didn’t work there either (despite working on Ubuntu 22.04 bare metal.)
(Note: I was literally moving the same USB BT dongles between the bare-metal machine and VMs.)
This has led me to the conclusion that there may be something about how HCI adapters are handled by VMware which is preventing WHAD from working within the VMs.
Can you confirm if you can run the above MITM command on any of the 4 combinations of x86/ARM Ubuntu 22.04/24.04 as a VMware VM? If so then I can try to replicate the same (I can also test on Windows or Linux host OSes instead of macOS; but VMware, rather than VirtualBox is a requirement, as that’s what we’ve standardized on for OST2, to avoid extra QA work.)
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 26
I think you should consider virtualization fixed for now as I said it worked on VMware on Mac and go ahead and merge the change into master. I’ll deal with other issues I’m seeing in other tickets or new tickets if necessary.
Unfortunately, I’m on vacation starting from tomorrow until the 15th of Feb. and I’m not sure I can bring my BT setup with me. I’ll do my best to try to solve this ASAP. Marking this issue as urgent.