开云体育

I am trying to figure out what type of port forwarding I need to do on the network to make Simpl Debugger work with VC-4.

This is not a question on how to use SIMPL Debugger with VC-4 on a local network.

This is a question on how to use SIMPL Debugger with VC-4?from a remote location via port forwarding.

?

I successfully forwarded the usual ports such as 443 and 41796 (so I can remotely get into the VC-4 web-interface and also use CrestronGo)... all that works fine.

Where I am getting stuck is when I try to remotely connect with Simpl Debugger. I am forwarding port 49300 and I am getting an error that says:

?

"The VC4 server rejected the web connection due to one of the following:

- the address has an invalid room id

- the address has an invalid token

- the room is not running

- the room is not in debugging mode

The SIMPL debugger cannot continue."

?

I know all of the above are good because this works perfectly fine when I am on the local network.
I am getting this error only when I try to remote in via port forwarding.

?

Now, I understand that VC-4 Debugger uses websockets (I have limited knowledge of this underlying technology) but as far as I know, Websockets runs on top of HTTP which in turn runs on top of TCP, no?
So in theory, I should still be able to have remote access by forwarding the appropriate TCP port.

?

I want port forwarding to work mainly for three reasons:

1- Some of my customers cannot give me VPN access but will give me temporary port forwarding. Not ideal, but has worked out fine for me through the years.

2- Sometimes I provide remote support using AnyDesk, which allows me to do TCP tunneling, which in turn allows me to connect to the remote processor straight from my machine. I have been doing this forever with appliance boxes.

3- I like to run VC-4 in a guest virtual machine environment and I need to establish the proper port forwarding between the guest and the host. I was able to make everything else work except Simpl Debugger (which is a big deal).

?

I know this group has some really bright minds. Anybody ran into this before?

?

?

?

?

?

I was erroneously thinking that the port # on the toolbox address entry was the 49300 port... but now I know that it was supposed to be the HTTPS port instead.
The "Port(if not default)" does not give any hint about this.

Anyway, I was able to get this to work.?

?

Now, for the greater good I want to suggest Anydesk for those of you that need a quick way to get direct access to a remote system when all you have is somebody with a laptop on the other side.?

And by that I mean you can directly access the processor or VC4 in your laptop as if you were sitting inside of the far-end network. (Because I hate when you are constrained to using toolbox on a remote machine through Teamviewer, It makes me claustrophobic!)

?

The feature is called TCP Tunneling.

Here are the instructions:
Once you have anydesk connected to the remote laptop, look for Actions -> Setup TCP Tunneling.
Then in there you will punch the usual ports. Note that "remote host" is the IP of the crestron processor (or VC-4) on the other side of the network. The example shown here is what is needed to access an appliance box (non-VC4).?
LocalPort? ? RemoteHost? ?????RemotePort
41794? ? ? ? 192.168.10.55? ? ? 41794

41796? ? ? ??192.168.10.55? ??? 41796??
22? ??? ????? ??192.168.10.55? ??? 22

?

Once you have the TCP Tunneling rules in place, on your toolbox you have to enter the loopback IP in the address field: 127.0.0.1

So when toolbox connects it will go through this path:
Toolbox -> loopsback into... -> Anydesk forwards to... -> the far-end Laptop, which in turn forwards to... -> the far-end crestron processor.

The big advantage of all this is that it allows you direct access to a far-end processor without any need for VPN nor having to ask anybody to open ports on firewall etc.?
All you need is somebody with a laptop running Anydesk on the far end. Thats it.

For VC-4 the steps are the same as above but you also need to add rules for 49300 and also forward the HTTPS port, such as this: