From: Ameretat Reith <ameretat.reith@gmail.com>
To: Ryan McGee <rwm.pc.repair@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wireguard bypass question
Date: Sat, 7 Oct 2017 16:54:54 +0330 [thread overview]
Message-ID: <20171007165454.0a7166d5@gmail.com> (raw)
In-Reply-To: <CANcRkim=9nUOQT5abRfTOVfXzVc1wAo+b_hNQjugHsxABhiWVw@mail.gmail.com>
On Thu, 5 Oct 2017 18:00:00 -0700
Ryan McGee <rwm.pc.repair@gmail.com> wrote:
> So I set up the VPN using Mullvad's guad here:
> https://mullvad.net/guides/running-wireguard-router/
>
> I've tried vpnbypass filling out just the domain
> "/netflix.com/vpnbypass" then I also tried adding the port ranges,
> IPs and ports found at:
> https://backlothelp.netflix.com/hc/en-us/articles/115000257627-What-are-Netflix-s-Aspera-IP-Addresses-and-Port-Ranges-
Ryan, Netflix IPs are much much more than this list.
> Nothing seems to work as netflix still sees me going through a VPN.
On which platform you want to watch Netflix? If It's Linux, you may mark
packets of one instance of browser by the power of namespaces and
abusing TOS field of IP packets and then on LEDE you can exclude these
packets from VPN by iptables. If you watch on any browser, dnsmasq and
IPset approach is cleanest approach [1]. If It's mobile, you need to
find Netflix and AWS IPs and route them outside of VPN by iptables. Last
approach works everywhere but It's most dirty method.
If I were you I would just start another access point in router and
exclude incoming traffic to that AP from VPN. Then I'd connect to this
AP just for watching Netflix.
1: In this case our interests are subdomains of `netflix.com` and
`nflxvideo.net`
prev parent reply other threads:[~2017-10-07 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 0:41 wireguard bypass question Ryan McGee
2017-10-06 0:52 ` Jason A. Donenfeld
2017-10-06 1:00 ` Ryan McGee
2017-10-06 1:04 ` Jason A. Donenfeld
2017-10-07 13:24 ` Ameretat Reith [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=20171007165454.0a7166d5@gmail.com \
--to=ameretat.reith@gmail.com \
--cc=rwm.pc.repair@gmail.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.