Question regarding Linux WiFi RSSI behavior in the current RuView build

[HamoodyBroFerraris]

Hello,

I hope you are well.

I have been testing RuView on Lubuntu in a virtual machine with a USB Wi-Fi adapter passed through to the guest, and I wanted to ask for your guidance regarding the Linux WiFi RSSI path in the current build.

For context, my environment is:

Lubuntu / Ubuntu-based Linux
Kernel: 6.17.0-19-generic
Architecture: x86_64
Virtual machine with USB Wi-Fi adapter passthrough

A few things are working as expected on my side:

the VM detects the USB Wi-Fi adapter correctly
Linux detects the wireless interface
iw dev works
iw dev scan successfully returns nearby access points
the verification pipeline also passes in a pinned environment, so the Python signal-processing pipeline appears reproducible

Because of that, I believe the remaining issue may be specific to the live Linux WiFi runtime path in the Rust sensing server.

While reviewing the current crates/wifi-densepose-sensing-server/src/main.rs, it appears that the source selection logic currently does the following:

for auto:
selects esp32 if probe_esp32(...) succeeds
selects wifi if probe_windows_wifi(...) succeeds
otherwise falls back to simulate
for task dispatch:
esp32 starts the UDP receiver path
wifi starts windows_wifi_task(...)
all other values appear to fall through to simulated_data_task(...)

In practice, on my Linux build, this seems to result in the following behavior:

--source auto reports “No hardware detected, using simulation”
--source wifi starts a Windows WiFi multi-BSSID pipeline and attempts to call netsh
--source linux shows source=linux in the status/UI, but appears to fall through to simulated data

I may be misunderstanding the intended runtime flow, so I wanted to ask whether you could kindly clarify the following:

Is Linux RSSI support currently implemented on a different branch or commit than the present main branch?
Is there a Linux task path that is expected to be wired into main.rs, but is not yet connected in the version I tested?
Is --source auto on Linux intended to detect an iw-based Wi-Fi path, but this detection is not yet active in the current build?

I appreciate the work that has gone into the project, and I wanted to check with you directly before drawing any incorrect conclusions from my testing.

Thank you very much for your time.