Solved
Speedport Smart 4 Plus: VPN / Wireguard Problem
6 months ago
Servus!
Ich habe ein Problem mir einen VPN -Zugang über meinen Speedport Smart 4 Plus einzurichten.
DynDNS läuft (soweit ich das beurteilen kann) so wie es muss.
Die im Speedport hinterlegte Öffentliche WAN-IP ist auch identisch mit der bei ipv64 angezeigten IPv4/A Adresse.
Wenn ich jetzt in den Reiter Netzwerk/Virtuelles Netz ( VPN ) gehe und dort einen VPN -Zugang anlege, den QR Code mit der Wireguard App auf meinem iPhone scanne, kriege ich aber keine Verbindung in mein Netzwerk. Die App legt den Tunnel an:
Wenn ich ihn aktiviere bleibt es beim Speedport beim VPN -Reiter weiterhin bei "Kein Client verbunden" und auch in den Systemmeldungen ist nichts zu einer VPN Verbindung zu finden.
Beim iPhone (natürlich im Mobilfunk und nicht im WiFi) funktioniert dann auch nichts mehr, kein Internet aber auch der Router lässt sich nicht aufrufen.
Jemand eine Idee? Danke euch!
804
11
6 months ago
Was zeigt das Log der WireGuard App auf dem iPhone?
1
Answer
from
6 months ago
2024-10-24 22:49:30.099379: [APP] App version: 1.0.16 (27)
2024-10-24 22:49:51.206778: [APP] startActivation: Entering (tunnel: Home)
2024-10-24 22:49:51.208842: [APP] startActivation: Starting tunnel
2024-10-24 22:49:51.209319: [APP] startActivation: Success
2024-10-24 22:49:51.221484: [APP] Tunnel 'Home' connection status changed to 'connecting'
2024-10-24 22:49:51.330593: [NET] App version: 1.0.16 (27)
2024-10-24 22:49:51.330657: [NET] Starting tunnel from the app
2024-10-24 22:49:51.538584: [NET] DNS64: mapped (Öffentliche WAN-IP) to itself.
2024-10-24 22:49:51.540081: [NET] Attaching to interface
2024-10-24 22:49:51.540780: [NET] UAPI: Updating private key
2024-10-24 22:49:51.541002: [NET] Routine: event worker - started
2024-10-24 22:49:51.541181: [NET] Routine: encryption worker 1 - started
2024-10-24 22:49:51.541217: [NET] Routine: handshake worker 4 - started
2024-10-24 22:49:51.541252: [NET] Routine: encryption worker 4 - started
2024-10-24 22:49:51.541269: [NET] Routine: encryption worker 5 - started
2024-10-24 22:49:51.541314: [NET] Routine: decryption worker 4 - started
2024-10-24 22:49:51.541350: [NET] Routine: decryption worker 5 - started
2024-10-24 22:49:51.541352: [NET] UAPI: Removing all peers
2024-10-24 22:49:51.541400: [NET] Routine: encryption worker 6 - started
2024-10-24 22:49:51.541394: [NET] Routine: decryption worker 2 - started
2024-10-24 22:49:51.541410: [NET] Routine: handshake worker 5 - started
2024-10-24 22:49:51.541423: [NET] Routine: handshake worker 2 - started
2024-10-24 22:49:51.541432: [NET] Routine: handshake worker 1 - started
2024-10-24 22:49:51.541504: [NET] Routine: encryption worker 2 - started
2024-10-24 22:49:51.541545: [NET] Routine: encryption worker 3 - started
2024-10-24 22:49:51.541566: [NET] Routine: handshake worker 6 - started
2024-10-24 22:49:51.541592: [NET] Routine: decryption worker 6 - started
2024-10-24 22:49:51.541648: [NET] Routine: decryption worker 3 - started
2024-10-24 22:49:51.541663: [NET] Routine: TUN reader - started
2024-10-24 22:49:51.541698: [NET] Routine: decryption worker 1 - started
2024-10-24 22:49:51.541768: [NET] Routine: handshake worker 3 - started
2024-10-24 22:49:51.542065: [NET] peer(sglY…dD3M) - UAPI: Created
2024-10-24 22:49:51.542137: [NET] peer(sglY…dD3M) - UAPI: Updating preshared key
2024-10-24 22:49:51.542217: [NET] peer(sglY…dD3M) - UAPI: Updating endpoint
2024-10-24 22:49:51.542298: [NET] peer(sglY…dD3M) - UAPI: Updating persistent keepalive interval
2024-10-24 22:49:51.542357: [NET] peer(sglY…dD3M) - UAPI: Removing all allowedips
2024-10-24 22:49:51.542410: [NET] peer(sglY…dD3M) - UAPI: Adding allowedip
2024-10-24 22:49:51.543036: [NET] UDP bind has been updated
2024-10-24 22:49:51.543115: [NET] Routine: receive incoming v6 - started
2024-10-24 22:49:51.543113: [NET] Routine: receive incoming v4 - started
2024-10-24 22:49:51.543163: [NET] peer(sglY…dD3M) - Starting
2024-10-24 22:49:51.543292: [NET] peer(sglY…dD3M) - Sending keepalive packet
2024-10-24 22:49:51.543343: [NET] peer(sglY…dD3M) - Routine: sequential receiver - started
2024-10-24 22:49:51.543380: [NET] peer(sglY…dD3M) - Sending handshake initiation
2024-10-24 22:49:51.543521: [NET] peer(sglY…dD3M) - Routine: sequential sender - started
2024-10-24 22:49:51.544246: [NET] Interface state was Down, requested Up, now Up
2024-10-24 22:49:51.544338: [NET] Device started
2024-10-24 22:49:51.544491: [NET] Tunnel interface is utun8
2024-10-24 22:49:51.546583: [APP] Tunnel 'Home' connection status changed to 'connected'
2024-10-24 22:49:51.546629: [NET] Network change detected with satisfied route and interface order [pdp_ip0]
2024-10-24 22:49:51.547272: [NET] DNS64: mapped (Öffentliche WAN-IP) to itself.
2024-10-24 22:49:51.547449: [NET] peer(sglY…dD3M) - UAPI: Updating endpoint
2024-10-24 22:49:51.547706: [NET] Network change detected with satisfied route and interface order [pdp_ip0, utun8]
2024-10-24 22:49:51.547974: [NET] Routine: receive incoming v4 - stopped
2024-10-24 22:49:51.548154: [NET] Routine: receive incoming v6 - stopped
2024-10-24 22:49:51.548182: [NET] DNS64: mapped (Öffentliche WAN-IP) to itself.
2024-10-24 22:49:51.548312: [NET] peer(sglY…dD3M) - UAPI: Updating endpoint
2024-10-24 22:49:51.548453: [NET] UDP bind has been updated
2024-10-24 22:49:51.548472: [NET] Routine: receive incoming v4 - started
2024-10-24 22:49:51.548495: [NET] Routine: receive incoming v6 - started
2024-10-24 22:49:51.548556: [NET] Routine: receive incoming v6 - stopped
2024-10-24 22:49:51.548608: [NET] Routine: receive incoming v4 - stopped
2024-10-24 22:49:51.548831: [NET] UDP bind has been updated
2024-10-24 22:49:51.548840: [NET] Routine: receive incoming v4 - started
2024-10-24 22:49:51.548848: [NET] Routine: receive incoming v6 - started
2024-10-24 22:49:56.209853: [APP] Status update notification timeout for tunnel 'Home'. Tunnel status is now 'connected'.
2024-10-24 22:49:56.571443: [NET] peer(sglY…dD3M) - Handshake did not complete after 5 seconds, retrying (try 2)
2024-10-24 22:49:56.571739: [NET] peer(sglY…dD3M) - Sending handshake initiation
2024-10-24 22:50:01.781196: [NET] Network change detected with satisfied route and interface order [pdp_ip0, utun8]
2024-10-24 22:50:01.782153: [NET] DNS64: mapped (Öffentliche WAN-IP) to itself.
2024-10-24 22:50:01.782455: [NET] peer(sglY…dD3M) - UAPI: Updating endpoint
2024-10-24 22:50:01.782537: [NET] peer(sglY…dD3M) - Sending handshake initiation
2024-10-24 22:50:01.783620: [NET] Routine: receive incoming v4 - stopped
2024-10-24 22:50:01.783732: [NET] Routine: receive incoming v6 - stopped
2024-10-24 22:50:01.784026: [NET] UDP bind has been updated
2024-10-24 22:50:01.784057: [NET] Routine: receive incoming v4 - started
2024-10-24 22:50:01.784085: [NET] Routine: receive incoming v6 - started
2024-10-24 22:50:06.303855: [NET] Network change detected with satisfied route and interface order [pdp_ip0, utun8]
2024-10-24 22:50:06.304804: [NET] DNS64: mapped (Öffentliche WAN-IP) to itself.
2024-10-24 22:50:06.305063: [NET] peer(sglY…dD3M) - UAPI: Updating endpoint
2024-10-24 22:50:06.305324: [NET] Routine: receive incoming v4 - stopped
2024-10-24 22:50:06.305395: [NET] Routine: receive incoming v6 - stopped
2024-10-24 22:50:06.305814: [NET] UDP bind has been updated
2024-10-24 22:50:06.305825: [NET] Routine: receive incoming v4 - started
2024-10-24 22:50:06.305851: [NET] Routine: receive incoming v6 - started
2024-10-24 22:50:06.971811: [NET] peer(sglY…dD3M) - Handshake did not complete after 5 seconds, retrying (try 2)
2024-10-24 22:50:06.972109: [NET] peer(sglY…dD3M) - Sending handshake initiation
2024-10-24 22:50:12.024948: [NET] peer(sglY…dD3M) - Handshake did not complete after 5 seconds, retrying (try 2)
2024-10-24 22:50:12.025160: [NET] peer(sglY…dD3M) - Sending handshake initiation
2024-10-24 22:50:17.107261: [NET] peer(sglY…dD3M) - Sending handshake initiation
2024-10-24 22:50:22.315902: [NET] peer(sglY…dD3M) - Handshake did not complete after 5 seconds, retrying (try 2)
2024-10-24 22:50:22.316266: [NET] peer(sglY…dD3M) - Sending handshake initiation
2024-10-24 22:50:27.319222: [NET] peer(sglY…dD3M) - Handshake did not complete after 5 seconds, retrying (try 2)
2024-10-24 22:50:27.319652: [NET] peer(sglY…dD3M) - Sending handshake initiation
Unlogged in user
Answer
from
6 months ago
Auf dem iPhone: Einstellungen-> VPN : Steht da der Schalter auf VPN -Status=Verbunden?
1
Answer
from
6 months ago
Ja:
Unlogged in user
Answer
from
6 months ago
Um die Komplexität zu reduzieren, funktioniert es denn ohne DynDNS, also wenn du die öffentliche WAN IP in der Wireguard Konfiguration verwendest?
1
Answer
from
6 months ago
Nein, im Log bleibt es bei Handshake did not complete after 5 seconds, retrying (try 2)
Ich nehme an, dass das Problem ist....?
Unlogged in user
Answer
from
5 months ago
Lösung gefunden? Habe das gleiche Problem mit dem Handshake.
2
Answer
from
3 months ago
Leider nicht...
Answer
from
3 months ago
Hallo @durwi & @vinc3nt,
ich kann euch leider keine Lösung präsentieren :-( Möchte euch aber unseren Digital Home Service empfehlen.
Grüße
Alexander
Unlogged in user
Answer
from
Accepted Solution
accepted by
2 months ago
Ich habe mittlerweile das Problem und die Lösung in meinem Fall gefunden. Mein ISP hatte mir keine eigene öffentliche IPv4 Adresse zugewiesen gehabt, sondern aus einem Pool. Das Problem ist nunmehr behoben, habe meine eigene öffentliche IPv4 Adresse und die Verbindung über Wireguard funktioniert einwandfrei.
1
Answer
from
2 months ago
Danke für das Update. D.h. der ISP ist gar nicht die Telekom? Das Problem mit der nicht-öffentlichen IP4 Adresse hätte man mit dieser Information vielleicht entdeckt.
Unlogged in user
Answer
from
Unlogged in user
Ask
from