Does Lagrange support SOCKS or HTTP proxies?
I found the headers issue in response when trying to test I2P connection.
Maybe my settings incorrect:
Related subjects:
Oct 09 · 4 days ago
14 Comments ↓
Hi.
im using stargate.gemi.dev:1994 as https proxy
🏃 skyjake [mod...] · Oct 10 at 04:12:
SOCKS is not supported. There is a feature request about it, though, so I may look into it eventually.
Lagrange only supports Gemini proxies (a Gemini server that responds to non-Gemini URIs, too).
@skyjake, thanks for the information. Should I note in my article that Lagrange only supports the HTTP option? However, it seems that it doesn't work either - HTTP is not supported, right? I mean connection to Gemini TCP over HTTP, I've tried to connect using it without success.
afair, http proxy (as understood normally) is using http protocol, that is http proxy must implement GET, POST etc. + CONNECT). Accessing gemini using http proxy obviously doesn't make much sense, as those two speak different protocols.
🏃 skyjake [mod...] · Oct 10 at 10:33:
Correct, Lagrange does not support any HTTP-native proxies, it only submits Gemini requests (or Gopher, Titan, Spartan, etc.).
Not sure I understand what is HTTP-native, removed it from the guide to not confuse new members.
btw, I'm using SOCKS/HTTP proxies in Yoda where it is work without issues, to visit Geminispace over I2P and Ygg(stack). Yoda also includes routing rules by regex, to separate different traffic by host match.
Thanks for info, because though it was my incorrect Agate configuration.
Proper SOCKS proxy support would be very helpful for those of us living in highly governmentally regulated locations...
Lagrange runs fine with proxychains, but native support would not involve editing the .desktop file.
I wonder if the people who are using Gemini for privacy have ever tried using it with I2P or any mesh (proxy).
@eugene
highly governmentally regulated locations
Earth soon..
I added SOCKS5 support to Alhena and now I'm discovering TOR (which I was only vaguely aware of previously). This really has been a learning experience.
@bluesman, thanks also you can try to test I2P connection with this socket type:
— shxxkkrws2m6qowjse5jpgmu64vzupnnhxrhdzrn6fr6m7ynddbq.b32.i2p
- what's really cool in I2P - there is no dedicated IP required, everyone can host their domain for free ;)
@ps I'm not even vaguely aware of I2P. Are you saying to try that link when I have TOR configured as my SOCKS5 proxy? If so, I basically get:
shxxkkrws2m6qowjse5jpgmu64vzupnnhxrhdzrn6fr6m7ynddbq.b32.i2p/<unresolved>:1965, status: HOST_UNREACHABLE(4)
Let me know. This sounds interesting. Reply in the Alhena thread if you want.
To open I2P links, you will want I2P router (e.g. i2pd)
but, if SOCKS work for Tor - it will work for I2P (for its users)
Here is my publications about how to setup it and open the link above to test, if you're interested in:
— ps.cities.yesterweb.org/uk/setup-i2pd-with-i2p-network-connection-over-yggdrasil.gmi
— ps.cities.yesterweb.org/uk/i2p-capsule-in-gemini-space-with-agate.gmi
- feel free to translate
Got it. I'll give it a try later today and report back. Tor does work and I did make a new release.
@bluesman you are welcome, I'm connecting Tor and I2P over Yggdrasil (or any other VPN) i2pd router supports Yggdrasil-only mode out of the box, but this is maybe subject for another thread.
Source