We have the following pools allocated to us:
- 172.22.33.0/24 (dn42)
- 172.23.187.0/24 (dn42)
- 192.168.222.0/24 (HSBXL internal non-routable LAN)
- 192.168.9.0/24 (Public WiFi, non routable)
- 192.168.13.0/24 (downstairs neighbour, non routable)
- 2001:6f8:147f::/48 (SixXS)
- 2001:470:7d73::/48 (TunnelBroker.net)
WiP: this is old informations
Moving to a new place will involve rebuilding the network, nearly from scratch.
The Gate will be our core router, but it will need some small modifications and updates
Here is how it is/will be laid out
And here is how we'll divide it:
|VLAN ID||Bridge name (on Gate)||Description||Active (Y/N)||IPv4 range||IPv6 range||Infos|
|Trunk||Trunk lines - Only for devices understanding 802.1Q|
|DN42 VPN links||172.22.33.0/27||Address pool used for DN42 VPNs|
|1||br-mgmt||Management LAN||Y||192.168.222.0/24||2001:6f8:147f:222::/64||Devices web interfaces: should be accessible only from wired LAN (VLAN 10, 11 and 12)|
|3||eth5.3||Wireless Antwerpen WAN||N|
|4||br-srv||Servers LAN||Y||172.22.33.32/27||2001:6f8:147f:4::/64||Quiet LAN for fixed services (SIP phones, network printers,...)|
|5||????||Emergency WAN||N||DHCP client||In case there is no internet (broken VDSL), this is where you plug your source of interwebs to share in the space|
|6||br-v6||IPv6 only LAN||Y||n/a||2001:6f8:147f:6::/64||IPv6 only network segment :-)|
|8||br-wifiwpa||WiFi WPA||Y||172.23.187.0/25||2001:6f8:147f:8::/64||One subnet for all access points (SSID: hsbxl), enables AP roaming|
|9||br-wifiopen||Open WiFi||Y||172.23.187.128/26||2001:6f8:147f:9::/64||Locked down subnet open to everybody, including neighbours (SSID: hsbxl-public)|
|10||br-0||Ground floor LAN||Y||172.22.33.128/27||2001:6f8:147f:10::/64|
|11||br-1||1st floor LAN||Y||172.22.33.160/27||2001:6f8:147f:11::/64|
|12||br-2||2nd floor LAN||Y||172.22.33.192/27||2001:6f8:147f:12::/64|
|13||br-3||3rd floor LAN||Y||172.22.33.65/27||2001:6f8:147f:13::/64|
|21||wan-1||Secondary uplink (Numericable ?)||N||This is a project|
|22||wan-2||N||This is a project|
|42||br-lan||HSBXL old LAN config (waiting for migration to multiple VLANs)||Y||172.22.33.129/25||2001:6f8:147f:42::/64|
|Members VPN||N||172.22.33.64/27||PROJECT :-)|
|n/a||n/a||PA system wiring||Y||n/a||n/a||Althrough this is CAT5E cabling, those cables are used to connect the speakers to the amplifier. SOME LINES HAVE 100V ON THEM BE CAREFUL !!!|
Why dividing the network like that ? Would everything in the same block be easier to manage ?
Of course it is !!
But since it's a hackerspace, people are very tempted in experimenting with stuff, and they should. :-)
Having 4 floors and the wifi in the same network will be a pain to debug in case the network go down or act funny because someone put a rogue DHCP server, announce an invalid or funky RA, made an ethernet loop, bridged two segments, use a crappy switch/hub, or is spoofing the gateway.
The worst that can happen with that setup is the wifi going down, or one floor misbehaving without interfering with the others.
Divide To Conquer, and let people play and experiment without any fear.
- Four (soon five) Unifis are broadcasting the HSBXL and HSBXL-PUBLIC (ground floor and garden), Powered by the ToughSwitch.
- One nanostation is our Wireless Antwerpen link, Powered by the ToughSwitch.
The VDSL uplink must be on a dedicated network interface or we lose bandwidth (peak at 20 Mb/s). As it is, The VDSL modem on a dedicated VLAN on the Cisco switch is an idea to scrap. This setup must be re-tried on the toughswitch. It is possible the gate is the bottleneck due to packets ping-pong on eth0
|Network/IPv6/tunnels||Network/Inside HSBXL||Network/Inside HSBXL/CoreSwitch|
|Network/Inside HSBXL/Router||Network/Inside HSBXL/TOUGHSwitch||Network/Monitoring|