Meshcentral: MacOS Router Not Working?

[kierer]

I've tried using the MacOS router from both Sierra and Mojave with the default meshaction.txt file (except for setting debugLevel to 2) to route a Microsoft Remote Desktop session via localhost:1234. On both systems, it seems the session is established with the MC server when I try to connect to localhost:1234, but I am unable to establish the RDP session- the Microsoft Remote Desktop client (Version 10.3.3 (1667)) never gets past the "Configuring remote PC" dialog and eventually times out with

We couldn't connect to the remote PC because the session couldn't be established in time. If this keeps happening, contact your network administrator for assistance.

Error code: 0x108

However, connecting via RDP locally on the LAN from the same macs to the machine with the mc agent installed works fine. I was also able to get routing of RDP to the same agent working from a Windows VM running under Parallels on one of the macs exhibiting the above issue, so it's not a general routing problem.

I'm running 0.4.6-t, but I saw this with 0.4.4 as well. Here's the output from meshcmd:

Redirecting local port 1234 to :3389.
Press ctrl-c to exit.
Client connected
Websocket connected

Might someone verify whether RDP routing (to a Windows agent, natch) is working for them from meshcmd for MacOS under 0.4.6-t?

Thanks in advance,
K

[Ylianst]

I will need to take a look at this. There are a lot of pending requests to improve the MeshCentral Router/MeshCmd tools for port mappings. I will need to spend some time making a round of improvements on these.

[kierer]

I have a little more information regarding this issue. It's not specific to the MacOS router- it affects, at minimum, the 64-bit ARM Linux router (and I suspect other Linux routers as well).

It seems to be that certain special characters in passwords (not ones that normally require escaping in json) cause auth to fail silently. The router seems to be connecting from the client side insofar as there are no exceptions, but there is also no indication in the meshcentral server logs that the router ever connected/disconnected. To reproduce, try creating a user account with a password that has all of these characters in it: (.+ then paste that into meshaction.txt and try connecting. If I have time a little later this week, I'll try pulling down the source and getting to the root cause, but I wanted to be sure to give you an update in the meantime. Cheers!