[Bug]: Cannot connect to TCP device, incomplete packet data

[irongiant33]

Describe the bug

I have a LilyGo TBeam V1.2 connected to the same network as a Linux machine (Ubuntu 22.04 LTS, Linux 6.5.0-26-generic x86_64) running the MNMC v0.3. I installed MNMC with the following script: https://gist.github.com/irongiant33/cef93c81fb13afb683d19eb5ed7e3fc3

When connecting to the radio over TCP port 4403, I get the error "Configuration timed out. Are you sure this is a Meshtastic device?"

The debug log is full of error messages like the one below:

[2024-04-09][02:27:26][ERROR][meshtastic::connections::stream_buffer] Incomplete packet data, expected 65532 bytes, found 4215 bytes

I port scanned the meshtastic radio and saw the following:

Host is up (0.022s latency).
Not shown: 65532 closed ports
PORT       STATE  SERVICE
80/tcp     open    http
443/tcp   open    https
4403/tcp open    ds-user

To Reproduce

1. Launch MNMC
2. Input IP address of Meshtastic radio, port 4403
3. attempt to connect
4. See error

Expected behavior

I would expect the MNMC to connect to the Meshtastic radio

Additional context

unsure if this is related to #453 #446 or #410

[hayschan]

Same issue here. I am using the Ebyte EoRa-S3 (the 400TB version, meaning 433-510 MHz).