jabjoe

It's not the DNS server. I'm sure of this because Termux uses a different DNS server but does the same. I also tried setting my phone to use OpenDNS directly. I'm pretty sure they are inspecting the DNS traffic. Exactly so changing DNS server doesn't help.

I don't see a problem when using IP directly. I mean the IP is static, so I could must buy a domain, but I'd also have to piss about with my setup.

I've emailed them. See what they come back with. I mean unless they block SSH, Wireguard and Tor, I've got to hand work arounds. I just doesn't like them fighting me.

If you're not in the UK, try a UK proxy?

O2 didn't until recently. EE does't currently (wife's network)

I've been doing some investigating. It's not just DNS. Termux doesn't use the system DNS, it uses Google. But there is still a interference with SSL on 443 and a different page on port 80.

Edit: oh and the IP address is current with ping.

"This page has been blocked for either a legal or technical reason."

But you can see the block page used yourself at: http://shieldcf.o2.co.uk/blacklist

Oh I know some ports are ok. My SSH and WireGuard get through. Port 80 is redirected to a block page place holder and 443 is interfered with so SSL fails.

No, stunnel is go othere end. If you doing only the client end, you.don't need it.

In your .ssh/config you want something like:

Host my-ssh-ssl Hostname us01.ssh0.net User sshocean-p1r4t2br Password myparrot2 Port 443 ProxyCommand ~/.ssh/https-tunnel.sh %h %p

Then you have a ~/.ssh/https-tunnel.sh something like:

#!/usr/bin/env bash { printf "GET /HTTP/1.1\r\nHost:$1\r\nUpgrade:websocket\r\n"; cat } | openssl s_client -connect $1:$2 -servername $1

That last bit, -servername is the SNI bit, if you need it. BUT I think that payload might be for port 2083. I think 443 might be just the OpenSSL connect directly.

So does using maglinks, it exists in git-annex. It's just the torrent client is super crap. Great idea, poorly implemented.

Yes the energy density is less, but the efficiency is better. ICE wastes like 2/3 of that extra energy. Still has more, but 1/3 that you might think.

Not sure exactly what you are after, but would stunnel4 do? You can use it to hide SSH with SSL and then use SNI so that a specific website name is SSH and others something else. You can probably do it with Apache or NGINX to if there is real websites too.

Client wise, just normal ssh, but with a custom config for that host with:

ProxyCommand openssl s_client -connect %h:%p

Edit: NGINX : http://nginx.org/en/docs/stream/ngx_stream_ssl_preread_module.html

Edit: Apache : https://trofi.github.io/posts/295-ssh-over-https.html