Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Lord Kitsuna <lordkitsuna112@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Bridge interfaces?
Date: Wed, 27 Sep 2017 22:45:32 -0700	[thread overview]
Message-ID: <CAH8WAOY8qiF8GbdOCNKqO9wbOMztaXwyci71KuvRgH3wFNMmWQ@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pD--t1gNhZ=W=LS1PC0Rz3umEY8pbpsbcmU8MSqp5XCw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 855 bytes --]

Oh hey missed this reply, thanks! That was what i needed working
beautifully.

On Sep 23, 2017 3:44 PM, "Jason A. Donenfeld" <Jason@zx2c4.com> wrote:

> Hi,
>
> Yes indeed this is possible. Enable ip forwarding (sysctl -w
> net.ipv4.ip_forwarding=1), and then make sure you have the correct
> routes set. You may have to add a few entries to your allowed-ips to
> ensure that the network is okay with wireguard, or, perhaps easier,
> would to just enable MASQUERADEing (iptables -t nat -A POSTROUTING -s
> 10.8.8.0/24 -o tinc0 -j MASQUERADE, where 10.8.8.0/24 is the wireguard
> network.)
>
> There are a lot of ways to skin the cat, and I suspect if you write
> back with details of network segments and whatnot, there might be
> others who might have their own useful opinions. Alternatively, you
> can always ask in #wireguard on Freenode.
>
> Jason
>

[-- Attachment #2: Type: text/html, Size: 1315 bytes --]

      reply	other threads:[~2017-09-28  5:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-23 20:42 Lord Kitsuna
2017-09-23 22:44 ` Jason A. Donenfeld
2017-09-28  5:45   ` Lord Kitsuna [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAH8WAOY8qiF8GbdOCNKqO9wbOMztaXwyci71KuvRgH3wFNMmWQ@mail.gmail.com \
    --to=lordkitsuna112@gmail.com \
    --cc=Jason@zx2c4.com \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).