Wireless Hacks
From the back cover we find that the book is targeted towards the intermediate to advanced wireless user, and I found that definitely to be the case. Some of the hacks use a lot of technical jargon, and assume a fair amount of background knowledge from the reader. You should probably already know how to get a wireless link up and running to really benefit from the book. But don't let that be a deterrent if you're a newbie. It's still a fun read, and provides a lot of ideas for the inquisitive and creative mind.
The book is very readable, (all the Hacks series books I have read would, like their venerable ancestor, UNIX Power Tools , make for great bathroom books). Each hack is self-contained, and can be read in just a few minutes. You can read the book straight through, or browse around, find what interests you and go from there. Most hacks have references to other hacks in the book, so reading it can be like browsing a web page sometimes. Many hacks also have references to further sources of information on the topic covered.There are hacks here for UNIX/Linux platforms mainly, but all you Ti/Al-Powerbook zealots will find plenty to lick your lips over as well, with several of the hacks devoted to wireless networking with OS X. There are even some for the Windows users as well. Many of the hacks (since they deal with hardware) could be utilized on any platform. Well, ok, you might have a bit of a hurdle to get your Pirouette cantenna hooked up to your vintage Apple ][c, but this book makes a good breeding-ground of ideas for those so inclined.
The book is divided into several chapters, each devoted to a particular topic. Each chapter contains a number of hacks related to that topic:
- Chapter 1, "The Standards," covers the alphabet soup of current wireless protocols, with a brief introduction to each.
- Chapter 2, "Bluetooth and Mobile Data," covers Bluetooth technology (need to use your Bluetooth-enabled cell phone to act as a modem for your laptop in a pinch? If only those phones weren't so pricey...*sigh*)
- Chapter 3, "Network Monitoring," is all about finding out what's going on on the local network, including various ways to sniff traffic, broadcast network services, perform network discovery, and analyze traffic.
- Chapter 4, "Hardware Hacks," gets down to the metal, discussing topics ranging from boosting signal strength to building your own access point from micro form-factor hardware to cabling and antenna guides.
- Chapter 5, "Do-it-Yourself Antennas," describes various ways to build your own antennas all the way from Pringles cans to milled aluminum wave guides (Don't forget to use ventilation when soldering ;-).
- Chapter 6, "Long distance Links," offers tips on setting up, well, long distance wireless links.
- Chapter 7, "Wireless Security," dispels the vendor-propagated myths of WEP 'security,' and gives practical advice on how you can avoid the guy next door from sniffing your private traffic (not that you'd have anything to hide, of course...).
Throughout the book there is a lot of information repeated from Building Wireless Community Networks, as well as a few hacks copied over from Linux Server Hacks [Slashdot review here], but all together it makes a very useful collection, and a nice addition to O'Reilly's Hacks series.
So what's my take on it? If you're doing just about anything with an 802.11x network, you'll likely find something fun or useful here. If you're brand new to wireless networking, you may want to come up to speed with something a bit more tutorial-oriented. Perhaps one drawback to the book is its recipe-style format. There's not a lot of background information offered with each hack, but rather a lot "do this, then this, and you get this." If you're not used to hacking and experimenting with things, you might find yourself a bit lost. It certainly isn't a college textbook, which can be both good and bad, depending on what you're looking for.
Overall, if you're the forward-thinking, range-extending, hardware-tinkering, soldering-iron wielding, average slashdot reader, you'll probably find it a fun read with lots of good ideas to offer.
You can purchase Wireless Hacks from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
We use nocat ( www.nocat.net ) at work. Its free, its open source, and it is highly customizeable.
I'll just toss in my $.02
Working for a company where security is of the utmost concern, I don't see 802.11 taking over anytime soon. While the speeds and reliability are getting better, it's still just too easy to find a way in. Not broadcasting the link help, but even that's not foolproof for people who know what their doing.
I don't know if you'll ever see this sort of technology in main stream business, but for home Lan's it sure is cool. Personally however, I'm just not a big fan of even thinking about sharing my $50 a month I spend on broadband internet service with anyone else.
Ref: Amazon has this book for the same price as bn
Spend $7.50 more to get free shipping.
You probably are resolving name lookups, but I'll bet what you are seeing one of two things:
1. They set a wildcard in their DNS server, so every query returns the same IP address, probably of their authentication server.
or
2. They have an HTTP proxy server that intercepts everybody who is not authorized for access, and then the DNS could still function normally.
The problem with number two is then in theory, if DNS queries still work right, then SSH, POP3, IMAP, etc probably works fine, and that would defeat the purpose. One #1, they could even assign a dummy IP address that doesn't route or translate to give internet access.
Trying is the First Step to Failing --Homer Simpson
I don't know how Starbucks does it in particular, but I've seen several different setups. Often times the authentication is done at the DHCP server, where a temporary IP on a network with no net access is assigned to unauthenticated clients, and an IP on the net-connected network is assigned once you have authenticated and restarted your network connection. On campus here @ WSU, your wifi will pick up a good IP but the only route to the internet is through a VPN tunnel you have to authenticate with, and load a kernel module that only exists for 2.2 and 2.4 Linux :-(. Another popular scheme is redirecting HTTP with a proxy, as was already mentioned.