Another example, for the curious. This one hosts a web server entirely in
userspace. All the kernel sees are incoming and outgoing encrypted
WireGuard UDP packets.
package main
import (
"io"
"log"
"net"
"net/http"
"golang.zx2c4.com/wireguard/device"
On Wed Jan 13, 2021 at 9:14 PM CET, Posegga, Joachim wrote:
> I am trying to connect multiple wireguard clients behind the same
> NAT-Gateway to a Mikrotik server with a public IP. I am not yet sure
> where exactly the problem is, but it seems that only one client at a
> time can establish a tunnel
On Wed, 13 Jan 2021 20:14:46 +
"Posegga, Joachim" wrote:
> Dear all,
>
> I am trying to connect multiple wireguard clients behind the same NAT-Gateway
> to a Mikrotik server with a public IP. I am not yet sure where exactly the
> problem is, but it seems that only one client at a time can
"Jason A. Donenfeld" writes:
> On Wed, Jan 13, 2021 at 5:46 PM Toke Høiland-Jørgensen wrote:
>> 5. also requires CAP_SYS_ADMIN (and I think by extension, so does 3.,
>> and 4.). From 'man setns':
>>
>>Network, IPC, time, and UTS namespaces
>> In order to reassociate itself
Dear all,
I am trying to connect multiple wireguard clients behind the same NAT-Gateway
to a Mikrotik server with a public IP. I am not yet sure where exactly the
problem is, but it seems that only one client at a time can establish a tunnel.
Is this a known problem due to the UDP transport,
