Tester für WireGuard Adapter gesucht

[Grizzelbee]

@negalein sagte in Tester für WireGuard Adapter gesucht:

Ich hab zB User, die den selben Key auf mehreren Geräten verwenden.
Für Laptop und Handy zB gibt es nicht für jedes Gerät einen eigenen Key.
Muss ich mal überlegen, ob ich pro Gerät einen Key erstelle. Ist ja eh gleich erledigt.

Du kannst natürlich auch allen Einträgen den selben Device-namen geben. Dem Adapter ist das egal.
Unabhängig davon werde ich den Fehler aber noch abfangen. Der Adapter sollte deswegen nicht so aus der Kurve gehen ...

[Grizzelbee]

@negalein und alle anderen:
Habe gerade einen neuen Fix veröffentlicht:

v1.5.10 (2023-08-17)

• (grizzelbee) Fix: Adapter doesn't crash anymore when user or device name is missing in config.

[Shadowhunter23]

@grizzelbee danke für den Adapter. Hab allerdings noch eine Frage.
Das Abfrageintervall steht als Standard auf 120 Sekunden.
Was wäre das kleinste Abfrageintervall was man einstellen kann?
Oder hätte ein kleineres Abfrageintervall irgendwelche Nachteile?

[David G.]

@shadowhunter23

Ich hab es auf 30 stehen.
Bisher keine Nebeneffekte erkannt.

[Grizzelbee]

Hallo SchadowHunter,

@shadowhunter23 sagte in Tester für WireGuard Adapter gesucht:

Was wäre das kleinste Abfrageintervall was man einstellen kann?

Der kleinste ist im Grunde 1 Sekunde. Über Sinn und Unsinn eines so kurzen Intervalls kann man sicherlich diskutieren.

Oder hätte ein kleineres Abfrageintervall irgendwelche Nachteile?

Ja. Je kleiner der Intervall desto höher die durch die Abfrage ausgelöste Systemlast. Deshalb habe ich 120 Sekunden als default genommen - um auch schwächere Systeme nicht sofort beim ersten Start zu zerlegen. Ich selbst habe bei mir 20 Sekunden eingestellt. Der kürzeste sinnvolle Intervall ist im Grunde die Zeit, die das jeweilige System - unter ca. 75% Last - benötigt um die Anfrage komplett zu verarbeiten - plus (mindestens) eine Sekunde. Sonst überlappen sich die Abfragen.

[Negalein]

@Grizzelbee

mit 1.6.2 kommen haufenweise dieser Meldungen.

Node.js: v18.19.0
NPM: 10.2.3
Admin: 6.15.2
JS-Controller: 5.0.17

2024-03-26 18:14:22.366  - warn: wireguard.0 (1754650) Setting Nega-wg0.peers.PBQtaueqfB/GxwU6AElLQWXiRRlIPtBofbK1By9oBFY=.connected to false is senseless. Please open an issue on github and provide a debug log sowing the occurrence of this issue.
2024-03-26 18:14:22.366  - warn: wireguard.0 (1754650) Setting Nega-wg0.users to null is senseless. Please open an issue on github and provide a debug log sowing the occurrence of this issue.

Issue hab ich erstellt.

[David G.]

Hat es von euch schonmal jemand geschafft, auf die wireguard Daten einer Fritzbox zu kommen?

[Grizzelbee]

@david-g sagte in Tester für WireGuard Adapter gesucht:

Hat es von euch schonmal jemand geschafft, auf die wireguard Daten einer Fritzbox zu kommen?

Ich befürchte dass du die Frage falsch gestellt hast - ich denke sie müsste lauten ob es schon ein jemand versucht hat an die Daten zu kommen.
Ich für meinen Teil kann sagen dass ich schon einmal darüber nachgedacht habe - mehr aber auch nicht.
Das wäre schon eine Menge Aufwand das nur zu versuchen und das bei völlig ungewissem Ausgang der Aktion. Deshalb scheue ich den Aufwand.
Wenn jemand klar sagen könnte ob u d wie man an die Daten kommt, würde ich es einbauen - aber für Forschung fehlen mir aktuell die Zeit und die Nerven.

Liebe Grüße
Grizzelbee

[David G.]

@grizzelbee

Ich hab zwar so keine Ahnung vom Thema, aber ich google das heute abend mal ^^.

