torwachter: rm d3 key as he does no longer want access as told by ruru. Also better...

[noc.git] / doc / Network.mdwn

diff --git a/doc/Network.mdwn b/doc/Network.mdwn
index 0687b38..3358ac5 100644 (file)
--- a/doc/Network.mdwn
+++ b/doc/Network.mdwn
@@ -6,18 +6,29 @@ NOC operates a number of networks, available as tagged VLANs on the core switche
 
 | Name     |  ID | DNS | CIDR                               | Comment                              |
 |----------|-----|-----|------------------------------------|--------------------------------------|
-| mgmt     |  32 | y   | 192.168.32.0/24                    | Management network                   |
+| realfunk |   6 | n   | 192.168.6.0/24                     | realfunk management network          |
+| mgmt     |  32 | y   | 192.168.32.0/24                    | management network                   |
 | iot      |  33 | y   | 192.168.33.0/24                    | IoT devices, room infrastructure     |
 | svc      |  34 | y   | 192.168.34.0/24                    | Services LAN, see below              |
 | [HAMNET] |  44 | n   | 44.0.0.0/8                         | Amateur Radio Digital Communications |
 | guests   | 127 | y   | 192.168.127.0/24                   | Exposed through the “realraum” SSIDs |
 | members  | 128 | y   | 89.106.211.32/27, 192.168.128.0/24 | Accessed with per-member credentials |
 | pub      | 130 | y   | 89.106.211.64/27                   | Publicly-available services          |
+| UPC      | 168 | n   | <dynamically assigned>             | UPC DOCSIS Internet                  |
 | `0xFF`   | 255 | n   | 10.12.240.240/28                   | Funkfeuer VLAN                       |
 
 [HAMNET]: https://wiki.oevsv.at/index.php/Kategorie:Digitaler_Backbone
 
 
+### `realfunk` -- realfunk management network
+
+This network will be used by realfunk to communicate between the ground station
+and things like SDR or similar stuff mounted on the roof. For now this network
+does not need DNS or connection to any other network. There also won't be any
+network services such as DHCP or recursive DNS. realfunk will probably run their
+own DHCP server.
+
+
 ### `svc` -- Services LAN
 
 This network is intended for services that aren't directly exposed to users
@@ -92,8 +103,10 @@ In r1w2, we have a rack hosting a number of devices:
 
 ### W2 -- realfunk
 
-realfunk receives the `0xFF` and `guests` VLANs trunked on a single fiber;
-the switch there, `sw2.mgmt.realraum.at`, provides untagged ports on either VLAN.
+realfunk receives the VLANs trunked on a single fiber; the switch there, `sw2`,
+provides untagged ports on guests, `0xFF`, and HAMNET, which are labelled on the
+device. Moreover, a single port (5) has the untagged guests LAN, along with
+tagged HAMNET packets, used by the desktop computer there.
 
 Moreover, there is a Funkfeuer node there; it *does not* advertise the realraum
 SSIDs.