From: Luis Ressel <aranea@aixah.de>
To: Saeid Akbari <saeidscorp@yahoo.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Some potential bug in wg-quick re. fwmark and default route
Date: Mon, 26 Mar 2018 22:53:57 +0200 [thread overview]
Message-ID: <20180326225357.4520db1c@vega.skynet.aixah.de> (raw)
In-Reply-To: <4993616.ZASKD2KPVS@scorpbook>
Hello Saeid,
I'm sorry your inquiry has gone unanswered for two weeks; it was simply
drowned by all the user questions. I'm glad I found it now, since you
raise a few interesting points.
As you have discovered, wg-quick is very limited (being the wacky shell
script that it is) and behaves oddly in some corner cases.
I'm drawing a few diagrams right now to see if I can find a way to
improve the add_route/add_default and del_if parts of wg-quick without
increasing the overall complexity too much. Both of your suggestions are
good ideas; if you have further input, that'd be much appreciated!
Cheers,
Luis
next prev parent reply other threads:[~2018-03-26 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 14:17 Saeid Akbari
2018-03-26 20:53 ` Luis Ressel [this message]
2018-04-14 0:41 ` Jason A. Donenfeld
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=20180326225357.4520db1c@vega.skynet.aixah.de \
--to=aranea@aixah.de \
--cc=saeidscorp@yahoo.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).