From: Nicholas Joll <najoll@posteo.net>
To: wireguard@lists.zx2c4.com
Subject: Update: exempting two things from WireGuard tunneling
Date: Mon, 5 Mar 2018 18:59:24 +0000 [thread overview]
Message-ID: <9de22427-0180-ac5a-cd7c-b5f9810ecbf9@posteo.net> (raw)
In-Reply-To: <d98b43d3-b847-c1c5-931a-5c3164061058@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 1456 bytes --]
Dear List
I've tried all sorts of things to answer my own question (the
question I asked the list a little while ago; my initial e-mail is
appended below) but to no avail. However, I've found something, on the
Wireguard list itself, which looks as though it may help - but I do not
understand it well enough. Might anyone help? The material I found is
located here: https://marc.info/?l=wireguard&m=148813372820847&w=2
Yours
Nicholas
-------- Forwarded Message --------
Subject: Exempting two things from WireGuard tunneling
Date: Fri, 2 Mar 2018 00:33:25 +0000
From:
To: wireguard@lists.zx2c4.com
Dear List
I'd like to exempt two things from WG: (1) some samba shares, accessed
via autofs, which give me enough trouble without having VPN dropouts
(courtesy of my VPN provider and/or my ISP) as well, (2) Netflix (which
I run via a Chrome app). The samba shares all have fixed IPs and most of
them are on a single Windows machine, on my home network, and another
share is to router-attached USB storage (and only works on Samba
protocol version 1, for some reason; the other shares work on version 3).
I imagine many people will want to do each of these things. There was
something on the list a long time back, I think, about 2, but it was too
technical for me to understand. (My VPN and Wireguard knowledge is
minimal, though I have Bash scripts that put WG up and take it down, and
tell it which servers(s) to use.)
With thanks,
N
[-- Attachment #2: Type: text/html, Size: 2654 bytes --]
next prev parent reply other threads:[~2018-03-05 18:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 0:33 Exempting " Nicholas Joll
2018-03-05 18:59 ` Nicholas Joll [this message]
2018-03-05 19:42 ` Update: exempting " Kalin KOZHUHAROV
2018-03-05 19:43 ` Jason A. Donenfeld
2018-03-06 9:56 ` Saeid Akbari
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=9de22427-0180-ac5a-cd7c-b5f9810ecbf9@posteo.net \
--to=najoll@posteo.net \
--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).