I usually do something like:
wg set wg0 peer ABCD allowed-ips 0.0.0.0/0
ip route add 0/1 dev wg0
ip route add 128/1 dev wg0
./tungate.sh proxyserver.wireguard.io
The tungate.sh script just ensures that proxyserver.wireguard.io is
reachable with the original route, and takes into account ifupdown
On Fri, Jul 22, 2016 at 11:32:11 +0200,
Baptiste Jonglez wrote:
Ok, excellent! Wireguard really doesn't care or even know about the
source NAT you may apply on the server (well, at least when thinking about
it at a high level).
I got this working now. I need to
On Fri, Jul 22, 2016 at 04:09:13AM -0500, Bruno Wolff III wrote:
> On Fri, Jul 22, 2016 at 10:18:21 +0200,
> Baptiste Jonglez wrote:
> >
> >Yes, the notion of "immediate next destinaton" does not make sense for
> >Wireguard. It encapsulates plain IP, not Ethernet.
>