[WireGuard] Using wireguard link as a proxy?
Quan Zhou
quanzhou822 at gmail.com
Fri Jul 22 17:35:02 CEST 2016
I happen to have a similar problem, using `AllowedIPs = 0.0.0.0/0` on both
sides of a wireguard link works, but when I try to add more peers, all but
one gets `(none)`. I know this is by design, but it would be sweet if I can
manually set gateways within a wireguarded network.
On Fri, Jul 22, 2016 at 11:14 PM, Bruno Wolff III <bruno at wolff.to> wrote:
> On Fri, Jul 22, 2016 at 14:42:52 +0200,
> "Jason A. Donenfeld" <Jason at zx2c4.com> wrote:
>
>> 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
>>
>
> The idea I am working on now is to use policy writing and rules, so that
> packets sent to the proxy server are routed using the normal routing table
> which includes the default route supplied by dhcp, but eveything else (well
> not 127/8) uses an alternate routing table that has a default route through
> wg0. This way I can use a fixed set up and not have to parse the routing
> info setup after a wireless connection is made.
>
> I need to do some reading to get the details for creating routing tables
> and rules for picking them, but expect this will work.
>
> _______________________________________________
> WireGuard mailing list
> WireGuard at lists.zx2c4.com
> http://lists.zx2c4.com/mailman/listinfo/wireguard
>
--
Regards,
Quan Zhou
+------------------------+
|pub [expires 2019-05-04]|
|2C0C 4D88 E631 4C73 4C44|
|CDE0 C0E 5470 1D2D 3F3EE|
+------------------------+
|pub [revoked 2016-04-16]|
|44D2 0307 1643 E80F 2E31|
|F081 FAFA 6643 7F9F D46F|
+------------------------+
|quanzhou822 at gmail.com |
|https://keybase.io/qzhou|
+------------------------+
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zx2c4.com/pipermail/wireguard/attachments/20160722/69712b6e/attachment.html>
More information about the WireGuard
mailing list