Ich selber habe wireguard im LCX (hatte überlegt zu wechseln), denke aber es werden immer mehr Leute die es in einer Fritte haben.

[Negalein]

@grizzelbee

Hallo

Ich hab in WG einen neuen Client hinzugefügt.
Dieser wird mir in ioB nicht angezeigt.

2025-07-14 07:58:20.560 - info: host.ioBroker instance system.adapter.wireguard.0 in version "1.8.0" started with pid 78643
2025-07-14 07:58:21.459 - debug: wireguard.0 (78643) Redis Objects: Use Redis connection: 0.0.0.0:9001
2025-07-14 07:58:21.514 - debug: wireguard.0 (78643) Objects client ready ... initialize now
2025-07-14 07:58:21.519 - debug: wireguard.0 (78643) Objects create System PubSub Client
2025-07-14 07:58:21.520 - debug: wireguard.0 (78643) Objects create User PubSub Client
2025-07-14 07:58:21.684 - debug: wireguard.0 (78643) Objects client initialize lua scripts
2025-07-14 07:58:21.690 - debug: wireguard.0 (78643) Objects connected to redis: 0.0.0.0:9001
2025-07-14 07:58:21.759 - debug: wireguard.0 (78643) Redis States: Use Redis connection: 0.0.0.0:9000
2025-07-14 07:58:21.803 - debug: wireguard.0 (78643) States create System PubSub Client
2025-07-14 07:58:21.804 - debug: wireguard.0 (78643) States create User PubSub Client
2025-07-14 07:58:21.896 - debug: wireguard.0 (78643) States connected to redis: 0.0.0.0:9000
2025-07-14 07:58:21.972 - debug: wireguard.0 (78643) Plugin sentry Initialize Plugin (enabled=true)
2025-07-14 07:58:22.277 - info: wireguard.0 (78643) starting. Version 1.8.0 in /opt/iobroker/node_modules/iobroker.wireguard, node: v20.19.1, js-controller: 7.0.7
2025-07-14 07:58:22.377 - info: wireguard.0 (78643) There is 1 wireguard host to monitor.
2025-07-14 07:58:22.426 - debug: wireguard.0 (78643) _knownInterfaces={"Nega-wg0":{"id":"wireguard.0.Nega-wg0","online":false}}
2025-07-14 07:58:22.426 - info: wireguard.0 (78643) Started 30 seconds monitoring interval for host [Nega]
2025-07-14 07:58:52.426 - debug: wireguard.0 (78643) Retrieving WireGuard status of host [Nega] on address [10.0.1.204]
2025-07-14 07:58:52.427 - debug: wireguard.0 (78643) Trying to reach host 10.0.1.204.
2025-07-14 07:58:52.427 - debug: wireguard.0 (78643) Connecting to host: [10.0.1.204] on port 22
2025-07-14 07:58:52.480 - debug: wireguard.0 (78643) ssh client :: authenticated
2025-07-14 07:58:52.480 - debug: wireguard.0 (78643) Executing command [sudo wg show all dump] on host 10.0.1.204.
2025-07-14 07:58:52.646 - debug: wireguard.0 (78643) Stream :: close
2025-07-14 07:58:52.647 - debug: wireguard.0 (78643) received rawdata: wg0 xxxxxxxxxx xxxxxxxxxx 51820 off
2025-07-14 07:58:52.648 - debug: wireguard.0 (78643) Workdata: [["wg0","xxxxxxxxxx/hdWQ=","xxxxxxxxxx","51820","off"],["wg0","xxxxxxxxxx","xxxxxxxxxx","(none)","10.252.1.1/32","0","0","0","off"],["wg0","xxxxxxxxxx","xxxxxxxxxx","(none)","10.252.1.2/32","0","0","0","off"],["wg0","xxxxxxxxxx","xxxxxxxxxx","(none)","10.252.1.5/32","0","0","0","off"],["wg0","xxxxxxxxxx","xxxxxxxxxx","(none)","10.252.1.6/32","0","0","0","off"],["wg0","xxxxxxxxxx","xxxxxxxxxx","100.65.12.60:55038","10.252.1.7/32","1752472647","132884","28060","off"],["wg0","xxxxxxxxxx","xxxxxxxxxx","185.129.173.57:60979","10.252.1.3/32","1752472662","210016","1609792","off"],[""]]
2025-07-14 07:58:52.648 - debug: wireguard.0 (78643) New Interface: wg0. Initialize object.
2025-07-14 07:58:52.649 - debug: wireguard.0 (78643) Host: Nega has 1 wireguard interface(s).
2025-07-14 07:58:52.649 - debug: wireguard.0 (78643) baseId: Nega-wg0
2025-07-14 07:58:52.650 - debug: wireguard.0 (78643) setAllKnownInterfacesOnlineState: _knownInterfaces: {"Nega-wg0":{"id":"wireguard.0.Nega-wg0","online":true}}
2025-07-14 07:58:52.651 - debug: wireguard.0 (78643) Setting Nega-wg0.peers to null is senseless.
2025-07-14 07:58:52.651 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on GitHub and fix your config.
2025-07-14 07:58:52.651 - debug: wireguard.0 (78643) Setting Nega-wg0.peers.xxxxxxxxxx to null is senseless.
2025-07-14 07:58:52.651 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on GitHub and fix your config.
2025-07-14 07:58:52.651 - debug: wireguard.0 (78643) Setting Nega-wg0.peers.xxxxxxxxxx.allowedIps to null is senseless.
2025-07-14 07:58:52.651 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on GitHub and fix your config.
2025-07-14 07:58:52.652 - debug: wireguard.0 (78643) Setting Nega-wg0.peers.xxxxxxxxxx to null is senseless.
2025-07-14 07:58:52.652 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on GitHub and fix your config.
2025-07-14 07:58:52.652 - debug: wireguard.0 (78643) Setting Nega-wg0.peers.xxxxxxxxxx.allowedIps to null is senseless.
2025-07-14 07:58:52.652 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on GitHub and fix your config.
2025-07-14 07:58:52.652 - debug: wireguard.0 (78643) Setting Nega-wg0.peers.xxxxxxxxxx to null is senseless.
2025-07-14 07:58:52.652 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on GitHub and fix your config.
2025-07-14 07:58:52.653 - debug: wireguard.0 (78643) Setting Nega-wg0.peers.xxxxxxxxxx.allowedIps to null is senseless.
2025-07-14 07:58:52.653 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on GitHub and fix your config.
2025-07-14 07:58:52.653 - debug: wireguard.0 (78643) Setting Nega-wg0.peers.xxxxxxxxxx to null is senseless.
2025-07-14 07:58:52.653 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on GitHub and fix your config.
2025-07-14 07:58:52.653 - debug: wireguard.0 (78643) Setting Nega-wg0.peers.xxxxxxxxxx.allowedIps to null is senseless.
2025-07-14 07:58:52.653 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on GitHub and fix your config.
2025-07-14 07:58:52.653 - debug: wireguard.0 (78643) Setting Nega-wg0.peers.xxxxxxxxxx to null is senseless.
2025-07-14 07:58:52.653 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on GitHub and fix your config.
2025-07-14 07:58:52.654 - debug: wireguard.0 (78643) Setting Nega-wg0.peers.xxxxxxxxxx.allowedIps to null is senseless.
2025-07-14 07:58:52.654 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on GitHub and fix your config.
2025-07-14 07:58:52.654 - debug: wireguard.0 (78643) Setting Nega-wg0.peers.YpcvgzbUTpuE5fptixxxxxxxxxx to null is senseless.
2025-07-14 07:58:52.654 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on GitHub and fix your config.
2025-07-14 07:58:52.654 - debug: wireguard.0 (78643) Setting Nega-wg0.peers.YpcvgzbUTpuE5fptixxxxxxxxxx.allowedIps to null is senseless.
2025-07-14 07:58:52.654 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on GitHub and fix your config.
2025-07-14 07:58:52.654 - debug: wireguard.0 (78643) Setting Nega-wg0.users to null is senseless.
2025-07-14 07:58:52.654 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on GitHub and fix your config.
2025-07-14 07:58:52.654 - debug: wireguard.0 (78643) Setting Nega-wg0.users.Nega to null is senseless.
2025-07-14 07:58:52.654 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on GitHub and fix your config.
2025-07-14 07:58:52.654 - debug: wireguard.0 (78643) Setting Nega-wg0.users.Max to null is senseless.
2025-07-14 07:58:52.654 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on GitHub and fix your config.
2025-07-14 07:58:52.654 - debug: wireguard.0 (78643) Setting Nega-wg0.users.Margret to null is senseless.
2025-07-14 07:58:52.655 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on GitHub and fix your config.
2025-07-14 07:58:52.655 - debug: wireguard.0 (78643) Setting Nega-wg0.users.Dina to null is senseless.
2025-07-14 07:58:52.655 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on GitHub and fix your config.
2025-07-14 07:58:52.655 - debug: wireguard.0 (78643) Setting Nega-wg0.users.Kloane to null is senseless.
2025-07-14 07:58:52.655 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on GitHub and fix your config.
2025-07-14 07:58:52.655 - debug: wireguard.0 (78643) Setting Nega-wg0.users.Mario to null is senseless.
2025-07-14 07:58:52.655 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on GitHub and fix your config.
2025-07-14 07:58:52.672 - debug: wireguard.0 (78643) Error while getObject: TypeError: Cannot read properties of null (reading 'common')
2025-07-14 07:58:52.673 - debug: wireguard.0 (78643) Error while getObject: TypeError: Cannot read properties of null (reading 'common')
2025-07-14 07:58:52.674 - debug: wireguard.0 (78643) Error while getObject: TypeError: Cannot read properties of null (reading 'common')
2025-07-14 07:58:52.675 - debug: wireguard.0 (78643) Error while getObject: TypeError: Cannot read properties of null (reading 'common')
2025-07-14 07:58:52.675 - debug: wireguard.0 (78643) Error while getObject: TypeError: Cannot read properties of null (reading 'common')
2025-07-14 07:58:52.675 - debug: wireguard.0 (78643) Error while getObject: TypeError: Cannot read properties of null (reading 'common')
2025-07-14 07:58:52.676 - debug: wireguard.0 (78643) Error while getObject: TypeError: Cannot read properties of null (reading 'common')
2025-07-14 07:58:52.676 - debug: wireguard.0 (78643) Error while getObject: TypeError: Cannot read properties of null (reading 'common')
2025-07-14 07:58:52.676 - debug: wireguard.0 (78643) Error while getObject: TypeError: Cannot read properties of null (reading 'common')
2025-07-14 07:58:52.677 - debug: wireguard.0 (78643) Error while getObject: TypeError: Cannot read properties of null (reading 'common')
2025-07-14 07:58:52.677 - debug: wireguard.0 (78643) Error while getObject: TypeError: Cannot read properties of null (reading 'common')
2025-07-14 07:58:52.677 - debug: wireguard.0 (78643) Error while getObject: TypeError: Cannot read properties of null (reading 'common')
2025-07-14 07:58:52.677 - debug: wireguard.0 (78643) Error while getObject: TypeError: Cannot read properties of null (reading 'common')
2025-07-14 07:58:52.677 - debug: wireguard.0 (78643) Error while getObject: TypeError: Cannot read properties of null (reading 'common')
2025-07-14 07:58:52.677 - debug: wireguard.0 (78643) Error while getObject: TypeError: Cannot read properties of null (reading 'common')
2025-07-14 07:58:52.677 - debug: wireguard.0 (78643) Error while getObject: TypeError: Cannot read properties of null (reading 'common')
2025-07-14 07:58:52.677 - debug: wireguard.0 (78643) Error while getObject: TypeError: Cannot read properties of null (reading 'common')

Es geht um diesen Client

2025-07-14 07:58:52.654 - debug: wireguard.0 (78643) Setting Nega-wg0.peers.YpcvgzbUTpuE5fptixxxxxxxxxx to null is senseless.
2025-07-14 07:58:52.654 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on GitHub and fix your config.
2025-07-14 07:58:52.654 - debug: wireguard.0 (78643) Setting Nega-wg0.peers.YpcvgzbUTpuE5fptixxxxxxxxxx.allowedIps to null is senseless.
2025-07-14 07:58:52.654 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on 
2025-07-14 07:58:52.655 - debug: wireguard.0 (78643) Setting Nega-wg0.users.Mario to null is senseless.
2025-07-14 07:58:52.655 - debug: wireguard.0 (78643) This usually only happens when you misconfigure this adapter. Please read the documentation on GitHub and fix your config.

[Negalein]

@grizzelbee

zum Test hab ich mal alle Objekte gelöscht und Adapter neu gestartet.
Jetzt kommen keine Objekte mehr.

---

PS: mit 1.7.0 ist wieder alles da.
Ausser den Namen in den Objekten.