3 ms·
Hah no. Nobody is running TCP on that link, let alone SSH.
by geocar 9mo ago
Hah no.
Nobody is running TCP on that link, let alone SSH.
- jacquesm 9mo agohttps://github.com/markqvist/Reticulum https://github.com/markqvist/Reticulum and RNode would be a better match.
- dsrtslnd23 9mo agoIn aerial robotics, 900MHz telemetry links (like Microhard) are standard. And running SSH over them is common practice I guess.
- BenjiWiebe 9mo agoWhy do you guess? I wouldn't expect SSH to be used on a telemetry link. Nor TCP, and probably not IP either.
- Rebelgecko 9mo agoOnce upon a time I worked on a project where we SSH'd into a satellite for debugging and updates via your standard electronics hobbiest-tier 915mhz radio. Performance was not great but it worked and was cheap.
- jacquesm 9mo agoThis is still done today in the Arducopter community over similar radio links.
- drzaiusx11 9mo agoI haven't heard much about the ArduCopter (and ArduPilot) projects for a decade, are those projects still at it? I used to run a quadroter I made myself a while back until I crashed it in a tree and decided to find cheaper hobbies...
- jacquesm 9mo agoThey're alive and well and producing some pretty impressive software. Crashing your drone is a learning experience ;) Remote NSH over Mavlink is interesting, your drone is flying and you are talking to the controller in real time. Just don't type 'reboot'!
- mardifoufs 9mo agoWell at least crashing drones into trees has never been cheaper hahaha. So it's super easy to get into nowadays, especially if it's just to play around with flight systems instead of going for pure performance.
- deleted 9mo ago[deleted]
- geocar 9mo agoELRS?
- jacquesm 9mo agoYou can run ELRS on 900 MHz but the bitrate is atrocious.
- Rebelgecko 9mo agoNope this predated ELRS by a bit. I wasn't super involved with the RF stuff so not sure if we rolled our own or used an existing framework
- nomel 9mo agowhat's wrong with tcp, on a crappy link, when guaranteed delivery is required? wasn't it invented when slow crappy links were the norm?
- OhMeadhbh 9mo agoBecause TCP interprets packet loss as congestion and slows down. If you're already on a slow, lossy wireless link, bandwidth can rapidly fall below the usability threshold. After decades of DARPA attending IETF meetings to find solutions for this exact problem [turns out there were a lot of V4 connections over microwave links in Iraq] there are somewhat standard ways of setting options on sockets to tell the OS to consider packet loss as packet loss and to avoid slowing down as quickly. But you have to know what these options are, and I'm pretty sure the OP's requirement of having `ssh foo.com` just work be complicated by TCP implementations defaulting to the "packet loss means congestion" behavior. Hmm... now that I think about it, I'm not even sure if the control plane options were integrated into the Linux kernel (or Mac or Wintel) Life is difficult sometimes.
- direwolf20 9mo agoIt will time out before your packet gets through, or it will retransmit faster than the link can send packets.