+Tunnel TCP-Traffic through DNS using dns2tcp:
+
+Server-side:
+~~~~~~~~~~~~
+1. Create necessary DNS-Records:
+dnstun.example.com. 3600 IN NS host.example.com.
+dnstun.example.com. 3600 IN A 192.168.1.1
+host.example.com. 3600 IN A 192.168.1.1
+
+2. Configure dns2tcpd on host.example.com.:
+# cat /etc/dns2tcpd.conf
+listen = 192.168.1.1 #the ip dns2tcpd should listen on
+port = 53 #" port " " " "
+user = nobody
+chroot = /tmp
+domain = dnstun.example.com. # the zone as specified inside dns
+ressources = ssh:127.0.0.1:22 # available resources
+
+3. Start the daemon:
+# cat > /etc/default/dns2tcp << EOF
+# Set ENABLED to 1 if you want the init script to start dns2tcpd.
+ENABLED=1
+USER=nobody
+EOF
+# /etc/init.d/dns2tcp start
+
+Client-side:
+~~~~~~~~~~~~
+You have two possibilities:
+- Use the DNS inside your network (DNS must allow resolving for external domains)
+# grep nameserver /etc/resolv.conf
+nameserver 172.16.42.1
+# dns2tcpc -z dnstun.example.com 172.16.42.1
+Available connection(s) :
+ ssh
+# dns2tcpc -r ssh -l 2222 -z dnstun.example.com 172.16.42.1 &
+Listening on port : 2222
+# ssh localhost -p 2222
+user@host.example.com:~#
+
+- Directly contact the endpoint (port 53 UDP must be allowed outgoing)
+# dns2tcpc -z dnstun.example.com dnstun.example.com
+Available connection(s) :
+ ssh
+# dns2tcpc -r ssh -l 2222 -z dnstun.example.com dnstun.example.com &
+Listenning on port : 2222
+# ssh localhost -p 2222
+user@host.example.com:~#
+
+Notice: using 'ssh -D 8080 ..' you will get a socks5-proxy listening on
+localhost:8080 which you can use to tunnel everything through your "dns-uplink".
+--
+Configure a MadWifi device for adhoc mode:
+
+Disable the autocreation of athX devices:
+# echo "options ath_pci autocreate=none" > /etc/modprobe.d/madwifi
+
+Remove the autocreated device for now:
+# wlanconfig ath0 destroy
+
+Configuration in /etc/network/interfaces:
+
+iface ath0 inet static
+ madwifi-base wifi0
+ madwifi-mode adhoc
+ ...
+
+Hints:
+ - Do not use interface names without ending 0 (otherwise startup fails).
+ - Only chooss unique names for interfaces.
+--
+Find dangling symlinks using zsh:
+
+% ls **/*(-@)
+--
+approx with runit supervision
+
+# apt-get install approx runit
+
+Add user approxlog for the logging daemon
+# adduser --system --home /nonexistent --no-create-home approxlog
+
+Create config directory
+# mkdir /etc/sv/approx
+
+Use /var/run/sv.approx as supervise directories
+# ln -s /var/run/sv.approx /etc/sv/approx/supervise
+
+# cat /etc/sv/approx/run
+# #!/bin/sh
+echo 'approx starting'
+exec approx -f 2>&1
+
+You normally do not need a logging service for approx, because it loggs
+to syslog too. So just for completion.
+# mkdir -p /etc/sv/approx/log
+# ln -s /var/run/sv.approx.log /etc/sv/approx/log/supervise
+# cat /etc/sv/approx/log/run
+#!/bin/sh
+set -e
+LOG="/var/log/approx"
+test -d "$LOG" || mkdir -p -m2750 "$LOG" && chown approxlog:adm "$LOG"
+exec chpst -uapproxlog svlogd -tt -v "$LOG"
+
+Now activate the new approx service (will be started within 5s)
+# ln -s /etc/sv/approx/ /var/service/
+
+Make the runit managed approx available with init-script interface.
+# dpkg-divert --local --rename /etc/init.d/approx
+# ln -s /usr/bin/sv /etc/init.d/approx