"Unthinking respect for authority is the greatest enemy of truth."

Welcome to Infoshop News
Sunday, May 19 2013 @ 01:04 AM CDT

Creating an Autonomous Wireless Network

News ArchiveSubmitted by anon:


This short document will teach you how to accomplish several different tasks.



We will create an autonomous wireless network. You could think of it as an "internet island" because what we will create is a free internet that may or may not be connected to the entire global internet.


Your internet could be used to share music, movies, books, or thoughts to those in your vicinity. You could create a pirate radio station that streams propaganda films or a bulletin board for community dissent.


Imagine it, your own private television station that can transmit 11 megabytes (two full mp3 songs) every second.


What information will you send into the wild?


Requirements


This should be possible for almost any computer connected to a wireless (sometimes called wifi or 802.11) modem. However, I have only tested this on one system: a Powerbook G4 running Mac OS X 10.3.3 with a built in Airport Extreme card on the en1 interface.


Aside from that, you will also need to be using a computer capable of running dsniff (http://naughty.monkey.org/~dugsong/dsniff/). Dsniff runs on many platforms including Linux, BSD, and OS X. It may also work with Windows.


Now, I must admit that I'm a recent convert to OS X. I've been using windows since 3.11. But I find OS X to be the most amazing system that I've ever used. Instead of describing its many virtues, I'll merely describe the simple steps needed to create your own network.




1) Open System Preferences and choose Network


2) Show Network Port Configurations


3) Click on Built In Ethernet, click on Duplicate and type Private Network


4) Show Private Network


5) Configure IPv4: Manually


6) IP Address: 10.0.2.1


7) Subnet Mask: 255.255.255.0


8) Router: 10.0.2.


9) Click AppleTalk and deselect Make AppleTalk Active


10) (optional) Repeat 4 - 9 for Airport




Ok, you are almost done. Let's take a second to see what we've done so far.


You told your computer to create a network called "Private Network". You gave it an address (10.0.2.1) which is private, so the network flows only through your computer until other people join it. Right now there is no way for anyone to connect to your network - but it does exist within your computer.


Also, something to keep in mind is that to turn on or off your "Private Network" you must show Network Port Configurations and deselect "Private Network". You won't need to do this often (normally you can just stop sharing it), but I've found that if it is on it will mess with some programs you may run (such as ettercap).


Now that we've created this network we want other people to be able to access it. This takes three simple steps.


11) Open System Preferences and select Sharing


12) Click Internet and Share your connection from: Private Network to computers using: AirPort.



If you were to click Start, your computer would start responding to becons being sent by any nearby computers. Your network will automatically assign computers IP addresses within your network and will route their traffic effortlessly.


Take a pause at this step and consider the implications of what you've just done. To give yourself some ideas click on AirPort Options.


Every wireless network is centered around an "Access Point" or AP. Each AP is allowed to choose its Network Name. This name will be displayed to other users, and they are free to choose any network they'd like or their computer may associate with the strongest signal present.


What happens if you chose the same name as another network? You literally shout over them; users will associate with whichever access point has the most power in their signal. This will depend on distance, the environment, but also the hardware that you are using. Surprisingly, it doesn't take very much to overpower a signal - especially if you place yourself closer to the intended audience. A building, for example, may have three different access points positioned on different floors. All of them use the same network name and are connected with ethernet cable to the building's wired internet connection. You can place your network in an area of the library with a relatively weak signal but nice chairs and lots of laptop users, for example, and easily hijack their connection.


Now that you've set up this network you are very close to being able to build anything. There is a slight problem, and that is you must learn something about routing information in a network. You see, there is another problem.


Let's say you named your network something intriguing like "You know" and clicked Start. Another person using a laptop sees your network and joins it. How do you alert them to who you are? What do you do when they try to go to google.com?


You need to create something similar to a Captive Portal. In other words, you want all the traffic to route back to your computer. Now this is a relatively complicated problem that does require actual programming skills. However, we're going to accomplish this task easily because all the requisite programs have been created for Mac and you can download them here.


Go ahead and install the Dsniff package, it will add a bunch of small text based programs to your computer. You can learn about each of them by typing man dsniff in the terminal. You will also need to tell your computer to forward traffic. This can be done be typing:



13) sudo pico /etc/hostconfig


14) Change IPFORWARDING=-NO- to be IPFORWARDING=-YES-




