Build a Wireless ISP on Linux
JuiceMan wrote to mention an article that goes into the the specifics of setting up a Wireless Internet Service Provider (WISP) using Linux and a few easy scripts. From the article: "Wireless clients will have questions, and the Linux-based management tools I'll discuss will help you answer them. Here are some quick examples of how you can answer typical user questions - Question: 'Is the Internet down today? Why can't my browser find www.flakyhost.com?' Solution: First, check your wireless network with the scanap script; it will tell you about the wireless signal quality of all associated clients, including the one that's giving you problems. Then, check IP connectivity with the pingall script; it will tell you about the latency to your ISP's gateway, the DNS, and all your clients, including the problematic one. If these two scripts establish that your network is OK, try www.flakyhost.com."
I still can't reach www.flakyhost.com!
Another WISP provides (expensive) connectivity from a nearby mountaintop, so I decided to subscribe to that service and share the bandwidth and cost with my neighbors.
On the one hand, yay for him, he's giving his neighbors bandwidth cheaper than his competition.
On the other hand, I wonder how long he'd be able to resell that bandwidth once his upstream WISP found out what he was doing?
Remember this previous article:m l?tid=126&tid=137&tid=193&tid=215&tid=95
http://slashdot.org/articles/04/06/01/0640250.sht
I think the best way to install a wisp is still with WRT54G.
Hervé Fulchiron
Zinside, Provider of Open Source solutions
http://www.zinside.com/
I'm not sure why you think this guy's networking skills are poor, but you seem to have overlooked the fact that he *wrote* those scripts - so he invested some time to save himself some time - sounds like a pretty standard geek response to me. If I every ended up running community wireless again, I would definitely spend the first few weeks writing some simple maintenance scripts before letting the neighbourhood know that there's (nearly-)free wireless available.
you have to type commands?? maybe you shouldn't be a network admin. I mean if you can't write network utitllity programs at the ethernet frame level using raw machine code and custom elf headers,typed in binary on your custom two key keyboard then you really don't know enough about networks to administer one.
Starting yesterday (Sunday), Staples is selling the Linksys BEFW11S4 802.11b AP/router (w/ 4-port switch) for $9.94. Linksys 802.11b Cardbus adapters are now $4.94. Please note these items are 802.11b only. (I imagine they are trying to clear out the older gear.) These prices are for in-store purchases only. I picked up a couple of each for spares - in a pinch 802.11b is 802.11better_than_nothing.
I'm not affiliated with Staples or Linksys except as a customer.
I want to drag this out as long as possible. Bring me my protractor.
You can install wifidog, nocat's successor if I may call it that on top of openwrt and voilà, instant gratification. You won't become an ISP, but your users will never know the difference ;)
In case you're wondering, openwrt is a replacement firmware for the wrt54g series of routers. It's a small gnu/linux distribution that does its job quite well.
I run a slightly larger ISP than the article author, but he's really nailed the essence of it.
In the commercial world, you run carrier grade gear, with SNMP built into it, but I still have original (two+ year old customers) with WET-11 radios installed, and the author's script worked great.
The most important thing I've learned running a WISP is that people treat it like a utility. When they turn the tap, they expect water, when they flip the switch, they expect light, and when they click "Go", they expect the internet. As the WISP operator, the sooner you stop treating it as a hobby and start treating your service like a utility, the longer you'll keep happy customers. Automating checks and finding problems before they occur is exactly how to do that.
WET-11s usually fail in two stages, with Stage 1 being a gradual degredation of packet success rate, usually after a "close" (1/4 mile) lighting strike. Stage 2 takes about 4 weeks to reach,and it's total failure. The sooner you catch the degredation, the faster you can respond and keep your customers happy. The article author's scripts aren't too hard to extend and automate to make that happen.
John Gorkos
Wildcat Wireless ISP
DeSoto, KS
You can use arping to debug WinXP. Machines have to respond to arp or they can't get their network traffic.
Are you sure it's latency and not congestion? Large downloads have little effect on latency.
If, on the other hand, you're using the $5 word "latency" to describe the $.50 symptom "slow", never mind.
Less Networks have a bootable cd that serves as a wi-fi hotspot server, which takes care of virtually all the hassle. If you are not going to be charging for access, then it's ideal. Forces a re-login every so often IIRC. Runs fine on a P2 with 128Mb RAM. You do need 2 nics (one in, one out) and an access point of course.
Using a commodity PC, and the software provided free by ZoneCD http://www.publicip.net/, I was able to setup a public Wifi Hotspot in about 30 minutes. Super easy, and gives you granular access levels to grant people different types of access (i.e. Super User, Average Joe, etc.). You can track user logins, and other usage stats via a webpage as well. It sure pissed off my wife to have to log in everytime though!
Because teenage pranks are fun when you're about to die!