Conversation
Notices
-
@knuthollund hi, I think the situation with IPv4 has not improved yet. Also https://fediverse.network/quitter.no still reports 65% availability.
OTOH I can confirm that quitter.no has been working very well during my whole testing period of almost a week over my #IPv6 socks #proxy.
In case other IPv4 !quitterno users want to try: I just did
ssh -D 5555 username@some-host-with-ipv6-connectivity
and set the socks proxy settings in firefox to localhost:5555.
Maybe there are still some little oddities even with IPv6, because every few minutes the ssh client logs a message like:
"channel 13: open failed: connect failed: No route to host"
but one doesn't notice anything of that in firefox.
For comparison I also tried a socks-proxy-over-ssh connection to an IPv4-only host and, as expected, firefox will give the same "cannot connect to quitter.no" error pages as via a direct IPv4 connection.
