Routing to a network behind a node
steven at honson.id.au
Sat Sep 8 12:23:50 CEST 2018
Have you added 172.16.0.0/24 to the AllowedIPs entry for the 172.16.215.2 Peer on 172.16.215.1?
Are you able to share your WireGuard configuration?
> On 8 Sep 2018, at 7:06 pm, M. Dietrich <mdt at emdete.de> wrote:
> i have setup a wg vpn with several nodes, lets say in a
> network 172.16.215.0/24. one of the boxes (ip 172.16.215.2) in
> that network has an interface to a different network with
> additional boxes, lets say 172.16.0.0/24. i would like to
> reach the boxes in that network directly so i established a
> route on another node in the wg network (172.16.215.1) like
> ip route add 172.16.0.0/24 via 172.16.215.2
> but once i ping 172.16.0.1 i get the error
> From 172.16.215.1 icmp_seq=1 Destination Host Unreachable
> ping: sendmsg: Required key not available
> it seems the package reaches wireguard but wireguard doesnt
> know the "via" and tells it has no key to route to 172.16.0.1
> which is fine. but why doesn wg honour the via and send it to
> the router 172.16.215.2?
> i think its more or less whats done if you route all your
> traffic through wg so i assume i do a terrible stupid mistake
> (i am no network or kernel routing expert which may be an
> excuse), can someone help?
> best regards,
> M. Dietrich
> WireGuard mailing list
> WireGuard at lists.zx2c4.com
More information about the WireGuard