Immutable Page History Attachments

Diff for "DevLoL/Location/Netzwerk"

Page name: Diff for "DevLoL / Location / Netzwerk"
Differences between revisions 30 and 40 (spanning 10 versions)
Revision 30 as of 2021-08-22 15:29:28
Size: 1967
Editor: ruabmbua
Comment:
Revision 40 as of 2021-11-12 00:17:37
Size: 2962
Editor: artdanion
Comment:
Deletions are marked like this. Additions are marked like this.
Line 14: Line 14:
 * 192.168.8.9 homeassistant test (kein backup!) https://git.devlol.org/devlol-systems/lxd-beta-nicht-cluster/-/tree/main/ansible-playbook/roles/homeassistant
Line 27: Line 28:
 * [[http://192.168.8.21|192.168.8.21]] prometheus - https://git.devlol.org/devlol-systems/lxd-beta-nicht-cluster/-/tree/main/ansible-playbook/roles/prometheus
Line 31: Line 33:
 * 192.168.8.36 devlol-gitlab-runner32 - https://git.devlol.org/devlol-systems/lxd-beta-nicht-cluster/-/tree/main/ansible-playbook/roles/gitlabrunner32
 * 192.168.8.222 zebra-zd220t - devlol lable drucker
'''Web-UI:''' zebra-zd220t.h19.devlol.org
Line 38: Line 43:

= hp switch area 42 (192.168.8.35) =
== vlans ==
1 - main vlan / devlol lan / switch management vlan

2 - Funkfeuer Mesh (Port 19, 20, 21, 22)

3 - Funkfeuer Client (Port 17, 18)

= Firewall (Router) =
Known Issues:

 * Konfigurieren eines GIF / GRE Tunnels für IPv6 resultiert in einem Kernel Crash beim Boot -> Reboot Loop. Bevor wir das wieder probieren, sollten wir checken, ob das ein OpenSense Bug ist.

DHCP

  • 192.168.8.0/24 neue range
    • Clients von 100 bis 250 (vor HackTheSpace 2021: 50 bis 250)

known devices

Web-UI: zebra-zd220t.h19.devlol.org

Transfernetz Richtung Dach

  • 192.168.7.0/24

known devices

  • 192.168.7.1 router 'dach'
  • 192.168.7.2 router 'unten'

hp switch area 42 (192.168.8.35)

vlans

1 - main vlan / devlol lan / switch management vlan

2 - Funkfeuer Mesh (Port 19, 20, 21, 22)

3 - Funkfeuer Client (Port 17, 18)

Firewall (Router)

Known Issues:

  • Konfigurieren eines GIF / GRE Tunnels für IPv6 resultiert in einem Kernel Crash beim Boot -> Reboot Loop. Bevor wir das wieder probieren, sollten wir checken, ob das ein OpenSense Bug ist.