Folding Forum

Hi, I'm new to the forum as well as a f@h contributer.
I've set up my desktop at work(Windows 10) to run f@h, but I'm working from home using my laptop (Ubuntu 18.04).
Should I use remote access from home to the desktop at work so that I'm able to get all client information?
I'm comfortable with seting up things related to the network, I just asking about what would be better for my use case.
Thanks in advance.

Easiest would be using a remote access to the desktop computer. If using GPU folding on that desktop, be aware that using MS RDP will stop GPU folding while you are connected

FAHControl can be configured for this kind of access, but might need port forwarding from the business router depending on how your LAN is set up. It uses the Telnet protocol over port 36330. It might be possible to set up a SSH tunnel between the systems, but have no idea of the details.

Hi, Joe, thanks for the fast response.

Joe_H wrote:Easiest would be using a remote access to the desktop computer. If using GPU folding on that desktop, be aware that using MS RDP will stop GPU folding while you are connected

I already access the work desktop thru RDP, but I'm trying to avoid this alternative.

Joe_H wrote:FAHControl can be configured for this kind of access, but might need port forwarding from the business router depending on how your LAN is set up. It uses the Telnet protocol over port 36330. It might be possible to set up a SSH tunnel between the systems, but have no idea of the details.

That's the part I still don't get.
When you say FAHControl to be configured to remote access, are you referring to the server running in my work desktop?
And I'd be able to access it by installing a FAH client in my Ubuntu personal laptop?

how much control do you have of your work environment? The easiest option is probably to install Teamviewer on your desktop but it requires your work PC to be accessible from outside your office which isn't usually something that is permitted.

HaloJones wrote:to install Teamviewer on your desktop

Clear, as I said above, I already access the desktop via RDP. See the image below:

https://drive.google.com/file/d/1pn3EVI ... sp=sharing

(This printscreen was taken from home while connecting to my work desktop via RDP)

What I'd like to do is to try an alternative approach, if that's feasible and applies to what I think the app architecture is about: the program running on my desktop acts like a server, and it allows a client to remotely access it.
Is this correct?
If I install a linux client on my home laptop, would it be able to access the f@h at my work?

I believe I saw someone being coached through setting up fan advanced control direct to another installation at a different location ... would depend how much control you have over corporate network access controls ... iirc a search on "dad" and "router" might find you the other thread ... even if it isnt exactly what you want it should get you the username if someone who might be a le to help

Port forwarding usually works on the target end. On your work router you would tell it that an incoming call on the public IP and port 36330 should go to the private IP of your work computer.

So, your work public IP is x.x.x.x and your internal network IP is 192.168.0.2, on your work router you set up port forwarding for x.x.x.x:36330 to go to 192.168.0.2:36330.

On your FAHControl on your Linux laptop, you would add a client using the public IP address of your work and port 36330. If the port forwarding on your work router/firewall is correct, it will pass the incoming connection from your home and get forwarded to the specific work computer that you are trying to monitor. This would allow you to see logs, stop/start/pause/finish the slots and even configure the client at work.

But it relies on some quite complex network configuration.

Neil-B wrote:I believe I saw someone being coached through setting up fan advanced control direct to another installation at a different location ... would depend how much control you have over corporate network access controls ... iirc a search on "dad" and "router" might find you the other thread ... even if it isnt exactly what you want it should get you the username if someone who might be a le to help

That's not an issue because I'm IT admin at work.
I also know how to setup the router, if needed.

HaloJones wrote:On your FAHControl on your Linux laptop, you would add a client using the public IP address of your work and port 36330

So, after installing FAHControl on my linux laptop and setting it up to remote, it won't do anything else but monitor my desktop at work. Am I right?

The point is that I wouldn't like to have the laptop folding, only the work desktop.

Fairly sure it was HaloJones above who was helping in the other thread ... so I'll duck out now and get out of the way

All you need running on the laptop is FAHControl. For Linux the client software is three separate downloads, as far as I know you don't need the others if you are only going to monitor other systems remotely.

The machine that's doing the work needs to be running proprietary drivers for you GPU and the run-time for OpenCL. RDP would disrupt those proprietary drivers. The machine that's doing the monitoring needs to be running FAHControl which will be looking for a routed port connection to FAHClient.

This can all be done with the FAH software as long as it can see a networked IP. From FAHControl, you can add a cleint to be added in the LEFT panel and the FAHClient needs to be configured to accept that connection. (There are passwords to be configured, too.)

That left panel will assume that there is a local connection to another FAHClient, but you don't have to use it .... or you can simply configure a local Client that uses N cpu threads.

If you do set up a FAHClient on the laptop, the GPU is most likely unsupported -- and even if it is, it would overheat the laptop. Installing the FAHClient daemon will try to configure client processing on both a CPU and a GPU but they're entirely independent of each other.

the FAHControl that i have here is monitoring two clients
"local" at 127.0.0.1:36330 and
"client5" at 192.168.1.5:36330

Local has both CPU and GPU slots
Client5 happens to also have CPU and GPU slots.

Obviously client5 is in the next room (by it's IP address) but it would have to be.

Neil-B wrote:Fairly sure it was HaloJones above who was helping in the other thread ... so I'll duck out now and get out of the way

Sorry if I sounded disrespectful, it wasn't my intention.

Thanks for your help

bruce wrote:The machine that's doing the work needs to be running proprietary drivers for you GPU and the run-time for OpenCL. RDP wouold disrupt those proprietary drivers.

Noted, thanks!

@bruce and @Joe_H, thanks, that's what I was looking for.

No disrespect taken .. you gave perfectly salient information that let those on the forums more technically able than I help you .. it was the right time for me to get out of the way ... hope you get things setup the way you want