From: Bzzzz <lazyvirus@gmx.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wg-quick can't down my vpn I/F and DNS problem
Date: Tue, 2 May 2017 18:54:55 +0200 [thread overview]
Message-ID: <20170502185455.4e88561e@msi.defcon1> (raw)
In-Reply-To: <CAHmME9rrgXSW5pbg56JwBXwcfey0MS-fT7zF-+SmiBwCa5a7bg@mail.gmail.com>
On Tue, 2 May 2017 18:31:14 +0200
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
Oops, sorry for the PM, I put my answer back in the loop.
> If your wg-quick config file is in /etc/wireguard and ends in ".conf"
> then you can use `wg-quick down vpnserver`. Otherwise, please specify
> the full path when calling wg-quick down.
Hi Jason, very nice work BTW,
this is _exactly_ what I do, on the server and the client, I've:
/etc/wireguard/vpnserver.conf
/etc/wireguard/vpnclient.conf
I created 4 scripts: SERVER||CLIENT_WG_UP||DOWN.sh that use this syntax,
(it either fails when typing it in command line).
So the command issued are:
wg-quick up vpnserver (works perfectly)
wg-quick down vpnserver (fails)
and d=C2=B0 for the client.
My setup is basic (but may be wrong) on both srv & cli, here's the srv
one:
[Interface]
Address =3D 10.11.12.1/24
ListenPort =3D 1194
PresharedKey =3D =E2=80=A6
PrivateKey =3D =E2=80=A6
[Peer]
PublicKey =3D =E2=80=A6
AllowedIPs =3D 0.0.0.0/0
The VPN is working, I made a try yesterday, passing by my cell phone
to reach my site and was amazed by the speed 'cos I keep my phone in gsm
mode, otherwise it eats my battery alive (so ~20kB max speed on an old
Xperia x10).
This isn't really a problem, as I use 2 lines that do the work
correctly; however, the DNS problem is a real concern.
Jean-Yves
next prev parent reply other threads:[~2017-05-02 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 15:27 wg-quick can't down my vpn I/F and DNS problem Bzzzz
2017-05-02 16:31 ` Jason A. Donenfeld
2017-05-02 16:54 ` Bzzzz [this message]
2017-05-02 17:08 ` Jason A. Donenfeld
2017-05-02 17:17 ` Bzzzz
2017-05-09 22:20 ` Bzzzz
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=20170502185455.4e88561e@msi.defcon1 \
--to=lazyvirus@gmx.com \
--cc=Jason@zx2c4.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.