Difference between revisions of "Network"

From Whitespace (Hackerspace Gent)
Jump to: navigation, search
Line 1: Line 1:
 
= intro =
 
= intro =
 
'''''This page was created for the sole purpose of creating clarity in the networking thingies at 0x20.'''''
 
'''''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
 
[[File: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|Big pipe server]]</ref>.
 
= VPN =
 
To link 2 locations you have 2 options:
 
# Provide your own infrastructure: connect the two sites with a physical cable
 
# 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>[[OpenVPN|Project OpenVPN]]</ref>.
 
  
 
= Connection to internet =
 
= Connection to internet =
Line 90: Line 74:
 
[[Wireless_Antwerp]]
 
[[Wireless_Antwerp]]
  
= LAN @ 0x20 =
+
= LAN @ Whitespace =
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 the old 0x20 network 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
+
==The Modem: DLink DSL-2740B==
auto eth1
+
We use this modem for the adsl connection to Dommel
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>
+
  
== Routing Configuration on Kimball ==
 
 
<pre>
 
<pre>
Kernel IP routing table
+
IP: 192.168.1.1/24
Destination    Gateway        Genmask        Flags Metric Ref    Use Iface
+
default        soekris.0x20.be 0.0.0.0        UG    0      0        0 eth0
+
172.22.32.0    *              255.255.255.0  U    0      0        0 eth0
+
172.22.42.0    *              255.255.255.0  U    0      0        0 eth1
+
 
</pre>
 
</pre>
  
== DHCP Service on Kimball ==
+
==Totoro: the router==
Kimball is configured to provide Dynamic Host Configuration to hosts on the eth1 (LAN) side of the network. The configuration can be found in '''''/etc/dhcp/dhcpd.conf''''':
+
The cisco RV082 router serves as the main router. It has the following functions:
<pre>
+
# The ddns-updates-style parameter controls whether or not the server will
+
# attempt to do a DNS update when a lease is confirmed. We default to the
+
# behavior of the version 2 packages ('none', since DHCP v2 didn't
+
# have support for DDNS.)
+
ddns-update-style none;
+
  
# option definitions common to all supported networks...
+
- dhcp server which gives out ip's in the range 172.22.32.100-200 (also gives the openDNS servers)
option domain-name "0x20.be";
+
- 2 WAN connections: One to Dommel, one to Wireless Antwerp. The connections are configured as load-balanced, but resort to failover when one of the connections is down.
option domain-name-servers 172.22.32.14;
+
  
default-lease-time 6000;
+
<pre>
max-lease-time 7200;
+
LAN side IP: 172.22.32.1/24
 +
Modem side IP: 192.168.1.2/24
 +
WA side IP: automatic(dhcp)
 +
</pre>
  
# If this DHCP server is the official DHCP server for the local
+
==Cisco AirPlus 2.4 ghz Wireless Access point==
# network, the authoritative directive should be uncommented.
+
There are a few of them around the space. You can reset the AP's to factory settings by holding the reset button for 20 seconds. They provide 2 wireless network:
#authoritative;
+
  
# Use this to send dhcp log messages to a different log file (you also
+
'''0x20'''
# have to hack syslog.conf to complete the redirection).
+
- WPA key: unicorns
log-facility local7;
+
- Is connected to Totoro (load-balancing between WA and Dommel)
  
subnet 172.22.42.0 netmask 255.255.255.0 {
+
'''0x20-WirelessAntwerp'''
        option routers 172.22.42.1;
+
- WPA key: unicorns
        option subnet-mask 255.255.255.0;
+
- Is directly connected to WA network
        option ip-forwarding off;
+
        range dynamic-bootp 172.22.42.100 172.22.42.200;
+
        default-lease-time 21600;
+
        max-lease-time 43200;
+
}
+
</pre>
+
  
As you can see, Kimball hosts the '''172.22.42.0/24''' network and also acts as it's default gateway on 172.22.42.1 which is it's own static address on eth1. At the moment we provide the '''range 172.22.42.100-172.22.42.200''' for DHCP.
 
  
I also had to tell dhcpd to listen for DHCP-requests on eth1 instead of on eth0. For this I updated the file '''/etc/default/isc-dhcp-server''':
+
= backup of old/out of date information: following things can be removed =
<pre>
+
# Defaults for dhcp initscript
+
# sourced by /etc/init.d/dhcp
+
# installed at /etc/default/isc-dhcp-server by the maintainer scripts
+
  
#
 
# This is a POSIX shell fragment
 
#
 
  
# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
+
== The schema ==
#      Separate multiple interfaces with spaces, e.g. "eth0 eth1".
+
'''''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
INTERFACES="eth1"
+
[[File:VPN_0x20.png]]
</pre>
+
  
 
+
= Sites =
= References =
+
== Whitespace ==
<references/>
+
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|Big pipe server]]</ref>.
 +
