F5F Stay Refreshed Power Users Networks Accessing Wireguard VPN on local devices isn't working on Windows.

Accessing Wireguard VPN on local devices isn't working on Windows.

Accessing Wireguard VPN on local devices isn't working on Windows.

S
Stachun
Junior Member
12
11-05-2019, 07:32 PM
#1
Hello everyone, I've configured a Wireguard Server on my local Docker host and connected it to a NAS in the same home network. The VPN is functioning properly for internet access on both my Windows laptop and Android phone. However, I'm having trouble accessing the NAS from my laptop, even though it's reachable through the Android phone. Additionally, I can't see any of my other devices on the home network via the VPN. Should I need to adjust any settings for direct access or tunneling into my home network? Wireguard output if you'd like more details. Cheers
S
Stachun
11-05-2019, 07:32 PM #1

Hello everyone, I've configured a Wireguard Server on my local Docker host and connected it to a NAS in the same home network. The VPN is functioning properly for internet access on both my Windows laptop and Android phone. However, I'm having trouble accessing the NAS from my laptop, even though it's reachable through the Android phone. Additionally, I can't see any of my other devices on the home network via the VPN. Should I need to adjust any settings for direct access or tunneling into my home network? Wireguard output if you'd like more details. Cheers

P
PinqNoLag
Member
181
11-05-2019, 08:55 PM
#2
I don't have any background on Wireguard, but if you have a Debian-based Linux server, I can guide you through setting up a Client-to-Site VPN using PrintNOLink. It seems you're unlikely to enable Network Discovery, but providing the client IP will make it visible.
P
PinqNoLag
11-05-2019, 08:55 PM #2

I don't have any background on Wireguard, but if you have a Debian-based Linux server, I can guide you through setting up a Client-to-Site VPN using PrintNOLink. It seems you're unlikely to enable Network Discovery, but providing the client IP will make it visible.

J
Juliieh
Junior Member
27
11-05-2019, 11:35 PM
#3
Network Transcending isn't functioning for VPNs in general or specifically for Wireguard.
J
Juliieh
11-05-2019, 11:35 PM #3

Network Transcending isn't functioning for VPNs in general or specifically for Wireguard.

B
BlaseGames
Member
169
11-06-2019, 03:50 AM
#4
I believe the answer hinges on configuration details but would appreciate a correction from you. The explanation seems to mix concepts slightly; a Site-to-Site VPN typically allows seamless communication between two networks as if they were on the same subnet. A Client-to-Site setup, on the other hand, creates a separate network for the client and connects to it via a static route. The VPN acts as a router, hiding your internal network from direct discovery while enabling clients to find each other. Your understanding about broadcasting and discovery is partially correct, but the setup differs significantly between the two models.
B
BlaseGames
11-06-2019, 03:50 AM #4

I believe the answer hinges on configuration details but would appreciate a correction from you. The explanation seems to mix concepts slightly; a Site-to-Site VPN typically allows seamless communication between two networks as if they were on the same subnet. A Client-to-Site setup, on the other hand, creates a separate network for the client and connects to it via a static route. The VPN acts as a router, hiding your internal network from direct discovery while enabling clients to find each other. Your understanding about broadcasting and discovery is partially correct, but the setup differs significantly between the two models.

B
BramOnTheMove
Member
64
11-06-2019, 08:58 PM
#5
Display your current IP ranges. Ensure routes are configured on the router to direct traffic to the correct subnet. Confirm whether the data is coming from the server or client side. Add the permitted IP addresses to enable subnets for data transfer.
B
BramOnTheMove
11-06-2019, 08:58 PM #5

Display your current IP ranges. Ensure routes are configured on the router to direct traffic to the correct subnet. Confirm whether the data is coming from the server or client side. Add the permitted IP addresses to enable subnets for data transfer.

0
0_x
Member
157
11-06-2019, 09:59 PM
#6
The server is connected via its home network (192.168.178.1/24) through a VPN at 10.13.13.1/24, which uses WireGuard. You need to include your home network in the VPN configuration? The advice suggests a possible network setup issue, but it seems the Android device should still be reachable if the configuration works.
0
0_x
11-06-2019, 09:59 PM #6

The server is connected via its home network (192.168.178.1/24) through a VPN at 10.13.13.1/24, which uses WireGuard. You need to include your home network in the VPN configuration? The advice suggests a possible network setup issue, but it seems the Android device should still be reachable if the configuration works.

J
JamTheJoker
Member
102
11-06-2019, 10:21 PM
#7
Check if communication is possible from the laptop to the remote network. Identify which device serves as the VPN client. Prepare those details for inclusion in the WireGuard configuration with permitted IP ranges.
J
JamTheJoker
11-06-2019, 10:21 PM #7

Check if communication is possible from the laptop to the remote network. Identify which device serves as the VPN client. Prepare those details for inclusion in the WireGuard configuration with permitted IP ranges.

Q
QUESALUPAX
Junior Member
8
11-13-2019, 01:26 AM
#8
I updated Wireguard with a distinct Docker image "place1/wg-access-server". It functions well when IP addresses are used instead of hostnames. Using local DNS for that should be a good idea.
Q
QUESALUPAX
11-13-2019, 01:26 AM #8

I updated Wireguard with a distinct Docker image "place1/wg-access-server". It functions well when IP addresses are used instead of hostnames. Using local DNS for that should be a good idea.