975
Comment:
|
3237
|
Deletions are marked like this. | Additions are marked like this. |
Line 2: | Line 2: |
Line 4: | Line 3: |
* Clients von 50 bis 250 | * Clients von 100 bis 250 (vor HackTheSpace 2021: 50 bis 250) |
Line 7: | Line 6: |
Line 9: | Line 7: |
* 192.168.8.2 mqtt | * 192.168.8.2 mqtt - https://git.devlol.org/devlol-systems/lxd-beta-nicht-cluster/-/tree/main/ansible-playbook/roles/mosquitto |
Line 11: | Line 9: |
* 192.168.8.4 asterisk intern | * 192.168.8.4 asterisk intern - https://git.devlol.org/devlol-systems/lxd-beta-nicht-cluster/-/tree/main/ansible-playbook/roles/asterisk * 192.168.8.5 nodered zum rumspielen: http://192.168.8.5:1880/ - kein backup! - https://git.devlol.org/devlol-systems/lxd-beta-nicht-cluster/-/tree/main/ansible-playbook/roles/nodered |
Line 13: | Line 12: |
* 192.168.8.7 tyr | * 192.168.8.7 devlock tür * 192.168.8.8 pihole (rennt auf lolneti) * 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 16: | Line 17: |
* 192.168.8.13 aptcacher auf port 3142 - https://git.devlol.org/devlol-systems/lxd-beta-nicht-cluster/-/tree/main/ansible-playbook/roles/aptcacher | |
Line 17: | Line 19: |
* 192.168.8.17 nodered zum rumspielen: http://192.168.8.17:1880/ | * 192.168.8.17 devlol-gitlab-runner - https://git.devlol.org/devlol-systems/lxd-beta-nicht-cluster/-/tree/main/ansible-playbook/roles/gitlabrunner |
Line 19: | Line 21: |
* 192.168.8.19 fileshare mit h5ai und upload per sftp mit lol/lol http://192.168.8.19 * 192.168.8.20 craftui |
* 192.168.8.19 fileshare * Weboberfläche: http://192.168.8.19/#fileshare * Rsync List: rsync --list-only rsync://192.168.8.19:/fileshare/ * Rsync download: rsync -r -v --progress rsync://192.168.8.19:/fileshare/ fileshare * Rsync upload: rsync -r -v --progress lokale_cooler_ordner rsync://192.168.8.19:/fileshare/<<BR>> * [[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 23: | Line 29: |
* 192.168.8.34 h801 led strip controller "devlol/h19/mainroom/ceiling1" (see [[https://devlol.org/wiki/MQTT|MQTT]]) | * 192.168.8.34 h801 led strip controller "devlol/h19/mainroom/ceiling1" (see [[https://devlol.org/wiki/MQTT|MQTT]]) * 192.168.8.35 hp switch in area 42 * 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.62 '''printpi''' * 192.168.8.106 '''kopf''' Light * 192.168.8.177 '''craftui''' user:craft * 192.168.8.180 '''devradiosdr''' * 192.168.8.208 '''touchlol''' pi im Schaufenster<<BR>> * 192.168.8.222 '''zebra-zd220t''' - devlol/lable-drucker * '''Web-UI:''' zebra-zd220t.h19.devlol.org<<BR>> * 192.168.8.225 '''mainstripe''' * 192.168.8.248 Frige Light |
Line 26: | Line 49: |
Line 30: | Line 52: |
Line 33: | Line 54: |
= 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
- 192.168.8.1 router 'unten'
192.168.8.2 mqtt - https://git.devlol.org/devlol-systems/lxd-beta-nicht-cluster/-/tree/main/ansible-playbook/roles/mosquitto
- 192.168.8.3 keller
192.168.8.4 asterisk intern - https://git.devlol.org/devlol-systems/lxd-beta-nicht-cluster/-/tree/main/ansible-playbook/roles/asterisk
192.168.8.5 nodered zum rumspielen: http://192.168.8.5:1880/ - kein backup! - https://git.devlol.org/devlol-systems/lxd-beta-nicht-cluster/-/tree/main/ansible-playbook/roles/nodered
- 192.168.8.6 bimlights
- 192.168.8.7 devlock tür
- 192.168.8.8 pihole (rennt auf lolneti)
192.168.8.9 homeassistant test (kein backup!) https://git.devlol.org/devlol-systems/lxd-beta-nicht-cluster/-/tree/main/ansible-playbook/roles/homeassistant
- 192.168.8.10 lolneti - Traeger des ganeticluster
- 192.168.8.11 lolneticlust - Cluster IP
192.168.8.13 aptcacher auf port 3142 - https://git.devlol.org/devlol-systems/lxd-beta-nicht-cluster/-/tree/main/ansible-playbook/roles/aptcacher
- 192.168.8.16 screeninvader.local
192.168.8.17 devlol-gitlab-runner - https://git.devlol.org/devlol-systems/lxd-beta-nicht-cluster/-/tree/main/ansible-playbook/roles/gitlabrunner
- 192.168.8.18 ?
- 192.168.8.19 fileshare
Weboberfläche: http://192.168.8.19/#fileshare
- Rsync List: rsync --list-only rsync://192.168.8.19:/fileshare/
- Rsync download: rsync -r -v --progress rsync://192.168.8.19:/fileshare/ fileshare
Rsync upload: rsync -r -v --progress lokale_cooler_ordner rsync://192.168.8.19:/fileshare/
192.168.8.21 prometheus - https://git.devlol.org/devlol-systems/lxd-beta-nicht-cluster/-/tree/main/ansible-playbook/roles/prometheus
- 192.168.8.32 ?
192.168.8.33 h801 led strip controller "devlol/h19/mainroom/ceiling0" (see MQTT)
192.168.8.34 h801 led strip controller "devlol/h19/mainroom/ceiling1" (see MQTT)
- 192.168.8.35 hp switch in area 42
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.62 printpi
192.168.8.106 kopf Light
192.168.8.177 craftui user:craft
192.168.8.180 devradiosdr
192.168.8.208 touchlol pi im Schaufenster
192.168.8.222 zebra-zd220t - devlol/lable-drucker
Web-UI: zebra-zd220t.h19.devlol.org
192.168.8.225 mainstripe
- 192.168.8.248 Frige Light
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.