I've noticed in the past that many of the public wireless networks that want you to pay to use allow DNS traffic to flow even before you've paid. I've often thought that'd you could use that to build a tunnel and not have to pay for service.
Mind you, I've never done it because it would be kind of rotten, but it did cross my mind.
You are right, I know people who do that when they travel through international airports. It doesn't work that fast (something like a 36k modem) , but it is free. AFAIK you do need a domain and a DNS server you control yourself.
not quite sure: but you can probably only connect to the local DNS (caching) server on the WLAN. DNS requests are forwarded to the server that is responsible for a certain domain. So to route the DNS packets (with other traffic encapsulated in it) to your DNS server, you need a domain... I guess...
The local wireless Domain Name Server will only accept DNS requests, and will only give you DNS replies.
So you create bogus DNS requests pointing to various places on your domian. But they aren't real places on your domain - they are encoded data. The wireless service doesn't know the answer to your DNS request, so it forwards the request to the domain to get the answer - it forwards the request to your domain. You configure your domain to decode your bogus DNS requests into g
The opulence of the front office door varies inversely with the fundamental
solvency of the firm.
Cheating Wireless networks (Score:5, Insightful)
Mind you, I've never done it because it would be kind of rotten, but it did cross my mind.
Re:Cheating Wireless networks (Score:3, Interesting)
Re:Cheating Wireless networks (Score:2)
Re:Cheating Wireless networks (Score:1)
Re:Cheating Wireless networks (Score:2)
Re:Cheating Wireless networks (Score:2)
The local wireless Domain Name Server will only accept DNS requests, and will only give you DNS replies.
So you create bogus DNS requests pointing to various places on your domian. But they aren't real places on your domain - they are encoded data. The wireless service doesn't know the answer to your DNS request, so it forwards the request to the domain to get the answer - it forwards the request to your domain. You configure your domain to decode your bogus DNS requests into g