Ok, you've done it. Dsniff includes a very easy program called dnsspoof. The way this program works is by telling your users that the address for any URL is your computer. If a user tries to go to google.com, their computer will ask your computer what the IP address is and your computer will respond 10.0.2.1 (your computer). Make sense?


I'll explain some more. But first open up a terminal and type:



15) man dnsspoof


16) sudo dnsspoof -i en1


Now that this program is running, let's say that someone joins your network, opens their web browser and types in nytimes.com. Dnsspoof will intercept this signal and respond 10.0.2.1 (It also passes more information, I believe). The user will try to access your computer's web server, and this is where you need to be a little creative.


To turn on your web share, you must:


17) Open System Preferences and select Sharing


18) Turn on Personal Web Sharing



Once this is running, dnsspoof will route all web traffic on your network that attempts to use a domain name (.com,org,net,info,etc) to your computer's "Personal Web Share" that is actually a fully featured Apache web server.


The best way to understand what is going on is to get two laptops and work with it. It makes sense if you test your hypotheses. One thing you'll quickly realize is that it is a lot easier to connect with OS X users. All PC users will be able to connect to you, but it is more difficult for them to see you - at least that is my experience.


So what are the kinds of things that you are now free to do?


Well, it is really up to your imagination. You can keep your network an island, or you can plug your ethernet cord into a wall or another laptop. You can present people with a website that only allows them to download your music. Or you could set up a full blown p2p network. You could allow people to send you files or you could let people post messages to each other. Because the user will be presented with a website of your choice whenever they access the world wide web you can give as detailed instructions as you would like.


You can redirect all types of different traffic to your computer. You can run any servers that you want: streaming mp3, ftp, web, ssh, email, WASTE, etc.


Hopefully these instructions have inspired interest in wireless networks. It's the future, and the movement needs people who understand it.

Share
  • Facebook
  • Google Bookmarks
  • Ask
  • Kirtsy
  • LinkedIn
  • Digg
  • Twitter
  • SlashDot
  • Reddit
  • MySpace
  • Fark
  • Del.icio.us
  • Blogmarks
  • Yahoo Buzz
Creating an Autonomous Wireless Network | 9 comments | Create New Account
The following comments are owned by whomever posted them. This site is not responsible for what they say.
comment by The Notorious John Doe
Authored by: Anonymous on Wednesday, April 21 2004 @ 06:49 AM CDT
I have been considering the possibilities of creating a wireless P2P internet for sometime (removing the ISPs from the internet), but don\'t have any experience with wireless. This sounds really awesome.

Perhaps if the author reads this, they could answer a couple questions for me or post a follow up article.

1. Is it possible to somehow integrate the freenet project with this, so that people can surf freenet and post their own websites to freenet while connected to the \"autonomous\" internet?

2. Using 2 wireless modems or routing, could a single computer act as both a client and a server for the \"autonomous internet\" so that the \"island\" grows in total signal distance as more people join the network (for example, I start a network in a park that goes as far as an apartment complex, but someone in the apart. complex joins in and their signal reaches downtown resulting in a collective signal that reaches downtown; then someone downtown joins in and their signal can reach the warehouse district etc...)

If these two things can be done, then a true alternative to the hierarchal Server-client internet can be created (at least in cities). No servers, just a bunch of people with wireless cards willing to donate a bit of their harddrive space to host the internet. The neat thing, is that theoretically the autonomous internet would grow faster as more people joined in (limited of course by the speed of the wireless card which is currently about 54mbps - which is not bad at all).
comment by j1o2n3a4s5
Authored by: Anonymous on Wednesday, April 21 2004 @ 10:15 AM CDT
speaking of WASTE. the most anarchistic p2p / network building tool out. would anybody be interested in forming a infoshop darknet mesh so we can share and talk securely?
comment by Jonathan Nil
Authored by: Anonymous on Wednesday, April 21 2004 @ 12:30 PM CDT
I\'m afraid I\'m no expert on this stuff, but you might be interested in the Seattle Wireless Network, which is trying to create a similar thing (don\'t know how succesful they\'ve been). They\'re FAQ answers some of your questions (although I admit some of the answers are a bit technical for me).

http://www.seattlewireless.net/
comment by afxgrin
Authored by: Anonymous on Wednesday, April 21 2004 @ 09:05 PM CDT
Well, a few problems........

