Difference between revisions of "Team Internet"

From Whitespace (Hackerspace Gent)
Jump to: navigation, search
(LAN: 172.22.32.0/24)
 
(32 intermediate revisions by 6 users not shown)
Line 1: Line 1:
[[File:Interwebz.gif|right|Interwebz for all!]]
+
{{Project
 +
|Current=Yes
 +
|Participants=Koenraad, Jaroslov, Bert, Fs111
 +
|Locations=Whitespace
 +
|Short description=Building the network!
 +
}}
  
 +
[[File:Interwebz.gif|right|Interwebz for all!]]
 +
{{Subpages}}
 
= Intro =  
 
= Intro =  
  
 
TeamInternet is a special interest group focussed on bringing a great internet experience into whitespace. In order to avoid endless mail and Thursday discussions, this special interest group will create a solution for everyone, if you are interested in joining, ping us.
 
TeamInternet is a special interest group focussed on bringing a great internet experience into whitespace. In order to avoid endless mail and Thursday discussions, this special interest group will create a solution for everyone, if you are interested in joining, ping us.
  
== What kind of internet connection do we have right now? ==
+
= WAN/Internet =
  
Right now we have telenet cable connection with traffic caps, blocked well-known-ports but decent speed. The costs are around
+
We plan to have two Internet uplinks in Whitespace. One wired DSL connection through the ISP [http://dommel.com Dommel] and one wireless connection to the Wireless Antwerp network.
40€ (can smbdy confirm?)
+
  
== What do we want? ==
+
== Dommel ==
  
* no traffic caps
+
After discussing multiple options, we decided to go with [http://dommel.com 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.
* fast download and upload
+
* no blocked ports
+
* good cost/service ratio
+
* native IPv6 would be cool!
+
* ... (add your own)
+
  
== The market ==
+
Note: We are currently not using anything of the ''web- and mailservice'' below.
  
A couple of month ago, Tom started a nice [https://spreadsheets.google.com/ccc?key=0AsZlEVXaL19IdFVuNENQZkIwc3ZpX1BEbjcwN041MkE&hl=en#gid=0 spreadsheet] with available options. This is a great base to go further. Let's update the doc w/ the latest offerings!
+
=== Connection details: ===
  
== Who is interested? ==
+
{|
 +
|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
 +
|}
  
* fs111
+
=== Advanced modem/router settings: ===
* tazo
+
* sandb, +1 no blocked ports, +1 no caps
+
* ... you?
+
  
== When do we start? ==
+
{|
 +
|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
 +
|}
  
I (fs111) think as soon as we are the official rentees of the space, not earlier, to avoid confusions.
+
=== web- and mailservice: ===
  
== LAN: 172.22.32.0/24 ==
+
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 Antwerpen ==
 +
 
 +
Since the installation of the Wireless Antwerp access-point on the Belgacom tower we now have line of sight to this wireless network. 
 +
 
 +
To make the connection we have a NanoStation M5. This is installed in the far corner of the slightly higher part of the roof of our building. Power is supplied through POE. The POE cable must be connected to the port on the NanoStation labelled main. The NanoStation can be configured through a web-interface.
 +
 
 +
<pre>
 +
The link to Wireless Antwerpen on the roof is now live. We have a policy
 +
routing setup where addresses in 10.97.212.0/24 range automatically go out
 +
via the WA link, and everything else via the regular Dommel link. You can
 +
reach machines in the WA internal network from the regular LAN range,
 +
however this still needs a bit of tuning.
 +
 
 +
Addresses in that new range are not yet given out by the DHCP server, but
 +
they will be as soon as we get this set up. The idea is that we'll put
 +
"known" MAC addresses (see Pamela) in the Dommel range, and visitors get on
 +
the WO link. So we'll also be doing a "guest" WIFI network for this. Of
 +
course, you can give yourself an IP address in this range (.1 is the soekris).
 +
 
 +
The dn42 link is down. The quagga on the soekris cannot handle BGP in more
 +
than one AS, and both dn42 and WA need us to use specific ASNs. If anyone
 +
still needs dn42, a fix will need to be found.
 +
 
 +
It's all a bit much for the soekris... we really need to replace it with
 +
something that has 1) more CPU, and 2) more ports. We'll need a minimum of 4
 +
ethernet ports. This will require some investment though.
 +
</pre>
 +
 
 +
'''configuration'''
 +
{|
 +
|Username/Password:
 +
|ubnt/ubnt
 +
|-
 +
|SSID:
 +
| wirelessgent-bgc5
 +
|}
 +
== Dyndns ==
 +
* dns: 0x20.dyndns.info
 +
* runs on soekris:
 +
** apt-get install ddclient
 +
**  check /etc/ddclient.conf
 +
** login: hackerspacebxl
 +
 
 +
= LAN: 172.22.32.0/24 =
  
 
'''172.22.32.1-10 reserverd for dn42 routers:'''
 
'''172.22.32.1-10 reserverd for dn42 routers:'''
 
<pre>
 
<pre>
* 172.22.32.1  -> router
+
* 172.22.32.1  -> VIAboard OpenWRT (00:0D:B4:04:D2:D5)
 
* 172.22.32.2  -> dn42 router
 
* 172.22.32.2  -> dn42 router
* 172.22.32.3  -> dn42 tazo.0x20.be
+
* 172.22.32.3  -> dn42 tomato.0x20.be
 
* 172.22.32.4  -> dn42 HSB
 
* 172.22.32.4  -> dn42 HSB
 
* 172.22.32.5  -> reserved for dn42 peering
 
* 172.22.32.5  -> reserved for dn42 peering
Line 47: Line 138:
 
* 172.22.32.8  -> reserved for dn42 peering
 
* 172.22.32.8  -> reserved for dn42 peering
 
* 172.22.32.9  -> reserved for dn42 peering
 
* 172.22.32.9  -> reserved for dn42 peering
* 172.22.32.10 -> reserved for dn42 peering
+
* 172.22.32.10 -> routerboard openvpn test ip
 
</pre>
 
</pre>
 
'''172.22.32.10-49 -> reserved for fixed ip's:'''
 
'''172.22.32.10-49 -> reserved for fixed ip's:'''
 
<pre>
 
<pre>
* 172.22.32.11 -> beagleboard
+
* 172.22.32.11 -> gatekeeper (beagleboard)    --> via dhcp
 
* 172.22.32.12 -> 0x20-AP-ch3
 
* 172.22.32.12 -> 0x20-AP-ch3
 
* 172.22.32.13 -> 0x20-AP-ch9
 
* 172.22.32.13 -> 0x20-AP-ch9
* 172.22.32.14 -> free
+
* 172.22.32.14 -> soekris
* 172.22.32.15 -> free
+
* 172.22.32.15 -> AP-dlink
* 172.22.32.16 -> free
+
* 172.22.32.16 -> sipura                      --> via dhcp
* 172.22.32.17 -> free
+
* 172.22.32.17 -> table                        --> via dhcp
* 172.22.32.18 -> free
+
* 172.22.32.18 -> TS server                    --> via dhcp
* 172.22.32.19 -> free
+
* 172.22.32.19 -> steveo                      --> via dhcp
 
* 172.22.32.20 -> free
 
* 172.22.32.20 -> free
* 172.22.32.42 -> audio system (via dhcp)
+
* ...
 +
* 172.22.32.22 -> Powerbook G4 iMarkt
 +
* 172.22.32.23 -> Shizzlebox
 +
* ...
 +
* 172.22.32.30 -> LaserJet4                    --> via dhcp
 +
* 172.22.32.42 -> audio system                 --> via dhcp
 
* ...
 
* ...
 
* 172.22.32.49 -> free
 
* 172.22.32.49 -> free
 
</pre>
 
</pre>
'''172.22.32.50-199 -> dhcp range'''<br>
+
'''172.22.32.50-149 -> dhcp range'''<br>
 +
'''172.22.32.150-169 -> openvpn range'''<br>
 
'''172.22.32.200-220 -> fixed ip via dhcp for accessible in dn42'''
 
'''172.22.32.200-220 -> fixed ip via dhcp for accessible in dn42'''
  
Line 79: Line 176:
  
 
== UTP Cabling in the space ==
 
== UTP Cabling in the space ==
All Ethernet cables are (going to be) connected to the patch panel in our rack. Here you have a scematic of how our cables are numbered.  
+
All Ethernet cables are (going to be) connected to the patch panel in our rack. Here you have a schematic of how our cables are numbered.  
 
[[File:network.png|frame|Network numbering in Whitespace]]
 
[[File:network.png|frame|Network numbering in Whitespace]]
 
For the time being only the circled numbers are present. The double circled are present and effectively connected to the patch panel already. This is an ongoing process cables will probably be installed as needed.
 
For the time being only the circled numbers are present. The double circled are present and effectively connected to the patch panel already. This is an ongoing process cables will probably be installed as needed.
Line 85: Line 182:
 
The cable guy is connected to port 60 on the patch panel.
 
The cable guy is connected to port 60 on the patch panel.
  
== DN42 ==
+
= DN42 =
 
* info: www.dn42.net
 
* info: www.dn42.net
 
* we are connected (peering with hsbxl for the moment)
 
* we are connected (peering with hsbxl for the moment)
 
* hsbxl: 172.22.33.0/24
 
* hsbxl: 172.22.33.0/24
 
* fix dns
 
* fix dns

Latest revision as of 16:13, 17 December 2011


Team Internet
WhitespaceLogo.gif
What:
Building the network!
Participants:
Koenraad, Jaroslov, Bert, Fs111
Locations:
Whitespace
Cornify
Interwebz for all!

Subpages

Intro[edit]

TeamInternet is a special interest group focussed on bringing a great internet experience into whitespace. In order to avoid endless mail and Thursday discussions, this special interest group will create a solution for everyone, if you are interested in joining, ping us.

WAN/Internet[edit]

We plan to have two Internet uplinks in Whitespace. One wired DSL connection through the ISP Dommel and one wireless connection to the Wireless Antwerp network.

Dommel[edit]

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:[edit]

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:[edit]

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:[edit]

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 Antwerpen[edit]

Since the installation of the Wireless Antwerp access-point on the Belgacom tower we now have line of sight to this wireless network.

To make the connection we have a NanoStation M5. This is installed in the far corner of the slightly higher part of the roof of our building. Power is supplied through POE. The POE cable must be connected to the port on the NanoStation labelled main. The NanoStation can be configured through a web-interface.

The link to Wireless Antwerpen on the roof is now live. We have a policy
routing setup where addresses in 10.97.212.0/24 range automatically go out
via the WA link, and everything else via the regular Dommel link. You can
reach machines in the WA internal network from the regular LAN range,
however this still needs a bit of tuning.

Addresses in that new range are not yet given out by the DHCP server, but
they will be as soon as we get this set up. The idea is that we'll put
"known" MAC addresses (see Pamela) in the Dommel range, and visitors get on
the WO link. So we'll also be doing a "guest" WIFI network for this. Of
course, you can give yourself an IP address in this range (.1 is the soekris).

The dn42 link is down. The quagga on the soekris cannot handle BGP in more
than one AS, and both dn42 and WA need us to use specific ASNs. If anyone
still needs dn42, a fix will need to be found.

It's all a bit much for the soekris... we really need to replace it with
something that has 1) more CPU, and 2) more ports. We'll need a minimum of 4
ethernet ports. This will require some investment though.

