OzarkBard
07-22-2003, 01:22 PM
What I am about to explain... some of you already know of. I am basically tattletelling a concept to take advantage of current open 802.11 standards in conjunction with MS XP's Wireless Zero Config service.
If any of you have been frequenting the "Troubleshooting" section of this forum, you may have come across a current problem with MS XP's Wireless Zero Config service, in which customers' using wireless laptop cards or USB clients (anything that keeps the ESSID in the computer instead of the wireless unit) will automatically try to jump onto nearby wireless AP's. Some people have posted workarounds pertaining to some particuliar equipment, but the majority still seem to be afflicted with this problem. However, along with this "bug" comes a forethought.... and I know that what I'm about to explain will make ISP's cringe....
Since wireless routers are now under $100, more and more people are buying them. The problem (or blessing depending on how you look at it), is that all of the newer ones are setup to plug right into an ISP's ethernet client (DSL, cable modem, most fixed wireless broadband) right out of the box... i.e. JoeBob-next-door can just plug this puppy into his cable modem and serve wirelessly without even having to setup the router (DHCP by default, and one simple button to clone MAC's to get around Radius servers), and it only takes a smattering of knowledge to set them up on different network configs.
Still with me? I went on about a 15-mile wardrive through the outlaying areas with a $50 antennae, about $50 cabling, and $300 one-watt amplifier... and was able to get onto at least 12 AP's with great signal, get an IP and pull web pages. A one-watt amp is able to go through at least one light outside wall and maintain signal with a small wireless router... routers that "normal" people just plug in and don't bother configuring since it works right out of the box. The most interesting aspect of this whole scenario is I'm in the middle of BFE!!! This town is about 50,000 residents in the middle of the poorest region of the US, with nothing bigger within a 2-hour drive... I can imagine what it would be like in a bigger city or the outlaying suburbs. With XP's "bug" automatically jumping to other AP's.. it creates the possibility of even the most inept wireless user the ability to "steal" internet. (although it's still a pain in the @ss if you want to remain on JUST THAT DAMN AP.. NO OTHERS!! GRR!!). And on the same account, someone that IS "technically proficient" can get into a LOT of mischief with a stolen connection... the ISP can only track as far as that customer that has the wireless AP. Yes, the customer can use WEP encryption (or other means of security), but the point is that most people simply won't bother.
Now, hehe, all illegal thoughts aside, there is also new possibility... sitting in my home a couple of weeks ago, I was able to connect to my buddy's wireless AP across the street and share files with his PC (although this can be done with almost any wireless equipment, XP's Zero Wireless Config makes it easy for "the common man"). He, in turn, shared that file with another guy about half mile away. This gave me an epiphany... it will only be a matter of time before someone creates an app or entirely new protocol for computer users with their own wireless AP to share files between other wireless clients, thereby creating essentially a new "internet". The technology is already there and open, it's just going to take some simplifying to get a large number of people to make this feasible... but the possibility is there with current standards!
As I said, some of you already understand this, but since MS has basically paved the road to common people stealing wireless internet with it's Wireless Zero Config service, I may as well openly post it for those that are "not so wirelessly inclined". I'm going wardriving this weekend in a larger city suburb; I just wonder how many AP's Ill be able to jump onto? >:)
If any of you have been frequenting the "Troubleshooting" section of this forum, you may have come across a current problem with MS XP's Wireless Zero Config service, in which customers' using wireless laptop cards or USB clients (anything that keeps the ESSID in the computer instead of the wireless unit) will automatically try to jump onto nearby wireless AP's. Some people have posted workarounds pertaining to some particuliar equipment, but the majority still seem to be afflicted with this problem. However, along with this "bug" comes a forethought.... and I know that what I'm about to explain will make ISP's cringe....
Since wireless routers are now under $100, more and more people are buying them. The problem (or blessing depending on how you look at it), is that all of the newer ones are setup to plug right into an ISP's ethernet client (DSL, cable modem, most fixed wireless broadband) right out of the box... i.e. JoeBob-next-door can just plug this puppy into his cable modem and serve wirelessly without even having to setup the router (DHCP by default, and one simple button to clone MAC's to get around Radius servers), and it only takes a smattering of knowledge to set them up on different network configs.
Still with me? I went on about a 15-mile wardrive through the outlaying areas with a $50 antennae, about $50 cabling, and $300 one-watt amplifier... and was able to get onto at least 12 AP's with great signal, get an IP and pull web pages. A one-watt amp is able to go through at least one light outside wall and maintain signal with a small wireless router... routers that "normal" people just plug in and don't bother configuring since it works right out of the box. The most interesting aspect of this whole scenario is I'm in the middle of BFE!!! This town is about 50,000 residents in the middle of the poorest region of the US, with nothing bigger within a 2-hour drive... I can imagine what it would be like in a bigger city or the outlaying suburbs. With XP's "bug" automatically jumping to other AP's.. it creates the possibility of even the most inept wireless user the ability to "steal" internet. (although it's still a pain in the @ss if you want to remain on JUST THAT DAMN AP.. NO OTHERS!! GRR!!). And on the same account, someone that IS "technically proficient" can get into a LOT of mischief with a stolen connection... the ISP can only track as far as that customer that has the wireless AP. Yes, the customer can use WEP encryption (or other means of security), but the point is that most people simply won't bother.
Now, hehe, all illegal thoughts aside, there is also new possibility... sitting in my home a couple of weeks ago, I was able to connect to my buddy's wireless AP across the street and share files with his PC (although this can be done with almost any wireless equipment, XP's Zero Wireless Config makes it easy for "the common man"). He, in turn, shared that file with another guy about half mile away. This gave me an epiphany... it will only be a matter of time before someone creates an app or entirely new protocol for computer users with their own wireless AP to share files between other wireless clients, thereby creating essentially a new "internet". The technology is already there and open, it's just going to take some simplifying to get a large number of people to make this feasible... but the possibility is there with current standards!
As I said, some of you already understand this, but since MS has basically paved the road to common people stealing wireless internet with it's Wireless Zero Config service, I may as well openly post it for those that are "not so wirelessly inclined". I'm going wardriving this weekend in a larger city suburb; I just wonder how many AP's Ill be able to jump onto? >:)