first, I understand that the tunnel is intended to link nodes across the internet. I have set that up with several local hams while we get RF links setup.
But I understand that a node CAN tunnel over the mesh to another node in certain situations, which I believe I need to do. Here is my situation:
I have a node on a remote site with an IP camera on it. There is no Internet there.
The camera config software can't detect the camera, I suspect because they're on different subnets (Hikvision camera).
I want to build a (temporary) tunnel from my node (where my PC is LAN) to the remote node. I assume this will allow my PC to be in the same subnet as the camera? If not I'm chasing the wrong solution anyway.
I setup my local node as a client and the remote node as a server. I disabled "aredn.@tunnel[0].wanonly" on the client. In the screenshot you'll see that the client has another tunnel which is disabled. If I enable that it will connect over the mesh. But the new tunnel will NOT connect.
Is this the right way to solve my problem of connecting to the camera? If so why won't it connect? If not, how can I talk to that camera without physical access to the site?
https://photos.app.goo.gl/4p9nrLhUEe39um4W9
You are here
node-node mesh tunnel
Mon, 11/28/2022 - 17:30
#1
node-node mesh tunnel
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
If the camera's node and the workstation with the camera software's node have a path,
why do you need a tunnel?
If the camera software is trying to "discover" the camera, it may not work due to multiple subnets. Look for a way to put in a specific IP for your camera instead (in your camera software)