Hi all. Sorry if I have just missed this but I have done a lot of reading and searching to no avail. I have recently configured a pair nodes and have it up and running connected to wan. What I can not figure out is how I can remotely get to my node and then switch to another node from my home network.
So the goal is to either be on my home 192 network or remote in on my VPN to my home 192 network, then be able to access my home node (KG4RVN-Home-1)(which I can do via its 192 address assigned by the home gateway), and then be able to move to another node (KG4RVN-Home-2).
Thanks all for any help in advance. I'm about to pull my hair out trying to get this to work.
Also if it helps any my home network is running on a Ubiquiti UDM-Pro.
73,
KG4RVN
So the goal is to either be on my home 192 network or remote in on my VPN to my home 192 network, then be able to access my home node (KG4RVN-Home-1)(which I can do via its 192 address assigned by the home gateway), and then be able to move to another node (KG4RVN-Home-2).
Thanks all for any help in advance. I'm about to pull my hair out trying to get this to work.
Also if it helps any my home network is running on a Ubiquiti UDM-Pro.
73,
KG4RVN
If I understand you correctly, you just need a router setup as an access point connected to your node. Make sure you set the SSID name and password and you can connect wirelessly in your home.
That won't accomplish what I'm trying to do.
I do 90% of my computer work remotely. So I use a VPN-->home network(192.x.x.x)--->mesh node via 192.168.x.x:8080.
From there I can access my home network but not a remote(neighbor) node. I can use the local IP to access the node wired to my gateway via 192.168.x.x:8080, but when I go to "mesh status"-->"Current Neighbors" and click on any neighbor that resolves as "http://xxxxxx.local.mesh:8080/" or even "10.x.x.x" I can not access it.
to freely access other nodes on the network, you need to be on the LAN side, not the WAN (gateway) side of the system. That means having a 10.x.x.x IP compatible with the mesh network. If you only wanted to access one other node on the network (from the WAN port) you could probably do it with various custom firewall rules inside the nodes - but that is above my pay grade.
Remote access via internet connection can also be accomplished by making your node a tunnel server and then using another (perhaps no- RF) node as a tunnel client. You can effectively connect onto the LAN at the tunnel client and move around from there.
BTW, I also have a GL iNet USB-150 that is flashed for AREDN. I have it normally configured to connect as a WiFi client to my phone operating as a hotspot. So I plug it into my laptop and it then connects to my hAP AC lite at home via a tunnel connection. That puts my laptop on the mesh from whereever I am.
keep in mind, by design this is the same as trying to reach your home LAN network from the internet. You could do similar and run a USB150 or other travel ready mesh node and tunnel connect to the mesh (forwarding 5525 through your home router to the mesh gateway node).
Joe AE6XE
I use either Mikrotik hAP or GL-iNet (AR150, AR300M, AR750)
and tunnel home. Everything on the mesh network is accessible
almost as though I was at home on my mesh computer.
I often run my WSJTX station remotely via VNC.
I hope this helps, Chuck