telosgroup.dev/swim
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added target for rpi builds + README

Browse Source 
Signed-off-by: PoetryInCode <solow@solow.xyz>
This commit is contained in:
Solomon W. 2025-02-24 23:27:32 -05:00
parent 21a4e01e81
commit 00076e2b42
No known key found for this signature in database
GPG Key ID: 875878764A31AD50
2 changed files with 18 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Cargo.toml
View File

@ -15,3 +15,6 @@ serde_json = "1.0.139"
tokio = { version = "1.43.0", features = ["full"] } tokio = { version = "1.43.0", features = ["full"] }
tracing = "0.1.41" tracing = "0.1.41"
tracing-subscriber = { version = "0.3.19", features = ["fmt", "env-filter"] } tracing-subscriber = { version = "0.3.19", features = ["fmt", "env-filter"] }
[target.armv7-unknown-linux-gnueabihf]
linker = "arm-none-eabi-gcc"

17
README.md
View File

@ -1,3 +1,16 @@
# swim # Swim
A traffic routing proxy A tunneling proxy-firewall combo.
Swim is, at it's simplest, a traffic router. You can create port mappings and it
it will forward connections on those ports over a connection to/as another port.
## Why?
For a while I had used SSH to tunnel traffic between my on-prem server and my
cloud servers. SSH is secure, and it's not difficult to use. However, it gets
harder if you are working on an unstable network, and you have lots of
connections to manage.
So swim takes the best parts of SSH and gives them a more robust protocol (QUIC),
pub/priv key authentication, and reports for monitoring managing connections.