BluVPN:Integration guide

Well hello. You probably visited this guide because you don't know where the hell to start with your server which will be integrated into the VPN.

There are two ways of getting access to the VPN

1.

If you do not have a server which will always be online, and you only care about getting a single machine into the VPN, BluABK and hawken are hosting OpenVPN servers that you can connect to. A guide for a user to connect to such server is yet to come, but consists of a few things that must happen. (Please move this to a separate page)

• OpenVPN must be installed. Here: http://openvpn.net/index.php/open-source/downloads.html
• BluABK or hawken must be poked so that you can get a key, a certificate and a public certificate. In this step you should also be handed a configuration file.
• These files must be put in their right directories, and the example configuration file must be edited. Remember, windows folks, that a "\" in "c:\program files\" must be written "c:\\program files\\"
• Launch!

2.

If you have a server, and you are willing to shift your home network to a new IP range, the guide is more complicated, but here we go.

Requirements

• A server which will always be online
• Willingness to move the home network into a /24 inside 10.159.0.0/16

Benefits

This solution will help BluVPN grow, and will generally be more awesome. You will also contact every BluVPN endpoint directly, so that there is minimal delay and extra traffic.

Step 1 - connect your server

• Connect the server to the VPN mesh/backbone. BluVPN:tinc
• Get BGP running so that your IP addresses will be set up correctly. BluVPN:BGP
• Install bind, and set up DNS zones. BluVPN:DNS

Step 2 - connect your home network

This is a guide yet to be made, but there are some ways of messing with your home network to get this right.

Possibility - run two networks on the same LAN

This will include disabling your router's DHCP server, setting it to a fancy static range, and putting the network interface of your server into this range with a static IP. Seconly, a second virtual interface (Often called eth0:0) will be created, using your LAN router address (10.159.x.1) and from here we will set up DHCP.

• BluVPN:DHCPD

Some messing with BGP and bind will be done, but that is pretty easy ;)

More awesome guide is revealed below:

Making linux forward packets

Make sure your server enables IP forwarding by default, often in /etc/sysctl.conf, and manually by

echo 1 > /proc/sys/net/ipv4/ip_forward

Make sure your server learns to NAT. This iptables rule has to be loaded on bootup too. For you to figure out (or this guide, later)

iptables -t nat -A POSTROUTING -s 10.159.0.0/16 ! -d 10.159.0.0/16 -j MASQUERADE

DHCP and router troubles

• Install and configure BluVPN:DHCPD
• Put your router in a obscure, static IP range (somewhere inside 10/8, 192.168/16 or *drumroll* 172.16/20)
• Disable your routers DHCP server
• Set a static IP for your server

Local network <3

Configure eth0:0 to use 10.159.x.1

Extra - set up 6to4

- Required: your server in DMZ and a bit of luck - How to - later, folks!