wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Kalin KOZHUHAROV <me.kalin@gmail.com>
To: "Mike O'Connor" <mike@oeg.com.au>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Traffic flow stopping
Date: Tue, 8 Jan 2019 09:13:27 +0100	[thread overview]
Message-ID: <CAKXLc7cNKDPQrv0cT1jRYPoSYPq1=kdZVu4F+GpxTdykYEJOjA@mail.gmail.com> (raw)
In-Reply-To: <8ca3e6e3-174b-c19a-f502-76b1550c5a9d@oeg.com.au>

Hello Mike,

On Tue, Jan 8, 2019 at 3:20 AM Mike O'Connor <mike@oeg.com.au> wrote:
> So I've been using Wireguard to route part of my class C to my home for
> about 4 months now, but for the last few days the traffic stops for a
> short while every few minutes.
>
Does it start on its own "after few minutes"?

> route part of my class C
>
Your configs show "allowed ips: 0.0.0.0/0, ::/0" that is you are
routing everything at wireguard level.
Or are you filtering/mangling in iptables ("fwmark: 0xca6c") only?

> I can not think of anything which has changed, turning OpenVPN back on
> fixes everything. I've tried reducing the keepalive thinking the NAT
> route could have been the issue but that has not help.
>
"turning OpenVPN back on" ?? What/where do you do that?

When ping fails, check your next hop:
ip route get 8.8.8.8

It may mess up your default route, examine network config before/after
"turning on OpenVPN"...
bash -c "ip addr; ip route; wg; cat /etc/resolv.conf; ip route get
8.8.8.8; ping -c3 8.8.8.8"

> Any ideas ? Any more tests or debug (if you tell me how) I could provide ?
>
Anything changing periodically like services that die and are
restarted, cronjobs?

Cheers,
Kalin.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      reply	other threads:[~2019-01-08  8:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18 10:36 Traffic flow stopping Mike O'Connor
2019-01-08  8:13 ` Kalin KOZHUHAROV [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='CAKXLc7cNKDPQrv0cT1jRYPoSYPq1=kdZVu4F+GpxTdykYEJOjA@mail.gmail.com' \
    --to=me.kalin@gmail.com \
    --cc=mike@oeg.com.au \
    --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).