eap_proxy VS Mosh

The inspiration is the EAP Proxy that I used to bypass the AT&T router and connect my router to the AT&T fiber, before I learned about the vulnerability that allowed me to copy the 802.1x certificate from the AT&T router to my router. https://github.com/jaysoffian/eap_proxy

I use an EAP proxy to put my router in front of theirs and got a %20 speed improvement.

With my wife, I built two kids both in college now. That's definitely the most impactful.

In the online world, I've contributed bits and pieces to open-source here and there as far back as the late 90s. I think my first contribution was to the shadow package, but I've contributed here and there to Apache, Radius, random packages that I use that I discover bugs in, etc.

A python script I wrote to allow folks to bypass AT&T's residential gateway was used by more people than I ever expected:

https://github.com/jaysoffian/eap_proxy

There are forum threads about people rooting these routers to try and extract the certificate/private keys from their provided router, which worked for a limited time with certain router models. For now, the most popular way to do it is with a tool like this: https://github.com/jaysoffian/eap_proxy

If you use a Ubiquiti router, then another method to bypass your ATT router is called EAP Proxy.

WEEELLLLLL, there is a way to get into a true bridge mode on some ATT fiber plans/service by using something like EAP-Proxy: https://github.com/jaysoffian/eap_proxy

If you're up for a more complex setup, it is possible to put your home network on AT&T Fiber without going through their boarder gateway. I've had luck using https://github.com/jaysoffian/eap_proxy to bypass the boarder gateway for traffic flows.

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.