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 7e0cafe..3358ac5 100644 (file)
--- a/doc/Network.mdwn
+++ b/doc/Network.mdwn
@@ -6,7 +6,8 @@ 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 |
@@ -19,6 +20,15 @@ NOC operates a number of networks, available as tagged VLANs on the core switche
 [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