Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Christophe Vanlancker <carroarmato0@inuits.eu>
To: smith151@ngs.ru
Cc: wireguard@lists.zx2c4.com
Subject: Re: Enable default route after establishing connection only
Date: Tue, 11 Feb 2020 14:59:11 +0100 (CET)	[thread overview]
Message-ID: <1037620993.52462.1581429551465.JavaMail.zimbra@inuits.eu> (raw)
In-Reply-To: <web-43707088@mx61.intranet.ru>

I think it's better to solve this at another level.

I use WireGuard on my phone, and I would rather have connections fail and me being aware of that rather than my connections working and falsely believing they are going through the tunnel.

----- Original Message -----
From: smith151@ngs.ru
To: wireguard@lists.zx2c4.com
Sent: Tuesday, 28 January, 2020 09:50:23
Subject: Enable default route after establishing connection only

I am using default route on wireguard. And sometimes 
remote server is not acceptable. The reasons may differ - 
planned maintenance of server, internet troubles, blocked 
IPs of server by country black list an so on.

In case when wireguard server is not reachable wireguard 
client always setting default route via wg0 peer. And all 
internet traffic is not available in this case. How can I 
set up wireguard to enable default route after 
establishing connection only?

I am using wireguard v.20200121 on Debian 10 buster. The 
config file of client is very simple:

```
[Interface]
Address = 1.2.3.2
PrivateKey = ClientPrivateKey=

[Peer]
PublicKey = ServerPublicKey=
Endpoint = 1.2.3.1:51820
PersistentKeepalive = 25
AllowedIPs = 0.0.0.0/0,::/0
```
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      reply	other threads:[~2020-02-11 13:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-28  8:50 smith151
2020-02-11 13:59 ` Christophe Vanlancker [this message]

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=1037620993.52462.1581429551465.JavaMail.zimbra@inuits.eu \
    --to=carroarmato0@inuits.eu \
    --cc=smith151@ngs.ru \
    --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).