Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: joe@solidadmin.com
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Problems with IP
Date: Fri, 20 Apr 2018 15:56:49 +0000	[thread overview]
Message-ID: <CAHmME9pZtn8i5dFC1xPNj-9x3yE+zKy86JWDtVB_mgJxNo=cpw@mail.gmail.com> (raw)
In-Reply-To: <c2634cf8-28bf-816f-fe91-6e988cc6bbdc@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1676 bytes --]

Hey Joe,

Maybe we should patch the rpm for RHEL in some way? I can probably work
around the old iproute2 by doing a different ip-rule(8) trick, if you'd be
up for shipping that.

Jason

--
Sent from my telephone.

On Fri, Apr 20, 2018, 16:48 Aaron Jones <aaronmdjones@gmail.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 20/04/18 14:32, bessonov.victor@e-queo.com wrote:
> > I've tried to run this instruction manually, result is still the
> > same. The system runs CentOS 7 and properly updated.
>
> Updated, yes; but not up to date. The version of iproute2 is too old.
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJa2f2dAAoJEIrwc3SIqzASCVMP/A9tBO8Sbl1z9rGK0q9vjdyK
> kMeFxKGVWqR4Xz8Sy9wfS+iKeXlBQxKukaZCTuSDr9WzsbpzvohYcE0FvGuDPZgf
> G9TgrGK9NAPow6pIdCfgeIIUnBQQ5geLtnxXKdrr7yaXn2rB8KWi1nwM+NbenNnC
> iJcPe7U9I+RzlDwESTHJMJJGR4hI8zbRSU4H3Nb2PEoYpizHUQuG56RGmOSDO08a
> 1+uol4iBsR0EEBqyt3PUDjuSTjXSAm6G328pErC+aU6I9wP+FHsFUvfMnVd7GDG1
> mJfVx2R8mLInlWX0gpL9YgelOC+/jIRDOeNKvdQAoqF3+7Tz+mT7J++/FLdQa3Sq
> mgHaX+Tvjw6Rnl9KEYC9DqclmHuaoeAHtp7FGnxOXrSOE6fwVh/4BsfKKb7ntU0C
> Wn0tRNrd/QagFm9Nyytm1g1IjoD/B+dXo9cT9p+bls/wBis4+jZZqJte40Kg1MaT
> TlUeyLqVqXMWoUyqqn7Rit4E5ejgPbQpPywdKlJKCQrW4OoU+ualW+t+LUrluPAQ
> ANQkenewaPmoEY4wLGJx02LeD8heYRGzVDkBMmohMiaSVgwibOfxcea7WiggcMNy
> HICqRz1rCHIhDa0togIb2YPSiVsz+7rqW6shUgFabpDV3c7edfaZNcu5KwW5laCk
> nY6A1S5hrgEOr3E8iPeK
> =mFFE
> -----END PGP SIGNATURE-----
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>

[-- Attachment #2: Type: text/html, Size: 2543 bytes --]

  reply	other threads:[~2018-04-20 15:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 14:32 bessonov.victor
2018-04-20 14:48 ` Aaron Jones
2018-04-20 15:56   ` Jason A. Donenfeld [this message]
2018-04-20 16:38     ` Tim Sedlmeyer
2018-04-20 18:51       ` 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='CAHmME9pZtn8i5dFC1xPNj-9x3yE+zKy86JWDtVB_mgJxNo=cpw@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=joe@solidadmin.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).