* Bind WG to listen on specific interface instead of 0.0.0.0
@ 2019-08-02 23:26 Max
0 siblings, 0 replies; only message in thread
From: Max @ 2019-08-02 23:26 UTC (permalink / raw)
To: wireguard
[-- Attachment #1.1: Type: text/plain, Size: 690 bytes --]
Hello,
I'm very much enjoying WireGuard. Thanks for all the hardwork!
I am currently running WG on a high port but would like to use it on port
53. It currently will not load on 53, I think because my system has
systemd-resolved running that is bound to 53 on localhost only.
I've tried a bit of Google-ing, I've read through the man pages for wg and
wg-quick I don't seen an option to restrict the interfaces or IPs on which
wg tries to bind [the port].
Is there something I'm missing or some other solution? I'd rather not have
to remove systemd-resolved. I did stop systemd-resolved and start wg on
port 53 which gets wg running but breaks local DNS resolution.
Thanks,
Max
[-- Attachment #1.2: Type: text/html, Size: 1480 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-08-25 15:51 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-08-02 23:26 Bind WG to listen on specific interface instead of 0.0.0.0 Max
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).