= VPN =
 +
To link 2 locations you have 2 options:
 +
# Provide your own infrastructure: connect the two sites with a physical cable
 +
# 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>[[OpenVPN|Project OpenVPN]]</ref>.

Revision as of 21:00, 25 June 2014

intro

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

Connection to internet

ISP: Dommel

After discussing multiple options, we decided to go with Dommel: fast access, cheap, no caps, no ports blocked. We went with the lower cost - lower speed option, with the idea that, if we want more, we can always upgrade.

Note: We are currently not using anything of the web- and mailservice below.

Connection details:

adsl-number 100987582393
news-server: news.dommel.be
news-login: xxx@schedom.be
news-pass: xxx
pop3-server: pop.dommel.be
smtp-server: relay.dommel.be
webmail: webmail.dommel.be
wan-ip: 83.101.72.80

Advanced modem/router settings:

protocol: rfc 2684 (aka 1483) multi-protocol over atm (bridged or routed)
vpi/vci: 8/35
ipaddress: automatic/dhcp
encapsulation: llc
password: not needed
nameserver1: 193.109.184.72
nameserver2: 193.109.184.75

web- and mailservice:

Your personal homepage at http://yourchoice.dommel.be has not yet been activated. To activate, login at https://crm.schedom-europe.net with username "info@0x20.be" and password "xxx". Click on "My Packages" -> Click on the "E" at the right of your adsl-account. You can configure your @dommel.be emailaccounts by clicking on the "O".


If you have any questions, please first check our support pages at https://crm.schedom-europe.net (click on "online faq"). If you cannot find an answer to your questions here, you can open a ticket at https://crm.schedom-europe.net (click on "support-desk"), or contact us by telephone every workingday between 09.00 and 18.00 (+32 70 224 305) or by fax (+32 70 224 305).

Wireless Antwerp

We also have a connection to the wireless antwerp network Wireless_Antwerp

LAN @ Whitespace

The Modem: DLink DSL-2740B

We use this modem for the adsl connection to Dommel

IP: 192.168.1.1/24

Totoro: the router

The cisco RV082 router serves as the main router. It has the following functions:

- dhcp server which gives out ip's in the range 172.22.32.100-200 (also gives the openDNS servers) - 2 WAN connections: One to Dommel, one to Wireless Antwerp. The connections are configured as load-balanced, but resort to failover when one of the connections is down.

LAN side IP: 172.22.32.1/24
Modem side IP: 192.168.1.2/24
WA side IP: automatic(dhcp)

Cisco AirPlus 2.4 ghz Wireless Access point

There are a few of them around the space. You can reset the AP's to factory settings by holding the reset button for 20 seconds. They provide 2 wireless network:

0x20 - WPA key: unicorns - Is connected to Totoro (load-balancing between WA and Dommel)

0x20-WirelessAntwerp - WPA key: unicorns - Is directly connected to WA network


backup of old/out of date information: following things can be removed

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>.