From: Chris Osicki <wg@osk.ch>
To: Gijs Conijn <egc112@outlook.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WG default routing
Date: Tue, 5 Jan 2021 21:12:12 +0100 [thread overview]
Message-ID: <20210105201212.GA31054@server> (raw)
In-Reply-To: <AM7P191MB088330591C4788BAEA9591888FD20@AM7P191MB0883.EURP191.PROD.OUTLOOK.COM>
On Mon, Jan 04, 2021 at 01:22:31PM +0000, Gijs Conijn wrote:
> That is what I am using the allowed IP's for
> I only want to route via the tunnel to my home LAN so I enter the WG subnet and the home LAN subnet in allowed IP's
> (As I understood Allowed IP's are not only Allowed but also routed via the tunnel)
>
> Regards, Erik
> DDWRT WireGuard user
>
> -----Oorspronkelijk bericht-----
> Van: WireGuard <wireguard-bounces@lists.zx2c4.com> Namens Chris Osicki
> Verzonden: zondag 3 januari 2021 22:55
> Aan: WireGuard mailing list <wireguard@lists.zx2c4.com>
> Onderwerp: WG default routing
>
> Hi
>
> I am quite new to wireguard, moving after years of OpenVPN, and found it simple and _really good_.
> One thing, however, makes me wonder. Why WG tries always to take over all my routing?
> My first try was with wg-quick, and noticed all my traffic went through the WG-VPN connection.
> It escapes me why. What is the idea behind this policy?
>
> On my Linux boxes it's not a problem, I don't have to use wg-quick and with few lines of bash in a script I have what I need. I have root.
> On my Android devices I don't have root, and I cannot change anything in routing etc.
> Why don't you provide an option to specify which net to route which way?
>
> Regards,
> Chris
>
Hi
As far as I can see after few tests, AllowedIPs config file option has nothing to do with routing and I hope
it will stay like this. It is just a filter and the next question arise: why this? Don't we have iptables/nftables?
Or is it for non Unix-like systems?
Regards,
Chris
next prev parent reply other threads:[~2021-01-05 20:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 21:54 Chris Osicki
2021-01-04 13:22 ` Gijs Conijn
2021-01-05 20:12 ` Chris Osicki [this message]
2021-01-05 20:25 ` Roman Mamedov
2021-01-05 21:13 ` Chris Osicki
2021-01-05 23:50 ` Phillip McMahon
2021-01-06 1:03 ` Corey Costello
2021-01-06 1:17 ` Samuel Holland
2021-01-04 13:38 ` Henning Reich
2021-01-05 20:15 ` Chris Osicki
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=20210105201212.GA31054@server \
--to=wg@osk.ch \
--cc=egc112@outlook.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 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).