From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Steven Caskey <crazycat362@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard on openwrt
Date: Fri, 1 Jun 2018 23:01:37 +0200 [thread overview]
Message-ID: <CAHmME9phNYTx4AEsk5jzzLFPJJXxudtSB-WbaUnKSCWTrb5rEg@mail.gmail.com> (raw)
In-Reply-To: <CAOcTSMvufQ2iGJ7x4-sNaVLDjFC-=eKXPpU=YOV-6r-3SgwcOA@mail.gmail.com>
Hi Steven,
That's not really the kind of open ended problem that's easy to deal
with on a mailing list. If you have particular logs that you think
indicates a bug or interesting behavior, feel free to share. But I
really think that for your case, you'll be better serviced by asking
gently in the IRC channel: #wireguard on Freenode.
Thanks,
Jason
prev parent reply other threads:[~2018-06-01 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 20:54 Steven Caskey
2018-06-01 21:01 ` Jason A. Donenfeld [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=CAHmME9phNYTx4AEsk5jzzLFPJJXxudtSB-WbaUnKSCWTrb5rEg@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=crazycat362@gmail.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).