[WireGuard] Using wireguard link as a proxy?
Bruno Wolff III
bruno at wolff.to
Thu Jul 21 22:57:42 CEST 2016
I am trying to test using a wireguard link as a proxy and I am having trouble.
On the source machine I am trying to route packets through wg0 using a
routing entry that has the remote end point tunnel address on a via command.
The idea is to have the packets sent through the tunnel and then to do
source nat on the remote side of the tunnel. The packets go to the interface,
but do not come out the other end. Ping reports:
>From 192.168.7.2 icmp_seq=69 Destination Host Unreachable
ping: sendmsg: Required key not available
So I think the destination address in the packet is being used to find the
tunnel key to use rather than the immediate next destination for the packet.
Has anyone else played with something like this an gotten it to work?
Some info on what I was trying:
default via 126.96.36.199 dev em1 proto static metric 100
188.8.131.52 via 192.168.7.1 dev wg0
184.108.40.206/27 dev em1 proto kernel scope link src 220.127.116.11 metric 100
192.168.7.1 dev wg0 proto kernel scope link src 192.168.7.2
wg source machine
allowed ips: 192.168.7.1/32
wg proxy machine
allowed ips: 192.168.7.2/32
tcpdump output from wg0
15:54:34.129798 IP 192.168.7.2 > 18.104.22.168: ICMP echo request, id 25371, seq 1, length 64
More information about the WireGuard