Long time delayed but at last I've done this afternoon.
As you know I'm mariner and I use to have internet access and sometimes
I want to know what happens in computer at home, the RDC is not an option
because always interfere with the GPU and all GPU work at the moment it's lost.
Well just start with the settings, could be at least three simple options:
(combinations of this could be a lot)
- Yes, or Yes and after Yes, your connection from abroad and of course your IP is unknown, not so
good no possible connection from computers at home because no known IP, domain, www address
to be entered in "remote_host.cfg" - you have a static IP address at home, marvellous that's the best.
- you have a dynamic IP address at home too, where BT has to search??
My option and most of yours is the 1st + the 3rd one.
1. looks like that we've to start from the end: for the 3rd point I've seen some programs
that checkout the public IP and every time it changes sends you an email to a user defined
address (in my case I'm using Direct Update version for x32 & x64, is not free), so from this
point one end is solved or we know the destination IP because is static or because every
times it exchanges we're advised.
2. we have to open an account in something like "DynDNS" or whatever you know that
gives you free account, properly setup and activated, preferably with the controller laptop
with it's own connection, so from the beginning won't be recognised your home network as
the dynamic address, at the end you should have and address like:
mydomain.dyndns-type.com3. now you have to open and forward port in your router, what does means this, well that
the traffic arrived to your router has to be redirected where needed, e.g. every computer
running BOINC.
a. you know your public IP at home (by means of static or the emailed ones when exchanges)
b. when you setup the computers in BT you need an IP address and a port (both external),
now the important is the port, e.g. four computers setup with internal IP as
ABC.DEF.HIJ.002 / 003 / 004 / 005 (better to have static IP in the Home (private) network) and you have public
IP as SDK.FAK.LÑN.VDF what you have to do in the router is define the access for
the incoming connection, so define in this case eight ports, e.g. 31416, ... 31423,
now you have to go to the option in the router to re-route this traffic where you need,
also, keep in mind that BT and TT uses BOINC port +1 one to obtain the TT data,
it makes a little longer but not complicated,
e.g.
i. 31416 --> IP ABC.DEF.HIJ.002 port 31416 (BOINC Port)
i. 31417 --> IP ABC.DEF.HIJ.002 port 31417 (BT & TT Port)
ii. 31418 --> IP ABC.DEF.HIJ.003 port 31416 (BOINC Port)
ii. 31419 --> IP ABC.DEF.HIJ.003 port 31417 (BT & TT Port)
iii. 31420 --> IP ABC.DEF.HIJ.004 port 31416 (BOINC Port)
iii. 31421 --> IP ABC.DEF.HIJ.004 port 31417 (BT & TT Port)
iv. 31422 --> IP ABC.DEF.HIJ.005 port 31416 (BOINC Port)
iv. 31423 --> IP ABC.DEF.HIJ.005 port 31417 (BT & TT Port)
v. and so on with other computers if needed.
c. on this way there is communication for BOINC - BT - TT
d. supposed that these ports have to be opened in the router, and of course before doing so, RTFM (Read The Fuc... Manual)
4. Now in all computer to be controlled you must enter or add the address created in DynDNS e.g. mydomain.dyndns-type.com
in the "remote_host.cfg"
5. Ready for success, now open BT and in every computer assign what you have noted in paper, to assign correctly data.
a. comp01 - Public IP SDK.FAK.LÑN.VDF - Port 31416 - password (the one in "gui_rpc_auth.cfg" of the proper computer comp01)
b. comp02 - Public IP SDK.FAK.LÑN.VDF - Port 31418 - password (the one in "gui_rpc_auth.cfg" of the proper computer comp02)
c. comp03 - Public IP SDK.FAK.LÑN.VDF - Port 31420 - password (the one in "gui_rpc_auth.cfg" of the proper computer comp03)
d. comp04 - Public IP SDK.FAK.LÑN.VDF - Port 31422 - password (the one in "gui_rpc_auth.cfg" of the proper computer comp04)
e. as you're aware if you're running BOINC in the controller laptop, as a normal localhost to be entered.
f. and so on if another computers are needed.
g. as you could note there is a GAP of one port between each computer, that is the communication needed for BT with TT (BOINC port +1).
6. supposed that everything is done and should be working.
I'm not able to view/read the values of TThrottle in the remote computers, because there are not working on the same port than BOINC??- every time you connect with a mobile - mobile modem you must refresh the dynamic address in order it gets the new IP otherwise you won't be able to connect computers (Direct Update has this option of "force update now", in the setup dynamic connection made)
- I don't know why but suspect that in the "remote_host.cfg" of all and every computer controlled must be entered the IP (internal/private) of the router
I've done it without values of TT and was quick enough, but as you could see you're loosing some information.
After setting up properly with TT too:
- disconnected from the WLAN
- connected trough Bluetooth modem connection (because of coverage 1st time as GPRS and 2nd as 3G)
- refreshed www address - IP with DirectUpdate
- starting BT log, how starts to get computer, this step has been slow, and some internal restarts because of time-out, no crash of program.
- after some minutes starting to get data from all computers and connection established.
- could see all data of all set-up computers in BT (included TT data).
- for sure that quicker mobile data connection will improve the starting up of comms in BT.
....
more to come (corrections will be made in this mail)
TThrottle uses the BOINC port + 1.
So if BOINC is using 31416 TThrottle is using 31417.
Both ports should be redirected.
When I had everything written in the initial post there has been a power failure at home >:(, now writing from the laptop, that has battery. ;)
Well now I'm away home, and I could recover my lost laptop, and working perfectly with BT
and controlling computers at home.
the only thing is that when only GPRS coverage that connection is painful slow and some BT
restarted are done while connecting to home computers.
if connection is 3G and over, connection are really smooth and quick enough, from the start-up
of the connection and refresh of dyndns address and full connection of 3 computers at home it
could take 3 minutes, I think is good enough.
;D