All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Ng <facboy@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard over VPN broken on windows
Date: Mon, 22 Jun 2020 11:56:22 +0100	[thread overview]
Message-ID: <CAN5wt5q4iW07HcJE2GGWuEAwtiPKOUarNTiDGWyHJ6kOCNWA1g@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pfyKr62RrAmV81NKs938CmQbqRtcab=yJzKw9V8iMc1A@mail.gmail.com>

it worked for me on a local build, it never worked in any released version.

i've been playing around with a local build, if i comment out the
device.BindSocketToInterface calls in defaulltroutemonitor.go,
everything seems to work fine.  in a single config i have one peer on
an OpenVPN interface, and one on the default interface.  both are
connected, i can ping both peers over the wg interface.  why must the
socket be bound to a particular interface?  or perhaps i don't
understand what those calls do.



On Mon, 22 Jun 2020 at 09:23, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> > 59e556f on wireguard-go breaks
>
> 59e556f fixes a regression, which never shipped in any release. There
> is nothing here that "once worked and now doesn't." What you have in
> mind has never worked.
>
> We're currently using IP_UNICAST_IF on the wireguard socket, attaching
> it to the default route. I'd much rather have something like Linux's
> policy routing and suppress_prefixlen, but I don't know how to do that
> (yet?) on Windows. If you have any ideas or want to do some research,
> I'd certainly be very interested.

  reply	other threads:[~2020-06-22 10:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-21 10:17 Wireguard over VPN broken on windows Christopher Ng
2020-06-22  8:23 ` Jason A. Donenfeld
2020-06-22 10:56   ` Christopher Ng [this message]
2020-06-22 13:15     ` Peter Whisker

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=CAN5wt5q4iW07HcJE2GGWuEAwtiPKOUarNTiDGWyHJ6kOCNWA1g@mail.gmail.com \
    --to=facboy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.