ABOUT SOCKS
I am posting this as it might aid others in getting the most out of a remote it connection.
I am Sunsen a one man company run by myself who has about 40 years of embedded SW and IT experience. I make special indoor growing and general horticultural sensors. Remote it is now installed on my first test of my a new VPD Sensor which has been installed at the University Of Wageningen here in The Netherlands, for testing.
I had a particular problem which remote it solved relatively easily with SOCKS . My sensor system consists of a sensor that hangs in the canopy and a server with OpenWRT on it and they connect over WIFI. As I login into my dashboard on the server with http it starts an additional websocket connection to the Server for real time update so a single remote it http channel doesn’t work. At this point I could not get a debug message in the console about what the problem was.
So I tried a SOCKS connection which didn’t work either but it did allow better debugging in console mode. This showed the problem was establishing the WS socket. After considering the problem I made a second SOCKS connection predefined to the WS port to which I wanted to connect. Thus I predefined 2 SOCKS channels one to the http port and another to the WS port number. This solved the problem. Amazing. Its an intuitive approach that works well.
I am also able to connect through the local WIFI network to the sensor itself by defining a third SOCKS connection to that specific local IP address.
I remember first reading about SOCKS protocol in about 1995 but had actually never used it before, more than 30 years later it seems to be a very important protocol addition to remote monitoring.
So hats off to the "remote it " crew!