Skip to content
This repository has been archived by the owner on Sep 29, 2024. It is now read-only.

LAN not reachable after a time #339

Open
sadden3194 opened this issue Nov 6, 2023 · 4 comments
Open

LAN not reachable after a time #339

sadden3194 opened this issue Nov 6, 2023 · 4 comments
Labels
bug Something isn't working WireGuard

Comments

@sadden3194
Copy link

sadden3194 commented Nov 6, 2023

Summary

Wireguard VPN connection active (Fritzbox router as Wireguard server), but no connection to LAN after unspecifc time.

Steps to reproduce

Import fritzbox wireguard config to the app.
My config looks like this:

[Interface]
PrivateKey = XXX
Address = 192.168.108.201/24
DNS = 192.168.108.250

[Peer]
PublicKey = XXX
PresharedKey = XXX
AllowedIPs = 192.168.108.0/24
Endpoint = vpn.myDomain.de:51888
PersistentKeepalive = 25

LAN: 192.168.108.0
DNS Server: 192.168.108.250 (Adguard)

What is the current bug behavior?

I am using your app on iphones and ipads. VPN connection works on demand and works without problems.
But after a while, I can't reach my local area network and dns resolution doesn't work anymore (because I cant reach my dns server 192.168.108.250):

For example: I can ping 8.8.8.8 with a response, but if I ping google.de I get no response.
If I try to ping the device IP (192.168.108.201) - I get no response.

Relevant logs and/or screenshots

I attached the logs
debug-20231106-131555 2.txt

@keeshux
Copy link
Member

keeshux commented Nov 11, 2023

Uhm this seems out of the Passepartout scope, it's an inherent bug of WireGuard as I see it.

@keeshux keeshux closed this as not planned Won't fix, can't repro, duplicate, stale Nov 11, 2023
@keeshux keeshux transferred this issue from passepartoutvpn/passepartout Nov 11, 2023
@keeshux keeshux reopened this Nov 11, 2023
@keeshux keeshux added bug Something isn't working WireGuard labels Nov 11, 2023
@sadden3194
Copy link
Author

With the original wireguard app I had not this problem.
Are you sure that this is not a bug of your app?

@keeshux
Copy link
Member

keeshux commented Nov 11, 2023

Then “sure” is not how I feel about it. 🤣 I keep this open.

@0xBF90E913
Copy link

I noticed that this problem occurs when there is a "PresharedKey" in the wg config. On other versions of WireGuard (or I don’t know what it depends on), where “PresharedKey” is missing in the config during generation, this error is not observed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working WireGuard
Projects
None yet
Development

No branches or pull requests

3 participants