From: Riobard Zhan <me@riobard.com>
To: wireguard@lists.zx2c4.com
Subject: WireGuard no inbound traffic after PPPoE interface bounce
Date: Wed, 19 Jun 2019 07:26:46 +0800 [thread overview]
Message-ID: <CAJxHB+0SvOBvZBkf6N9eyLXC8Hu1dHKgEawAL3QyCt7YKNi-pA@mail.gmail.com> (raw)
Hi,
My WAN interface (ppp0) is a PPPoE link. When ppp0 bounces (trigged by
sending SIGHUP to pppd so it disconnects and reconnects due to
`persist` option) with the same IP address assigned by my ISP,
WireGuard no longer sees any inbound traffic. However, if a different
IP address is assigned by my ISP when ppp0 bounces, WireGuard will be
working fine. This behavior can be reliably repeated on Debian 9 and
WireGuard 0.0.20190123.
I'm wondering what could be the cause and is there any thing I could
do to mitigate this? Thanks very much!
- Rio
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2019-06-22 7:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAJxHB+0SvOBvZBkf6N9eyLXC8Hu1dHKgEawAL3QyCt7YKNi-pA@mail.gmail.com \
--to=me@riobard.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).