From: Roman Mamedov <rm@romanrm.net>
To: Chris <wireguard@spam-free.eu>
Cc: wireguard@lists.zx2c4.com
Subject: Re: [FR] How can I expose the wireguard tunnel as a socks5 proxy on the client?
Date: Fri, 9 Oct 2020 19:32:48 +0500 [thread overview]
Message-ID: <20201009193248.6212a0ee@natsu> (raw)
In-Reply-To: <d888c808-fffb-1d61-cdf4-752e61e33fd1@spam-free.eu>
On Fri, 9 Oct 2020 16:19:22 +0200
Chris <wireguard@spam-free.eu> wrote:
> Maybe I oversimplify your problem, but from what I read, your standard route
> will be using the Iranian net.
> And - I guess - it is only a limited numer of IP addresses, that you would like
> to reach through the tunnel.
>
> I don't know your OS, but simply adding ip routes pointing to the tunnel for the
> desired destinations would do the job.
OK, a desired destination would be *.youtube.com, how would you go about that?
You can't add routes to domain names of websites, not to mention to wildcards
of domain names; and websites can resolve into a lot of IPs, which will change
randomly due to load balancing, or due to sites migrating their hosting over
time. So just resolving them right now and using specific IPs likely wouldn't
work for long.
One solution is the browser extensions that I mentioned coupled with a SOCKS
proxy on remote side. Another is what David suggests with dnsmasq and ipset,
which seems like it'll be more transparent from the usage standpoint, but also
more complex to set up.
--
With respect,
Roman
next prev parent reply other threads:[~2020-10-09 14:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 12:11 Rudi C
2020-10-09 13:22 ` Roman Mamedov
2020-10-09 13:30 ` Rudi C
2020-10-09 13:34 ` Roman Mamedov
2020-10-09 13:46 ` Rudi C
2020-10-09 14:05 ` Roman Mamedov
2020-10-09 14:08 ` David Kerr
2020-10-09 14:19 ` Chris
2020-10-09 14:32 ` Roman Mamedov [this message]
2020-10-09 14:26 ` Max R. P. Grossmann
2020-10-14 11:04 ` Thireus
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=20201009193248.6212a0ee@natsu \
--to=rm@romanrm.net \
--cc=wireguard@lists.zx2c4.com \
--cc=wireguard@spam-free.eu \
/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).