From: ae <aeforeve@mail.ru>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "WireGuard mailing list" <wireguard@lists.zx2c4.com>,
"Roelf Wichertjes" <roelf@roelf.org>
Subject: Re[2]: problem wireguard + ospf + unconnected tunnels
Date: Mon, 10 Jul 2017 20:06:03 +0300 [thread overview]
Message-ID: <1499706363.749987194@f388.i.mail.ru> (raw)
In-Reply-To: <CAHmME9qUHN_G2vf7A_haTpk+yMK6rVe42B56N9LFLP7tBh-VkQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
>Hey ae,
>
>Thanks for your detailed reports, especially the nice Python
>reproducer you sent. And sorry for the delay in getting back to you
>and investigating this. I actually don't receive any of your emails. I
>don't know if it's because mail.ru has a bad spam score, or because
>the HTML part of your email contains embedded javascript, but there's
>something sufficiently sketchy that precludes them from being
>delivered to my mailbox. Luckily others on the list brought this
>thread to my attention.
>
>I successfully debugged and fixed the Python reproducer you sent me.
>Could you try the following patch, and see if applying it results in
>ospfd working properly?
>
>https://git.zx2c4.com/WireGuard/patch/?id=177335d5b460cce07631dff8bea478b73e184247
yes - work
+ Pair of missing functionality - which I lacked when replacing with wireguard
1) src addr tunnel
2) work in only preshared crypto
[-- Attachment #2: Type: text/html, Size: 1619 bytes --]
next prev parent reply other threads:[~2017-07-10 16:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 21:09 ae
2017-07-04 15:55 ` Roelf "rewbycraft" Wichertjes
2017-07-04 17:10 ` Re[2]: " ae
2017-07-07 15:08 ` Roelf "rewbycraft" Wichertjes
2017-07-07 15:47 ` Re[2]: " ae
2017-07-10 0:46 ` Jason A. Donenfeld
2017-07-10 17:06 ` ae [this message]
2017-07-10 17:09 ` Re[2]: " Jason A. Donenfeld
2017-07-10 17:26 ` Re[4]: " ae
2017-07-08 14:21 ` Indefinite queuing for unconnected peers (Was: problem wireguard + ospf + unconnected tunnels) Baptiste Jonglez
2017-07-08 18:51 ` Roelf "rewbycraft" Wichertjes
2017-07-10 0:53 ` 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=1499706363.749987194@f388.i.mail.ru \
--to=aeforeve@mail.ru \
--cc=Jason@zx2c4.com \
--cc=roelf@roelf.org \
--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).