All,
I recently purchased a Ubiquity M5 (XW). I have successfully installed the AREDN firmware and the node booted up at which point I was able to configure it.
My intent for this node is that it be a way to access my mesh network via an internet connection for demos and such.
At the moment I have not had much luck getting this lashup to work.
Here are the steps I have taken.
1. Configured Ubiquity M5 (XW) as an AREDN node.
2. Installed and configured a Cisco 3750 as dtd device.
3. Connected devices to switch.
4. Installed tunneling software.
5. Configured server
6. configured client.
7. No connection.
8. I then tried to connect to a server that I know works and still no connection.
9. After perusing the forum I found an article that suggested that I do a 15 second reboot, reconfigure the node and reinstall the tunneling software.
10. Still no connection.
11. I then telneted into the server I am trying to connect to <telnet mesh.graysquared.com 5525 and got the following response;
VTUN server ver 3.X 03/22/2019
11. I then established a terminal connection to the node and did the same thing. This is the response I got;
VTUN server ver 3.X 03/22/2019
12. So, I know I can reach the server. I know that it's a connection that is actively being connected to.
13. I looked at the vtun configuration file and it looks fine to me.
I am completely stumped and am not sure how to proceed. Do keep in mind that the node I am using has no RF connection whatsoever.
Chuck
WB6YOK
You are here
VPN Tunnel Troubles
Mon, 03/02/2020 - 22:10
#1
VPN Tunnel Troubles
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
The system log (type "logread" from the command line on the mesh node at both sides of the fence) is full of errors every 5 seconds:
Tue Mar 3 02:53:54 2020 daemon.err vtund[3340]: Can't resolv server address: mesh.greysquared.com
On the vtun client side, change the vtun server name from a hostname to the IP address.
Do you have config settings for 2 servers to connect to? 10.1.10.59 looks like or could be a mesh network address and unexpected for reaching a server over the internet (because a 10.x.x.x address is non-routable over the internet by definition). However, you are reaching 10.1.10.59 address, presumably over the mesh network itself or to a home LAN network, and the vtun server on the other end denied the connection. This is usually due to one of these issues:
1) check very carefully the hostname of the client node must EXACTLY match the name typed into the tunnel configuration on the server.
2) the passwords don't match.
Joe AE6XE