No Address propperty in output server config about wgserverforwindows HOT 4 CLOSED

Ahh ok, I guess because you're not using internet sharing, WireGuard needs to know what interface to listen on locally.

I'll make this an enhancement to add the address property to the server config. Have to verify that it doesn't break anything else.

from wgserverforwindows.

Hi @b4tman, this is intentional. The server configuration file does not need to know its own public address. That property is targeted only to the client configs, which obviously need to know what endpoint they're connecting to.

I can confirm that my server configuration file has only ListenPort and PrivateKey, and I am able to connect successfully.

from wgserverforwindows.

Hello @micahmo. Yes WireGuard client can connect to server without Address in server config. But when no internet sharing or routing enabled, using only point-to-point network, clients unable to connect to server directly by it's VPN Address. I mean appications like RDP etc.
When I add Address= to server config, evrything works fine. May be I miss something?

from wgserverforwindows.

Just a note that while investigating #26, I discovered that putting the Address line in the server configuration file breaks the WireGuard configuration sync. You can see if I try to sync the configuration with that line, WireGuard rejects it.

> wg.exe syncconf wg_server $env:appdata\WS4W\server_wg\wg_server.conf
Line unrecognized: `Address=10.254.0.1'
Configuration parsing error

I'm not sure how adding that line fixed your issue. Maybe it was a coincidence. But I've rolled back that change for now. If you can figure out a way to add it so that WireGuard is happy with, I can put it back.

from wgserverforwindows.