Slashdot Mirror
Advice On A New-School Old-School BBS
An anonymous reader asks I am thinking about setting up a local "community" network over WiFi minus internet connection. In other words, I would like to run a small server isolated from the web as an experiment in small scale networks (e.g., serving a café-heavy one-block radius.)
I have plenty of clever ideas -- discussion/gripe boards, weird artistic projects -- anything to bring back the old-school BBS memories where online users were drawn from a single geographic location. But everything I've learned so far is how to act as a small node on someone else's network. How can I make my own -- and make it wireless?
Google doesn't pull much up that I can find: it is mostly targeted towards those building a (free or profit) Internet access point." (Read on for more.)
" Does anybody have sources of information for how to learn about setting up the network I have in mind? Basic tutorials and those covering more advanced issues such as security would be very helpful. Finally, is there anyone out there with real world experience? Beyond imparting technical help, do you have suggestions for implementation? What worked, and what didn't? Did the lack of internet access make the project unpopular? (And if you did provide internet access as a teaser, how did you handle liability and financial issues?)"
(This reminds me of the Community Memory Project; can anyone point to some modern equivalents?)
The tech side to this is relatively simple. What you're going to want to do is to basically create your own IP-based network that isn't the Internet... that means your WiFi should have a DHCP server that hands out 10.x.x.x (unroutable) addresses to anybody who wants to get one to get them on board...
.com, .net, .org and for that matter any "real" web request to a "Hello World!" webserver that explains that your WiFi link isn't offering a connection to the Internet, instead it's a one-of-a-kind location that's offering...
Once there, your DNS universe is gonna be a bit funny. You should map all
From there, you just assign your own server names to whatever have to offer, and serve it using standard Internet technologies for web content.
I think your problem is that you're not searching on the right term on Google. What you want to do is called an "intranet"... and it's really nothing more than setting up Internet-designed IP-based stuff and forgetting to add the link to the outside world.
Now, how you're gonna promote such a thing... well, that's up to you.
You're gonna want to redirect all web requests to your BBS web page. The thing that people naturally do when they connect to a hot spot is to try to surf. If they get redirected, they'll see what your hot spot is for. You might also support various file sharing protocols with one visible machine. On that machine have one visible file that says README with instructions on how to surf to the BBS.
Of course if you wanted to be more old-school you could set up a public-access *NIX login, or even run an old-school BBS type deal via telnet. It would still be a good idea to route people to a website explaining how to get in. For that check out here and here, and here
This software provides an "Active Portal" which basically means any web traffic is redirected from wherever it was supposed to go to some specified machine.
Its not a difficult thing to do manually either with iptables. (from memory its something like: iptables -T nat -I prerouting -P tcp -dport 80 -d ! localnet -j DNAT --dest localbox). Just make sure you have a DNS server running that sends all requests back to your IP or else their browser will give them an error.
From there, you just set up and run apache on 'localbox' and you're off!