> On Oct 28, 2020, at 5:07 PM, Pierre Emeriaud <petrus.lt+open...@gmail.com> > wrote: > > Le mar. 27 oct. 2020 à 23:46, j...@snoopy.net.nz <j...@snoopy.net.nz> a > écrit : >> >> >> >> Hi Pierre, >> >> The error may indicate that port 53 on 127.0.0.1 is already used by another >> service. This appears to be confirmed by your netstat example. This is >> probably a dns service. > > Thanks Joe. This is indeed a dns daemon, several in fact. But nothing > should prevent wireguard from using port 53 on any other IP address > than 127.0.0.1 here. (well, nothing but the code that has been > implemented) > Can you specify separate rdomains for the wg interfaces and still use port 53 on all plus a dns daemon? I have not experimented with any of this guidance.
- wg(4) listen on a specific interface / address Pierre Emeriaud
- Re: wg(4) listen on a specific interface / address Brian Brombacher
- Re: wg(4) listen on a specific interface / add... Pierre Emeriaud
- Re: wg(4) listen on a specific interface / address j...@snoopy.net.nz
- Re: wg(4) listen on a specific interface / add... Pierre Emeriaud
- Re: wg(4) listen on a specific interface /... Brian Brombacher
- Re: wg(4) listen on a specific interfa... Brian Brombacher
- Re: wg(4) listen on a specific in... Pierre Emeriaud
- Re: wg(4) listen on a specifi... Brian Brombacher
- Re: wg(4) listen on a spe... Pierre Emeriaud
- Re: wg(4) listen on a spe... Theo de Raadt
- Re: wg(4) listen on a spe... Pierre Emeriaud
- Re: wg(4) listen on a spe... Theo de Raadt
- Re: wg(4) listen on a specific interface /... Theo de Raadt
- Re: wg(4) listen on a specific interfa... Pierre Emeriaud
- Re: wg(4) listen on a specific in... Theo de Raadt