Had a Delta flight that used gogoinflight internet. On my initial outbound flight I noticed DNS still worked without paying, so when I was flying back home, I had set up a simple iodine tunnel on my homelab in advance.
I was surprised by how completely unusable it was. Of the few sites I even attempted to load, I only just barely managed stallman.org after modifying my browsers maximum timeout via a flag (and it look ~5 minutes).
SSH was also not usable, even a simple "whoami" took ~1 minute to finally execute.
So yeah fun as a cool gimmick, but other than _maaaaybe_ connecting to a single IRC channel, its not practical for anything.
Same experience here, I've never been able to use it for anything worthwhile. On one flight I was able to send an email by manually telnetting to an SMTP server and I eventually got an email out with a single line of text but that's been about it.
I'm wondering if the problem has something to do with TCP retransmissions exploding the number of DNS requests. In the iodine client terminal there was a continuous flow of DNS requests and (most of the time) answers, so the communication at that level was kind-of working... but at the SSH level, it was practically unusable.
Had a Delta flight that used gogoinflight internet. On my initial outbound flight I noticed DNS still worked without paying, so when I was flying back home, I had set up a simple iodine tunnel on my homelab in advance.
I was surprised by how completely unusable it was. Of the few sites I even attempted to load, I only just barely managed stallman.org after modifying my browsers maximum timeout via a flag (and it look ~5 minutes).
SSH was also not usable, even a simple "whoami" took ~1 minute to finally execute.
So yeah fun as a cool gimmick, but other than _maaaaybe_ connecting to a single IRC channel, its not practical for anything.