iodine VS Squid

Obligatory dns tunnel software for exfil. It is super noisy if you do dns querylogging, so I'd not use it for anything major, but it is a fun research tool.

https://github.com/yarrick/iodine

It's worth noting that you (re) invented what iodine does: https://code.kryo.se/iodine/

(https://github.com/yarrick/iodine)

It’s slow, but it works and is a handy “last resort” tool.

I've noticed that airline wifi doesn't block DNS traffic. You can likely accomplish the same thing with a DNS tunnel like Iodine (https://github.com/yarrick/iodine).

While working in an environment where VPN connections were pretty much all blocked⁰ a friend of mine had success using https://guacamole.apache.org/ to access a remote machine¹. Not quite the same as a direct VPN connection but worth a try if nothing else functions, it looks enough like normal HTTPS traffic that he got away with it.

To keep your wireguard setup more as-is, you could try https://kirill888.github.io/notes/wireguard-via-websocket/ to tunnel that via a web server. In fact https://github.com/erebe/wstunnel which that uses could be used just as well with any other UDP based VPN.

I once tinkered with https://github.com/yarrick/iodine and successfully connected to resources over the wireless on a train, bypassing its traffic capture and sign-up requirement, so that might be an option, though I think fully blocking external DNS is more common now so this is less likely to work²³.

--

[0] practically only HTTP(S) permitted, not even SSH, DPI in use that detected just using SSH or OpenVPN over port 443

[1] NOTE: be careful breaching restrictions like this, you are at risk of an insta-sacking if discovered, or worse if operating in some securiry environments!

[2] and the latency when it does work is significant!

[3] and that much traffic over port 53 might get noticed by the heuristics of data exfiltration scanner, encouraging sysadmins to notice and implement a way to block it

There's also iodine, a C program that tunnels IPv4 packets over DNS. Useful for bypassing captive portals on wifi, since DNS usually isn't restricted.

https://github.com/yarrick/iodine

Regarding cloudflare DNS over HTTPS: It could be that it tries to server data encoded as JSON, which is impossible in JSON. Some control characters and bytes 128-255 cannot be represented as JSON strings.

A regular proxy on port 53 might work? Is it necessary to actually use DNS?

Otherwise there's https://github.com/yarrick/iodine

Get ready for iodine

https://github.com/yarrick/iodine

Or IP-over-DNS

Well, you're really exhausting your options here (and possibly your IT department's patience). Iodine would still be an option, it creates a tunnel through DNS traffic. Nearly impossible to block/filter out but you shouldn't expect a lot of bandwidth. Try it out! Although if you're only going to use low-bandwidth applications through the tunnel anyway you might as well use your own mobile data plan instead of your school's WLAN.

I “invented” IPFS when I though “wouldn’t it be nice if we could combine Squid-Cache with BackupPC

A couple of dedicated server-side resource caching solutions have emerged over the years: Memcached, Varnish, Squid, etc. Other solutions are less focused on web resource caching and more generic, e.g., Redis or Hazelcast.

Web caching (more techical, probably not useful) there squid-cache

Also, the fact it is distributed by HTTP allow companies (and ISPs) to cache content in Squid servers (http://www.squid-cache.org/). And this is quite a feature!

If your router is compatible with custom firmware (Tomato or DD-WRT) you can flash it and use the logging features of those platforms. Otherwise no there isn't really an "app or software" that can do this, you need a piece of hardware that sits between the LAN devices and the internet connection. That can be a full-fledged computer, if you're willing to use it as firewall or router (pfSense), DNS server (PowerDNS) or proxy server (Squid).

You could use a squid proxy elsewhere to uplift the crypto/cipher/PKI, which would get you browsing the full web again- however, you'd potentially fall victim to an unpatched Safari based exploit.

http://www.squid-cache.org

How to caching dependencies? By using a caching webproxy like squid? Or another way that you recoment?

Just get pfSense or its competitor opnsense, it would serve you well as very flexible firewall/gateway, as well you can install well known squid proxy as addon that can be a proxy with authorization, as well transparent proxy/cache + you can add pfBlocker that will add additional protection, + possibility to use VLAN to separate WiFi between LAN/guest and easily add captive portal if needed + IDS/IPS (either via snort or suricata) + many, many more via intuitively easy understandable web interface (as far as you know networking). Any old computer would be more that enough to serve 25 people even on a couple of gigabit WAN channels

see: http://www.squid-cache.org/