configuration

Username/Password: ubnt/ubnt
SSID: wirelessgent-bgc5

Dyndns[edit]

  • dns: 0x20.dyndns.info
  • runs on soekris:
    • apt-get install ddclient
    • check /etc/ddclient.conf
    • login: hackerspacebxl

LAN: 172.22.32.0/24[edit]

172.22.32.1-10 reserverd for dn42 routers:

* 172.22.32.1  -> VIAboard OpenWRT (00:0D:B4:04:D2:D5)
* 172.22.32.2  -> dn42 router
* 172.22.32.3  -> dn42 tomato.0x20.be
* 172.22.32.4  -> dn42 HSB
* 172.22.32.5  -> reserved for dn42 peering
* 172.22.32.6  -> reserved for dn42 peering
* 172.22.32.7  -> reserved for dn42 peering
* 172.22.32.8  -> reserved for dn42 peering
* 172.22.32.9  -> reserved for dn42 peering
* 172.22.32.10 -> routerboard openvpn test ip

172.22.32.10-49 -> reserved for fixed ip's:

* 172.22.32.11 -> gatekeeper (beagleboard)     --> via dhcp
* 172.22.32.12 -> 0x20-AP-ch3
* 172.22.32.13 -> 0x20-AP-ch9
* 172.22.32.14 -> soekris
* 172.22.32.15 -> AP-dlink
* 172.22.32.16 -> sipura                       --> via dhcp
* 172.22.32.17 -> table                        --> via dhcp
* 172.22.32.18 -> TS server                    --> via dhcp
* 172.22.32.19 -> steveo                       --> via dhcp
* 172.22.32.20 -> free
* ...
* 172.22.32.22 -> Powerbook G4 iMarkt
* 172.22.32.23 -> Shizzlebox
* ...
* 172.22.32.30 -> LaserJet4                    --> via dhcp
* 172.22.32.42 -> audio system                 --> via dhcp
* ...
* 172.22.32.49 -> free

172.22.32.50-149 -> dhcp range
172.22.32.150-169 -> openvpn range
172.22.32.200-220 -> fixed ip via dhcp for accessible in dn42

Register IP in the DHCP[edit]

  • Login to dhcp server: 172.22.32.1. If you don't have access, put your pubkey on your user page on the wiki and notify somebody who has already access.
  • You need the MAC address of the device you want to add (Hint: ifconfig | ipconfig /all | ip -0 addr)
  • Config is in /etc/dnsmasq.conf
  • Add entry at:
# IP 172.22.32.15-49 - Fixed IP's - Document on the wiki 'TeamInternet' page
dhcp-host=xx:xx:xx:xx:xx:xx,172.22.32.xx,hostname

UTP Cabling in the space[edit]

All Ethernet cables are (going to be) connected to the patch panel in our rack. Here you have a schematic of how our cables are numbered.

Network numbering in Whitespace

For the time being only the circled numbers are present. The double circled are present and effectively connected to the patch panel already. This is an ongoing process cables will probably be installed as needed.

The cable guy is connected to port 60 on the patch panel.

DN42[edit]

  • info: www.dn42.net
  • we are connected (peering with hsbxl for the moment)
  • hsbxl: 172.22.33.0/24
  • fix dns