From: Adrian Sevcenco <adrian.sev@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: tunnel no longer established :: how to debug?
Date: Wed, 2 Jun 2021 09:36:14 +0300 [thread overview]
Message-ID: <ef038c91-f2bd-9e05-f49a-c1700a0f25af@gmail.com> (raw)
Hi! After a change of connection point (the same ISP but different location, but with the same wireless, and end-points)
the tunnel no longer is established. Nothing in the wg configuration is changed ...
from the "client" machine to the "server" end-point i can do:
root@hal: ~ # nc -u -vz sev.HHHHHH 43333
Ncat: Version 7.80 ( https://nmap.org/ncat )
Ncat: Connected to HHH.HHH.HHH.HHH:43333.
Ncat: UDP packet sent successfully
Ncat: 1 bytes sent, 0 bytes received in 2.01 seconds.
How can i debug further to see why the connection is not established?
Thanks a lot!
Adrian
next reply other threads:[~2021-06-02 6:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 6:36 Adrian Sevcenco [this message]
2021-06-02 7:23 ` tunnel no longer established :: how to debug? - solved Adrian Sevcenco
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=ef038c91-f2bd-9e05-f49a-c1700a0f25af@gmail.com \
--to=adrian.sev@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).