2ae74e2fb3a0389502428babce14531b8b349576
howto/wireguard.md
| ... | ... | @@ -179,3 +179,11 @@ You can add cron entries to periodically "re-resolve" the DNS: |
| 179 | 179 | ```sh |
| 180 | 180 | * * * * * /path-to-the-script/reresolve-dns.sh |
| 181 | 181 | ``` |
| 182 | + |
|
| 183 | +## Windows client note |
|
| 184 | + |
|
| 185 | +The official WireGuard for Windows client may reject configurations where multiple tunnels have overlapping `AllowedIPs` ranges. If you need such a setup, an unofficial fork that removes this restriction is available at <https://github.com/TES286-org/wireguard-windows>. |
|
| 186 | + |
|
| 187 | +This is **not** official WireGuard or DN42 software and has not been independently audited. Use it at your own risk and review the code before deployment. |
|
| 188 | + |
|
| 189 | +For DN42, ensure the client does not install routes automatically; route selection should be managed by BGP or an external routing program. Do not use overlapping `AllowedIPs` unless you understand the data-plane and routing implications. |
|
| ... | ... | \ No newline at end of file |