From: Kalin KOZHUHAROV <me.kalin@gmail.com>
To: Nicholas Joll <najoll@posteo.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Update: exempting two things from WireGuard tunneling
Date: Mon, 5 Mar 2018 20:42:25 +0100 [thread overview]
Message-ID: <CAKXLc7dPyiqBYCNedFc6cPyGCh3j4RmO7fKU+BNsH4g8T2dJKw@mail.gmail.com> (raw)
In-Reply-To: <9de22427-0180-ac5a-cd7c-b5f9810ecbf9@posteo.net>
On Mon, Mar 5, 2018 at 7:59 PM, Nicholas Joll <najoll@posteo.net> wrote:
> I've tried all sorts of things to answer my own question (the questio=
n 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 itse=
lf, which looks as though it may help - but I do not understand it well eno=
ugh. Might anyone help? The material I found is located here: https://marc.=
info/?l=3Dwireguard&m=3D148813372820847&w=3D2
>
May be it was too vague of a question/statement...
> I'd like to exempt two things from WG:
>
What does exempt mean?
You can "NOT route" packets via a wg interface (fix your routing,
subnets, etc.), or BLOCK packets with a firewall (e.g. nftables,
iptables). 1st is better if possible (requires redesign), 2nd may be
easier. Combining both is the best.
> (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,
>
"samba shares" is like "red car"...
there are quite a few protocols involved with them, most of them run
atop UDP and TCP or both.
> (2) Netflix (which I run via a Chrome app).
... cannot help you much here, but I guess it is some tcp, udp and rtp
mix to some large cloud of IPs.
> 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).
>
draw a map (on paper) or ascii art or something, put some IP
addresses, fake if you are worried.
> 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.)
>
Those are some (aadvanced) routing rules, you probably can live with
standard, if you can choose the IP addresses/networks you connect to
(home).
Really, try to draw a diagram. If you cannot - then it is probably too
complex and wireguard is not gonna help you.
Cheers,
Kalin.
next prev parent reply other threads:[~2018-03-05 19:33 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 ` Update: exempting " Nicholas Joll
2018-03-05 19:42 ` Kalin KOZHUHAROV [this message]
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=CAKXLc7dPyiqBYCNedFc6cPyGCh3j4RmO7fKU+BNsH4g8T2dJKw@mail.gmail.com \
--to=me.kalin@gmail.com \
--cc=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).