I was looking the whole day for a way to connect to geminispace via my school network, that forces an HTTP proxy and port 443.
I was able to bypass it with a linode server listening for SSH on port 443, and using sshuttle to proxy.
It would have beed simpler if I had found a gemini-to-gemini proxy since I could just have a simple SSH tunnel, but I couldn't find any. If you know one, please give it to me!
I work on Windows, but sshuttle only works on unix-like systems. WSL saved me, and I forced most of the traffic to go through the chain.
So I have Lagrange -> Windows Network -> Wsl network -> SSH tunnel through HTTP network through Windows network -> Internet. Albert
2 years ago 路 馃憤 danrl, mozz
@shway I know this exists, but I prefer using a client made for Gemini, and it was a bit of a challenge, it has been 3 years already that I started my battle against this school's network and restrictions, and this is one of the best accomplishments I could ever have dreamt of. Plus I can now play Minecraft servers while not in lessons :) ! 路 2 years ago
https://portal.mozz.us/gemini/station.martinrue.com/albertlarsan68/b0cde798459545809ef8c9683258623b 路 2 years ago
https://portal.mozz.us/gemini/station.martinrue.com/albertlarsan68/b0cde798459545809ef8c9683258623b
It would have been even simpler if Lagrange accepted a SOCKS proxy, because SSH can create a SOCKS proxy for you, even on Windows. 路 2 years ago
@danrl Yes, it took huge amounts of research. I built a gemini-to-gemini proxy for this exact function, but it was directly using the HTTP CONNECT method, and didn't work (because 1965 is not 443), so I ditched the code. 馃槶 I now regret this (I could rebuild it, but I am lazy...) 路 2 years ago
that鈥檚 a great setup you came up with to work around the stupid filtering rule! 路 2 years ago