Building a cheap secure wireless (WLAN) infrastructure with OpenVPN and Linux (an advanced tutorial of OpenVPN)
Step 1: Outlining the setup
It is always a good practice is to visualize the layout. And for this kind of setup you might need it later on when you get stuck. So here we have an outline of our desired result:

As you can see we need to have a central switch and each meeting room has to have an RJ-45 plug that is patched to that switch. Also on that switch has to be connected the OpenVPN gateway and the Gateway to the internet, which could maybe be hooked up to an ADSL connection OR tunneled through to your real internet gateway. You should run a proxy server on it to disallow malicious surfing and have maybe a guest access procedure with authentication. Also to mitigate “rogue” connections, make sure you place the APs not next to a window or close to a door.
Step 2: Designing it all
As seen in the outline, to get this setup running smoothly we need the to design the following:
- Placement of the AP’s in each meeting room. Make sure they are out of sight and well situated.
- Product selection for the AP’s, make sure you just take Access Points , no need for Routers or Access points with heavy encryption. Simple ones will do (if you have any recommendations leave them in the comments please).
- Product selection for the switch. The switch should be quite good and should be gigabit. The reason is that you want to provide the maximum bandwidth to each Access point (making them 802.11g, so 54mbit). If you have 6x 54mbit going to your switch that is already over 300mbit/s so its wiser to just buy a gigabit switch. They don’t cost an arm and a leg anymore.
- You need a server for OpenVPN, It has to have 2 gigabit ethernet cards and should be reliable (read: RAID setup!), however it does not have to be a monster with processor power or brand new. an entry level DELL Server will do just fine. Just make sure you install Linux on it ( Fedora Core 6 for this tutorial)
For this how-to we use the LAN network of 172.10.1.0/24 which the clients will access over the VPN. - You need to have 2 private IP networks separated for your setup, a class C (/24) range should be enough unless you want to provide access to more then just ~250 users at once. For this tutorial, the “public” IP range will be 10.1.1.0/24 and the VPN range will be 192.168.1.0/24 just to make it easier.
- Name the AP’s according to where they are (e.g.: M2F3 = Meeting Room 2 Floor 3).
- The OpenVPN Server IP in the public network will be 10.1.1.2, whereas the LAN IP will be 172.10.1.45. It will also host the DHCP Server and the DNS Server for the “public” network.
- Make sure you have everyone’s name that has a laptop that will need access to the LAN.
Also please create extensive documentation about the placement, the IPs and the Management IPs of the AP’s etc. This is crucial for administration later on. I have seen cases where everything was working very smoothly but for some reason something on one AP needed to be changed and no-one knew the Management IP much less the password for the AP. This can be delaying causes for something that could have been solved quickly. An example of an IP and traffic map that might be necessary to understand everything is here:

Looking at pictures often helps you understand more then just plain text.
Technorati Tags: central authentication, cheap solution, corporate lan, fast secure, linux unix, openvpn, open source, security, wep encryption, wireless infrastructure, wlan, wlan meetingroomPopularity: 58% [?]
Where *nix and security meet the general public
WOW, that is some long article. Must have taken ou ages to put this together, kudos thou. Very well done.
//Kr0ll
Thanks, it did. Anyone with recommendations for APs or switches?
I think, is better to edit the copied .vars and set the following which you will find near the end of this file:
export KEY_COUNTRY=”IN” # Two letters youe countary code
export KEY_PROVINCE=”UT” # Name of your State/Provice
export KEY_CITY=”Chandigarh” # Name of your city
export KEY_ORG=”Anu’s Linux@HOME” # Name of your organization
export KEY_OU=”Wireless Network” # Name of the Unit/Division
export KEY_EMAIL=”admin@cto.homelinux.net” # Admin’s e-mail
before you run . ./vars
nice one, thanks.
Yes that would be an easier way and saves you a lot of time.
//Flosse
[…] Secure wireless Filed under: Linux — 0ddn1x @ 2007-01-04 04:09:43 +0000 http://blog.2blocksaway.com/2006/12/11/building-a-cheap-secure-wireless-wlan-infrastructure-with-openvpn-and-linux-an-advanced-tutorial-of-openvpn/ […]
Wow. Nice work.
I am part of popular demand and would like a pdf version.
thanks!
PDF version of this article will be available within this weekend. Also the IPtables tutorial will be done then!
Thanks to everyone
Hello
Thanks for posting the pdfs…however, when I open them in Preview or Acrobat 5/6 Reader or Pro, I see the images, but no text.
This is for both this article and the IPtables. Is there compatibility issue that I am unaware?
sorry, my bad. It is now fixed on the articles that have PDF and TXT versions. This means all iptables parts, the openvpn and the porn blocking proxy. PDF and txt will from now on uploaded as the articles are written
cheers to you!
[…] [ link ] Converter em pdf. […]
hi nice site.
thanks… glad someone finds it useful