UDPspeeder VS Mosh

It's been a while since I set it up, but iirc I ended up going with https://github.com/wangyu-/UDPspeeder

Pretty sure I used the suggested config and it's been working flawlessly in the background.

Or something like that. With wireguard, it's just a matter of pointing the config at the local socket for the fec tunnel (or any other type of tunnel, there was a dicussion about making it look like TCP http traffic the other day), so it's pretty much plug and play.

I just use nbd-server, nbd-client (kernel module nbd). While at home things are fine, when not at home things can get bad unless you use something like UDPspeeder <https://github.com/wangyu-/UDPspeeder> then you just need to deal with slower speeds.

I do backups with borg while connected through ethernet.

The good news is you can implement some kind of ghetto error-correction at a higher level. Set up a tunnel to your pbx with a VPN which supports FEC -- something like UDPspeeder and configure it to send duplicates or triplicates of every packet. In this case, you're sacrificing bandwidth to improve reliability.

All it needs is a bit of reed solomon encoding in the transport for additional reliability https://github.com/wangyu-/UDPspeeder

Try pairing tmux with mosh, it's how I've been working for years whenever I'm forced to admin through a brittle straw. Mosh combats lag pretty well and doesn't care if your connection drops intermittently. https://mosh.org/

Curious what advantages this has over mosh?

https://mosh.org/

Normal ssh is TCP-based. But there is also a different implementation named mosh.

Do you know mobile shell (mosh)? [1]

Seems like most of the features you need are what mosh offers. I've been using it for decades, probably, and it is pretty awesome for latent mobile connections (read as: throttled 2G @16kBit/s).

https://github.com/mobile-shell/mosh

I use tmux, but as far as unreliable connections, I've found mosh[0] to be the best solution to the problem (when you have the ability to install it). It basically runs a background process on connection not tied to the session that your client will automatically reconnect to if the connection fails. I regularly close my laptop, travel between home and work, open it back up and the connection is available almost instantly.

[0] https://mosh.org/

If you haven’t already, and I know this doesn’t hold up for GUI emacs or vim, but consider running them through https://mosh.org/

FWIW, I wouldn't try to parse escape sequences "directly" from the input bytestream -- it's easy to end up with annoying bugs. Longer-term it's probably better to separate the logic e.g.:

- First step (for a UTF-8-input terminal emulator) means "lexing" the input bytestream as UTF-8 into a stream of USVs, which involves some subtleties (https://github.com/mobile-shell/mosh/blob/master/src/termina...).

- Second step is to run the DEC parser/FSM logic on the sequence of USVs, which is independent of the escape sequences (https://vt100.net/emu/dec_ansi_parser ; https://github.com/mobile-shell/mosh/blob/master/src/termina...).

- And then the third step is for the terminal to execute the "dispatch"/"execute"/etc. actions coming from the FSM, which is where the escape sequences and control chars get implemented (https://github.com/mobile-shell/mosh/blob/master/src/termina...).

Without this separation, it's easier to end up with bugs where, e.g., a UTF-8 sequence or an ANSI escape sequence is treated differently when it's split between multiple read() calls vs. all in one call.

Btw, you can use mosh to hide the latency of SSH. https://mosh.org/