TCP Echo Server
TCP Echo Server is a lightweight Go-based service that echoes Transmission Control Protocol (TCP) data back to clients, helping homelab users verify that a…
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
22/100 Low
- Maintained
- 0last commit 2936 days ago
- Popular
- 2618 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- No data
- Security check
- 58no serious findings, tests, OpenSSF Scorecard 1.8/10
Based on 4 of 5 factors.
- GitHub stars
- 18
- Open issues
- 0
- Last commit
- 2018-11-06
- License
- BSD-3-Clause
- Activity
- stale
Checked yesterday - source: GitHub (venilnoronha/tcp-echo-server)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Enter the server's IP before starting Give the app the IP address of the tcp-echo-server machine; the port is optional and uses 9100 by default. If the IP is missing or wrong, the app cannot find the server and the connection will fail. source
- Open or allow port 9100 on the server The app looks for the echo server on TCP port 9100 when no port is set. If your firewall or router blocks that port, your device will not be able to talk to the server even when the IP is correct. source
- Use a native app, not a web browser Run the app on an Android or iOS build because browsers do not support raw TCP sockets. If you open it in a web browser, the connection will fail with "TCP sockets are not supported in web browsers." source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How do I run TCP Echo Server in Docker?
Run the Docker image with a TCP port mapping, such as docker run -p 9000:9000 venilnoronha/tcp-echo-server:latest. The example server listens on port 9000 with the hello prefix.
What does the server send back to a client?
It prepends a preconfigured prefix to the data it receives and writes it back on the connection. In the example, sending world returns hello world.
How can I manually test the server locally?
Send text over netcat to the listening port, for example echo world | nc localhost 9000. The expected example response is hello world.
Can I connect to it from a phone web browser?
No, browsers do not support raw TCP sockets. Use an Android or iOS native app build instead, because opening the connection in a web browser will fail.
Answers sourced from github.com, github.com
Community
- Simple TCP or UDP echo server : r/bash - Reddit (reddit)
- Expose local TCP server to the internet : r/selfhosted - Reddit (reddit)
- tcp - How to make an Echo server with Bash? - Stack Overflow (forum)
- sockets - How to write a python echo server that doesn't disconnect ... (forum)
- TCP echo server, "accept failed", reference good example needed (forum)
- TCP Echo Server problem - #2 by rtel - forums.freertos.org (forum)
Collected 48 days ago - public community threads