I am troubleshooting a tunnel that worked previously but has stopped after updating nightly build. (I think...)
MikroTik hAP is the tunnel server and the client I am using is a Microuter dongle style router w AREDN firmware- all are latest nightly 1181-xxx.
When I telnet from outside my network in to port 5525 I see:
VTUN server ver 3.X 10/30/2019
Is this correct? I do not see "waiting for connection" for example. Port forwarding seems to be working.
How can I troubleshoot further? I considered uninstalling/reinstalling the VTUN server.
Thanks-
Clifford
You are here
Troubleshooting tunnel that stopped connecting.
Tue, 11/05/2019 - 00:54
#1
kk6qms
Troubleshooting tunnel that stopped connecting.
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
I get the same kind of response here when I telnet over 5525 to a node running the last stable release: "VTUN server ver 3.X 03/22/2019" followed by a NL and what looks like a couple of tabs; I do not get "waiting for connection" or any other prompt/data. I suspect that the date in that response is likely the firmware release date and the "ver 3" is related to the firmware top level version number. My tunnel is running fine (or, at least until I wrote this).
HTH,
- Don - AA7AU
Clifford
Only two other things to check:
the tunnel client's password must match
the tunnel client's node name must match (and not be too long).
What is the node name of the client trying to connect to your server?
73-
Clifford
PS client name is KK6QMS-MICROUTER