search

ryanblenis / MeshCentral-RoutePlus

Port routing plugin for the MeshCentral project
Apache License 2.0
30 stars 5 forks source link

Configure individual "My Computer" #11

Open dhunt84971 opened 4 years ago

dhunt84971 commented 4 years ago

This is a feature request. Is it possible to configure more than one "My Computer"?

Specifically, instead of having a single computer as the target for all configured routings, which is currently selected by clicking on , would it be possible to make this target node settable for each individual route?

BTW, I love this plug-in and find it very useful.

ryanblenis commented 4 years ago

Glad you're finding it useful! Also glad the latest MC update has a few fixes for RoutePlus / WorkFromHome extensions keeping remote connections open in the way it does- so stability should be greatly improved in 0.5.52 (I am testing now as well).

As for your request, yes it is possible, the caveat is that the connection is tied to the user who assigns the route (viewed in Events tabs and server console), so even if "admin//Jim" assigns the route but has nothing to do with user "Sally" accessing user "Joe"'s computer, it will appear in the event logs as if Jim was accessing Joe's computer (because the route needs a credential to bind to). I'm not a huge fan of this implementation because Jim is not actually accessing Joe's computer, Sally is.

The current implementation of RoutePlus limits this and keeps the logs clean (as "My Computer" should be Jim's). It can work, it's just not great for logging, and I think I'd need to implement a "service account" or dedicated "RoutePlus routing account" which will take some additional work and foresight for permissions/integration into MeshCentral to be done correctly to both assign permissions and report on.

I do agree that this would indeed be handy, but will take a bit of work given the above scenario, so it will take a bit of time.

dhunt84971 commented 4 years ago

Ah, I didn't realize the "My Computer" was actually intended to be MY COMPUTER. :-)

I've been using that to point to the Mesh Central Server itself, most of the time, since this has a public IP, so I can open ports that are public facing and use it to "tunnel" to computers (or IOT devices) that would otherwise be completely inaccessible to me. By assigning this to the Mesh Central server I make the routed back-end device/service accessible to multiple computers. Anyway, that is my current use case.

If I find some time, I'll dig a little deeper into the logging and Mesh Central permissions for my own education to better understand what is going on under the hood.

Thanks again for such a great plugin!