Network Overview: Unterschied zwischen den Versionen

Aktuelle Version vom 8. März 2018, 14:34 Uhr

Switching Infrastructure

The Ethernet switching infrastructure consists of a HP ProCurve 2824 Gigabit core switch, concentrating all the links from the wall sockets and linking to the firewall via an LACP Trunk using two Gigabit links.

The core switches are manageable via SSL and SSH on their hostnames flz-sw-01 and flz-sw-02 respectively, or simply https://flz-sw.mgmt.fablab.local for the one currently in operation.

There are various unmanaged Netgear 5-port Gigabit switches spread across the room to be used as access switches.

WiFi Infrastructure

WiFi is provided on 2.4 and 5 GHz by a Cisco/Linksys WRT610N running OpenWRT. The access point is connected to the core switch via a VLAN trunk carrying VLANs 10,11,13 and 69.

The AP can be managed on https://flz-ap.mgmt.fablab.local

Firewall Infrastructure

The firewall is running on a passively cooled system manufactured by Kontron sporting an Intel Core(TM) Duo CPU L2400 @ 1.66GHz, 3GB of memory and an internal 320GB 2.5'' SATA disk. The device has one 100Mbit interface (fxp0) connected to mhs's (?) Mikrotik for the internet uplink. The first Gigabit Ethernet interface is used for the management network, the second and third Gigabit interface are used for link aggregation group 0 (lagg0), forming an LACP trunk with the core switch, carrying VLANs 10,11,12 and 13.

The firewall can be managed on https://flz-fw.mgmt.fablab.local

@@ Zeile 1: / Zeile 1: @@
+<div class="mw-parser-output">
+== Switching Infrastructure ==
-== Switching Infrastructure ==
+The Ethernet switching infrastructure consists of a HP ProCurve 2824 Gigabit core switch, concentrating all the links from the wall sockets and linking to the firewall via an LACP Trunk using two Gigabit links.
-The Ethernet switching infrastructure consists of a HP ProCurve 2824 Gigabit core switch, concentrating all the links from the wall sockets and linking to the firewall via an LACP Trunk using two Gigabit links. The core switches are manageable via SSL and SSH on their hostnames flz-sw-01 and flz-sw-02 respectively, or simply [https://flz-sw https://flz-sw.mgmt.fablab.local] for the one currently in operation.
+The core switches are manageable via SSL and SSH on their hostnames flz-sw-01 and flz-sw-02 respectively, or simply [https://flz-sw https://flz-sw.mgmt.fablab.local] for the one currently in operation.
 There are various unmanaged Netgear 5-port Gigabit switches spread across the room to be used as access switches.
 == WiFi Infrastructure ==
-WiFi is provided on 2.4 and 5 GHz by a Cisco/Linksys WRT610N running OpenWRT.
-The access point is connected to the core switch via a VLAN trunk carrying VLANs 10,11,12,13 and 69.
+WiFi is provided on 2.4 and 5 GHz by a Cisco/Linksys WRT610N running OpenWRT. The access point is connected to the core switch via a VLAN trunk carrying VLANs 10,11,13 and 69.
 The AP can be managed on [https://flz-ap https://flz-ap.mgmt.fablab.local]
 == Firewall Infrastructure ==
-<nowiki>The firewall is running on a passively cooled Intel CoreDuo with 4GB of memory and an internal 320GB 2.5'' SATA disk.
-The device has one 100Mbit interface (fxp0) connected to Dataway's Mikrotik for the internet uplink.
+&nbsp;
+<nowiki>The firewall is running on a passively cooled system manufactured by Kontron sporting an Intel Core(TM) Duo CPU L2400 @ 1.66GHz, 3GB of memory and an internal 320GB 2.5'' SATA disk.
+The device has one 100Mbit interface (fxp0) connected to mhs's (?) Mikrotik for the internet uplink.
 The first Gigabit Ethernet interface is used for the management network, the second and third Gigabit interface are used for link aggregation group 0 (lagg0), forming an LACP trunk with the core switch, carrying VLANs 10,11,12 and 13.
 </nowiki>
 The firewall can be managed on [https://flz-fw https://flz-fw.mgmt.fablab.local]
+</div>