3 ms·
Waaay back in 2012, I wrote a TCP tunnel-over-DNS-TXT as a mental exercise for myself, as DNS traffic was (is still?) allowed through the Captive Portals that c
by DaiPlusPlus 3y ago
Waaay back in 2012, I wrote a TCP tunnel-over-DNS-TXT as a mental exercise for myself, as DNS traffic was (is still?) allowed through the Captive Portals that corp/academia/soulless-hospitality throw up on their Wi-Fi networks - I had it preconfigured as a tunnel for RDP traffic into my home box (WS2003) - the bandwidth was appalling (only slightly better than 56K) but the feeling of stickin' it to the man is unbeatable.
It's just unfortunate now that there's no way you'll squeeze a semi-usable desktop experience through dial-up-tier RDP anymore. IIRC, I had to use 16-color mode on a 640x480-sized desktop (good enough for e-mail!).
Of course, today, people just whip-out their phone's tether/hotspot.
- avar 3y agoIt's worth noting that you (re) invented what iodine does: https://code.kryo.se/iodine/ https://code.kryo.se/iodine/
- woleium 3y agoI tried the same thing, but ended up using icmp as the performance was better. Looks like there are several implementations: https://en.m.wikipedia.org/wiki/ICMP_tunnel https://en.m.wikipedia.org/wiki/ICMP_tunnel
- oriettaxx 3y agoand now is fun with Wireguard: if they only access to the internet is the DNS udp, you can easily route all traffic on it :) I set it up and it works, of course, then I tried to use it with public limited wifi (hotels, airports) but still have to find what I thought was more common: a connection where the only open DNS traffic is DNS