From: Roman Mamedov <rm@romanrm.net>
To: "Patrick O'Sullivan" <irish@insaneirish.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Why does 'allowed-ips' affect route selection behavior?
Date: Sun, 15 Apr 2018 23:58:01 +0500 [thread overview]
Message-ID: <20180415235801.411a50af@natsu> (raw)
In-Reply-To: <CA+bb15uz7jkD2GZhSQANkH9JPi5Sq2g20wrm0avTRFiOMJ55iA@mail.gmail.com>
On Sun, 15 Apr 2018 14:49:23 -0400
"Patrick O'Sullivan" <irish@insaneirish.com> wrote:
> $ sudo ip route get 4.2.2.1
> 4.2.2.1 dev wg0 table 51820 src 10.111.111.100
^^^^^^^^^^^
> cache
> Can someone please explain this behavior?
Probably will be easier to do if you show the output of "ip -4 rule".
--
With respect,
Roman
next prev parent reply other threads:[~2018-04-15 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-15 18:49 Patrick O'Sullivan
2018-04-15 18:58 ` Roman Mamedov [this message]
2018-04-15 22:26 ` Jason A. Donenfeld
2018-04-16 1:06 ` Patrick O'Sullivan
2018-04-16 1:13 ` Jason A. Donenfeld
2018-04-16 12:29 ` Tim Sedlmeyer
2018-04-15 18:58 ` mikma.wg
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=20180415235801.411a50af@natsu \
--to=rm@romanrm.net \
--cc=irish@insaneirish.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).