dns tunnel
TRANSCRIPT
Domain Name System tunnel
also known as Socks via SSH over DNS Tunnel and Socks via SSH over DNS.
and how to get free wifi access
Pain in the ass
No Wifi Syndrome
Come on! Face it!
Why DNS?
Firewalls Wireless access point
allow DNS traffic.
Client ( my NB ) running Iodine
DNS Server
Server running IodinedThe Internet
Client ( my NB ) running Iodine
DNS Server
Server running IodinedThe Internet
Client ( my NB ) running Iodine
DNS Server
Server running IodinedThe Internet
Client ( my NB ) running Iodine
DNS Server
Server running IodinedThe Internet
Block by Firewall
Client ( my NB ) running Iodine
DNS Server
Server running IodinedThe Internet
Block by Firewall
DNS Traffic
Client ( my NB ) running Iodine
DNS Server
Server running IodinedThe Internet
Block by Firewall
DNS Traffic
DNS Traffic
Client ( my NB ) running Iodine
DNS Server
Server running IodinedThe Internet
Block by Firewall
DNS Traffic
DNS Traffic
IP Traffic
DEMO
Setup
• One Server
• One Client
Setup - Server
• Host on Amazon EC2
• Access through SSH
• Ubuntu 14.04
• Run
• Hosting some websites
Setup - Domain
• From GoDaddy
Setup - Domain
•3 A Record
•@ => EC2 Server IP
•nas => my own NAS IP
• tunnel1 => EC2 Server IP
Setup - Domain
• 3 NS Record
• @ => GoDaddy nameserver
• @ => GoDaddy nameserver
• tunnelme => tunnel1.howardchang.me ( which => EC2 Server IP )
Commands - 1 on Server
• sudo iodined -c -f -p 5353 10.0.0.1 -P howard tunnelme.howardchang.me &
• Use iodined to listen traffic from tunnelme.howardchang.me :5353
• sudo iptables -t nat -A PREROUTING -i eth0 -p udp --dport 53 -j DNAT --to :5353
• sudo iptables -t nat -A POSTROUTING -s 10.0.0.0/24 -o eth0 -j MASQUERADE
• Use iptables to forwarding the port from 53 ( port for DNS ) to 5353
Commands - 2 on Server
• ping 10.0.0.1
• Use ping to check the connection between Client and itself
Commands - 1 on Client
Commands - 2 on Client
• sudo iodine -f -P howard 54.178.145.50 tunnelme.howardchang.me
• Use iodine to connect to tunnelme.howardchang.me via the DNS we just build ( 54.178.145.50 )
Commands - 3 on Client
• ssh -qTfnN2 -D 8080 [email protected] -i Dropbox/amazon.pem
• Use iodine to connect to tunnelme.howardchang.me via the DNS we just build ( 54.178.145.50 )
Start!
• Setup done, what’s next?
• To be honest, I don’t know how to do IP over DNS.
• But I know how to use SSH over DNS tunnelling
• It works!
SSH
• Allow you to access remote server via command line
• I use aliasing here, so `ec2` will connect ec2 server for me.
• ssh [email protected] -i Dropbox/amazon.pem
• for DNS tunneling ssh access
Server
Client
From ntu-peap to NTU
Success!
Using SSH to connect to serverwith wifi NTU ( without login )