Page 1 of 1

Remote Client - Can Connect but No Communication

Posted: Tue Mar 24, 2020 4:35 pm
by exsuscito
I have two clients running on two separate machines, they're both running version 7.5.1.

I am able to connect to the client running locally using FAHControl, and I am able to connect to the remote client but nothing happens. The remote client's status is constantly "Updating" and every control in the GUI is visible but disabled.

I used Wireshark to examine the traffic between the two endpoints on my network on port 36330 and this is what I found after restarting FAHControl:

Code: Select all

.[H.[2JWelcome to the Folding@home Client command server.
> updates clear
updates add 0 4 $heartbeat
updates add 1 5 $ppd
updates add 2 1 $(options cpu-usage command-allow-no-pass no-assembly core-priority proxy-pass checkpoint cause command-port pause-on-battery passkey proxy-enable command-deny-no-pass user password deny proxy-user cpu-affinity verbosity gpu-usage allow team proxy power *)
updates add 3 4 $queue-info
updates add 4 1 $slot-info
info
log-updates start
configured

ERROR: unknown command or variable 'updates'
> 
ERROR: unknown command or variable 'updates'
> 
ERROR: unknown command or variable 'updates'
> 
ERROR: unknown command or variable 'updates'
> 
ERROR: unknown command or variable 'updates'
> 
ERROR: unknown command or variable 'updates'
> 
ERROR: unknown command or variable 'info'
> 
ERROR: unknown command or variable 'log-updates'
> 
ERROR: unknown command or variable 'configured'
> 
Any clue what's happening here?

Here is my configuration on the remote client:

Code: Select all

<config>
  <!-- Client Control -->
  <fold-anon v='true'/>

  <!-- HTTP Server -->
  <allow v='127.0.0.1 192.168.0.0/22'/>

  <!-- Network -->
  <proxy v=':8080'/>

  <!-- Remote Command Server -->
  <command-allow-no-pass v='127.0.0.1 192.168.1.2'/>
  <password v='redacted'/>

  <!-- Slot Control -->
  <power v='full'/>

  <!-- User Information -->
  <passkey v='redacted'/>
  <user v='exsuscito'/>

  <!-- Folding Slots -->
  <slot id='0' type='CPU'/>
  <slot id='1' type='GPU'/>
</config>

Re: Remote Client - Can Connect but No Communication

Posted: Tue Mar 24, 2020 5:35 pm
by jonault
Did you restart the remote client after changing its configuration file to allow remote access?

Re: Remote Client - Can Connect but No Communication

Posted: Tue Mar 24, 2020 5:39 pm
by exsuscito
I thought I did that but apparently not, it is working now.

I used /etc/init.d/FAHClient restart