Difference between revisions of "Networkbak"

From Whitespace (Hackerspace Gent)
Jump to: navigation, search
Line 23: Line 23:
 
For a whole bunch of reasons, option #1 is a bit impractical, so the way to go is through the interwebs.  
 
For a whole bunch of reasons, option #1 is a bit impractical, so the way to go is through the interwebs.  
 
That is exactly what is done between 0x20 and IBBT, we've created a so called Virtual Private Network or VPN, which in this case is nothing more than a point-to-point tunnel over the internet connecting 0x20 and IBBT in the same private network. This setup is documented in project OpenVPN<ref>[[OpenVPN|Project OpenVPN]]</ref>.
 
That is exactly what is done between 0x20 and IBBT, we've created a so called Virtual Private Network or VPN, which in this case is nothing more than a point-to-point tunnel over the internet connecting 0x20 and IBBT in the same private network. This setup is documented in project OpenVPN<ref>[[OpenVPN|Project OpenVPN]]</ref>.
 +
 +
= LAN @ 0x20 =
 +
I'm currently in the process of creating a new intranet at 0x20 with server [[Kimball]] as the central server for DHCP, DNS and Routing.
 +
== Network interfaces on Kimball ==
 +
Kimball has two network interfaces:
 +
<pre>
 +
# The primary network interface
 +
# eth0 is the WAN-side of our router and takes an IP from Dommel over DHCP
 +
auto eth0
 +
iface eth0 inet dhcp
 +
 +
# eth1 is the LAN-side of our router. It has a static ip and currently it uses Soekris as DNS server
 +
auto eth1
 +
iface eth1 inet static
 +
address 172.22.42.1
 +
gateway 172.22.42.1
 +
netmask 255.255.255.0
 +
network 172.22.42.0
 +
broadcast 172.22.42.255
 +
nameserver 172.22.32.14
 +
</pre>
  
 
= References =
 
= References =
 
<references/>
 
<references/>

Revision as of 16:04, 18 May 2012


Networkbak
WhitespaceLogo.gif
What:
Documenting network stuff at 0x20
Participants:
cedric
Locations:
0x20
Cornify

intro

This page was created for the sole purpose of creating clarity in the networking thingies at 0x20.

The schema

note: This schema accepts patches. You can find the .dia-file (sudo apt-get install dia) at http://members.0x20.be/cedric/Network_0x20.dia VPN 0x20.png

Sites

Whitespace

Whitespace, our hackerspace, has a LAN which connects local machines in the network 172.22.32.0/24. We provide ethernet and Wifi access to connect to the network.

IBBT

Our friends from IBBT (http://www.ibbt.be) have provided us with a virtual server in their data center, which is awesome! It has a massive internet connection and that is why this server is often referred to as "Big Pipe"<ref>Big pipe server</ref>.

VPN

To link 2 locations you have 2 options:

  1. Provide your own infrastructure: connect the two sites with a physical cable
  2. Use existing infrastructure to connect the two sites: connect through the interwebs

For a whole bunch of reasons, option #1 is a bit impractical, so the way to go is through the interwebs. That is exactly what is done between 0x20 and IBBT, we've created a so called Virtual Private Network or VPN, which in this case is nothing more than a point-to-point tunnel over the internet connecting 0x20 and IBBT in the same private network. This setup is documented in project OpenVPN<ref>Project OpenVPN</ref>.

LAN @ 0x20

I'm currently in the process of creating a new intranet at 0x20 with server Kimball as the central server for DHCP, DNS and Routing.

Network interfaces on Kimball

Kimball has two network interfaces:

# The primary network interface
# eth0 is the WAN-side of our router and takes an IP from Dommel over DHCP
auto eth0
iface eth0 inet dhcp

# eth1 is the LAN-side of our router. It has a static ip and currently it uses Soekris as DNS server
auto eth1
iface eth1 inet static
address 172.22.42.1
gateway 172.22.42.1
netmask 255.255.255.0
network 172.22.42.0
broadcast 172.22.42.255
nameserver 172.22.32.14

References

<references/>