Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Koala Aloha <28387a164997@woerm.at>
To: wireguard@lists.zx2c4.com
Subject: Re: LEDE Netflix bypass
Date: Sun, 10 Dec 2017 11:43:13 +0100	[thread overview]
Message-ID: <711f5c99-4e70-82a7-e5e4-bee2a008cb4e@woerm.at> (raw)
In-Reply-To: <CAL++zqyRjyPH0Jm-niSGj2AN3U8y-b5FumR1tVtzzd3UESauAQ@mail.gmail.com>

Hello Daniel (and hi list),

Have you seen the thread 'wireguard bypass question' [0] yet?
I think that might give you some advice on how to proceed with your
configuration.

I guess using a Linux network namespace [1], [2], [3], [4] that never
routes through your VPN, might be a solution for you. This way you won't
have to deal with figuring out which domains/ip netflix might want to
access.

If you don't always want to provide a passphrase or your user shouldn't
have root at all, you can also configure the '/bin/ip netns exec [...]'
command as 'NOPASSWD' your user via. 'visudo' in your 'sudoers.d'.

[0]: https://lists.zx2c4.com/pipermail/wireguard/2017-October/001787.html
[1]:
https://sgros.blogspot.co.nz/2017/04/how-to-run-firefox-in-separate-network.html
[2]:
http://hintcafe.net/post/78293519027/running-a-process-inside-a-network-namespace
[3]: https://blogs.igalia.com/dpino/2016/04/10/network-namespaces/
[4]:
https://github.com/Phaeilo/openvpn-namespace/blob/4bb1935dfc2c3c062b2dd84479f3194d2d8da635/firefox.sh

 - Koala

  reply	other threads:[~2017-12-10 10:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08 18:43 Daniel Barber
2017-12-10 10:43 ` Koala Aloha [this message]
2017-12-11 19:11   ` Koala Aloha

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=711f5c99-4e70-82a7-e5e4-bee2a008cb4e@woerm.at \
    --to=28387a164997@woerm.at \
    --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).