pfatt VS Mosh

See https://github.com/MonkWho/pfatt/blob/faa80d09f9c00e4a67bc3cacf2eab5a1631ec3f9/bin/pfatt.sh#L142-L151https://github.com/MonkWho/pfatt/blob/supplicant/bin/pfatt.sh .

I read through the PFATT Guide by MonkWho, but this setup was different. Setting up PFSense as a man in the middle to the gateway. I only have 2 Ethernet ports on my PFSense box, so this physical setup wouldn't work too well. I couldn't find mention of the supplicant method anywhere.

pfSense/OPNsense: https://github.com/MonkWho/pfatt

The bypass methods you are referring to were for prior models of the att router. My understanding is your model is not compatible. See the GitHub repo.

For ATT there is a wonky workaround for their gateway (used it for a while, not sure if it was me or pfatt but it reduced speeds): https://github.com/MonkWho/pfatt

I then used this pfatt.sh script and followed the instructions here: https://github.com/MonkWho/pfatt/tree/supplicant

Word of advice... Don't bother yourself with supplicant mode. It supposedly broke around 2.45. spent many of hours trying to get it to work again but it was a no go. Also ng_etf should be preloaded so you shouldn't have to bother with that. See the defacto replacement GitHub for this and other issues.

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/

I've been using Kitty's SSH features for as long as I can remember but I recently setup Mosh and I really like how it doesn't drop connections and supports roaming.

I am surprised many people write about ssh into a server. Mosh[1] feels more responsive and it also supports longer sessions.

[1] - https://mosh.org/

Also they support Mosh which I install on my servers. It's way better than plain ssh when you're on mobile networks and wifi, especially with connections that are unreliable or bandwidth-constrained.

I’ve recently been experimenting with MoSH (Mobile Shell). Basically think SSH but with UDP - so more resilient to shoddy network conditions, roaming access points, etc.

If it is not for production (e.g. running as a daemon or a server) and you only care about the development, another ad-hoc way is using screen/tmus-like software incl. byobu, and combine it with mosh.