I hereby claim:
- I am leonhandreke on github.
- I am leonhandreke (https://keybase.io/leonhandreke) on keybase.
- I have a public key whose fingerprint is 17C2 D042 2B11 814D 5EB2 2912 08C3 BA58 0249 7EB1
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
Leon@stockholm /Users/Leon/Development $ mkdir lol | |
Leon@stockholm /Users/Leon/Development $ cd lol | |
Leon@stockholm /Users/Leon/Development/lol $ ls | |
Leon@stockholm /Users/Leon/Development/lol $ git init | |
Initialized empty Git repository in /Users/Leon/Development/lol/.git/ | |
Leon@stockholm /Users/Leon/Development/lol $ touch file.c | |
Leon@stockholm /Users/Leon/Development/lol $ git add file.c | |
Leon@stockholm /Users/Leon/Development/lol $ git commit -a -m "Initial Import" | |
[master (root-commit) ca7eeae] Initial Import | |
0 files changed, 0 insertions(+), 0 deletions(-) |
The HaDiNet network interconnects roughly 1000 student rooms, currently using a single LAN. This network will now be upgraded to give each user a separate /29 IP subnet routed to his room. In the case that users require larger subnets, it should be easy to route another subnet to a room. Therefore, management software is required to configure the network. | |
Currently, the HaDiNet uses a star topology, with the core switch situated in the K3 building and other routers connected to it with 1Gbit fiber links. However, interconnection of the edges of this star is planned. Soon, all switches will be able to route IP packets. Essentially, they are giant routers with enormous backblane and routing capacity (at least to me, being a network newbie, it's pretty impressive). | |
In a perfect world, the central management software would put each room into a separate VLAN, attach the router closest to the actual room to that VLAN (basically, let the switch that the port leading to the room is on also be the gateway router for |
The HaDiNet network interconnects roughly 1000 student rooms, currently using a single LAN. This network will now be upgraded to give each user a separate /29 IP subnet routed to his room. In the case that users require larger subnets, it should be easy to route another subnet to a room. Therefore, management software is required to configure the network.
Currently, the HaDiNet uses a star topology, with the core switch situated in the K3 building and other routers connected to it with 1Gbit fiber links. However, interconnection of the edges of this star is planned. Soon, all switches will be able to route IP packets. Essentially, they are giant routers with enormous backblane and routing capacity (at least to me, being a network newbie, it's pretty impressive).
In a perfect world, the central management software would put each room into a separate VLAN, attach the router closest to the actual room to that VLAN (basically, let the switch that the port leading to the room is on also be the gateway router for
Subject: Hinweis auf ein Video via @KITKarlsruhe | |
Date: Thu, 15 Nov 2012 11:40:06 +0100 | |
From: Leon Handreke <leon.handreke@student.kit.edu> | |
To: denis.elbl@kit.edu | |
CC: klaus.ruemmele@kit.edu | |
Sehr geehrter Herr Elbl, | |
mit großem Interesse habe ich soeben die von Ihnen über den | |
Twitter-Account @KITKarlsruhe versendete Nachricht [0] mit dem Hinweis |
#!/bin/bash | |
set -x | |
# your Strava login details go here | |
EMAIL=leonh@ndreke.de | |
PASSWORD=your_secret_password | |
FILE=$1 |