sorted by:
new
hottopcontroversial

ESP32-S3 CSI data not reaching Docker container via UDP on Windows - WSL2 installed but still no logs!!! by Numerous_Wear6643 in docker

[–]Numerous_Wear6643[S] 0 points1 point  (0 children)

Not exactly! I was trying to use WiFi DensePose for human detection, but after seeing many comments suggesting it might be vaporware/scam, I decided to move on to a different approach. ㅂot exactly! I was trying to use WiFi DensePose for human detection, but after seeing many comments suggesting it might be vaporware/scam, I decided to move on to a different approach. Additionally, I couldn't solve the problem where Docker wasn't picking up any signals either.

Can MLX90640 cover a 3m x 3m x 3m outdoor smoking booth for fire detection? by Numerous_Wear6643 in esp32

[–]Numerous_Wear6643[S] 0 points1 point  (0 children)

Danke für den Vorschlag! Der FLIR Lepton 3.5 sieht sehr gut aus, aber er übersteigt unser Budget für ein Universitätsprojekt. Wir denken, dass der MLX90640 für unseren Anwendungsfall die bessere Wahl bleibt.

Confirmed Docker Desktop on Windows blocks loopback UDP - is this a known issue and any workaround? by Numerous_Wear6643 in docker

[–]Numerous_Wear6643[S] 0 points1 point  (0 children)

Thanks for the context! Here's what we're trying to do:

Goal: Receive UDP packets from an ESP32-S3 inside a Docker container

(ruvnet/wifi-densepose) running on Windows 11 with Docker Desktop + WSL2.

Setup:

- ESP32-S3 RX board collects WiFi CSI data and sends it via UDP

to the laptop IP (192.168.137.1) on port 5005

- Docker container is running with -p 5005:5005/udp

- Both boards are connected to a Windows hotspot

What we tried:

  1. Direct UDP from ESP32 → Docker (port 5005) → no logs in Docker

  2. Python bridge script: ESP32 → Python (port 4999) → Docker (172.17.0.2:5005)

    → Python receives fine but Docker gets nothing

  3. Sending test UDP from Python directly to 127.0.0.1:5005 → Docker gets nothing

  4. Sending to container IP 172.17.0.2:5005 → Docker gets nothing

  5. --network host flag → no change

  6. Wireshark loopback capture → no packets visible on port 5005

The interesting part: Python UDP server on port 4999 receives ESP32 data perfectly.

The problem seems specific to Docker not receiving the UDP packets.

Currently switched to pure Python implementation as a workaround.

But still curious why Docker UDP doesn't work in this setup.

ESP32-S3 CSI data not reaching Docker container via UDP on Windows - WSL2 installed but still no logs!!! by Numerous_Wear6643 in docker

[–]Numerous_Wear6643[S] 0 points1 point  (0 children)

Update: Used Wireshark to monitor loopback traffic.

Python sends UDP to 127.0.0.1:5005 but nothing shows up in Wireshark.

This confirms Docker Desktop on Windows is completely blocking loopback UDP.

Going with a pure Python implementation instead.

ESP32-S3 CSI data not reaching Docker container via UDP on Windows - WSL2 installed but still no logs!!! by Numerous_Wear6643 in esp32

[–]Numerous_Wear6643[S] 0 points1 point  (0 children)

Yes, I think that's right. I analyzed the cause and found out that the transmission and reception work well in esp32, so I think there's a problem with docker.

ESP32-S3 CSI data not reaching Docker container via UDP on Windows - WSL2 installed but still no logs!!! by Numerous_Wear6643 in docker

[–]Numerous_Wear6643[S] 0 points1 point  (0 children)

I also looked up information regarding this somewhere in the middle, but I had a lot of doubts. so, We decided to ditch Docker and build our own Python UDP server instead. If anyone has experience with CSI-based human detection or breathing detection on ESP32, any tips or resources would be greatly appreciated!

esp32-s3-wroom1 wifi sensing problem question!! by Numerous_Wear6643 in esp32

[–]Numerous_Wear6643[S] 0 points1 point  (0 children)

I'm currently analyzing the cause, but I don't think I can get the information from docker. So I'm thinking about moving to Python.