How do we decide what the Passphrase for the network will be? And how do we decide who is \'trustworthy\' or not?

Once someone is added to the mesh it\'s hard to get them off. And once they\'re on, any member can monitor all packets which are passing through.

It\'s just a matter of getting the network\'s passphrase and trading keys with a current member of the mesh.

WASTE is better suited to making networks between people who know each other personally and can trust the members. Plus it\'s performance scales poorly once the network/mesh gets over the magical 50 user limit. :-)

btw, I\'m on one of the larger public WASTE meshes and this can be a severe problem. If we plan to do this, we need to plan ahead and do it properly.

Anyone who\'s interested in doing this live in Southern Ontario? Because there\'s going to be a fun way for us all to meet....

email me if you want to discuss this WASTE craziness some more.
comment by
Authored by: Anonymous on Wednesday, April 21 2004 @ 09:52 PM CDT
I\'ll follow bluetooth as best as I can for a while, as opposed to 80211b/g. The first thing that stands out to me is that it is in the other direction - creating _smaller_, tight networks through typically a single cell. Connecting devices can be limited to ten metres or so, meaning the networked is more controlled rather than expansive. Diversity of tactics, eh?


Devices can easily interconnect too, so one trades with the internet and distributes to the other devices - like leafs in the gnutella protocol. Finally, you\'re limited to the number of devices you can connect to. But ultimately, one large group can be connected to an internet through one device (I guess you\'d call this device like a router). It can be laptop/pc independent, but doesn\'t have to be. I\'m sure others have more experience with this than I. Interactions should be as quick as possible so everyone can get what they want, therefore the fastest device acts as the wireless network server/router, something else I learned from using gnutella. (BTW, I think gnutella is great in learning how to make a network work for you instead of the other way around, but I\'m not fanatical about it.)
comment by
Authored by: Anonymous on Thursday, April 22 2004 @ 02:45 AM CDT
i disagree with the 50 users limit i too and on the stress mesh with you. and my opinion is that it is a limit of the routed listener ratio.
and that saying about packets that flow thru you being snoopable by others in the network is false.
the keys from one to the next are compared for transfers and shared sure some that are passive passive connections pass thru a active. but that doesn\'t mean you can grab a persons private keys / passwords and recreate the virtual connection and decrypt it.
if you don\'t trust somebody it\'s as simple as don\'t accept a public key from them
as far as creating a wireless network goes i would not rely on centralized messaging systems and that\'s still y i choose WASTE. that is completely free from hierarchy and where you can control every aspect of control and access to yourself.
comment by protocol
Authored by: Anonymous on Thursday, April 22 2004 @ 02:51 AM CDT
First off, this would only work in an area with high wireless density, like some large cities. And depending on how the routing was set up (decentralized) , it would be just as good as freenet, and people could provide their own crypto. i think this would be a great idea. the only problem being that keeping it off the internet would not be possible, as one could always connect their node and make it a proxy. check out my link for a good similar project (Shhh!! its not public yet ;-) but based on the wired net
comment by Milos Rancic
Authored by: Anonymous on Thursday, April 22 2004 @ 11:20 PM CDT
As I saw on Internet and in some business solutions is Serbia (2.4GHz 80km), more or less cheep wireless networks are possible; but... If we want to make something like that, we need to work on it very sirious:

1. We need solutions: What hardware do we need? Solutions in Serbia assumes Cisco motherboards with price 800 EUR for each, 1600 EUR for link; I saw a lot cheeper solutions on Internet, but only if you eat popcorn i USA ;-)

2. How to make connections? We do not need targeted links, we need fuzzy links... How to make interconnections for our network?

3. If there is no anarchists in Greenland, we need some connection between Americas and Euroasia-Africa. We need some Internet tunnels to communicate between distant LANs/WANs.

I suggest making some kind of forum or mailing list for that purpose if it doesn\'t exist. So we can start to study that problem.

In USA it is more easy then in other parts of the world. And we need to make solutions for the most part of the world.
comment by Synonymous
Authored by: Anonymous on Sunday, April 25 2004 @ 10:25 AM CDT
Excellent article 10/10!

Anyway to get this working on Linux or Windows too? It seems Mac is quite a head in making autonomous networks.

Please do a follow up article on this subject, a organization of people running their own wireless networks for a national or international independent internet is very kool.