fosrl / fosrl/windows

Windows client struggles to maintain connectivity with private resources on lan

Open
#31 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
22
Forks
10
Avg merge
1m
Merged PRs (30d)
1

Description

### Describe the Bug

I recently migrated from Tailscale to Pangolin, and Tailscale was consistent in that connecting to anything in my tailnet felt exactly the same. With Pangolin, it seems like the pangolin windows client really struggles. The linux machine clients seem fine when connecting to newt private resources, but my connection constantly disconnects and reconnects to a server on the same LAN with Pangolin, and it sometimes switches to relay and then back to holepunch with the remote server running newt.

[pangolinclientlogs_20260307_redacted.txt](https://github.com/user-attachments/files/25822450/pangolinclientlogs_20260307_redacted.txt)

### Environment

- OS Type & Version: (e.g., Ubuntu 22.04)
- Pangolin Version: ee-1.16.2
- Gerbil Version: 1.3.0
- Traefik Version: 3.6.9
- Newt Version: docker compose 1.10.2
- Client Version: Windows 0.7.1

### To Reproduce

site two is a private resource pointing to 192.168.0.0/24 (remote)
site four is a private resource pointing to 10.0.0.0/24 (local, same subnet as windows user client with issue)
Pangolin server is hosted on a vps, with UDP 21820 and 51820 open and TCP 80 and 443 open.

dnsoverride=false, dns over tunnel = false.

status json:
{
"connected": true,
"registered": true,
"terminated": false,
"version": "0.7.1",
"agent": "Pangolin Windows",
"orgId": "--ORG REDACTED--",
"peers": {
"2": {
"siteId": 2,
"name": "docker04-vm",
"connected": true,
"rtt": 38452500,
"lastSeen": "2026-03-08T01:42:47.6497075-06:00",
"endpoint": "--LOCAL PUBLIC IP REDACTED--",
"isRelay": false
},
"4": {
"siteId": 4,
"name": "docker01-vm",
"connected": true,
"rtt": 79374900,
"lastSeen": "2026-03-08T01:42:51.8179768-06:00",
"endpoint": "--REMOTE PUBLIC IP REDACTED--",
"isRelay": true
}
},
"networkSettings": {
"ipv4_addresses": [
"100.55.55.1"
],
"ipv4_included_routes": [
{
"destination_address": "100.66.66.0",
"subnet_mask": "255.255.255.0"
},
{
"destination_address": "192.168.0.0",
"subnet_mask": "255.255.255.0"
},
{
"destination_address": "10.0.0.0",
"subnet_mask": "255.255.255.0"
}
],
"ipv4_subnet_masks": [
"255.255.255.0"
],
"mtu": 1280
}
}

### Expected Behavior

pangolin client should connect to local and remote machines consistently, without disconnecting/reconnecting or switching back and forth between relay and holepunch.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.