Agent relay through agent? #5278
norbythegeek
started this conversation in
General
Replies: 1 comment 3 replies
-
how is ur meshcentral hosted? but as a general rule the meshagent will always use the DEFAULT ROUTE (in ur case the testpath) to connect to your meshcentral server, unless it can be access via another way ie: mesh ip 192.168.88.99 -> vm ip 192.168.89.99 but the VM has a route to 192.168.88.99 WITHOUT going to the gateway first using iptables or windows route table |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
First, I just found MeshCentral, and love it. This will enable my small cloud-based company to ditch our MSP that I'm currently only really using for remote access. MeshCentral is much lighter than SolarWinds TakeControl and much less expensive.
I have a unique use case. We run a testing lab for ISP equipment, and have a VM connected to the user-end network equipment. The VM's default route goes through the test path, so we can run throughput tests. The VM also has another "back-door" interface that connects to the local lab LAN for remote access.
Since the VM only has Internet access if the test path is up and running, I currently have an agent loaded on an always-connected machine on the main LAN, and relay RDP through there to the test VMs. Would it be possible to install an agent on the test VMs, but still have their connection route through the relay? This would give me the flexibility of running a full agent on the test VMs, and still have them always-connected to the MeshCentral server.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions