wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Mike O'Connor <mike@oeg.com.au>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Traffic flow stopping
Date: Tue, 18 Dec 2018 21:06:03 +1030	[thread overview]
Message-ID: <8ca3e6e3-174b-c19a-f502-76b1550c5a9d@oeg.com.au> (raw)

Hi All

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.

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.

A few detail:

Version 0.0.20181119-wg1~trusty 

CLIENT:

root@gw:~# wg
interface: wg-p2p
  public key: 3zLzaSoTwf+h5AYgvGMz0XnGYJGQX4tPbZcMziULk1I=
  private key: (hidden)
  listening port: 51820
  fwmark: 0xca6c

peer: xSccymCZDUxcD7vFrGtwAiyYGclQ1hUQCmy8nLDLLgc=
  endpoint: 202.191.98.193:51820
  allowed ips: 0.0.0.0/0, ::/0
  latest handshake: 21 seconds ago
  transfer: 3.58 GiB received, 12.20 GiB sent
  persistent keepalive: every 10 seconds
root@gw:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.


^C
--- 8.8.8.8 ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 4999ms


SERVER:

interface: wg-p2p
  public key: xS*gc=
  private key: (hidden)
  listening port: 51820

peer: 3z*k1I=
  endpoint: 203.122.224.57:51820
  allowed ips: 0.0.0.0/0
  latest handshake: 21 seconds ago
  transfer: 12.20 GiB received, 3.58 GiB sent
  persistent keepalive: every 10 seconds

Any ideas ? Any more tests or debug (if you tell me how) I could provide ?


Thanks

Mike

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

             reply	other threads:[~2019-01-08  2:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18 10:36 Mike O'Connor [this message]
2019-01-08  8:13 ` Traffic flow stopping Kalin KOZHUHAROV

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=8ca3e6e3-174b-c19a-f502-76b1550c5a9d@oeg.com.au \
    --to=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).