Hi David,
thanks for your help.
Currently, serverB has only 1 wireguard interface, which contains both peers
(serverA and serverC). It is no issue to create a second wireguard interface
though.
In the configuration you propose (I think there is a typo and the third config
is for serverC), I d
> On 10 Aug 2024, at 18:18, 04-psyche.tot...@icloud.com wrote:
>
> Hi all,
>
> I am working on a wireguard network.
>
> I have a setup like this:
>
> serverA (10.0.0.0) => serverB (10.0.0.1) => serverC (10.0.0.2)
>
> - serverA connects to serverB with AllowedIPs = 0.0.0.0/0
> - serverB conn
Hi Crystal,
Yes, both server A and C can access serverB, which has a fixed, public IP.
Thanks for the advice. I can make it work for only ssh’ing into either machine,
but not for using all internet via serverC’s connection, from serverA.
I believe the wireguard configuration will use allowedIPs
On Sat, Aug 10, 2024 at 09:18:48AM +0100, 04-psyche.tot...@icloud.com wrote:
> Hi all,
>
> I am working on a wireguard network.
>
> I have a setup like this:
>
> serverA (10.0.0.0) => serverB (10.0.0.1) => serverC (10.0.0.2)
>
> - serverA connects to serverB with AllowedIPs = 0.0.0.0/0
> - serv
4 matches
Mail list logo