[ wireguard-dev ] About configuring allowedip

[Baptiste Jonglez]

On Thu, Feb 23, 2017 at 02:03:37PM +0100, Nicolas Prochazka wrote:
> Hello, i'm trying to do this with wireguard, withtout success :
> 
> peer1 ---> peer2   : config ok , works
> peer3 ---> peer1  : config ok , works
> peer3 --->peer1 ---> peer2  : not ok .
> 
> I suspect allowed-ip configuration, but all my tests does not works.
> perhaps I must create two wireguard interface on peer 1 and do
> forwarding/routing ?
> i'm using ipv6 as internal ip.

It should work with a single interface for both peers, but you need to
activate forwarding in the kernel:

    # sysctl net.ipv6.conf.default.forwarding=1

> so my question is :
> - two interface ?
> - specifiq magic allowedip ?
> ( allowed ip is confusing for, it is using for routing and for evicting
> paquet ? )
> 
> Regards,
> Nicolas

> _______________________________________________
> WireGuard mailing list
> WireGuard at lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.zx2c4.com/pipermail/wireguard/attachments/20170223/eee5e422/attachment-0001.asc>